On Mon, 23 Feb 2015, Hendrik Boom wrote:

> On Mon, Feb 23, 2015 at 01:19:04PM +0000, KatolaZ wrote:
> > On Mon, Feb 23, 2015 at 01:04:05PM +0000, Nuno Magalhães wrote:
> > > On Sun, Feb 22, 2015 at 2:38 PM, Ста Деюс <sthu.deus@???> wrote:
> > > > But, at the first, what is planned to perform to protect «Devuan» from
> > > > the guys, that got hold of the fantastic project «Debian»? In other
> > > > words, if the guys come to «Devuan» and by their cruelty will start
> > > > to «help» some of developers to corrupt the project, do abnormal,
> > > > unnatural for the project things -- similar like constitution of
> > > > «Debian» appeared, finnaly the «systemd» was forcibly set up: how we
> > > > will protect our project?
> > >
> > > Very good question.
> >
> > Well the answer is simple: if such an unlikely "invasion" would
> > happen, we will always have the opportunity to fork Devuan, for the
> > good of its users :)
>
> This suggests that one of the goals of Devuan should be easy forkability.
>
> But it's not clear to me what this involves technically.
>
> Any suggestions?

perhaps the SDK is a good start on this ;^)

> Are there aspects of the existing structure of Debian that made it more
> difficult to fork?

no, not really. I'd say Debian until its version 7 is really fork
friendly, not just technically, but also politically: a good amount of
DDs have welcomed our fork seeing it brings some resilience and fresh
air. The architecture of the OS is very open to ad-hoc usage and we
should keep up with that.

I also believe that without Devuan today, in one or two years from now
systemd would be really hard to remove and that might make Debian harder
to fork in the direction of init-freedom.



ciao