Hi, Thanks for the suggestion. I am happy you are excited about the promise of GitHub.
The only thing left to do is to make it happen, and I kindly invite you to join the others interested in precisely making it happen. Just send a message around showing your availability to code in this direction, and I am sure that people will point you to what is left to do. Doru On Sat, Nov 2, 2013 at 2:21 PM, kilon alios <kilon.al...@gmail.com> wrote: > and its alive again ! > > If anyone cares about my personal opinion, and I hope not many people do , > I think it would be better for Pharoers to embrace Github. Not because > smalltalkhub is more prone to crashes , not because it has much less > features, but because of the amount of exposer it can give to our > community. > > I think that if more and more Github users, and there are tons of them out > there, starting seeing Pharo project popping around like mushrooms , they > may ask the question "What the hell is Pharo" and maybe just maybe this > bring more people to our side that may try Pharo , love it and want to help > us make it more awesome. > > So if we could make committing to Gihub as convenient as committing to > Smalltalkhub then its a matter of porting projects to it. Imagine what > would happen if one of those great smalltalkhub projects became the project > of the month for Github. > > > On Sat, Nov 2, 2013 at 1:36 PM, Sven Van Caekenberghe <s...@stfx.eu>wrote: > >> >> On 02 Nov 2013, at 12:23, Johan Brichau <jo...@inceptive.be> wrote: >> >> > >> >> On 02 Nov 2013, at 05:51, Marcus Denker <marcus.den...@inria.fr> >> wrote: >> >> >> >> Something is fundamentally wrong here. >> > >> > Yes. And it is hurting the trust people have in smalltalkhub. This is >> not the way to promote the community either. >> > >> > I hope there are at least monitoring and auto-restart services running! >> > >> > Johan >> >> I suspect that the problem is that a database (Mongo DB) is involved so >> that before each (potentially automatic) restart a human has to make sure >> that the database is not corrupt. If the application/webapp and the DB are >> really very well separated then that should be less of a problem. >> >> That being said, the situation should definitively be improved ;-) >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"
