[Engine-devel] Engine meeting
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi: I just learned that this team's open project meeting is held as a teleconference. Would you consider switching it to a regular IRC meeting, perhaps with an occasional phone call? IRC meetings have many advantages in an open project: low barrier of access, easier to understand for non-native speakers, meeting log is archivable and searchable, and more inviting for the project. For phone meetings, do you publish the audio recording? That is not optimal, but at least it allows for someone to transcribe the discussion. Cheers - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPcx1j2ZIOBq0ODEERAj1+AKDla8pokm8KifAoFOj/FE4fsXAP3wCeOJRL oQfAO+hE2tXx5fbifJUeasY= =Ftj6 -----END PGP SIGNATURE-----
On 28/03/12 16:17, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi:
I just learned that this team's open project meeting is held as a teleconference.
Would you consider switching it to a regular IRC meeting, perhaps with an occasional phone call?
We actually discussed this option a few months ago and decided to keep it via phone, it seemed right at the time when we mostly discussed features design and tried to get to conclusions for on-going (endless ;)) threads.
IRC meetings have many advantages in an open project: low barrier of access, easier to understand for non-native speakers, meeting log is archivable and searchable, and more inviting for the project.
For phone meetings, do you publish the audio recording? That is not optimal, but at least it allows for someone to transcribe the discussion.
All the results of the calls are documented in the wiki pages of the different features and being reflected in the different mailing threads that we have. Having said that I think it is time to reconsider the decision because we are soon moving to a stabilization cycle before May's release. I suggest we'll have our next meeting on IRC and see how it goes. Thanks, Livnat
Cheers - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFPcx1j2ZIOBq0ODEERAj1+AKDla8pokm8KifAoFOj/FE4fsXAP3wCeOJRL oQfAO+hE2tXx5fbifJUeasY= =Ftj6 -----END PGP SIGNATURE----- _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
+1 on moving status meetings to irc, starting next one. On 28/03/12 16:48, Livnat Peer wrote:
On 28/03/12 16:17, Karsten 'quaid' Wade wrote: Hi:
I just learned that this team's open project meeting is held as a teleconference.
Would you consider switching it to a regular IRC meeting, perhaps with an occasional phone call?
We actually discussed this option a few months ago and decided to keep it via phone, it seemed right at the time when we mostly discussed features design and tried to get to conclusions for on-going (endless ;)) threads.
IRC meetings have many advantages in an open project: low barrier of access, easier to understand for non-native speakers, meeting log is archivable and searchable, and more inviting for the project.
For phone meetings, do you publish the audio recording? That is not optimal, but at least it allows for someone to transcribe the discussion.
All the results of the calls are documented in the wiki pages of the different features and being reflected in the different mailing threads that we have.
Having said that I think it is time to reconsider the decision because we are soon moving to a stabilization cycle before May's release.
I suggest we'll have our next meeting on IRC and see how it goes.
Thanks, Livnat
Cheers - Karsten
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/28/2012 07:48 AM, Livnat Peer wrote:
All the results of the calls are documented in the wiki pages of the different features and being reflected in the different mailing threads that we have.
That's great, and I agree that it is all being done very transparently. One thing that an IRC meeting provides is a record of the process - the discussions that leads to decisions. (That's harder to capture with audio, so we usually stick with documenting decisions and what we remember of why.) Also, the IRC channel has many people on it lurking, who learn from the meeting, and may occasionally have useful input. - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPcyeV2ZIOBq0ODEERAoLGAJ0bXbSJh7e3Cg5G73/Up63H56h7yACg3lx4 zgc6/w/s+wFFY/g/aGTOlwA= =Jp1g -----END PGP SIGNATURE-----
Karsten, I'm guessing we'll need someone to learn how to master the wiki bot, in order to set the agenda, AI's, etc. Can you point /me to a wiki? Can I create a test channel to try it out? On 28/03/12 17:00, Karsten 'quaid' Wade wrote:
On 03/28/2012 07:48 AM, Livnat Peer wrote:
All the results of the calls are documented in the wiki pages of the different features and being reflected in the different mailing threads that we have.
That's great, and I agree that it is all being done very transparently.
One thing that an IRC meeting provides is a record of the process - the discussions that leads to decisions. (That's harder to capture with audio, so we usually stick with documenting decisions and what we remember of why.) Also, the IRC channel has many people on it lurking, who learn from the meeting, and may occasionally have useful input.
- Karsten _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/28/2012 08:27 AM, Doron Fediuck wrote:
Karsten, I'm guessing we'll need someone to learn how to master the wiki bot, in order to set the agenda, AI's, etc. Can you point /me to a wiki?
Doron: These are the basic commands: http://wiki.debian.org/MeetBot
Can I create a test channel to try it out?
We could, but I think #ovirt is quiet enough that folks won't mind if we do a b it of testing there. I can meet with you for testing, and I'll be sure to attend the Engine meeting on IRC and help with the meetbot until you don't need me anymore. :) - - Karsten
On 28/03/12 17:00, Karsten 'quaid' Wade wrote:
On 03/28/2012 07:48 AM, Livnat Peer wrote:
All the results of the calls are documented in the wiki pages of the different features and being reflected in the different mailing threads that we have.
That's great, and I agree that it is all being done very transparently.
One thing that an IRC meeting provides is a record of the process - the discussions that leads to decisions. (That's harder to capture with audio, so we usually stick with documenting decisions and what we remember of why.) Also, the IRC channel has many people on it lurking, who learn from the meeting, and may occasionally have useful input.
- Karsten _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
- -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPcy9/2ZIOBq0ODEERAnRMAKDP56ry2nVsZkaGQ0Qnh+mkMzpINwCfSL2h Nm94nra7PI0byh/yqowELDI= =/BaD -----END PGP SIGNATURE-----
On 28/03/12 17:34, Karsten 'quaid' Wade wrote:
On 03/28/2012 08:27 AM, Doron Fediuck wrote:
Karsten, I'm guessing we'll need someone to learn how to master the wiki bot, in order to set the agenda, AI's, etc. Can you point /me to a wiki?
Doron:
These are the basic commands:
http://wiki.debian.org/MeetBot
Can I create a test channel to try it out?
We could, but I think #ovirt is quiet enough that folks won't mind if we do a b it of testing there. I can meet with you for testing, and I'll be sure to attend the Engine meeting on IRC and help with the meetbot until you don't need me anymore. :)
- Karsten
Excellent! cya in the next engine meeting!
On 28/03/12 17:00, Karsten 'quaid' Wade wrote:
On 03/28/2012 07:48 AM, Livnat Peer wrote:
All the results of the calls are documented in the wiki pages of the different features and being reflected in the different mailing threads that we have.
That's great, and I agree that it is all being done very transparently.
One thing that an IRC meeting provides is a record of the process - the discussions that leads to decisions. (That's harder to capture with audio, so we usually stick with documenting decisions and what we remember of why.) Also, the IRC channel has many people on it lurking, who learn from the meeting, and may occasionally have useful input.
- Karsten _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
participants (3)
-
Doron Fediuck -
Karsten 'quaid' Wade -
Livnat Peer