Hi Gabor. On Wed, Oct 12, 2011 at 2:07 PM, Gabor Szabo <[email protected]> wrote:
> On Wed, Oct 12, 2011 at 6:03 AM, Shmuel Fomberg <[email protected]> > wrote: > > 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. > > I think the only solution is to change the license of Movable Type > back to some open source license. That probably won't happen. > > I really don't see how it is related to the license. > 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. > > We generally develop in the open. for example, you can go to: https://github.com/movabletype/movabletype/tree/develop and see what I did today. (except when we work on security bugs) Our bug-tracker is also open to the public. > 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. > > What is 'open source development model'? Also, we release every three months, more or less. but again, if a patch just missed the planning of a release, it will have to wait a long time for inclusion and release... Shmuel.
_______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
