Date: Tue, 9 Apr 2019 12:24:01 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Nero <nero@w1r3.net>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Project reorganisation
Message-ID: <20190409122401.64499c5c@ncopa-desktop.copa.dup.pw>
In-Reply-To: <20190409084131.GA9046@lucy.icvn.de>
References: <20190409084131.GA9046@lucy.icvn.de>
Precedence: list
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 boundary="Sig_/xFPjt=UQSzabVTz7j=cutAE"; protocol="application/pgp-signature"

--Sig_/xFPjt=UQSzabVTz7j=cutAE
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Tue, 9 Apr 2019 08:41:31 +0000
Nero <nero@w1r3.net> wrote:

> Hi,
>=20
> I didn't ACK the project goals because i dont see it as a general
> purpose distribution.

Can you clarify? how do you see it? If its not general purpose, what
specific purpose is it for?

> Both i and my (undiclosed) employer use Alpine for the good base
> system to application payload ratio.

application payload ratio?

> This is the main feat, the secondary is the diskless netboot.

Running diskless was one of the original features, and we will continue
support that.

netboot has been added afterwards.

> I did't ACK the new governance model that is currently RFC'ed as well.
> If i get to be in a Team, i'll have authority over others to make
> decisions, if im not, im subject to it (as far as you have leverage
> towards volunteers without contracts). Both is poison for compromises
> being made on equal terms.

The governance RFC is about "bootstrapping" the organization. Who can
decide what, when. Sort of a "constitution" if you like. This is not
the final goal but just enough to get us started so we have a
documented way to create and modify rules.

How the teams are organized is something that needs to be worked on
down the road.

That said, the idea here is not having a team lead telling what the
other team members should do or not do. The idea is to have a group of
people to help each other to achive a specific goal. It could for
example be help each other to manage the alpine linux servers (dns, web
site, bugtracker etc), or a team that help each other to review and
merge PRs that has to do with PHP or python etc.

> I have interests in this project, im able to represent them, and im
> ready for compromises with other people having different goals. This
> is how i expect cooperations between persons/companies with different
> interests to work.

Yes. That is how I think it should work. Everyone should be able to
express their needs and contribute, "scratch their itch" and I want
that to happen in a friendly manner. Having some documented rules will
help us achieve that.

> Also, please don't institutionalize "ownership" over a community
> effort.

How do you mean?

-nc

--Sig_/xFPjt=UQSzabVTz7j=cutAE
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBILYQCL1LfHE581DKTrNCQfZSVoFAlyscsEACgkQKTrNCQfZ
SVoQwQ/+KRFLa51d4SrdbZFPk40CvNOKlbK35hRqqBcOJsRclW93KaARxBC7k1j2
qnSjD+waOSmj7dzdG/aPhST/2pzUKWMKQV83i4pj4RtlJtlZS5OznbAtIsiWeYM0
IMIyU2BiU1FPlooWRQhZwTtneGPJGfP8ANPGE3u9p3JJ2w7g7rzkvuyp+tDUE/mI
ar6j+y0MIaXLIkM85EIvt/0QGl3FBfqCbd8kBXJmXah9/wExeL3VjCIBSr3JRckz
/G2pcrI4dweMPeRuZlXgYO8nUbJC8LFEkO77KntxlZ16LPdW4/5594ZRbwKc7dxZ
5WnafyPeChDBlcnoC3pl3sTgDLyn23zSOqGszb0m2EWuTqesWGhZYx2Uo7YcCpjn
ZOuX8pindjiZp99tC42B7JVzPdgLO/vyVpv9sQ8/zvj63JSXYwAb+YDyZl66Crt2
hVUj3uiAa/xymKDQ9pNgVf2s9Mf1mXa6Y2S04GzlfH4AsWkzSzZYcsnloXGr02Uv
ZqJHSLohg43AThXsNlMsgEfnv7axLYKDmA9GODcLItwzLcY1dkRlcC9XfD+QOGVQ
qjIDBMGXZg/Q0Bsl1smUYYLVMv2KvKbFtS9GPS55XLmDvZRxiXE70L2j0zwB2V7N
ThBUaDynVtfRc/v4YxHpjoNxXPcj0S/B9CX6qW3D0XIwpCljdXc=
=/zaT
-----END PGP SIGNATURE-----

--Sig_/xFPjt=UQSzabVTz7j=cutAE--


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---