Stuart Prescott writes ("Re: GR proposal: code of conduct"):
> - From the IRC perspective, we welcome the CoC -- it's nice to have
> a document to point people to which clearly articulates the sort of
> behaviour we want and the sort of environment we would like to
> maintain. A CoC is a great asp
On 14 February 2014 13:42, ChaosEsque Team wrote:
> The systemd fans ban anyone who say f__k-that to systemd.
Not respecting the communication culture of the project is a perfectly
reasonable reason for a ban, regardless of the opinion expressed by
the banned or held by the banners.
> What can w
On 14/02/2014, Axel Wagner wrote:
> ChaosEsque Team writes:
>> Everyone knows that the systemd crap is armtwisting and trys to
>> pull everyone and everything along with it.
>
> I believe (and
> will continue to believe) that the strong supporters of sysvinit within
> the development community of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
- From the IRC perspective, we welcome the CoC -- it's nice to have
a document to point people to which clearly articulates the sort of
behaviour we want and the sort of environment we would like to
maintain. A CoC is a great aspirational device a
Hi,
ChaosEsque Team writes:
> Everyone knows that the systemd crap is armtwisting and trys to
> pull everyone and everything along with it.
Please provide some numbers on this statement of fact. I believe (and
will continue to believe) that the strong supporters of sysvinit within
the developmen
Honestly, f__k systemd and f__k lennart, and f__k the fans of them.
Where's linus in all of this?
The systemd fans ban anyone who say f__k-that to systemd.
What can we do?
Can we fork debian? (Why do we have to...)
Why do 4 people get to decide to send thousands and thousands of people into
the
6 matches
Mail list logo
