public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] request for spec files used for building gentoo-install livecd
Date: Mon, 26 Sep 2005 08:42:31 -0500	[thread overview]
Message-ID: <4337FAC7.2070701@gentoo.org> (raw)
In-Reply-To: <200509261045.55909.pauldv@gentoo.org>

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

Paul de Vrieze wrote:
> On Saturday 24 September 2005 08:14, Mike Rosset wrote:
> 
>>It was a dicussion, you kicked me because you didnt agree. I cant
>>resolve my issue if I cant discuss it.
>>
>>It was actually a simple request, I have decided to forgo ever getting
>>this spec file any time soon. and will create my own. Which it sounds
>>like I'll replace later anyways... seems pointless
>>
>>But I really dont see how you can expect people to give quality
>>debugging feed back when no help is returned, for projects that are
>>using your project.
>>
>>I dont care about politics, I'm not a lawyer I was wrong to bring up
>>GPL . I'm just trying to keep conformed to the "gentoo-installer" cd.
>>haveing the spec file makes that alot easier.
> 
> 
> Please guys,
> 
> Gentoo is made for users too. Don't be overly protective, but find honour 
> in the fact that he chooses to use gentoo and the installer project to 
> base his work on. You should help him, and inquire what the project is 
> about. If he finishes you might even ask whether you can showcase it. 
> Possibly even leading to an article on newsforge (or other newssite) 
> leading for POSITIVE publicity for gentoo. Not kick people out of IRC 
> channels only if they don't agree with you. And indeed the GPL does not 
> make you release the spec file. The open nature of gentoo should.

Its sad. This is the second time I've hear of folks going into the
installer channel asking them about things/offering help and
suggestions, then getting kicked and flamed. It has certainly put a
black eye on the installer project from my point of view. Seems like
they are more afraid of someone else coming up with a better idea that
having an *open* view on the project.

-- 
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operations Manager

---
GPG Public Key:  <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1  4D07 416F A15D 27F4 B742

ramereth/irc.freenode.net

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-09-26 13:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  5:21 [gentoo-releng] request for spec files used for building gentoo-install livecd Mike Rosset
2005-09-23 12:23 ` Chris Gianelloni
2005-09-23 23:45   ` Mike Rosset
2005-09-24  3:40     ` Andrew Gaffney
2005-09-24  6:14       ` Mike Rosset
2005-09-24  6:50         ` Ted Kosan
2005-09-24  7:48           ` Mike Rosset
2005-09-24 13:19             ` Chris Gianelloni
2005-09-24 15:06               ` Mike Rosset
2005-09-24 13:16           ` Chris Gianelloni
2005-09-26  8:45         ` Paul de Vrieze
2005-09-26 13:42           ` Lance Albertson [this message]
2005-09-26 13:50             ` Andrew Gaffney
2005-09-26 13:54             ` Chris Gianelloni
2005-09-26 21:10             ` Mike Rosset

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=4337FAC7.2070701@gentoo.org \
    --to=ramereth@gentoo.org \
    --cc=gentoo-releng@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