Open Stack

> On Sep 4, 2015, at 4:05 PM, Sylvain Bauza <sbauza at redhat.com> wrote:
> 
> 
> 
> Le 04/09/2015 19:06, Doug Hellmann a écrit :
>> Hi, Tim,
>> 
>> We have 2 ongoing projects to improve documentation across OpenStack
>> that might qualify as low-hanging fruit. They aren't bugs, so they won't
>> show up in the bug tracker, but they represent a large number of
>> relatively small patches that need to be made across many projects, so
>> folks can pick a project they are interested in to get started.
>> 
>> For the first project, we are automating the documentation of plugins
>> (drivers, extensions, etc.) in projects using the integration of
>> stevedore and sphinx. The work is described in more detail in
>> https://etherpad.openstack.org/p/6A6mb0lafP and there's a list of all of
>> the affected projects there for people to sign up to help out.
>> 
>> For the section, we are automating the documentation of configuration
>> options in projects using the integration of oslo.config and sphinx.
>> That's being tracked in
>> https://etherpad.openstack.org/p/automating-oslo-config-documentation
>> with a similar list of places for folks to sign up to help.
>> 
>> Both projects were mentioned on the openstack-dev list a while back in
>> http://lists.openstack.org/pipermail/openstack-dev/2015-August/073338.html
>> 
>> I can help with reviews, advice, and debugging help before and after
>> the summit, but won't be available for the on-site training.
>> 
>> Do you think this work would be a good candidate for the upstream
>> training?
> 
> I'm not Tim but...
> 
> YEAH ! Really good projects for helping newcomers to understand how to provide some changes upstream. Why ? Because it doesn't need to really know the project you want to work in, but it still needs to understand the libraries and some Python stuff. Sounds a really good opportunity for win-win between the contributors and the project.
> 
> +2 from my opinion, thanks a lot Doug (and I missed your previous August e-mail from the ML, sadly)

There’s another set of relatively easy patches related to cleaning up the default logging setting in our libraries described in https://etherpad.openstack.org/p/library-logging-default-handlers.

I haven’t heard from anyone other than Sylvain about whether these are useful ideas, so let me know if I should script the submission of all of these patches myself.

Doug

> 
> -Sylvain
> 
>> Doug
>> 
>> Excerpts from Tim Freund's message of 2015-08-10 03:24:06 -0400:
>>> Hi Everyone -
>>> 
>>> We'll open registration for the Tokyo Upstream training soon, and we're
>>> doing something a little different this time:  we are pairing students
>>> with mentors right away and allowing them to work through some of the
>>> technical details of OpenStack contribution before class begins.
>>> 
>>> To do that, we need to fill our roster of Upstream mentors!
>>> 
>>> We need people who are willing to mentor students via IRC and email
>>> before and after the class that occurs on October 25th and 26th, and we
>>> also need people who can be with us in Tokyo to help students complete
>>> hands on exercises.
>>> 
>>> Please fill out the following form if you can help in either role:
>>> http://goo.gl/forms/fczq3NZ16g
>>> 
>>> Our students will be looking for bugs tagged as low-hanging-fruit, so
>>> you can also help by tagging such bugs appropriately in Launchpad.
>>> 
>>> If you're unfamiliar with Upstream training, and you'd like to learn
>>> more, we have basic course information and a complete training schedule
>>> on the wiki[1].  You can read about our Vancouver training session in
>>> Superuser[2].
>>> 
>>> [1] https://wiki.openstack.org/wiki/OpenStack_Upstream_Training
>>> [2]
>>> http://superuser.openstack.org/articles/what-building-legos-can-teach-you-about-open-source
>>> 
>>> Please direct additional questions or comments to the
>>> community at lists.openstack.org list with the [upstream] tag.  You can
>>> also reach out to me directly.
>>> 
>>> Thanks for your help!
>>> 
>>> Tim
>>> 
>> _______________________________________________
>> Community mailing list
>> Community at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
>