I went ahead and requested a list and pointed to this thread. If any one
feels this is not a good idea, please burp now.

Suresh

From:  Saminda Wijeratne <[email protected]>
Reply-To:  Airavata Dev <[email protected]>
Date:  Wednesday, October 30, 2013 at 12:17 AM
To:  Airavata Dev <[email protected]>
Subject:  Re: Architecture Mailing List

> +1 for an architecture list. Just incase Apache doesn't allow it we could try
> tagging the subject of the mail so that we can use filters.
> 
> For commits there's a separate mailing list[1]. But for jenkin builds the
> mails are directed to the dev list.
> 
> 1. http://mail-archives.apache.org/mod_mbox/airavata-commits/
> 
> 
> On Tue, Oct 29, 2013 at 10:57 PM, Danushka Menikkumbura
> <[email protected]> wrote:
>> +1.
>> 
>> Also I would rather that we had another list for build/commit mails (Do we
>> get commit mail at the moment BTW?).
>> 
>> Thanks,
>> Danushka
>> 
>> 
>> On Wed, Oct 30, 2013 at 8:16 AM, Suresh Marru <[email protected]> wrote:
>>> Hi All,
>>> 
>>> We are getting some architecture input randomly but I guess we are loosing
>>> valuable input from some of the PMC and community who do not have enough
>>> time to develop and catch up heavy dev list traffic but still invaluable to
>>> provide architectural feedback.
>>> 
>>> How about we request a new mailing list and use it solely for Architecture
>>> discussions? In the long run, I am not sure if we will be able to use this
>>> list and probably will add up confusion of one more additional list. However
>>> we need to make progress on Airavata 1.0 and random 2.0 discussion which get
>>> buried in current active development traffic.
>>> 
>>> What does ever one think about having such a separate mailing list and
>>> encourage every one from PMC and also from interested users and
>>> representatives from fellow apache projects join the list and contribute? If
>>> it is advisable, we can cc to dev list that way we are not missing any one
>>> at the same time selected members are only getting emails what they would
>>> like.
>>> 
>>> Thoughts?
>>> 
>>> Suresh
>>> 
>> 
> 


Reply via email to