On Mon, 2018-12-31 at 18:31 +0100, Jonas Meurer wrote:
> Pirate Praveen:
> > On 2018, ഡിസംബർ 31 5:19:22 PM IST, Jonas Meurer <jonas@freesources.org> wrote:
> > > Pirate Praveen:
> > > > On 12/28/18 11:06 AM, Thomas Goirand wrote:
> > > > > If the problem is hardware and connectivity, then IMO you can easily
> > > > > find a sponsor for it. My company could well offer it for example
> > > > > (hosted in Geneva with very nice connectivity to almost everywhere).
> > > > >
> > > > > Setting-up a repository isn't hard. And for a start, I don't think
> > > you
> > > > > really need a buildd network, just amd64 is ok-ish.
> > > >
> > > > I'd like go ahead with this offer and create rolling.debian.net (as
> > > > someone suggested already to avoid reusing volatile). I think we can
> > > > take the setup discussions offlist.
> > >
> > > Please don't name it 'rolling'. This term is used a lot in the sense of
> > > 'rolling releases' by other distributions, and also in discussions
> > > about
> > > constantly usable testing.
> >
> > Well, it only makes things clear as the packages in this repo will be rolling.
>
> ... as packages do in unstable, testing and ${stable}-backports. So it's
> not a particularly good term to describe the unique feature of the new
> repo either. In my eyes, 'fastpaced' makes the point far better.
>
> But as said, the main argument against calling it 'rolling' is that it
> would create confusion due to the name already being used in other
> (Debian-related) contexts.
At the risk of bikeshedding, some alternate names that might be less
confusing:
- fresh-apps
- evergreen
- rolling-apps
Ben.
--
Ben Hutchings
Power corrupts. Absolute power is kind of neat. - John Lehman
Attachment:
signature.asc
Description: This is a digitally signed message part