X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from jeremythomerson.com (mail.jeremythomerson.com [74.117.189.38]) by lists.alpinelinux.org (Postfix) with ESMTP id 6F17D1EB587 for ; Fri, 25 Feb 2011 04:51:55 +0000 (UTC) Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by jeremythomerson.com (Postfix) with ESMTP id 1C80A1C584 for ; Thu, 24 Feb 2011 22:59:38 -0600 (CST) Received: by wwb39 with SMTP id 39so1577058wwb.25 for ; Thu, 24 Feb 2011 20:51:53 -0800 (PST) Received: by 10.216.191.215 with SMTP id g65mr6642032wen.16.1298609513150; Thu, 24 Feb 2011 20:51:53 -0800 (PST) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Reply-To: jeremy@thomersonfamily.com Received: by 10.216.13.2 with HTTP; Thu, 24 Feb 2011 20:51:33 -0800 (PST) In-Reply-To: <2491400ce48a2baa83e7db5f2e46577e@ytre.org> References: <2491400ce48a2baa83e7db5f2e46577e@ytre.org> From: Jeremy Thomerson Date: Thu, 24 Feb 2011 22:51:33 -0600 Message-ID: Subject: Re: [alpine-devel] Organizing Alpine Linux project To: Natanael Copa Cc: alpine-devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary=0016e659fd08bbb879049d141621 --0016e659fd08bbb879049d141621 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Feb 24, 2011 at 9:10 AM, Natanael Copa wrote: > Hi, > > So, we have experienced a growth recently and I think its about time that > we try have some official organization structure. I would like to try avoid > bureaucracy and strict rules. We want this to be a fun place to be. > > Here is what I propose: > > We define the Alpine Linux goal. > Suggestion: > Provide an operating system that is (in priority order): > 1) Secure > 2) Small/non-bloated > 3) Simple > 4) Fast > > Of course there are trade-offs so consider the above as a general guideline > rather than a strict rule. > > We split us up in the following teams/subprojects: > * Infrastructure Team > * Developer Team > * Documentation Team > > We also need a Security Team, but I'll come back to that later. > > = Infrastructure Team = > The goal is to provide and maintain the needed hardware and services that > are needed to keep the Alpine Linux project running. This includes web > sites, bugtracker, mail servers, mailing lists, IRC channels etc. As long as > it possible and makes sense we want use Alpine Linux for this. We should eat > our own dog food. > > Currently its nangel that is the (un)official coordinator. I think we have > many candidates for people to join this team: clandmeter, jbilyk. > > Please let me know if you want help setup and run our infrastructure. > I think for the next year or so at least, I will have more time to help with this, and wouldn't mind assisting nangel, et al with whatever I can. > = Developer Team = > They do the developing work, build packages, bootscripts, installer, > package manager, etc. We can probably divide this in subteams/subprojects > later. For example package maintainers can be splitted up in maintainer > teams like "kernel maintainers", "base libs (uclibc)", "python team", "perl > team", etc. We will probably also have a Release Team and a "stable > maintainers" that comes here under. > > I suggest me as coordinator for this team. Those who have commit access are > automatically members here. > I won't be much help with the kernel stuff, but wouldn't mind helping with any java-oriented packages specifically. I'm a java junkie. I've created a few general packages as well that I'll try to maintain better than I have been. > = Documentation Team = > Are responsible for the official documentation. (current in wiki) > I suggest mattx86 as team coordinator here. Is this ok? > There are many candidates for team members. (jbilyk, mhavela, etc) > > = Security Team = > I think we need a security team which follows sec lists and figures out > what packages that are vulnerable to us. They create tickets and kicks the > developers in the rear part til they have fixed the issue. Ilemme Haave that > offered do this but have been totally missing so currently there is nobody > doing this important job so volunteers are welcome. > > Please let me know if you are interested beeing a part of the security team > or want be the security team coordinator. > > I suggest that all team members gets an official @alpinelinux.org email > address. We probably don't need to do mail hosting for this but can forward > to our current email addresses. > > We could also have Marketing team, Recruitment team and Art team but I > think its better we start small. > > If you feel you belong to the team or feel for be a coordinator of a team, > please let me know. I would prefer that the team coordinators are active > involved and reasonable responsive on requests. > > Maybe each team should have a subproject in the bugtracker? Maybe we should > have a separate email list for each team? > Subproject in the bug tracker would be useful for pulling up a list of "what I need to work through". In my monitoring of this mailing list, I don't think we need separate mailing lists for them (yet). > Other ideas, thougts? > Jeremy Thomerson --0016e659fd08bbb879049d141621 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Feb 24, 2011 at 9:10 AM, Natanael Co= pa <ncopa@alp= inelinux.org> wrote:
Hi,

So, we have experienced a growth recently and I think its about time that w= e try have some official organization structure. I would like to try avoid = bureaucracy and strict rules. We want this to be a fun place to be.

Here is what I propose:

We define the Alpine Linux goal.
Suggestion:
Provide an operating system that is (in priority order):
1) Secure
2) Small/non-bloated
3) Simple
4) Fast

Of course there are trade-offs so consider the above as a general guideline= rather than a strict rule.

We split us up in the following teams/subprojects:
* Infrastructure Team
* Developer Team
* Documentation Team

We also need a Security Team, but I'll come back to that later.

=3D Infrastructure Team =3D
The goal is to provide and maintain the needed hardware and services that a= re needed to keep the Alpine Linux project running. This includes web sites= , bugtracker, mail servers, mailing lists, IRC channels etc. As long as it = possible and makes sense we want use Alpine Linux for this. We should eat o= ur own dog food.

Currently its nangel that is the (un)official coordinator. I think we have = many candidates for people to join this team: clandmeter, jbilyk.

Please let me know if you want help setup and run our infrastructure.

I think for the next= year or so at least, I will have more time to help with this, and wouldn&#= 39;t mind assisting nangel, et al with whatever I can.
=A0
=3D Developer Team =3D
They do the developing work, build packages, bootscripts, installer, packag= e manager, etc. We can probably divide this in subteams/subprojects later. = For example package maintainers can be splitted up in maintainer teams like= "kernel maintainers", "base libs (uclibc)", "pyth= on team", "perl team", etc. We will probably also have a Rel= ease Team and a "stable maintainers" that comes here under.

I suggest me as coordinator for this team. Those who have commit access are= automatically members here.

I won'= t be much help with the kernel stuff, but wouldn't mind helping with an= y java-oriented packages specifically. =A0I'm a java junkie. =A0I'v= e created a few general packages as well that I'll try to maintain bett= er than I have been.
=A0
=3D Documentation Team =3D Are responsible for the official documentation. (current in wiki)
I suggest mattx86 as team coordinator here. Is this ok?
There are many candidates for team members. (jbilyk, mhavela, etc)

=3D Security Team =3D
I think we need a security team which follows sec lists and figures out wha= t packages that are vulnerable to us. They create tickets and kicks the dev= elopers in the rear part til they have fixed the issue. Ilemme Haave that o= ffered do this but have been totally missing so currently there is nobody d= oing this important job so volunteers are welcome.

Please let me know if you are interested beeing a part of the security team= or want be the security team coordinator.

I suggest that all team members gets an official @alpinelinux.org email address. We probably = don't need to do mail hosting for this but can forward to our current e= mail addresses.

We could also have Marketing team, Recruitment team and Art team but I thin= k its better we start small.

If you feel you belong to the team or feel for be a coordinator of a team, = please let me know. I would prefer that the team coordinators are active in= volved and reasonable responsive on requests.

Maybe each team should have a subproject in the bugtracker? Maybe we should= have a separate email list for each team?

<= div>Subproject in the bug tracker would be useful for pulling up a list of = "what I need to work through". =A0In my monitoring of this mailin= g list, I don't think we need separate mailing lists for them (yet).
=A0
Other ideas, thougts?

Jeremy Thomerson=A0
--0016e659fd08bbb879049d141621-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---