On Tuesday 14 January 2014 11:44:53 jdd wrote:
Le 14/01/2014 11:00, Jos Poortvliet a écrit :
The question I now have for all of you is: WHAT ELSE CAN WE DO?
the main problem I encounter working for the marketting team is the release notes writing.
people knowing what is new do not like / have time to write it and marketting team do not know what is new and what is so exciting with the new thing
reading the factory list is the only way I know for now and it's pretty boring for non coder people (let alone understanding what happen)
for exemple I still do not know what oine find so exciting about plymouth... (not to doiscuss this particular point, just an example)
any idea?
Not entirely on-topic, but I think we had a 'solution' for 13.1: rely more on the developers to fill up https://en.opensuse.org/openSUSE:Major_features For 12.3, the marketing team tried to fill in all the gaps. We used a script from Michal that went over all packages and extracted the change log. That is rarely enough so we also looked on the web etc etc to be complete. And then the problem is that, as you point out, we're not programmers/developers/packagers so we don't understand half the stuff we have to summarize. So, that did not work. Now, we just ignore everything that is not put by a developer on the Major_features page (with the exception of a few big things like the kernel, GNOME, KDE...). We could build in something in OBS to let developers add things there for the feature list - perhaps something for the future. Until then, this works... BTW the process is described on https://en.opensuse.org/openSUSE:Product_highlights_writing which I updated recently. Also, see the tasks in progress.opensuse.org: https://progress.opensuse.org/issues/437 it essentially has the above information :D This way, hopefully, we get the developers to point us to the part that we should write about in a way that we can actually do it despite our lack of technical knowledge. Hugs, J
thanks jdd