Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2024-11-29
15:56:25 sean-k-mooney ill be finishing soso but ill try and take a look before i leave for today
15:56:28 ildikov sean-k-mooney: bauzas: I deleted the parts we said are outdated, but I don't know how people are supposed to find the tracking etherpad and interact with it, so I wasn't able to write that part myself
15:56:54 ildikov sean-k-mooney: no rush, thank you for adding it to your todo list
15:57:21 sean-k-mooney ildikov: the delete look correct but ya we shoudl add a short paragah on how to use the etherpad
15:58:18 ildikov sean-k-mooney: great! And yes, I'm hoping to rely on you and bauzas to type up that paragraph.
15:58:25 sean-k-mooney its basiclly add you reivw by addign a new bullet under the correct section with a link to the bug/bluepirnt in lanchpad then under that add either a link to the gerrit topic or each patch
15:59:05 sean-k-mooney you can also addd a short note like needs second +2 or simlar
15:59:54 sean-k-mooney we dont actully have a copypaste template to use but we proably can add one
16:00:56 sean-k-mooney the last thing i woudl suggest peopel do is ping use on irc (via matrix bride if that is easier) to let us know but lests see what bauzas things
16:00:57 ildikov 'copypaste template' to easily add a new entry you mean?
16:00:59 sean-k-mooney *thinks
16:01:09 sean-k-mooney ildikov: yep
16:01:28 ildikov ok, cool
16:01:41 sean-k-mooney you can see that each itme is basiclly just this
16:01:43 sean-k-mooney https://blueprints.launchpad.net/nova/+spec/openapi-2
16:01:45 sean-k-mooney https://review.opendev.org/q/topic:%22openapi%22+project:openstack/nova
16:01:47 sean-k-mooney awaiting reviews
16:02:04 sean-k-mooney i.e. the lauchpad tarcker, followed by a gerrit link and then a note
16:02:12 sean-k-mooney https://etherpad.opendev.org/p/nova-2025.1-status#L33
16:02:23 ildikov oh yeah, that can make sense to template
16:03:22 ildikov how can people find the etherpad?
16:03:27 sean-k-mooney i tend to also add teh title after the bug link in teh case of a bug so you know what it is before you click
16:03:43 ildikov if we add the link to the doc, then it needs to be updated at the beginning of every release cycle
16:03:51 sean-k-mooney ildikov: so we can add a link to the current release
16:03:54 sean-k-mooney ya
16:04:32 sean-k-mooney also i might be going senile in my mid 30s but i tought it used to be in the topic or the irc channel
16:04:48 sean-k-mooney when we used runways it definatlly was
16:05:10 sean-k-mooney but i think when we moved form freenode to oftc we lost the ablity to have per channel topics in the same way
16:05:29 sean-k-mooney so i would like to add it to the channel topic if we can i just dont know where/host to do that
16:06:32 ildikov yeah, that would be great to have it in the IRC channel header as well
16:07:03 sean-k-mooney i dont have op here but maybe we can ask infra about htat
16:07:21 sean-k-mooney basically somethign liek "This channel is for Nova development https://etherpad.opendev.org/p/nova-2025.1-status. For support of Nova deployments, please use #openstack"
16:08:34 sean-k-mooney or "This channel is for Nova development | development-planning: https://etherpad.opendev.org/p/nova-2025.1-status"
16:16:19 ildikov I'll try to figure that out
16:16:43 ildikov apparently you don't need op to make that change, but I wasn't able to
16:17:02 ildikov I think my nick name is not registered anymore, which might be the issue
16:39:47 sean-k-mooney i had the same issue but my nic is defintly registered
16:41:43 sean-k-mooney i get "#openstack-nova: You're not channel operator"
16:41:46 sean-k-mooney when i try
16:45:18 sean-k-mooney bybe we need to message ChanServ to do this instead of using /topic
16:45:28 sean-k-mooney *maybe
16:52:38 ildikov could be
16:52:48 ildikov can check with OpenDev folks next week
16:53:19 sean-k-mooney i tried setting it via chanserve and the TOPIC comamnd is not availbale
16:56:29 ildikov yeah, I got to that point too
16:56:50 sean-k-mooney we do not have autoop enabled iether but most of the infra folks are listed as channle masters so we can always ask them to change it
16:57:06 sean-k-mooney but ya let leave them enjoy there break
16:57:14 ildikov +1 :)
17:00:45 sean-k-mooney #topic "This channel is for Nova development | development-planning: https://etherpad.opendev.org/p/nova-2025.1-status"
17:01:17 ildikov I have an appointment, I'll add the paragraph we talked about to the docs patch afterward
17:01:23 sean-k-mooney :( i was wondering if meetbot was listing outside of meeting but i guess i cant hack the system tyat way
17:01:42 sean-k-mooney ack no rush thanks for doing this o/
17:01:53 ildikov good try though! :)
17:02:02 ildikov sure thing, happy to help!
17:02:20 ildikov if you're not around by the time I'm back, have a nice weekend!
18:10:18 frickler sean-k-mooney: ildikov: ^^ like that?
18:27:18 ildikov frickler: Thank you for the update!
18:28:41 ildikov There was one note about using the #openstack channel, prolly for ops questions. Not sure if the team wants to keep that over logs.
18:29:05 ildikov Other than that the change looks good to me
19:31:48 gmann sean-k-mooney: ildikov I think instead of cycle specific etherpad in topic, we should add this page https://docs.openstack.org/nova/latest/contributor/contributing.html
19:32:43 gmann and etherpad of every cycle can be updated in this page. The main goal of this page is to 'have everything what new contributors need or current status of Nova processs/tasks'
19:41:09 opendevreview Ildiko Vancsa proposed openstack/nova master: Update contributor process documentation https://review.opendev.org/c/openstack/nova/+/936759
19:43:23 opendevreview Artom Lifshitz proposed openstack/nova-specs master: WIP: vTPM live migration https://review.opendev.org/c/openstack/nova-specs/+/936775
19:44:02 opendevreview Artom Lifshitz proposed openstack/nova-specs master: WIP: vTPM live migration https://review.opendev.org/c/openstack/nova-specs/+/936775
19:44:21 opendevreview Artom Lifshitz proposed openstack/nova-specs master: WIP: vTPM live migration https://review.opendev.org/c/openstack/nova-specs/+/936775
19:52:24 opendevreview Ghanshyam proposed openstack/nova master: Add current release task tracking etherpad in contributing.html https://review.opendev.org/c/openstack/nova/+/936776
19:55:13 gmann sean-k-mooney: ildikov ^^ something like this and then add this page in channel Topic as a single place to get all information https://docs.openstack.org/nova/latest/contributor/contributing.html
19:57:29 sean-k-mooney[m] gmann: the spec repo supprts redirect so maybe we could have a short like or something to the current on
19:58:27 gmann sean-k-mooney[m]: did not get. you mean some short url in Topic?
19:59:35 sean-k-mooney[m] in the topic or docs like with the reqirment redirects
19:59:39 ildikov gmann: I'm ok with your link placement, but the process still needs to be outlined
19:59:52 gmann sean-k-mooney[m]: cinder channel use https://tiny.cc/ to short the url but I am not sure if that is good idea and how long tiny.cc can hold/support url
20:00:28 gmann ildikov: we do have that right, I mean all detail doc can be linked from contributing.html
20:00:40 gmann contributing.html is also shown as first page on github repo
20:01:06 ildikov sure, that works
20:01:19 sean-k-mooney[m] im fine with just updating it in the doc each release too
20:01:26 sean-k-mooney[m] so we dont have to make it fancy
20:01:57 gmann yeah and this way it can be referred from non-IRC users also
20:03:22 opendevreview Ildiko Vancsa proposed openstack/nova master: Update contributor process documentation https://review.opendev.org/c/openstack/nova/+/936759
20:03:52 gmann channel topic as "This channel is for Nova development | development process, planning: https://docs.openstack.org/nova/latest/contributor/contributing.html | this channel is logged at https://meetings.opendev.org/irclogs/%23openstack-nova/ "
20:03:58 gmann sean-k-mooney[m]: ildikov ^^ like this?
20:04:48 sean-k-mooney[m] if we are going to update the topic then a direct link is beter
20:05:08 gmann contributing.html is more consistent across all the openstack projects so it will be easy to have i fill/link with all required info
20:05:11 sean-k-mooney[m] i.e. lets not send them to the docs just to send them else where
20:05:35 sean-k-mooney[m] i would personally would be annoyed by that but that just me
20:06:17 gmann sean-k-mooney[m]: but etherpad as direct link is just a one information to them but to know complete process of team/contact detail/how to merge patch etc are in contributing.html
20:06:22 sean-k-mooney[m] we can see what others think next week in the team meeting \
20:06:43 gmann ++
20:06:54 ildikov it depends on whether the assumption is that most people who got to this channel already know some of the basics and would benefit from the direct link to development planning
20:07:21 sean-k-mooney[m] well the ehterpad as i said is not required
20:07:22 ildikov or if we expect more people popping up here still being in need of the top-level doc for how to contribute
20:07:43 sean-k-mooney[m] its just an extra place to help the core reviews to organise some things
20:07:57 sean-k-mooney[m] itis somethign i personally dont partically like
20:08:10 sean-k-mooney[m] but it helps sylvain so we have it
20:08:31 gmann for me, Topic users are more of new people, anyone already know Nova ask core or in meeting
20:09:16 gmann For example, how many of us who are active in IRC/project read the Topic. I have not for many channel I am active in
20:09:45 sean-k-mooney[m] i normally only look at it for the link to the ehterpad
20:09:50 gmann this is more of new people who want to join this channel can know about what this channel is for and how to get involved
20:09:58 gmann ohk
20:10:04 sean-k-mooney[m] i.e. form when it used to have the runway etherpad link

Earlier   Later