-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/08/15 08:10, Pančur, Matjaž wrote: > Hi all, > > As Lana pointed out in her last What’s Up, Doc? mail, labs are now in a > separate repo and also not under the original scope of the Training guides > any more. So we need to (at least) redefine the project’s scope and I would > also really like to reignite it from it’s (unformal?) freeze. > > Steps that I think we need to do: > - redefine scope (now focused on the Upstream training and Training slides) > - reorganise and expand the team > - prepare Upstream material for the Tokyo summit > - prepare the Upstream material in shorter versions (Sean already has some > material for 2 or 4 hour versions, more suitable for user groups) > - start submitting patches for the Training slides (this appears as the most > difficult part). > - to avoid duplication of the content between longer and shorter versions of > the slides, I propose to build this shorter versions with an automated > process of “cherrypicking” the right slides from the longer version (so we > can just define the which slides from the longer version would appear in 2 > and which in 4 hour versions). This way, it will be easier to maintain. > > As Lana suggested to Sean, some project’s statuary things can be postponed > and resolved at the Tokyo Summit. In the mean time, I already took some steps > I believe are good in any case: > > 1. I cleaned up the project's bug queue (it went from 59 to 6): > - a lot of bugs in our queue that are now obsolete (as they were for > Icehouse version and it is no longer published). > - quite a few bugs were in status Fix committed and as the patch was > already in the master branch, I changed the status to Fix released (so that > they don’t show in the bug queue anymore) > - the queue still contains 4 bugs for the labs. Should I move them to the > OpenStack-manuals?
Great work, thanks! > 2. I already talked with a colleague from my lab to help with the project. If > there are no objections, I can also post this mail to the Docs regular ML to > try to gather more interested candidates? Definitely, please go ahead. > 3. I intend to start submitting patches for the Training slides. I believe > that once the thing starts rolling, more community members will chip in. > Slides will be as “generic” as it is possible (regarding OpenStack Releases). > A lot of (beginner oriented) content is now stable enough to not change much > between versions. I agree. > > We can also discuss all this tomorrow on our regular IRC meeting. I’ll put > this stuff on the agenda. > > Thoughts? Suggestions? Thanks for moving forward on this, Matjaz :) L - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJV24XtAAoJELppzVb4+KUybXcIALgFVh04shkDogc2i4+y456T ZdELUJdF8ECO6w75G8g87EsvADqY12mJlwC2ckcEGAieLGD6AGFYEI3qdU4ZqA0z 5Le6H6xV3gG6OaOiRHspFhiMwCzOt8O1SZh04K32WWCuza/HfH32D5HBWZWpeHJk rbOiCksYOLSjFsIHwbHWPMkNG5Y/do+cjC+hHcvum3rJDs19rokxEH4vt4K4kDBc NuYty8HLLUdNLY7PUcouuwymkz8A2VcizzNNcWBQaGvm8oXPit3VRUTOUDWHHRVn 8kAxJGqSZIUXnG7edzFu4yE/08pYSrLRqYATr0tGpjMlLPMxo/HS/YTC6XojbxU= =xlcd -----END PGP SIGNATURE----- -- Mailing list: https://launchpad.net/~openstack-doc-core Post to : openstack-doc-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-doc-core More help : https://help.launchpad.net/ListHelp
