I can't even make a comment on an issue without it being held in moderation.
Kenneth Reitz http://kennethreitz.com/contact-me On Tue, Sep 28, 2010 at 6:59 PM, Kenneth Reitz <[email protected]> wrote: > On Tue, Sep 28, 2010 at 6:25 PM, Giovanni Bajo <[email protected]> wrote: > >> On mar, 2010-09-28 at 14:52 -0400, Kenneth Reitz wrote: >> > I managed to get this fixed. >> >> How? >> >> > http://www.pyinstaller.org/ticket/152 > > > >> > I have to admit, I'm extremely disappointed in the way this project is >> > managed. This is literally the slowest moving project I've ever seen. >> >> All contributions are made by volunteers in spare time. It is very rare >> to be paid for custom PyInstaller development. The development is made >> in the public so anybody can join. > > > I am very well aware that this project is a free, open-source, project. > And, it is by far the slowest moving open source project I've encountered in > years. This project has enormous potential, yes goes by mainly unnoticed. > This is mainly due to the poor documentation. > > >> > Has anyone considered putting the project up on GitHub? >> >> Changing the infrastructure will not make more development happen, and >> will drain resources in the migration. >> > > Managing the repository on GitHub could foster tremendous growth. Anyone > could fork the repository, edit the wiki, make contributions, raise issues, > and send pull requests within a matter of moments. It would take 4 minutes > to 'migrate' the repository (it literally took me 4 minutes: > http://github.com/kennethreitz/pyinstaller). > >> >> > > Submitting diffs to a forum is extremely 1998. >> >> We have a trac instance to track patches. This said, if people want to >> post patches in the mailing-list, they are still welcome. It's still >> much more helpful than getting a random complaint. >> >> Open source projects are no longer managed by people passing around diffs > and patches to mailing lists and trac instances. We did that in 1998. Now we > have distributed source control, which allows you to send a reference to an > actual (set of) commits. Patches are what is causing this project to drag > behind. Someone submitted a patch to add Python 2.7 support a MONTH ago and > it STILL isn't merged in? This should have taken mere moments. > > >> -- >> >> Giovanni Bajo :: Develer S.r.l. >> [email protected] :: http://www.develer.com >> >> Blog: http://giovanni.bajo.it >> Last post: Compile-time Function Execution in D >> >> -- >> You received this message because you are subscribed to the Google Groups >> "PyInstaller" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<pyinstaller%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/pyinstaller?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
