incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: [ASFCS40] IRC Meeting for Release Tasks?
Date Thu, 16 Aug 2012 18:33:25 GMT
++1. Plus, it should not become the default method for doing development.
If the dev list becomes simply a log of irc discussions, then this
needs to be shut down at once.

On Aug 15, 2012, at 3:04 AM, Mohammad Nour El-Din <nour.mohammad@gmail.com> wrote:

> Hi
> 
> Great idea, just a couple of notes:
> 1- Any discussions made their the conclusions should be shared on the
> mailing lists
> 
> 2- Any decisions that need to be discussed in public and maybe voted for
> also must go on mailing lists
> 
> If it didn't happen on the mailing lists then it didn't happen
> 
> Even if this meeting would only be a status meeting sending the latest
> status to mailing lists would also be important to give others who might
> not be able to attend the meeting or people who might be interested to join
> when they see there are some tasks to do
> 
> I know that u maybe already know this, just sending this as a reminder :)
> 
> Sent from my Samdung Galaxy S3
> Apologies for any typos
> On Aug 15, 2012 6:06 AM, "Alex Huang" <Alex.Huang@citrix.com> wrote:
>> 
>> 
>> 
>>> -----Original Message-----
>>> From: Joe Brockmeier [mailto:jzb@zonker.net]
>>> Sent: Tuesday, August 14, 2012 11:52 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Re: [ASFCS40] IRC Meeting for Release Tasks?
>>> 
>>> On Tue, Aug 14, 2012 at 02:35:51PM -0400, David Nalley wrote:
>>>> I think this is an excellent idea and hope it continues just as a
>>>> weekly meeting for the project just for folks to give status on
>>>> things.
>>>> A couple of comments though:
>>>> 
>>>> * I assume since you are proposing this you are willing to act as
>>>> moderator, and make sure these meetings get announced, logged, and
>>>> summary and minutes get posted here. Perhaps we can even get meetbot
>>>> [1] or some analogue up and running to automate this at some point.
>>> 
>>> Absolutely. And once we get agreement on time, I'll also put together a
>>> tentative agenda (suggestions welcome) as well.
>>> 
>>>> * If a lot of people aren't used to the multi-threaded, async method
>>>> that well attended IRC meetings take perhaps it is a good idea to
>>>> adopt some protocol - IRC meetings can be wonderful if you are used to
>>>> them, and bewildering if you are new to them, esp if there are a lot
>>>> of people present and talking. At the same time, you don't want to
>>>> burden the meeting with too much formality, so perhaps it's a wait and
>>>> implement if there are problems. Off the top of my head this is a
>>>> relatively common one that a number of projects have used [2]
>>> 
>>> For now, I think that a wait-and-see approach is probably best. If we
> find
>>> meetings getting chaotic, then we might want to use the approach from
> the
>>> Fedora wiki. (In my experience, even some of the Fedora meetings don't
>>> follow the formal approach.)
>>> 
>> 
>> Absolutely agree on doing IRC on the release.  Will be a welcomed change
> to mailing lists.
>> 
>> --Alex


Mime
View raw message