Proposed DanielMD License for Review.
im-thinking at clix.pt
Tue Aug 28 12:08:14 UTC 2001
After i read your comment's (mailing list members) and my post again, i
realized that i was trying to oblige people to do something that is suppose
to flourish naturally. If the program is used and becomes popular, people
will want their names in the developers page and will add themselfs to the
mailing list, a community will be created its the logic evolutionary step.
In Resume what i want is this, I created the program, and want to make the
source code/bin/docs available to others to change as they please, they can
use them as they want, and make compilations (A work that is a compilation
of existing new and derivative works - from the OpenBSD site).
I want the developers to hack as they please, and use the code or part's of
the code in other Open Source licensed applications, basically let the code
What i DON'T want, is to have 100 completely incompatible distributions
that will retard the development and evolution of the code, and latter will
lead to the hard task of standardization like in the case of the Linux OS
undergoing right now (http://news.cnet.com/news/0-1003-200-6445478.html).
I will give an example of what i want people to do and what i don't want
people to do, and oblige them under licensing terms not to do it.
Let's say i released the code of ProgramX and, developerX, sees the code,
likes the program, but needs/wants to add a feature, i want him to be able
to add that feature, and optionally send me the feature to include in the
Official ProgramX Distribution, if i see that it's a public interest
feature i will add it to the Official ProgramX Distribution, if i see
otherwise i chose not to include it in the Official Distribution, but i
want him DeveloperX to be able to release his own distribution, with the
added word's ProgramX Hacked Distribution.
For example, DeveloperX send's me a suite of features, that he uses, like
random special effect's wend the initial splash screen start's or end's, i
want to be able to say to him, Look this is very cool, but it will increase
the size of the code immensely so i will not include it on the Official
ProgramX distribution, but you can create a Hacked Distribution.
Resume: You can Hack the Code, and Create your Distribution, but First you
have to send a RFC to (the malling list ) with the hacked code, so that
(the development team ) has the opportunity to put it the Official
Distribution, if it's in the official distribution, there will be no need
to create more distributions, and Standardization will not be a problem.
Resuming even more: Hack IT, Send IT For Comment, Approved and Polished for
standardization issues (included in the Official Distribution), Not
Approved (you can create your own Hacked Distribution).
I DON'T Think that software can be more free that THIS, without
compromising development evolution and standardization.
I have composed a proposal, it's a mesh of the MIT license, Apache, and
some costume conditions, that i think will do the trick.
Proposed DanielMD License for kind review from the [license
-discuss at opensource.org] mailing list
Copyright (c) 2001, DanielMD
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
1. The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
2. The end-user documentation included with the redistribution, if any,
must include the following acknowledgment:
"This product includes software developed by the ProgramX Development
Alternately, this acknowledgment may appear in the software itself, if and
wherever such third-party acknowledgments normally appear.
3. The names "ProgramX" and "ProgramX Development Team" must not be used to
endorse or promote products derived from this software without prior
written permission. For written permission, please contact
authors at ProgramX.org.
4. Products derived from this software may not be called "ProgramX", nor
may "ProgramX" appear in their name, without prior written permission of
the ProgramX Development Team.
5. Distributions derived from this software, must include the suffix
"Hacked Distribution", and should not be published, without prior written
permission of the ProgramX Development Team.
6. Any modifications to the code, may be submitted to the ProgramX mailing
list, in the form of a RFC (Request For Comment) for inclusion in the
Official ProgramX Distribution, the modifier has the right not to do so if
he wishes, and create his personal Distribution under the terms of
7. Sublicensing this software is not allowed without without prior written
permission of the ProgramX Development Team.
8. In case of death of the original author or lack of maintenance for a
period no less than 2 years, ProgramX source code and documentation,
becomes Public Domain.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
Thank you for you time and have a nice day.
More information about the License-discuss