[opensuse-project] knowing what we do
Hey all, As the openSUSE team works on our tools like openQA, we would like to keep you up to date on what we do, our progress and perhaps see if some of you who are interested in these tools can help out. But working in the open sounds easier than it is. We organize our work in a public task tracker [1] and our code goes on github [2]. We also blog about it [3] and give talks [4] at oSC. Still, we have tended to communicate too much over our internal IRC channel and mailing list, something we want to change in the future coding sprints. The question I now have for all of you is: WHAT ELSE CAN WE DO? How could we reach you? Engage you? What would make you help out if you can? We really want to have a decent plan AND execution not only in the technical area but also when it comes to working in and around the openSUSE community. Please help us with that! Hugs, Jos [1] see https://progress.opensuse.org/projects/openqa-improvement for openQA [2] see https://github.com/openSUSE-Team/openQA as example for, again, openQA [3] see http://lizards.opensuse.org/2013/06/06/openqa-in-opensuse/ as example [4] see www.youtube.com/watch?v=KjKqN3eIFWQ - openQA
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? thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On Tuesday, January 14, 2014 11:44:53 AM 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?
thanks jdd
+1 And this difficulty to find the awesome new features and the impact on the user experiences makes the announcements occasionally shattered or not so strong enough. A little more clarity on features and changes will make awesome announcements too to reach a wide users target. Regards, Rick Chung | Member openSUSE Projects -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
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
On 01/14/2014 05:00 AM, Jos Poortvliet wrote:
Hey all,
As the openSUSE team works on our tools like openQA, we would like to keep you up to date on what we do, our progress and perhaps see if some of you who are interested in these tools can help out.
But working in the open sounds easier than it is. We organize our work in a public task tracker [1] and our code goes on github [2]. We also blog about it [3] and give talks [4] at oSC.
Still, we have tended to communicate too much over our internal IRC channel and mailing list, something we want to change in the future coding sprints.
The question I now have for all of you is: WHAT ELSE CAN WE DO?
How could we reach you? Engage you? What would make you help out if you can?
I would say it is like everything else, the sooner people can be involved and the smaller the chunks the better the participation will be. When a complete plan is presented and the goals and development plan are already laid out and mostly determined it is very difficult for those that were not part of the conception of the plan to buy in, get involved, and contribute. My $0.02 Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On Tuesday 14 January 2014 09:42:05 Robert Schweikert wrote:
On 01/14/2014 05:00 AM, Jos Poortvliet wrote:
Hey all,
As the openSUSE team works on our tools like openQA, we would like to keep you up to date on what we do, our progress and perhaps see if some of you who are interested in these tools can help out.
But working in the open sounds easier than it is. We organize our work in a public task tracker [1] and our code goes on github [2]. We also blog about it [3] and give talks [4] at oSC.
Still, we have tended to communicate too much over our internal IRC channel and mailing list, something we want to change in the future coding sprints.
The question I now have for all of you is: WHAT ELSE CAN WE DO?
How could we reach you? Engage you? What would make you help out if you can? I would say it is like everything else, the sooner people can be involved and the smaller the chunks the better the participation will be.
When a complete plan is presented and the goals and development plan are already laid out and mostly determined it is very difficult for those that were not part of the conception of the plan to buy in, get involved, and contribute.
My $0.02
Valuable dollars, thanks. /J
Robert
participants (4)
-
jdd -
Jos Poortvliet -
Rick Chung -
Robert Schweikert