public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] base-system needs developers who care
Date: Wed, 24 Aug 2016 12:17:32 -0500	[thread overview]
Message-ID: <20160824171732.GB25523@whubbs1.gaikai.biz> (raw)
In-Reply-To: <20160824160505.3d07b9d6@abudhabi.paradoxon.rec>

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

On Wed, Aug 24, 2016 at 04:05:05PM +0200, Lars Wendler wrote:
> On Tue, 23 Aug 2016 20:08:30 -0400 Anthony G. Basile wrote:
> 
> >On 8/23/16 8:03 PM, Lars Wendler wrote:
> >> I have some kind of interest for these packages:  
> >
> >Lars, maybe once we get some names we should get a meeting of
> >base-system together and coordinate our efforts.  In particular, I
> >mostly have interest in those packages that make up @system for the
> >stages I build.
> >
> 
> Guys, I'd like to take the opportunity to "revive" the #gentoo-base IRC
> channel for coordination between base-system developers. 
> Perhaps "revive" is not the appropriate word considering that the
> channel never stopped to exist but rather became extinct.
> 
> Opinions?

Sure, I'm fine with using it; I'm there anyway.

> Furthermore what about the devs currently being listed in base-system
> team but stopped taking care of the team's packages for years?
 
I would say contact them individually and ask them if they want to stay
on the team.

> Oh, and to all new team members:
> Please keep in mind to *not* use EAPI-6 for base-system packages yet, so
> we can retain a somewhat stable upgrade path even for very old systems.

This was always a huge mistery that never really made sense.
Once the pm is upgraded on a system to eapi 6, I don't see the reason to
hold back any base system packages to older eapis, especially once eapi
6 has been stable for a year.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2016-08-24 17:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 23:17 [gentoo-dev] base-system needs developers who care Robin H. Johnson
2016-08-23 23:36 ` Anthony G. Basile
2016-08-24  0:03 ` Lars Wendler
2016-08-24  0:08   ` Anthony G. Basile
2016-08-24  1:06     ` Benda Xu
2016-08-24 14:05     ` Lars Wendler
2016-08-24 14:08       ` Pacho Ramos
2016-08-24 14:42         ` Upgrading Old Gentoo - Was " M. J. Everitt
2016-08-29 17:18         ` Joshua Kinard
2016-08-24 15:32       ` Mike Gilbert
2016-08-24 15:49         ` Michael Orlitzky
2016-08-25  8:00         ` Alexis Ballier
2016-08-24 17:17       ` William Hubbs [this message]
2016-08-24 20:33       ` Andreas K. Huettel
2016-08-24  1:11 ` William Hubbs
2016-08-24 17:24   ` Robin H. Johnson
2016-08-24  1:25 ` Patrick McLean
2016-08-24 12:04 ` Jason Zaman
2016-08-24 15:37 ` Mike Gilbert
2016-08-25  8:01 ` Alexis Ballier
2016-08-28  6:34   ` Daniel Campbell

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=20160824171732.GB25523@whubbs1.gaikai.biz \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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