New project mailing lists

[Khem Raj]

> On Oct 13, 2015, at 10:39 AM, Mark Hatle <mark.hatle at windriver.com> wrote:
> 
> On 10/13/15 12:36 PM, Khem Raj wrote:
>> 
>>> On Oct 13, 2015, at 10:33 AM, Philip Balister <philip at balister.org> wrote:
>>> 
>>> On 10/13/2015 01:28 PM, Paul Eggleton wrote:
>>>> On Tuesday 13 October 2015 13:03:40 Philip Balister wrote:
>>>>> At OEDEM we talked about creating a list:
>>>>> 
>>>>> openemebdded-architecture - Discussions about overall OpenEmbedded
>>>>> Architecture and status
>>>>> 
>>>>> Any objections to the name and description? I'd like to ask Michael to
>>>>> set this up.
>> 
>> what will this achieve that oe-devel can’t do ? people are already subscribed to oe-devel
>> and prefixing with [architecture] prefix might be enough. We already use subject prefix filters on oe-devel
>> messages.
> 
> The discussion was that most of us are filtering out oe-devel to the things we
> care about.. and thus missing architectural discussions..
> 


It seems we want a new list for convenience which could otherwise be another filter on someones list ?
oe-devel is far reaching then this new list would be, Its important to get opinion from developers
and users who are at fringes of project too. If they don’t reciprocate, atleast they have the information
thats being discussed. It will also have good learning for new folks who are looking out to learn about
OE without much effort of advertising the new list.

> Architectural being more then just meta-openembedded, or oe-core... but layer
> index, and other things affecting the overall infrastructure and architecture of
> OpenEmbedded.

yes thats all part of open embedded

> 
> At this point, I think a new list is the best answer..  while I don't really
> want a new list -- the reality is without it a lot of us are going to miss
> relevant discussions.

with a bit of discipline we can have it right. IMO its more important to let community have the convenience
then few who can not set filters.

> 
> --Mark
> 
>> 
>>>> 
>>>> Seems like a bit of a mouthful, and I am a little concerned about yet another
>>>> mailing list diluting the audience, but then the consensus at the meeting did
>>>> seem to be that we need another one. I don't really have a better alternative
>>>> name, FWIW.
>>>> 
>>>> I will say that if we are creating a new mailing list, we need to be *crystal
>>>> clear* about where people should send questions or problems (and patches),
>>>> particularly when they are doing so for the first time - given that this is
>>>> already a problem with the current number of lists.
>>>> 
>>> 
>>> I agree, that is why I wanted to ask the full TSC for thoughts before
>>> talking with Michael about the actual creation. I jsut want to make sure
>>> we do not forget.
>>> 
>>> 
>>>>> Also, in the spring at OEDAM we talked about a security list. I think we
>>>>> should ask that list be created under the yp domain as security will
>>>>> involve developing tools that do not cleanly fall into the build system
>>>>> space (Tools to validate your build system). I sent Sona an email to see
>>>>> if the list was created, my impression is there have been discussions,
>>>>> but no list. This came up when some people had a security discussion and
>>>>> I suggested they join this group.
>>>>> 
>>>>> I propose:
>>>>> 
>>>>> Yocto-security - Discussions about tools and techniques to improve
>>>>> embedded system security.
>>>> 
>>>> This did already get created:
>>>> 
>>>> https://lists.yoctoproject.org/listinfo/yocto-security
>>> 
>>> Thanks, I did a quick look and didn't find it. I emailed Sona, but no
>>> response (not surprising given I didn't wait and TZ).
>>> 
>>> Philip
>>> 
>>>> 
>>>> Cheers,
>>>> Paul
>>>> 
>>> --
>>> _______________________________________________
>>> tsc mailing list
>>> tsc at lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/tsc
>> 
>> 
>> 
> 
> --
> _______________________________________________
> tsc mailing list
> tsc at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/tsc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/tsc/attachments/20151013/4c9e8ceb/attachment.sig>