*** sudhir has joined #openinfralabs | 03:46 | |
*** sudhir has quit IRC | 07:22 | |
*** sudhir has joined #openinfralabs | 07:27 | |
*** bburns has quit IRC | 14:03 | |
*** tzumainn has joined #openinfralabs | 14:41 | |
*** sudhir has quit IRC | 15:48 | |
*** ganeshrn has joined #openinfralabs | 17:07 | |
msdisme | fungi: did the change you made mean we have the meeting manager live for openinfralabs - does that mean a bouncer is set up also? | 17:23 |
---|---|---|
*** bburns has joined #openinfralabs | 17:24 | |
fungi | msdisme: it's not really a "bouncer" | 17:24 |
fungi | we publish logs of the channel | 17:25 |
msdisme | cool | 17:25 |
fungi | linked in the /topic for convenience | 17:25 |
fungi | http://eavesdrop.openstack.org/irclogs/%23openinfralabs/ | 17:25 |
msdisme | sweet | 17:25 |
fungi | (that's getting renamed to eavesdrop.opendev.org at some point in the near future) | 17:25 |
fungi | that's been in place since 2020-03-27 as you can see from the log history | 17:26 |
* msdisme so, to add us to that top level page we follow this instruction set: The IRC meetings schedule is driven by the opendev/irc-meetings repository. To propose a change, please submit a change to that repository in Gerrit. | 17:28 | |
msdisme | sorry, did not mean to italicize | 17:28 |
msdisme | is the convetion to hold meetings in openstack-meeting? | 17:28 |
fungi | nah, you can hold meetings in any channel you like | 17:29 |
msdisme | and if we expect to also do video conf's on occassion is there a preferred place to put those videos? | 17:29 |
msdisme | cool | 17:29 |
fungi | i don't know what folks do for hosting recording of video calls | 17:29 |
fungi | (or audio for that matter) | 17:29 |
fungi | i think it varies depending on what platforms they're using | 17:30 |
msdisme | ok - I will see if they can go into gitlab or off openinfra web site | 17:31 |
fungi | i think osf has a youtube channel they post some stuff to, like recordings of conference sessions | 17:32 |
msdisme | maybe even better! | 17:33 |
fungi | but that's not accessible from mainland china, so i think they also stick copies somewhere else | 17:33 |
msdisme | got it | 17:33 |
fungi | there's a proposed spec in opendev for possibly hosting a node in https://en.wikipedia.org/wiki/PeerTube | 17:34 |
fungi | though we haven't seen significant interest in that yet | 17:34 |
fungi | https://review.opendev.org/625450 | 17:35 |
bburns | Hi fungi, Thought I should say hi, I am Bill Burns from Red Hat, working with msdismr on this... | 17:35 |
fungi | howdy bburns! | 17:35 |
fungi | can't remember if we maybe met at ocw, though i'm pretty sure i've conversed with you by e-mail | 17:36 |
msdisme | ok, entering the "even more naive question zone" - meetbot/supybot is installed (at least, I think you did that??) - so if we want to hold the meeting in this channel where do the logs go? same place you identified? | 17:36 |
bburns | Could be...both even...;-) | 17:36 |
hewbrocca | bburns and I are old OpenStack hands fungi | 17:36 |
fungi | ahh, cool. i'm terrible with names ;) | 17:37 |
bburns | Same here...and fungi was not obvious! ;-) | 17:37 |
hewbrocca | I used to run a lot of our OpenStack eng at RH, and bburns led the OPNFV team | 17:37 |
hewbrocca | among many other things | 17:38 |
fungi | msdisme: yeah, meeting logs and minutes are also hosted from the same server, but under a different tree based on the meeting "name" | 17:38 |
fungi | independent of the channel in which they're held | 17:38 |
bburns | Well, not to be confused with Mike Burns, who is Mr release for Openstack.. ;-) | 17:38 |
fungi | msdisme: so for example the opendev sysadmin nee openstack-infra team meeting logs and minutes are at http://eavesdrop.openstack.org/meetings/infra/ | 17:41 |
fungi | the meeting name in that case is "infra" | 17:41 |
fungi | whatever is passed to the #startmeeting command | 17:42 |
fungi | so if you `#startmeeting oilabs` then you'll get meeting logs and minutes appearing under http://eavesdrop.openstack.org/meetings/oilabs/ | 17:42 |
msdisme | (I was hunting up the #startmeeting command with Bill's help before throwing on your mercy :-)) | 17:42 |
msdisme | cool - so we would have one for oilabs perhaps, different one for operatefirst, etc ? and need to be good about keeping the name convention the same. | 17:43 |
fungi | yep, that would work | 17:43 |
fungi | https://docs.opendev.org/opendev/system-config/latest/irc.html#starting-a-meeting | 17:44 |
fungi | that's where we maintain some notes on the meetbot plugin for supybot right now | 17:44 |
msdisme | cool - so, we will figure out a schedule, do the gerrit request, and let the fun begin :-) | 17:44 |
fungi | the irc-meetings schedule entry is optional, by the way. that's just to make it easier for people to find the date and time info, and it also produces calendar files people can import into their personal schedules | 17:45 |
fungi | meetbot doesn't really care if your meeting is on time, or scheduled at all | 17:46 |
msdisme | nice | 17:46 |
fungi | as i mentioned in the tools thread recently, the opendev sysadmins are also using it to record scheduled maintenance activities | 17:48 |
fungi | http://eavesdrop.openstack.org/meetings/opendev_maint/2020/opendev_maint.2020-04-10-17.00.html | 17:50 |
fungi | as an example | 17:50 |
msdisme | so it records logs too:? | 17:50 |
fungi | yep, the full logs link at the top of the minutes page will take you to them | 17:51 |
msdisme | nice | 17:51 |
bburns | +1 | 17:51 |
fungi | and every line has an anchor (the minutes make use of that too, so you can link straight to that point in the conversation) | 17:51 |
fungi | here's a good example of where the openstack nova team makes extensive use of meeting topics: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-30-16.00.html | 17:53 |
msdisme | So, do agendas get posted first, then pasted in after startmeeting? | 17:54 |
fungi | here's an openstack technical committee meeting which made use of action items: http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-03-05-14.00.html | 17:55 |
fungi | usually folks write up agendas somewhere (mailing list, etherpad, wiki article, whatever...) and then link to them at the start of the meeting | 17:56 |
msdisme | got it - is there already an etherpad assocaited with this space? | 17:56 |
fungi | not really, etherpad names are arbitrary so you can pick whatever you like or just take an autogenerated random one | 17:57 |
msdisme | have you seen them work well for fleshing out epics an stories? | 17:58 |
fungi | it really depends. i've seen them excel at collaborative note-taking | 18:01 |
fungi | for collaborative authoring of prose it's also fairly workable | 18:01 |
fungi | if you need something with more permanence or well-defined revision control, that's what git's for | 18:01 |
fungi | etherpads make great scratch space for temporary brainstorming and drafting stuff though | 18:02 |
fungi | also we have a related service: https://ethercalc.openstack.org/ | 18:02 |
fungi | basically the same except for spreadsheets | 18:02 |
*** jamesmcarthur has joined #openinfralabs | 21:30 | |
msdisme | cool - Bill and I were thinking it woud be a good way to start fleshing out an epic - we'll coordinate with you tomorrow, if that is ok, to find a time that you will also be available :-) | 23:48 |
msdisme | larsks: ,knikolla | 23:51 |
msdisme | naved001: thoughts on an epic you'd like to see a focused collaborative meeting on - eg. monitoring | 23:52 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!