If you take a open source proyect, and develop another open source
proyect based on it, you are forking. You must continue with the same
license the original authors used. This is a must, if you can't
convince all the original authors to allow you to use a different
license (hard if theres a lot of then, easy if theres only one).
Forking is fun, but heres a caveat: the original proyect may go faster
and develop features you may need, but you cant have in your fork.
Forking is a good idea if you want to follow different guidelines, not
a good idea if you have the same ideas of the original authors.
Forking is sometimes obligatory wen the original authors are stubborn
and too slow to update a proyect. Sometimes forking is a good idea if
the original proyect is poisoned by bloat, and you want to use a axe
and remove all the complexity (perhaps that was the case of firefox?).
Normally is not a good ideas, and all open source projects have
smarted up and include most features in "plugins", so the core is
small, not bloated, and flexible for everyone need.
On 29 December 2011 07:31, Sajith Vimukthi <sajith.vim(a)gmail.com> wrote:
Hello All,
I am planning to develop a new Open Source project keeping mediawiki as the
baseline. I wonder how the liciening policy of mediawiki will affect my
intention. Could somebody help me on whether it is possible to develop my
own app using mediawiki and distribute it as an opensource project?
Thanks,
Regards,
Sajith Vimukthi Weerakoon,
T .P No : ++94-716102392
++94-727102392
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
--
ℱin del ℳensaje.