List Archive: gentoo-trustees
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Tue, 2005-09-20 at 11:49 -0500, Grant Goodyear wrote:
> > From: Seemant Kulleen <email@example.com>
> > How does this agreement play to things like that? If eselect goes on
> > (and based on its technical merits, there is every reason that it
> > should) to become the default tool in gentoo, then where does that leave
> > us? I'm with Grant on this: I'm not convinced.
> Unsurprisingly, eselect was exactly what I was thinking about when I
> raised that question.
The other thing is that only code written after the agreement is signed
This would mean that if eselect were to become and official project and
it was decided that all official projects needed to have the protection
of the foundation that any code written from that point forward would be
covered under the agreement, not the code that came before. For a
project as robust as eselect that would mean that until a fair few
revisions happened most of the code would only be copyrighted to the
I also believe that it should be up to the individual project whether
they want to have their code protected. However, it is, (and I feel like
a broken record here) an all or nothing deal for that project. Having
only a few members of a project sign is futile. I'm just saying that I
feel that copyright protection and official status should go hand in
hand. I have no problem with the code being hosted on our infra, I do
have a problem marking the code as official Gentoo code and having no
way to protect it.
Gentoo Foundation Board of Trustees
firstname.lastname@example.org mailing list