| *** elodilles is now known as elodilles_ooo | 12:33 | |
| fungi | gouthamr: "The next meeting of the OpenStack TC is today, 2025-06-09..." did it move to mondays or is that just for this week? | 13:15 |
|---|---|---|
| gouthamr | Ugh 😑 sorry mistake | 13:51 |
| gouthamr | Ty for noticing and flagging it fungi | 13:54 |
| fungi | no worries, i always have to look at my calendar just to remember what day of the week i'm currently experiencing | 13:56 |
| mnasiadka | And I thought I'm the only one that doesn't know what day it is today... | 16:26 |
| gouthamr | tc-members: does anyone have bandwidth to continue a DCO doc patch on the contributors guide this week? I’m away from my computer and can’t get back to it until the weekend: https://review.opendev.org/c/openstack/contributor-guide/+/950839 | 17:53 |
| gouthamr | was hoping we can land a minimal version and tinker it later if necessary… | 17:54 |
| spotz[m] | gouthamr: I've got 2 things on my todo list but can add that. Looks like it needs some rearranging | 18:15 |
| gouthamr | thank you spotz[m] !! | 19:19 |
| spotz[m] | gmaan: Can you clarify your comment o the DCO doc patch? I think you want more visibility on it but at the same time I think it's in the right place under git in the first file from a flow stand point. There are some grammar fixes and I agree with the comment on the last file. Want to do all the changes in one patch though | 20:45 |
| fungi | an easy way to increase "visibility" is to find a few more logical places to add a note with a link to the main section it's documented in | 20:46 |
| gmaan | spotz[m]: my main concern is that it is not visible form index and nobody will find it unless anyone go to page content of git | 20:46 |
| spotz[m] | gmaan: I wonder if we can link from the index too | 20:48 |
| gmaan | current CLA is under gerrit topic but it is visible from index also https://docs.openstack.org/contributors/code-and-documentation/index.html | 20:48 |
| gmaan | same we can do | 20:48 |
| fungi | pretty sure the main toc lists the second-order headings from each chapter | 20:49 |
| gmaan | I am not sure if that is more closed to git | 20:49 |
| gmaan | or maybe my question can be "what is reason to move CLA from gerrit to git section?" | 20:49 |
| fungi | so as long as you promote that section heading high enough in the hierarchy it should be listed on the main page | 20:49 |
| spotz[m] | CLA would be removed under Gerrit and DCO would be added under Git | 20:50 |
| gmaan | spotz[m]: my suggestion is to have a separate page for it and link it in index as a section parallel to git, gerrit | 20:50 |
| fungi | in theory i agree that the dco material is better associated with git than gerrit (with the cla it was presented to the user in gerrit and they had to agree to it there, with the dco they need to use specific git workflow) | 20:51 |
| spotz[m] | Yeah I don't see it as a standalone topic | 20:52 |
| spotz[m] | AKA there is no DCO without git sign off (unless we solved my corner case for gerrit) | 20:53 |
| gmaan | well, it is when we see it as what CLA is needed for openstack contribution? what command we need to run or so is different thing. | 20:53 |
| gmaan | when any of us or new contributors discuss "OpenStack contribution need DCO to sign" to organization or taking official approval then having it visible at top index page make sense instead of searching it in git detail | 20:55 |
| spotz[m] | Ok thinking | 20:55 |
| gmaan | spotz[m]: I am not thinking about implementation, we can list in git or other places whereever we need implementation but for question about "OpenStack contribution CLA" we should have at top like other LF project has, at least I seen those as a separate/detailed topic | 20:56 |
| spotz[m] | ok so a DCO sign-off after task tracking in the index and before Git? | 20:57 |
| gmaan | ++ | 20:58 |
| gmaan | As we are transition to different CLA, it should be easily/explicitly visible in contributor guide. we can link it in other places also which does not harm | 21:00 |
| spotz[m] | Ok timing wise do we want this ready to just replace in which case not merge right away or do we need it to cover both topics for a short while? | 21:02 |
| gmaan | there is no time deadline for this. what we need for timing was resolution which is merged | 21:18 |
| gmaan | tooling/doc updates can go in parallel | 21:18 |
| spotz[m] | Cross your fingers this goes to the open review:) | 22:34 |
| opendevreview | Amy Marrich proposed openstack/contributor-guide master: DCO doc changes revision https://review.opendev.org/c/openstack/contributor-guide/+/952173 | 22:35 |
| spotz[m] | I think the rebase conflict on the main one is keeping this one from going in:( | 22:38 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!