>*Should a non profit foundation be established and all or some control 
be transferred to it?  Should copyrights be >transferred too?*
*
*
I served on the Plone Foundation board for 3 years, and I'm very familiar 
with the benefits of transferring the copyright/trademark to a non-profit 
foundation. I can say that it helped with receiving donations/grants and 
strengthening the community as well as reducing risk. 
http://plone.org/foundation

We had a lot of support from Eben Moglen, the general counsel for the FSF, 
and here you can read the conservancy proposal:
http://plone.org/foundation/materials/archive/proposals/conservancy/
http://plone.org/foundation/materials/archive/conservancy

Nate

On Thursday, August 30, 2012 1:23:18 AM UTC-4, Roberto Rosario wrote:
>
> All that has happened in the past 60 hours or so including the results 
> have show that Mayan EDMS the code, and Mayan EDMS the project, have broken 
> through any initial expectations of growth, market penetration, acceptance 
> or any idea I or anyone else may have had from the day it was started or 
> the day it was released one and a half years ago.  I also think this is an 
> important pivotal point and the good time to make changes if there is the 
> need for them to ensure the continued growth and future of the project.
>
> I value everyone's opinion and take them into account and the people in 
> this mailing list are the oldest supporters of the project so your opinions 
> are specially important and helpful during this process as have been since 
> the beginning of the project itself.
>
> I would like everyone to chime in if they can on the following topics (or 
> any other you want to bring out):
>
> - Should Mayan EDMS be licensed under another Open Source license (BSD, 
> MIT, Apache, other)?  A non Free license?
> - Should it remain Free Software or move to a full commercial product.
> - Should a new specific license be crafted for it (ie: Mayan EDMS Shared 
> Source License or something like that)
> - Should the development branch remain open, closed, or shared on a case 
> by case basis?
> - Should the release strategy remain the same or should there be 
> a deferred model of a commercial release and have that same version become 
> the latest Free Open Source version a period after that (6 month a a year?) 
> to benefit both commercial and non-commercial users? 
>  Another completely different release strategy?
> - Should there continue to be only one version of the Source Code or 
> should there be a commercial and a community version?
> - Should there be a completely different release strategy?
> - Is the current release cycle adequate?  Or Too slow?  Too fast?
> - Should a non profit foundation be established and all or some control 
> be transferred to it?  Should copyrights be transferred too?
> - Is the software/project transparent enough or too much?
> - Is the new licensing plan proposed (GPL, Redistribution, Commercial and 
> Developer) adequate, too complicated or too limited?
>
> """
>
>    - ** GPL ** – You can install *Mayan EDMS* as is, but can sell your 
>    services for *Mayan EDMS*, you must provide the source code or 
>    directions where to get the source code to your clients, modifications to 
>    the source code must be made public.
>    - ** Redistribution ** - You can sell *Mayan EDMS* as well as your 
>    services, you can modify *Mayan EDMS* adding new features or changing 
>    the name and you can keep your changes closed.
>    - ** Commercial ** – Same as *GPL* but includes email and telephone 
>    support for a number of hours per month.
>    - ** Developer ** – Allows you to use *Mayan EDMS* to create a new 
>    product using all or parts of the source code and allows you to sell your 
>    new product independently.
>    - """
>
> Any other topic regarding but not limited to code hosting (github, etc), 
> the current website hosting, website design or anything else is also most 
> welcomed.
>
> Feel free to post or to continue emailing me in private as most have done, 
> any method is perfectly fine.  Thank you very much,
>
> --Robert
>
>

-- 



Reply via email to