We have https://fedoraproject.org/wiki/Zodbot, but it doesn't seem very complete around the meetbot plugin., and I can't find the source we're using for that. The docs say "#help" instead of "#halp" (which the bot itself tells you to use), for example. And, I think we changed it to that you need to provide a meeting name -- except we seem to do it as a parameter to #startmeeting, although the FESCo meeting template calls for also setting #meetingname. This is confusing to me — what are people _supposed_ to do?
Oh, and there's #meetingtopic, which seems to be in no one's meeting SOP. Should it be???
I can work on updating this sometime this coming week. I am heading out of town for the remainder of the weekend soon.
We did make the meeting name with #startmeeting a requirement so that people coiuld find their logs, and it is a parameter. I thought I had added that tot he document when I did that, evidently not. #meetingname is not required, but if you want to change the name in the herald of the room you are in during a meeting, #meetingname will do it, it just won't change the name of the logs, which is set with the name you give with #startmeeting.
#meetingtopic will change the topic of the meeting as well, but I believe there are other ways to do that as well these days.
Like I said above, I will plug away at this during the week.
Thanks,
Dave Shier
(odin)
On Mar 12 2016, at 9:48 am, Matthew Miller <mattdm@fedoraproject.org>
wrote:
We have https://fedoraproject.org/wiki/Zodbot, but it doesn't seem very
complete around the meetbot plugin., and I can't find the source we're using for that. The docs say "#help" instead of "#halp" (which the bot itself tells you to use), for example. And, I think we changed it to that you need to provide a meeting name -- except we seem to do it as a parameter to #startmeeting, although the FESCo meeting template calls for also setting #meetingname. This is confusing to me — what are people _supposed_ to do?
Oh, and there's #meetingtopic, which seems to be in no one's meeting
SOP. Should it be???
--
Matthew Miller <mattdm@fedoraproject.org> Fedora Project Leader _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject .org
I think #meetingname may actually be required. In the instances I've noticed, #startmeeting <name> does *not* work. It doesn't seem to do anything.
On Sat, 12 Mar 2016 at 11:08 David Shier davidjshier@gmail.com wrote:
I can work on updating this sometime this coming week. I am heading out of town for the remainder of the weekend soon.
We did make the meeting name with #startmeeting a requirement so that people coiuld find their logs, and it is a parameter. I thought I had added that tot he document when I did that, evidently not. #meetingname is not required, but if you want to change the name in the herald of the room you are in during a meeting, #meetingname will do it, it just won't change the name of the logs, which is set with the name you give with #startmeeting.
#meetingtopic will change the topic of the meeting as well, but I believe there are other ways to do that as well these days.
Like I said above, I will plug away at this during the week.
Thanks,
Dave Shier (odin)
On Mar 12 2016, at 9:48 am, Matthew Miller mattdm@fedoraproject.org
wrote:
We have https://fedoraproject.org/wiki/Zodbot, but it doesn't seem very complete around the meetbot plugin., and I can't find the source we're using for that. The docs say "#help" instead of "#halp" (which the bot itself tells you to use), for example. And, I think we changed it to that you need to provide a meeting name -- except we seem to do it as a parameter to #startmeeting, although the FESCo meeting template calls for also setting #meetingname. This is confusing to me — what are people _supposed_ to do?
Oh, and there's #meetingtopic, which seems to be in no one's meeting SOP. Should it be???
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraprojec...
infrastructure mailing list infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraprojec...
I've seen people in meetings get frustrated because it wouldn't let them start it without it, as it should. Unless the codes been changed again.
Sent using Boxer
On Mar 12, 2016 11:14, Chaoyi Zha cydrobolt@fedoraproject.org wrote:
I think #meetingname may actually be required. In the instances I've noticed, #startmeeting <name> does *not* work. It doesn't seem to do anything.
On Sat, 12 Mar 2016 at 11:08 David Shier davidjshier@gmail.com wrote:
I can work on updating this sometime this coming week. I am heading out of town for the remainder of the weekend soon.
We did make the meeting name with #startmeeting a requirement so that people coiuld find their logs, and it is a parameter. I thought I had added that tot he document when I did that, evidently not. #meetingname is not required, but if you want to change the name in the herald of the room you are in during a meeting, #meetingname will do it, it just won't change the name of the logs, which is set with the name you give with #startmeeting.
#meetingtopic will change the topic of the meeting as well, but I believe there are other ways to do that as well these days.
Like I said above, I will plug away at this during the week.
Thanks,
Dave Shier
(odin)
On Mar 12 2016, at 9:48 am, Matthew Miller mattdm@fedoraproject.org wrote:
We have https://fedoraproject.org/wiki/Zodbot, but it doesn't seem very complete around the meetbot plugin., and I can't find the source we're using for that. The docs say "#help" instead of "#halp" (which the bot itself tells you to use), for example. And, I think we changed it to that you need to provide a meeting name -- except we seem to do it as a parameter to #startmeeting, although the FESCo meeting template calls for also setting #meetingname. This is confusing to me — what are people _supposed_ to do?
Oh, and there's #meetingtopic, which seems to be in no one's meeting SOP. Should it be???
On Sat, Mar 12, 2016 at 08:06:11AM -0800, David Shier wrote:
I can work on updating this sometime this coming week. I am heading out of town for the remainder of the weekend soon.
Thanks -- that'd be awesome.
We did make the meeting name with #startmeeting a requirement so that people coiuld find their logs, and it is a parameter. I thought I had added that tot he document when I did that, evidently not. #meetingname is not required, but if you want to change the name in the herald of the room you are in during a meeting, #meetingname will do it, it just won't change the name of the logs, which is set with the name you give with #startmeeting.
My key concern is making sure all meetings are easily findable and consistent on http://meetbot.fedoraproject.org/.
On Sat, Mar 12, 2016 at 02:04:32PM -0500, Matthew Miller wrote:
We did make the meeting name with #startmeeting a requirement so that people coiuld find their logs, and it is a parameter. I thought I had added that tot he document when I did that, evidently not. #meetingname is not required, but if you want to change the name in the herald of the room you are in during a meeting, #meetingname will do it, it just won't change the name of the logs, which is set with the name you give with #startmeeting.
My key concern is making sure all meetings are easily findable and consistent on http://meetbot.fedoraproject.org/.
I mean, concern with the above. I also would like getting started with Fedora meetings to be less intimidating to people.
The ability to find meetings is why we have the requirement for a meeting on #startmeeting. I tested it an hour ago and it still gives you the error and aborts the meeting routine without it. Like I say, I'll update the doc this week.
Thanks,
Dave Shier
Sent using Boxer
On Mar 12, 2016 2:04 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Sat, Mar 12, 2016 at 08:06:11AM -0800, David Shier wrote:
I can work on updating this sometime this coming week. I am heading out of town for the remainder of the weekend soon.
Thanks -- that'd be awesome.
We did make the meeting name with #startmeeting a requirement so that people coiuld find their logs, and it is a parameter. I thought I had added that tot he document when I did that, evidently not. #meetingname is not required, but if you want to change the name in the herald of the room you are in during a meeting, #meetingname will do it, it just won't change the name of the logs, which is set with the name you give with #startmeeting.
My key concern is making sure all meetings are easily findable and consistent on http://meetbot.fedoraproject.org/.
On Sat, 12 Mar 2016 09:47:22 -0500 Matthew Miller mattdm@fedoraproject.org wrote:
We have https://fedoraproject.org/wiki/Zodbot, but it doesn't seem very complete around the meetbot plugin., and I can't find the source we're using for that. The docs say "#help" instead of "#halp" (which the bot itself tells you to use), for example. And, I think we changed it to that you need to provide a meeting name -- except we seem to do it as a parameter to #startmeeting, although the FESCo meeting template calls for also setting #meetingname. This is confusing to me — what are people _supposed_ to do?
Oh, and there's #meetingtopic, which seems to be in no one's meeting SOP. Should it be???
So, the upstream for this is a supybot-meetbot plugin. It's pretty dead. There have been several attempts to revive it, but none worked.
I think we are probibly stuck forking it and maintaining it ourselves.
Right now we have a supybot-meetbot package in fedora/epel that we have patches against for some bugfixes, etc. We should possibly just bite the bullet and fork and clean things up some. There's also patches floating around that do voting and tallying, etc.
The reason for the #help vs #halp was that the upstream folks wanted a distinction between asking for help about the meeting commands and asking in a meeting for help on some task or thing.
We made meeting name required in startmeeting because some people were not setting it and we wanted to require it so meetings would be organized better.
#meetingtopic is a higher level topic. All #topics after that would fall under it. So, it's not really needed/user much. An example might be a special meeting on a specific topic might use it and have sub #topics for various parts of the discussion.
kevin
On Mon, Mar 14, 2016 at 09:41:07AM -0600, Kevin Fenzi wrote:
The reason for the #help vs #halp was that the upstream folks wanted a distinction between asking for help about the meeting commands and asking in a meeting for help on some task or thing.
I'm not clear which is which. Maybe change the ask-for-help thing to #helpwanted, and have #help tell you help? I dunno. I don't think either are heavily used. Ralph implemented my idea of collecting #help for feeding into some sort of global list, but I didn't follow through on the "doing something with that" part, and there's a chicken-and-egg problem with people using it.
We made meeting name required in startmeeting because some people were not setting it and we wanted to require it so meetings would be organized better.
Yeah. I'm just not sure if #meetingname is still required or useful, and what happens when for example one does
#startmeeting FESCO (2016-03-18) #meetingname fesco
#meetingtopic is a higher level topic. All #topics after that would fall under it. So, it's not really needed/user much. An example might be a special meeting on a specific topic might use it and have sub #topics for various parts of the discussion.
Ah that makes sense. I'm gonna start using that for Council meetings, where we rotate between
#meetingtopic Open Floor #meetingtopic Tickets & Ongoing #meetingtopic Subproject Report ($nameofteam)
and
#meetingtopic $somespecialthing
like
#meetingtopic Objective Review
On Mon, 14 Mar 2016 11:52:01 -0400 Matthew Miller mattdm@fedoraproject.org wrote:
On Mon, Mar 14, 2016 at 09:41:07AM -0600, Kevin Fenzi wrote:
The reason for the #help vs #halp was that the upstream folks wanted a distinction between asking for help about the meeting commands and asking in a meeting for help on some task or thing.
I'm not clear which is which. Maybe change the ask-for-help thing to #helpwanted, and have #help tell you help? I dunno. I don't think either are heavily used. Ralph implemented my idea of collecting #help for feeding into some sort of global list, but I didn't follow through on the "doing something with that" part, and there's a chicken-and-egg problem with people using it.
Yeah, #help was supposed to be the plugin help and #halp was supposed to be the "I want to ask for help in the logs" one. But I agree this is confusing and we should probibly just drop it. ;)
We made meeting name required in startmeeting because some people were not setting it and we wanted to require it so meetings would be organized better.
Yeah. I'm just not sure if #meetingname is still required or useful, and what happens when for example one does
#startmeeting FESCO (2016-03-18) #meetingname fesco
It overrides the meetingname passed on the startmeeting call. You can change the name anytime during the meeting with #meetingname.
#meetingtopic is a higher level topic. All #topics after that would fall under it. So, it's not really needed/user much. An example might be a special meeting on a specific topic might use it and have sub #topics for various parts of the discussion.
Ah that makes sense. I'm gonna start using that for Council meetings, where we rotate between
#meetingtopic Open Floor #meetingtopic Tickets & Ongoing #meetingtopic Subproject Report ($nameofteam)
and
#meetingtopic $somespecialthing
like
#meetingtopic Objective Review
Sure, that should be valid I think.
kevin
I've done the following this evening.
Expanded the #startmeeting, #meetingname, #meetingtopic, and #endmeeting calls description.
Dropped the #help reference (it would be seen with #commands now anyway).
Added notation that this, as we use it, is a fedpkg package and that you would need fedpkg to work with the source that we have deployed. Maybe not so required, but if someone that's not worked with our packages before wants to try something it could be helpful.
Added notation that to install the plugin on your own system you would need to run 'su -c dnf install supybot-meetbot' or similar, and that this will also install the main supybot code as needed.
Please review when you have time and let me know if I missed something, opened a new can of worms somewhere, or could still go deeper on something still.
On Mon, Mar 14, 2016 at 3:08 PM, Kevin Fenzi kevin@scrye.com wrote:
On Mon, 14 Mar 2016 11:52:01 -0400 Matthew Miller mattdm@fedoraproject.org wrote:
On Mon, Mar 14, 2016 at 09:41:07AM -0600, Kevin Fenzi wrote:
The reason for the #help vs #halp was that the upstream folks wanted a distinction between asking for help about the meeting commands and asking in a meeting for help on some task or thing.
I'm not clear which is which. Maybe change the ask-for-help thing to #helpwanted, and have #help tell you help? I dunno. I don't think either are heavily used. Ralph implemented my idea of collecting #help for feeding into some sort of global list, but I didn't follow through on the "doing something with that" part, and there's a chicken-and-egg problem with people using it.
Yeah, #help was supposed to be the plugin help and #halp was supposed to be the "I want to ask for help in the logs" one. But I agree this is confusing and we should probibly just drop it. ;)
We made meeting name required in startmeeting because some people were not setting it and we wanted to require it so meetings would be organized better.
Yeah. I'm just not sure if #meetingname is still required or useful, and what happens when for example one does
#startmeeting FESCO (2016-03-18) #meetingname fesco
It overrides the meetingname passed on the startmeeting call. You can change the name anytime during the meeting with #meetingname.
#meetingtopic is a higher level topic. All #topics after that would fall under it. So, it's not really needed/user much. An example might be a special meeting on a specific topic might use it and have sub #topics for various parts of the discussion.
Ah that makes sense. I'm gonna start using that for Council meetings, where we rotate between
#meetingtopic Open Floor #meetingtopic Tickets & Ongoing #meetingtopic Subproject Report ($nameofteam)
and
#meetingtopic $somespecialthing
like
#meetingtopic Objective Review
Sure, that should be valid I think.
kevin
infrastructure mailing list infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraprojec...
----------- Dave Shier
infrastructure@lists.fedoraproject.org