Ha oh yeah sorry about that, I thought it was for *security
notifications* and just signed up without thinking.  Will you post fix
notifications on the main list?

On Mon, Nov 16, 2009 at 2:41 PM, Cédric Krier <[email protected]> wrote:
> On 16/11/09 00:38 +0100, Cédric Krier wrote:
>> On 10/09/09 23:03 +0200, Cédric Krier wrote:
>> > On 10/09/09 16:53 +0200, Cédric Krier wrote:
>> > > Hi,
>> > >
>> > > I think it is time to have a new mailling for dev (tryton-dev) where we 
>> > > could
>> > > post code to review, technical stuff about Tryton etc.
>> > > And I propose to have also one private (tryton-security) for security 
>> > > people
>> > > where others will be able to post security issue.
>> > >
>> >
>> > So I created tryton-dev google groups:
>> >
>> > http://groups.google.com/group/tryton-dev
>> >
>> > Please, interested people suscribe to it, we will start using it next week.
>> >
>>
>> tryton-security is available:
>>
>> http://groups-security.tryton.org/
>>
>
> I did not realize that so much people wanted to fix security issues :-)
>
> We can not accept everybody on this mailing list because this mailing list is
> for security developers that will fix reported issues and the major difficulty
> is that the information must be kept secret until fix exist and is applied on
> all series. So we must keep the number of people aware as tiny as possible.
>
> So I first unsubscribe everybody who ask to be member just after the previous
> email.
>
> Here is the rule:
> Anybody, who think must be on the list because he think he has the skill to
> fix security issues, can ask with a motivation email to the mailing list to be
> member.
> The security people will verify the validity of the subscription and will
> accept or deny it.
>
>
> --
> Cédric Krier
>
> B2CK SPRL
> Rue de Rotterdam, 4
> 4000 Liège
> Belgium
> Tel: +32 472 54 46 59
> Email: [email protected]
> Jabber: [email protected]
> Website: http://www.b2ck.com/
>

--~--~---------~--~----~------------~-------~--~----~
[email protected] mailing list
-~----------~----~----~----~------~----~------~--~---

Reply via email to