On Wed, Oct 12, 2011 at 6:03 AM, Shmuel Fomberg <[email protected]> wrote: > Hi all. > You may or may not work, but now I work for Six Apart, on Movable Type. > Now, there is the company, but also the a community, that maintain a fork > (called Open Melody) of the previous major version. > Sometimes that people submit a pull request, with useful patches. and that > is good. > but on the other side, in the company we have release cycles. > (planning-implementing-testing-release) > it means that when a patch comes, it probably won't enter to the upcoming > release, and we can not even tell when it will added to the product until it > actually marked in some release for inclusion. > so practically the submitter is getting a "thank for your patch. it will be > integrated sometime in the future" massage, and I think that this is very > discouraging for them. > but I don't know how to fix that. > And ideas? > Shmuel.
I think the only solution is to change the license of Movable Type back to some open source license. That probably won't happen. Even that might not help as I guess Google has the same problem with Android. That is "open source" but I think they develop it in an internal branch and only after it is finished and released to the mobile companies, only then they publish the source openly. So external developers are kept in the dark. Having an open source license is not enough. You need to have an open source development model. And even that might not encourage a lot of contribution if the release cycle is long and/or unpredictable. Gabor _______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
