On 8/31/14, Werner Baumann wrote:
> I don't feel the need to talk about "open soure" on depian-project at
> the moment. But if you do, don't forget the origins. A good summary is
> at http://oreilly.com/openbook/opensources/book/raymond2.html. It is
> really worth reading from first hand what the
On 9/3/14, Jakub Wilk wrote:
> * Scott Kitterman , 2014-09-03, 07:59:
>>We could have an on stage censor with a switch for the microphone.
>
> And broadcast delay.
Better still, a button on everyone's seat in the audience,
so everyone can play censor - that would be a hoot!
Or perhaps a +1/-1 bu
On 9/4/14, Scott Kitterman wrote:
> On September 3, 2014 10:23:14 AM EDT, Ian Jackson
> wrote:
>>Piotr Ożarowski writes ("Re: Code of Conduct violations handling
>>process"):
>>> yeah, lets do censorship. I lived in a country with censorship¹, we
>>> didn't have people swearing and nobody dared t
On 9/4/14, Ian Jackson wrote:
> Piotr Ożarowski writes ("Re: Code of Conduct violations handling process"):
>> Some people want(ed) to codify in CoC other political correctness
>> "things" that I don't agree with. I like our current CoC and I don't
>> want to change it.
>
> Neil Gaiman writes:
>
>
On 9/4/14, Ian Jackson wrote:
> Russ Allbery writes ("Re: Code of Conduct violations handling process"):
>> What case? Ian raised a bunch of general questions about how we plan on
>> enforcing our CoC, with no reference to any specific incident. You seem
>> to be convinced that this is about som
On 9/4/14, Zenaan Harkness wrote:
> On 9/4/14, Ian Jackson wrote:
>> Russ Allbery writes ("Re: Code of Conduct violations handling process"):
>>> What case? Ian raised a bunch of general questions about how we plan on
>>> enforcing our CoC, with no referenc
On 9/4/14, Russ Allbery wrote:
> Piotr Ożarowski writes:
>> [Ian Jackson, 2014-09-03]
>>> Piotr Ożarowski writes ("Re: Code of Conduct violations handling
>>> process"):
>
Some people want(ed) to codify in CoC other political correctness
"things" that I don't agree with. I like our curr
On 9/4/14, Patty Langasek wrote:
> On Wed, Sep 03, 2014 at 12:29:36PM +0100, Ian Jackson wrote:
>> I think more guidance for the teams involved would be helpful. The
>> Debconf and Debian CoC statements are too difficult to amend. The DC
>> and Debian teams should develop a process document whic
On 9/4/14, Russ Allbery wrote:
> Zenaan Harkness writes:
>
>> More facts trickle out. Thank you for stepping up to the plate.
>
>> Any chance someone could crush an egg shell already and just post a link
>> to the brouhaha? Or summarise the events?
>
>> Are
Once again, you rant multiple lists whilst hiding who you are.
I am Zenaan Harkness. I have some (not all) strongly held views.
As an aside, I shall use systemd and have tried a few times now, but
have a technical issue or two with my setup when using systemd, which
I need to find time to solve
By emailing each of the above email mailing lists, it's not hard to
guess who you are.
It is sad.
It is in your interests (for sanity, to stop your tsunami of loss of
respect, etc) to simply stop.
Take a holiday.
Come back in a time (weeks, months) that provides for you to return to
communicati
Note: I am not (yet) a developer and am therefore without franchise
(voting rights) in the Debian community.
On 3/20/14, Russ Allbery wrote:
> While it's probably too late in this process to change what we're going to
> vote on, I just ran across this today, and it may be of general interest
> in
On 5/26/14, Russ Allbery wrote:
> Anthony Towns writes:
>> Which is more important, avoiding sudden upheavals where possible,
>> or ensuring individual ctte members have breaks?
>
>> If the latter's more important, then it's better not to special case
>> things now; if the former's more importa
On 5/26/14, Russ Allbery wrote:
> Michael Gilbert writes:
>> On Sun, May 25, 2014 at 1:37 PM, Russ Allbery wrote:
>
>>> We could combine both features, though: set a term length of two years,
>>> and then say that people can serve for two terms in succession but then
>>> have to leave the committ
encumbered in only a DFSG-Free
sense, or would, as MJR implies (see below, from -vote),
simply self-destruct?
On Wed, 2004-02-25 at 23:51, MJ Ray wrote:
> On 2004-02-25 11:57:30 + Zenaan Harkness <[EMAIL PROTECTED]> wrote:
>
> > It kind of feels intuitively attracti
To my personal mind, why would anyone choose anything other than Debian
or Fedora (or Slackware or Gentoo for the masochists)?
Debian is where it's at - DEB packaging is "Borderline flawless":
http://people.debian.org/~srivasta/talk.html
And if you must cow-tow to the RPM masses, pick the biggest
On Fri, 2004-02-27 at 23:01, Zenaan Harkness wrote:
> To my personal mind, why would anyone choose anything other than Debian
> or Fedora (or Slackware or Gentoo for the masochists)?
>
> Debian is where it's at - DEB packaging is "Borderline flawless":
> http
On Sun, 2004-02-29 at 12:02, Frank Lichtenheld wrote:
> On Sun, Feb 29, 2004 at 11:34:59AM +1100, Zenaan Harkness wrote:
> > How is the Debian logo so different from "front cover texts"?
>
> Because it is not distributed in Debian 'main' ?
Is this a valid res
On Sun, 2004-02-29 at 15:41, Andrew Suffield wrote:
> On Sun, Feb 29, 2004 at 03:18:38PM +1100, Zenaan Harkness wrote:
> > Why should our logo not be Free?
>
> No reason. I think we've actually tried to do this before now and hit
> some snag or other, and just not cared en
On Sun, 2004-02-29 at 17:19, Don Armstrong wrote:
> On Sun, 29 Feb 2004, Zenaan Harkness wrote:
> > The Debian logo{, and all other non-free parts of the Debian website
> > listed here, if there are any} are licensed according to the GNU GPL
> > {LGPL|X|?} license.
>
>
On Sun, 2004-07-04 at 08:47, James Thayer wrote:
> Once GNU Hurd is ready for production use, will you still support Linux
> versions of Debian, or will GNU Hurd be the only kernel Debian supports?
> That is, will you support both?
Asking such a question implies that you don't understand the De
21 matches
Mail list logo
