Just saw the announce message for Backdrop project on irc :
Backdrop: The comprehensive CMS for SMB & NP | Weekly meetings Thur 1:00pm PT (4:00PM ET, 22:00 CET) | Github https://github.com/backdrop
I like the idea of announcing a time every week where most people gather and fire the discussions.
It would be an arbitrary time that works well for most of us.
Do you mean internal or general?
Because for general, I think scheduled discussion without agenda are awkward.
I mean general and agree on the need for an agenda.
We could use lab to schedule discussions.
Like creating a new project called "weekly meeting" and assign tasks to this "weekly meeting" project. Then, on every meeting, we take the list of tasks assigned to the meeting project, and once discussed and settled, we remove the project from the task.
Crowd-generated agenda :-)
I consider the lab to have replaced the need for all being at the same place at the same time online?
Can I close this as wontfix?
From a group dynamics point of view I don't think a tracker like phabricator can replace the magic of people being at the same (virtual) place at the same time, two different things, and both have their own purpose and pros/cons. In blender development they host a weekly, open IRC meeting which I experienced to be a really nice pace maker and "big picture" coordination and reporting tool for the decentralized group of core contributors - whether this would also work or make sense for the apertus project I can't say, but I wouldn't reject the idea on grounds of "we have phabricator" in any case.
So from my side +1 to give it a shot, I'd happily assist in making it happen, but of course this mainly depends on core people wanting/being able to invest time to give it a try, so ultimately your call to decide. :)
As an addendum to the previous comment, I'm posting the meeting notes from the latest blender development meeting as a reference to get a feeling how in-depth (or rather: how "big picture"!) these meetings are, and also because I think it's interesting to see how each meeting produces a small management summary of what's currently going on - and this I think is something from which the various apertus projects (especially the Beta of course) could definitely benefit.
Hi,
Here are notes from today's 15 UTC meeting in irc.freenode.net #blendercoders.
- Blender 2.8 project
- Summary of Workflow Workshop highlights has been posted: https://code.blender.org/ Rest of docs are still in progress.
- Bastien Montagne works on UI layout engine, for better handling of columns: https://developer.blender.org/D2395
- Julian Eisel tested layout previews: https://www.youtube.com/watch?v=RHYWtZP7pyA&feature=youtu.be
- OpenGL upgrade is continuing happily, nothing to report.
- Other projects
- Luca Rood accepted a 3 month Blender Development Fund grant to work on cloth. https://wiki.blender.org/index.php/User:Lucarood/Weekly_Reports
- We still really need more bug fixers and triagers!
That's it for this week,
-Ton-
Sebastian and I are on IRC most of the time and we use it a lot in general, so I don't think a weekly IRC meeting would be a problem.
Still leaves the question of agenda and summary and probably finding good dates as well.
Also it will be additional work for somebody to organize and coordinate.
Best,
Herbert
Cool, then if Sebastian agrees as well (don't want to force anything on anyone here :)) I'd propose we do a few meetings in the coming weeks to try this out! I'll take care of coordination and organization and I'll get in touch on IRC so we can figure out the rest easier. \o/
Great! I am all for it.
We werre holding some mini IRC meetings recently for specific topics with specific groups. E.g. on Tuesday we did a website redesign content/structure meeting. If you can get the stone rolling and coordinate larger meetings for the entire team that would be great!
Ok so today we discussed on IRC when/how to approach the first test meetings - see logs here: http://irc.apertus.org/index.php?day=13&month=12&year=2016
Summary:
First meeting will happen either Monday 19th or Tuesday 20th of December at 19:00, I will announce it in the next days.
It will be announced on team@apertus.org and axiom-dev@googlegroups.com for the first meeting.Wider announcements on axiom-community@googlegroups.com and elsewhere will gradually happen with the following meetings, as soon as we gain the confidence and know-how to sensibly moderate it with a larger audience as well.
Just announced the meeting on team@apertus.org and axiom-dev@googlegroups.com:
Hi everyone,
We are trying out an idea originally brought up by Philippe to establish regular general IRC meetings for the team and everyone else to attend. (see https://lab.apertus.org/T260)
We will do the first one on Monday 19th at 19:00 (IRC channel information: https://www.apertus.org/irc-chat) - please be on time to attend!
As this is a first, we will need to figure out how exactly this works for us, but generally the idea is:
- Everyone gives a quick report about what he/she is actively (!) working on: recent progress, blockers, call for help, etc. (so everyone's up to speed with what's going on)
- Possibility to decide questions that can instantly be decided on, but require multiple team members to be present (the more the merrier!)
- Quickly convene follow-up discussions right after the general meeting if necessary, e.g. to discuss something more in detail in a smaller circle of people involved with a specific problem
- Decide on the next meeting date & time (until we have a regular, fixed date & time)
This is of course just a non-conclusive list of things that worked in other open source projects' regular IRC meetings, we will figure out what specifcally works for us, as stated already. For every meeting there will be a moderator (I'll take on this task for the first ones), who will also sum up the discussion and post a summary (probably to the mailing lists and wiki).
That's it, I invite you all to join if you have time, the more people who are actively involved with apertus attending, the more we will all be able to make from these meetings
Best,
Simon
Some improvement tasks to work on regarding this:
Some notes regarding moderation:
- Remove the Elphel support remark on https://www.apertus.org/irc-chat
done!
- Instead add IRC meeting announcement/schedule to https://www.apertus.org/irc-chat
Are we ready for doing fully publically announced meetings yet? or only team meetings for now (internal)?
- Also add IRC meeting announcement/schedule to the #apertus IRC channel topic
- Possibly archive meeting notes (digests) on http://irc.apertus.org/?
irc.apertus.org is a custom programmed IRC log viewer, I would prefer to host meeting summaries in a different place: maybe a wiki page?
Btw you can link to specific IRC chat lines with this syntax: http://irc.apertus.org/index.php?day=19&month=12&year=2016#53
#53 specifies the line ID
Yeah you're right, let's wait with that until we go officially public with this. (also the IRC channel topic)
- Also add IRC meeting announcement/schedule to the #apertus IRC channel topic
- Possibly archive meeting notes (digests) on http://irc.apertus.org/?
irc.apertus.org is a custom programmed IRC log viewer, I would prefer to host meeting summaries in a different place: maybe a wiki page?
Looked that way to me a bit ;) no problem, let's just ditch the archiving part until we deem it necessary for some reason (actually what we decided on in the meeting anyway, my bad to bring it up again) :)
Thanks for the ID specifier syntax, very good to know!
@simonrepp: thank's for summarizing the outcome of the meeting via mail!
i think this structured and announced (at least for people on the mailing list) communication is a good step. in this form i think IRC is a usable tool ;)