From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org,
Using OE <openembedded-users@lists.openembedded.org>
Subject: Re: Discussion regarding the future of OpenEmbedded mailing lists
Date: Wed, 25 Feb 2009 13:50:18 -0500 [thread overview]
Message-ID: <49A592EA.1050602@balister.org> (raw)
In-Reply-To: <1235587135.2621.47.camel@andromeda>
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
Michael 'Mickey' Lauer wrote:
> Am Mittwoch, den 25.02.2009, 16:08 +0000 schrieb Martyn Welch:
>> Wolf, Josef wrote:
>>> Martyn Welch wrote:
>>>
>>> [ ... ]
>>>> There has been a proposal on the openembedded-devel mailing list
>>>> to re-organise the lists provided on openembedded.org.
>>> [ ... ]
>>>> Openembedded-devel - for humans to post patches and ask questions
>>>> Openembedded-commits - commits, bugs, logs, etc
>>>> Openembedded-private - core team
>>> To be honest, I am somewhat confused by the naming of the lists.
>>> If I understand correctly, the intent of the new lists are
>>>
>>> OE-private: core-team.
>>> All the other projects I know of would call this list
>>> FOOBAR-devel
>>>
>>> OE-devel: rest of the world.
>>> All the other projects I know of would call this list
>>> FOOBAR-users
>>>
>>> Is there any reason for this strange (that is: non-standard) naming
>>> scheme? Is OE-private meant to contain really private (confidential?)
>>> traffic? If not, I'd guess many people (like me) would mis-interpret
>>> the intent of this list.
>> Yes - it is my understanding that the traffic on Openembedded-private is really private (I believe that OpenEmbedded is now legally registered as a non-profit in Germany and I should imagine there are certain discussions which need a degree of privacy).
>
> Correct, although it's not because of the e.V., but rather for companies
> who may want to contact us in order to get some work arrangements, but
> don't want to be disclosed.
And it is not a very exciting list either. No one is missing anything
not being on it.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-02-25 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 9:47 Discussion regarding the future of OpenEmbedded mailing lists Martyn Welch
[not found] ` <B6FF18F4244BAE4991D05BF4F7A7649293467E@MCHP7I5A.ww902.siemens.net>
2009-02-25 16:08 ` Martyn Welch
2009-02-25 18:38 ` Michael 'Mickey' Lauer
2009-02-25 18:50 ` Philip Balister [this message]
2009-03-02 18:38 ` Michael 'Mickey' Lauer
2009-02-26 13:22 ` Marco Cavallini
2009-02-26 19:40 ` Michael 'Mickey' Lauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49A592EA.1050602@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
--cc=openembedded-users@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox