From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Gentoo's Social Contract & Bugzilla
Date: Fri, 04 Aug 2006 18:53:51 -0500 [thread overview]
Message-ID: <44D3DE0F.9020401@gentoo.org> (raw)
In-Reply-To: <44D3D87B.8040905@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
Peter Gordon wrote:
> Matthew Marlowe wrote:
>> If we could get a license donated, my vote would be to switch to Atlassian
>> Jira, http://www.atlassian.com/software/jira. It seems to be gaining
>> mindshare rather quickly, and the company I work for just shelled out $2,400
>> because they liked it so much more than RT/Bugzilla. I believe it supports
>> multiple DB backends, including all the usual suspects.
>
> Maybe it's just me, but I think that having such a core component of the
> distribution be proprietary is in complete violation of Gentoo's Social
> Contract[1] (if not the letter of it, then its spirit of openness). It
> states:
>
> "Gentoo will never never depend upon a piece of software or
> metadata unless it conforms to the GNU General Public License,
> the GNU Lesser General Public License, the Creative Commons -
> Attribution/Share Alike or some other license approved by the
> Open Source Initiative (OSI)."
>
> Isn't this one of the driving reasons why our forums run phpBB instead
> of something like vBulletin, for example? :)
>
> [1] http://www.gentoo.org/main/en/contract.xml
I'm not entirely sure if this is directed towards the supporting web
applications or of Gentoo itself. To me its directed towards the meta
distribution and not any of the underlying support mechanisms of Gentoo.
If we were to use some non-gpl webapp, the underlying Gentoo system you
run does not depend on a non-gpl piece of software. A bug tracking
system is not an underlying component of Gentoo. Its just a tool that
helps with development of Gentoo.
But anyways, some people view it in the strict sense and they're
entitled to it. That's just how I view it when I read it. Its a bit
vague on what Gentoo really is. Is it talking only about the meta
distribution? Or that plus the underlying supporting systems that help
run Gentoo?
--
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: 188 bytes --]
next prev parent reply other threads:[~2006-08-04 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <886253338-1154701653-cardhu_blackberry.rim.net-693078490-@bwe059-cell00.bisx.prod.on.blackberry>
2006-08-04 23:22 ` [gentoo-dev] Monthly Gentoo Council Reminder for August Matthew Marlowe
2006-08-04 23:30 ` Gentoo's Social Contract & Bugzilla (was: "Re: [gentoo-dev] Monthly Gentoo Council Reminder for August") Peter Gordon
2006-08-04 23:37 ` Ciaran McCreesh
2006-08-04 23:42 ` [gentoo-dev] Re: Gentoo's Social Contract & Bugzilla Peter Gordon
2006-08-04 23:53 ` Lance Albertson [this message]
2006-08-05 7:11 ` Luis Francisco Araujo
2006-08-05 8:32 ` Peter Gordon
2006-08-05 10:07 ` Wernfried Haas
[not found] <1003509466-1154735876-cardhu_blackberry.rim.net-316651646-@bwe002-cell00.bisx.prod.on.blackberry>
2006-08-05 0:24 ` Matthew Marlowe
2006-08-05 0:29 ` Jakub Moc
2006-08-05 0:59 ` Ciaran McCreesh
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=44D3DE0F.9020401@gentoo.org \
--to=ramereth@gentoo.org \
--cc=gentoo-dev@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