On Fri, Jun 25, 2010 at 8:21 AM, Stéphane Ducasse <stephane.duca...@inria.fr > wrote:
> restart a nice application with a nice model. > Squeaksource was developed literally a couple of days. I remember when they > said monday "wait until friday" :) > What should be in ? I'm thinking of: Important: - fork / merge tracking (like github, so we can contribute to a package even if we don't have write access on main repository) - scriptable API (automate patch integration from PharoInbox, image building) - easy mirroring Would be nice: - documentation integration (automatically display HelpSystem doc. on web page) - issues tracking + project management Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > Stef > > On Jun 25, 2010, at 12:33 AM, Richard Durr wrote: > > > What could such a solution be? > > > > On Thu, Jun 24, 2010 at 7:52 PM, Lukas Renggli <reng...@gmail.com> > wrote: > >> I think it is the time to let squeaksource.com die. After all it > >> served its purpose and made Monticello what it is today: the standard > >> code and versioning system of Smalltalk fully supported by Pharo, > >> Squeak, and GemStone; and partially by Cincom Smalltalk and VA > >> Smalltalk. > >> > >> I doubt that something can rescue squeaksource.com as it is now. Any > >> change means an incredible investment of work and the people that set > >> it up about 7 years ago are moving elsewhere. > >> > >> I think somebody should jump in and provide a much better solution. > >> > >> Lukas > >> > >> On 24 June 2010 14:52, Philippe Marschall > >> <philippe.marsch...@netcetera.ch> wrote: > >>> On 06/24/2010 12:17 PM, Göran Krampe wrote: > >>>> On 06/24/2010 10:04 AM, laurent laffont wrote: > >>>>> What can be done / how can we help / what's needed to improve > >>>>> squeaksource uptime ? > >>>> > >>>> I am not sure how SS is being deployed but one option might be to move > >>>> to another web server as a frontend and use FastCGI or SimpleCGI > >>>> (Blackfoot on SM). > >>> > >>> Believe me when I tell you, the web server is the least of the issues. > >>> What mostly happens are Socket/Semaphore related issues, eg. a thousand > >>> Processes hanging on the same Semaphore. > >>> > >>> What could be done is moving to an up to date image/vm but this is a > bit > >>> of work. > >>> > >>> Cheers > >>> Philippe > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project@lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> > >> -- > >> Lukas Renggli > >> www.lukas-renggli.ch > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project@lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project@lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
