Message-ID: <1446122261.9302.50.camel@df1844j>
Subject: Re: [alpine-devel] v3.3 feature freeze
From: Leonardo Arena <rnalrd@gmail.com>
To: vkrishn4@gmail.com
Cc: alpine-devel@lists.alpinelinux.org
Date: Thu, 29 Oct 2015 13:37:41 +0100
In-Reply-To: <201510291624.21420.vkrishn4@gmail.com>
References: <20151022180104.1feeb73a@ncopa-laptop>
	 <201510291311.01965.vkrishn4@gmail.com> <1446105556.9302.26.camel@df1844j>
	 <201510291624.21420.vkrishn4@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
	boundary="=-t0c0hJy7L8sQhKr1KOqv"
Precedence: list
Mime-Version: 1.0


--=-t0c0hJy7L8sQhKr1KOqv
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On gio, 2015-10-29 at 16:24 +0530, V.Krishn wrote:
> > On gio, 2015-10-29 at 13:11 +0530, V.Krishn wrote:
> > >=20
> > > Criteria is not upstream stability release but,
> > > 1. Does these pkgs' normal updates get backported ?
> > > 2. If we decide fitting main is one CD or two do we want them in main
> > > then ? 3. Pkgs like these are easy to maintain and maybe
> > > tagged/delegated to new or less experienced maintainers.
> > > 4. Note, there is no stopping for main devs in maintaining community
> > > pkgs.
> >=20
> > I think to it's one of the relevant criteria. Maintaining a package in =
a
> > stable Alpine branch, when upstream does not provide maintenance
> > releases, puts a load on the Alpine package maintainer that needs to
> > backport the security patches at least, and possibly other bugfixes too=
.
> >=20
> > So I think one of the main questions to determine whether the package g=
o
> > to main/community is:
> >=20
> > - Is the maintainer willing to ensure that package foo-1.1.0 will have
> > ~2years of security fixes/critical bug fixes available for version 1.1?
> > If yes, stay in main, if no, go to community, where you are free to bum=
p
> > to version 2.x.
> > Or did I get the purpose of community repo wrong?
>=20
> Moving to community does not undermine maintainer's capability.
> Nor does community undermines pkgs usability.
> (users only needs to be a bit more aware while using those pkgs).
> eg. if I were to pkg a group-ware like citadel.org I would let it stay in=
=20
> community, even if I can or am willing to do a "2years of security=20
> fixes/critical bug fixes".
> Just thinking in terms of AL philosophy and things like "Small. Simple.=
=20
> Secure" , security-oriented, lightweight ...etc.
>=20


I didn't think much in these terms for community repo, although it makes
sense. I think the original idea why community repo was born, it's
because we want to diminish the backporting work to stable branches,
which is the harder part, and allowing more people to contribute/help
with maintenance by giving GIT write access.

To me community means "no maintenance releases, no system/core packages,
and possibly lower quality packaging". Main for me is instead
"system/core packages included but not only these, maintenances
releases, better packaging quality".

If maintainer wants to keep the package in community even though
upstream provide maintenance releases for ~2y, I'm fine with that.

And I don't have objections in having non-system/core packages in main,
as long as there are maintenance releases.


> I think presently most important is if a main dev+maintainer thinks it go=
es in=20
> main/, that has overriding vote.

+1

- leo


--=-t0c0hJy7L8sQhKr1KOqv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAABAgAGBQJWMhMVAAoJELAPckZGG2T6dcEIAIafPc2P7rukA/4bkb+41HDt
QSPK28djRs4wh7EoHYfwWpieOIzk5oiTnu1NGrPNL4YFYUBs/1l7Ak7vDEvkRMbR
g/xdFB/R75BmMEW0l9t9MVHtfmyFPR6q92uXaWQikAnm++6sKk7/ttxO2Lo7nJNV
tTdJkPdZ0sHCbgC2MtKZNUsn7qaphwErfiKa6MPeOQze+jDx96Z3C0SzqA8L/dGi
ijxkxXM1iUKegHoOWa3nzjlnKvRBfyT1CvRVL2kQ8UGFlCkVNtSTzcwT4LMNHTZ0
buAFk98jU3H19a+pCJAP7hEYDxz8gdHJ4ZqVWTH3qlNZofbnhfSN4lQc5Ql7LGg=
=UpIt
-----END PGP SIGNATURE-----

--=-t0c0hJy7L8sQhKr1KOqv--



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---