-1 for allowing non-ASL licensed code into the repository.
The goal of the repository should be twofold:
1) provide a central venue for communal development
2) facilitate introduction of developers to the Habari and allow them
to prove their worth
The Habari community and project have officially endorsed ASL as its
license of choice. By allowing communal development (1) under a
different license, we are in conflict with that choice. Additionally,
allowing GPL code could potentially make things more difficult if we
want to integrate it as a core plugin. Additionally, we should be
introducing developers to the ASL as part of (2).
However, we definitely should have a distribution directory which
allows any and all plugins/themes. The function of this directory is
to point people to Habari plugins, which does not conflict with
pointing people to GPL plugins.
~Arthus
On Dec 3, 2008, at 11:15 PM, Owen Winkler wrote:
>
> Chris J. Davis wrote:
>>
>> For the record I am in favor of option 1. We need a centralized
>> location
>> for plugins and themes, and providing that for the community is a
>> good
>> thing, and serves our participation model.
>
> The plugin and theme directory is a fine place to centralize
> distribution, and may link to GPL-licensed projects and code that is
> off-site.
>
> Our participation model only works for us if our contributors are
> submitting code that can be used in our project. If only for this
> reason and none of the myriad of others, the repositories that our
> project maintains should only house ASL-compatible code.
>
> -1 for leaving our repository open to include potentially tainting
> code.
>
> Owen
>
> >
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---
