Tuesday, 2019-04-16

openstackgerritKendall Nelson proposed openstack/contributor-guide master: Added more details IRC in Communication  https://review.openstack.org/65280200:01
openstackgerritKendall Nelson proposed openstack/contributor-guide master: Updates Outdated Event Info  https://review.openstack.org/65214100:33
openstackgerritKendall Nelson proposed openstack/contributor-guide master: Added more details IRC in Communication  https://review.openstack.org/65280200:34
*** rmstar has joined #openstack-upstream-institute01:48
*** rmstar has quit IRC01:51
*** rmstar has joined #openstack-upstream-institute01:52
*** diablo_rojo has quit IRC03:41
*** masayukig has quit IRC06:27
*** masayukig has joined #openstack-upstream-institute06:55
spotzdiablo_rojo_phon: in regards to your question in the ops channel I'd say installation guides are the most commonly accessed at least for new people06:59
*** masayukig has quit IRC08:05
*** masayukig has joined #openstack-upstream-institute08:05
*** gkadam has joined #openstack-upstream-institute08:09
*** gkadam has quit IRC08:10
rmstaris this where a new contributor can get help? :)12:46
ildikovrmstar: it's one of the places :)12:49
ildikovrmstar: what do you need help with?12:49
rmstarildikov: i would like to start off by contributing to documentation.  I started looking into launchpad, but have some questions how things work. Can I sign up for a mentor or something? :)12:53
ildikovrmstar: the people who are most knowledgable about documentation are on the #openstack-doc channel12:56
ildikovrmstar: most of the documentation is handled by the project teams in case you would like to contribute content relevant to any of the OpenStack services12:56
rmstarildikov: I am thinking of working with bugs first.  But do i need to notify anyone before contributing?12:58
spotzrmstar: Not at all12:58
ildikovrmstar: the base tool is Sphinx and you will see a collection of .rst files, this page is one of the examples on restructured text cheat sheet: https://thomas-cokelaer.info/tutorials/sphinx/rest_syntax.html12:59
ildikovrmstar: if you found a bug on Launchpad you would like to look into you need to assign it to yourself and that should be enough notification to people that you are working on it13:00
ildikovrmstar: you can also leave comments on the bug as you progress13:00
rmstarildikov spotz:  thanks :)13:05
rmstarildikov: i guess my confusion is more about launchpad.  ie. which branch is the fix supposed to go?  which repository? etc.13:06
ildikovrmstar: can you link in the bug?13:08
spotz^13:09
rmstarildikov: as an example:  https://bugs.launchpad.net/openstack-manuals/+bug/168069513:11
openstackLaunchpad bug 1680695 in openstack-manuals "Missing HA Guide Content: Testing" [Low,Confirmed]13:11
rmstarwow.  that was unexpected  lol13:12
spotzrmstar: Not to us:)13:12
rmstarspotz: lol.  it's pretty cool. :)13:12
spotzSo that branch is Pike so depending it might be needed in master and then backported or if not needed in newer releases it could just be done as a backport. There's also the question of whether Pike is on extended maintenance or not...13:13
ildikovI can't see the HA guide in the latest set of docs13:15
ildikovnot sure if we're still maintaining it13:15
rmstarildikov: this was what i was trying to find too.13:15
spotzIt may be the doc aspiers is working on:)13:15
rmstarspotz: i am not sure how to checkout Pike.  I did git branch -r but did not see Pike in there.13:15
spotzIn which case its now in the ops docs SIG area13:16
rmstarspotz: ok.  i have to read up about SIG.  Not entirely sure what that is :)13:16
spotzrmstar git checkout -b pike should work but I think that doc might have moved....13:17
ildikovrmstar: I would check with the docs team that what's up with that document13:17
spotzrmstar the channel to ask is openstack-operations13:17
ildikovand what spotz says :)13:18
spotzI just asked, I'm not sure who's awake though cause I'm not used to being on European time:)13:18
ildikovrmstar: is this bug specific to what you're doing and you would benefit from the docs update even if it's covering an older OpenStack release?13:19
rmstarildikov, spotz:  alright.  thanks guys.  I think i just picked a confusing bug to work with.  I will try the same with a different bug and see if i can figure it out. :)13:19
ildikovspotz: I'm in China right now... :)13:19
rmstarildikov: no.  I was just picking a bug at random to try to understand what to do.13:19
ildikovrmstar: in that case if you can double check with people if the bug is still valid and close in case not that's a big help to the community in cleaning up the bug backlog13:20
rmstarit's so cool to work with people around the world. :)13:20
ildikovpeople in the openstack-doc channel might be able to advise on help needed areas13:20
spotz:) Though I'm usually in CST and ildikov is usually in CEST:)13:20
rmstaralright guys.  thank you very much.  i will check with the guys in openstack-doc then. :)13:21
ildikovlol, yes, we are moving around to keep looking like we don't sleep :)13:21
rmstarlol13:22
spotzok smccginnis says that is the one aspiers is working on so it's in a different location or will be once finished:)13:22
ildikovthe bug could still be closed with a note that work is ongoing in aspiers's group13:23
spotztrue that13:23
rmstarildikov: so i can close it?13:23
spotzYeah and say its being worked on by the OPS docs SIG13:25
rmstarspotz: alright.  thanks.  My first bug.  lol13:25
ildikovrmstar: I would ping aspiers in the #openstack-doc channel and sync up with him and then close the bug with a comment on your learnings of what's going on13:25
rmstarildikov: ok.13:25
ildikovhe may also have some bits for you to work on at the end :)13:26
rmstarwhat timezone is he in?13:26
spotzCEST and he's in channel so ping and if he's about he'll answer:)13:26
spotzAtleast usually he is:)13:26
rmstarspotz: cool.  thanks :)13:26
spotzrmstar: No prob:)13:27
spotzI wonder if it's sad we know who's working on things in different projects on sight......13:31
rmstarspotz: actually, it means you are valuable :)13:32
spotzAwww13:32
ildikov:)13:33
rmstarwhen i become more involved, i'd like to know who's working on what too. :)13:34
ildikovit's impossible to follow everything that's going on around here, but it's indeed nice to know a handful of people to reach out to13:40
ianychoirmstar, would you kindly help to document how to contribute documentation?15:54
*** diablo_rojo has joined #openstack-upstream-institute17:21
rmstarianychoi: sure.  let me know what is needed. :)17:48
*** irclogbot_2 has quit IRC18:39
*** irclogbot_3 has joined #openstack-upstream-institute18:41
*** martial has joined #openstack-upstream-institute21:02
openstackgerritJay Bryant proposed openstack/contributor-guide master: Add Extended Maintenance Info  https://review.openstack.org/65316723:20

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!