Hi Ancor, On Thu, Feb 18, 2016 at 10:13 AM, Ancor Gonzalez Sosa <ancor@suse.de> wrote:
On 02/02/2016 10:31 PM, Simon Lees wrote:
On 02/02/2016 10:01 PM, Ancor Gonzalez Sosa wrote:
I think that should be one of the main goals of the openSUSE Conference. To turn those veteran users into contributors, removing single points of failure in the process.
There are quite some things within the project that would benefit from more hands, and sure there are some hands looking for something to do. We should have a series of talks/workshops/BoFs about that.
In my side, I plan to have session "openSUSE needs you: software.opensuse.org" (tentative title) to fix the issue that the mentioned page highly depends on coolo and myself looking for some spare minutes now and then, with no time to do deep changes/fixes.
What sort of help are you after with software.o.o ?
Sorry for the late reply. I have been busy.
I'm trying to summarize and shape everything into a talk. But, here are some links grouped by topic, in no particular order:
1) Content (wording, info available, organization, etc.)
http://lists.opensuse.org/opensuse-web/2015-11/msg00001.html https://github.com/openSUSE/software-o-o/issues/39 (related to previous) https://progress.opensuse.org/issues/8804 https://bugzilla.suse.com/show_bug.cgi?id=953927 https://bugzilla.suse.com/show_bug.cgi?id=865731 https://github.com/openSUSE/software-o-o/issues/55
2) Searching and communication with OBS (most of them are caused by wrong assumptions from software.o.o on how the distro and/or ports are handled in OBS)
https://bugzilla.suse.com/show_bug.cgi?id=953773 https://progress.opensuse.org/issues/10490 https://bugzilla.suse.com/show_bug.cgi?id=930505 https://bugzilla.opensuse.org/show_bug.cgi?id=948370 https://github.com/openSUSE/software-o-o/issues/57 https://github.com/openSUSE/software-o-o/issues/56
3) Others
https://progress.opensuse.org/issues/10346 https://progress.opensuse.org/issues/7578
As you can see, the whole thing needs some love. Even the automated tests are broken right now.
My challenge is to come up with a understandable full picture and kind of a plan so I can scream for help in more concrete ways (although the call from help in the first link was already focused enough... and didn't resulted in any help).
I very much believe call for help does not help always. But, I have given a thought over it for quite a while now. I do not know if these are the best steps, but this is what I think can be a good start. 1. Really come out of hallway conversations. For example, mentoring 101 was practically, started within a few discussions inside a corner, and was just done. It is great. However, once the development started the discussions (if there were any) should really be done at opensuse-web (all of them). This goes to OSEM, the landing page. There have been discussions in the past about all of the projects, like hey this is how it looks, please give feedback. This can only create more people who want to give feedback, but not contributors in terms of code or anything other than that. So, developers really need to go out, learn to handle a bit of trolling but talk in public. 2. Send commit messages to the relevant mailing list. So if it is opensuse-web related project, then send commit messages. It will make people aware of the development. With so many projects, it is really difficult to find something on github. 3. Send new bugs that are created to the relevant mailing lists. This will people know about the bugs in the systems, and make them aware. I might want to throw in a reminder of open bugs once a month, but I am not sure of the strategy. 4. GSoC, encourage mailing list conversations. This is something I have wished for long, but did not put in any effort to achieve this. All the Google Summer of Code discussions should be done at the relevant mailing lists. Private Mentor-Student topics should be limited to personal conversations. This has in the past helped projects like apache get a better success rate in long term students. I will be interested in knowing the communities opinion.
Cheers
[Rest of the mail stripped]
PS.- cc'ing people who already contacted me off-list asking for details. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
-- Regards Manu Gupta -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org