From: hasufell <hasufell@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo, GitHub, and the Social Contract
Date: Mon, 16 Feb 2015 03:26:57 +0000 [thread overview]
Message-ID: <54E16381.8020409@gentoo.org> (raw)
In-Reply-To: <CAGfcS_nAnfXzE-=1KAdZdPsYbt6-5VFF2hKzJhEfjOgxVt_RrQ@mail.gmail.com>
Rich Freeman:
> On Sat, Feb 14, 2015 at 9:42 PM, hasufell <hasufell@gentoo.org> wrote:
>> Andreas K. Huettel:
>>>
>>> * The Gentoo Social Contract states [1]:
>>> "Gentoo will 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)."
>>>
>>
>> This has already been violated numerous times, including the development
>> of emul-linux-x86-* packages.
>>
>
> A principle being violated in the past isn't a good reason to simply
> abandon it. Principles like this one are always going to be hard to
> hit 100%, but that doesn't mean that we shouldn't do the best we can.
>
> That said, I don't really see how the 32-bit packages violate this.
> If they happen to include non-FOSS that really isn't GENTOO depending
> on them. I don't think anything essential in Gentoo depends on any
> non-FOSS components of any packages in the tree. Having non-stuff in
> the tree isn't the same as depending on them. Neither is having a
> random package that depends on a non-free package - we're talking
> about GENTOO depending on something, not a random package in the tree.
>
> If some project wanted to ONLY accept contributions via pull requests
> on github, then I could start seeing some concern.
>
Scripts no one can read except the team (even after being asked to
publish them) is by definition propriety software. It was used to
develop and package emul-linux-x86-* packages until this very day.
No one cared, at any time. I just find this a bit confusing, because of
the sudden bikeshed about github which IS already widely used in gentoo
(whether everyone likes it or not).
Git is distributed, so I do not see a single reason to SOLELY depend on
github. I'm not sure why people confuse this. If we don't, then ~95% of
this discussion becomes obsolete.
next prev parent reply other threads:[~2015-02-16 3:27 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 20:48 [gentoo-project] Gentoo, GitHub, and the Social Contract Andreas K. Huettel
2015-02-14 20:55 ` Anthony G. Basile
2015-02-14 21:09 ` Kristian Fiskerstrand
2015-02-14 21:23 ` Alexander Berntsen
2015-02-14 21:25 ` Andrew Savchenko
2015-02-14 21:37 ` Rich Freeman
2015-02-14 21:42 ` Kristian Fiskerstrand
2015-02-14 21:56 ` Rich Freeman
2015-02-14 22:08 ` Alexander Berntsen
2015-02-14 22:13 ` Ciaran McCreesh
2015-02-14 22:23 ` Alexander Berntsen
2015-02-14 22:31 ` Ciaran McCreesh
2015-02-14 22:35 ` Andrew Savchenko
2015-02-14 22:40 ` Ciaran McCreesh
2015-02-14 23:10 ` Daniel Campbell
2015-02-14 23:15 ` Ciaran McCreesh
2015-02-15 13:03 ` Andrew Savchenko
2015-02-15 17:30 ` NP Hardass
2015-02-15 17:43 ` Alexey Lapitsky
2015-02-15 19:24 ` Rich Freeman
2015-02-17 9:07 ` Robin H. Johnson
2015-02-14 23:13 ` Andrew Savchenko
2015-02-14 23:19 ` Ciaran McCreesh
2015-02-15 13:02 ` Andrew Savchenko
2015-02-14 23:36 ` Rich Freeman
2015-02-15 12:55 ` Andrew Savchenko
2015-02-15 5:54 ` Michał Górny
2015-02-15 12:45 ` Andrew Savchenko
2015-02-15 2:23 ` Mart Raudsepp
2015-02-15 2:57 ` Ben de Groot
2015-02-15 10:09 ` Markos Chandras
2015-02-15 13:17 ` Dirkjan Ochtman
2015-02-15 9:55 ` Alexey Lapitsky
2015-02-15 12:39 ` Andrew Savchenko
2015-02-15 13:50 ` Michał Górny
2015-02-15 15:05 ` Andrew Savchenko
2015-02-15 15:21 ` Michał Górny
2015-02-15 17:01 ` Anthony G. Basile
2015-02-15 15:27 ` Ciaran McCreesh
2015-02-15 13:03 ` Patrick Lauer
2015-02-15 2:15 ` Matthew Thode
2015-02-15 6:00 ` Michał Górny
2015-02-15 6:20 ` Matthew Thode
2015-02-15 12:29 ` Andrew Savchenko
2015-02-15 2:42 ` hasufell
2015-02-15 4:12 ` Rich Freeman
2015-02-15 12:23 ` Andrew Savchenko
2015-02-16 3:26 ` hasufell [this message]
2015-02-16 11:19 ` Rich Freeman
2015-02-17 6:37 ` Jorge Manuel B. S. Vicetto
2015-02-17 11:55 ` Rich Freeman
2015-02-17 14:01 ` Jorge Manuel B. S. Vicetto
2015-02-18 4:14 ` Dean Stephens
2015-02-18 17:56 ` hasufell
2015-02-18 18:05 ` Matt Turner
2015-02-18 18:47 ` hasufell
2015-02-18 19:19 ` Matt Turner
2015-02-18 22:09 ` Rich Freeman
2015-02-20 21:05 ` hasufell
2015-02-21 0:19 ` Rich Freeman
2015-02-20 4:49 ` Dean Stephens
2015-02-15 6:04 ` Michał Górny
2015-02-15 16:17 ` Anthony G. Basile
2015-02-15 17:42 ` Ciaran McCreesh
2015-02-15 18:39 ` Anthony G. Basile
2015-02-15 19:08 ` Ciaran McCreesh
2015-02-15 19:23 ` Seemant Kulleen
2015-02-16 13:43 ` Anthony G. Basile
2015-02-16 22:14 ` Michael Jones
2015-02-17 6:52 ` Jorge Manuel B. S. Vicetto
2015-02-17 14:18 ` Andrew Savchenko
2015-02-18 2:19 ` hasufell
2015-02-16 13:28 ` Anthony G. Basile
2015-02-15 23:24 ` Patrick Lauer
2015-02-16 0:06 ` Rich Freeman
2015-02-17 6:48 ` Jorge Manuel B. S. Vicetto
2015-02-17 9:01 ` Robin H. Johnson
2015-02-17 12:10 ` Rich Freeman
2015-02-18 3:47 ` [gentoo-project] Infra Kickstarter? Robin H. Johnson
2015-02-18 13:30 ` Pavlos Ratis
2015-02-19 0:31 ` Andreas K. Huettel
2015-02-19 12:16 ` vivo75
2015-02-26 8:38 ` Patrick Lauer
2015-02-15 11:06 ` [gentoo-project] Gentoo, GitHub, and the Social Contract Amadeusz Żołnowski
2015-02-15 12:18 ` Andrew Savchenko
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=54E16381.8020409@gentoo.org \
--to=hasufell@gentoo.org \
--cc=gentoo-project@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