On Mon, 14 Mar 2016 11:52:01 -0400
Matthew Miller <mattdm(a)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