On 13 January 2018 at 20:57, Benoit St-Jean via Pharo-dev <[email protected]> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <[email protected]> > To: Pharo Development List <[email protected]> > Cc: > Bcc: > Date: Sat, 13 Jan 2018 12:57:00 +0000 (UTC) > Subject: Re: [Pharo-dev] Blame support P7 >> So what would be the alternative? > > A centralized server (e.g. Cincom Public Repository, SqueakSource, > SmalltalkHub, SqueakSource 3). After that, all you need is a detailed > project/package/framework description. Google will index it. > > The whole "GitHub adventure" was started on the premise that it would give > Pharo more visibility.
>From what I remember of mail list discussions, the primary reason to move to github, which was reducing the need for a 24x7 operations team to support our code repository servers. http://forum.world.st/SmalltalkHub-bugs-hangs-tp4792551p4792598.html There was an argument that support effort would make the servers more reliable, but it seems both SqueakSource3 and Smalltalkhub were started in response to SqueakSource issues at some time. So ti still seems reasonable to make use of these 3rd party maintained VCS services. > > Besides, Smalltalk code on GitHub leaves a very bad impression on newcomers. > I was recently told "I just gave up on Smalltalk when I saw 200+ files"... > It was too late. I told the poor guy it was just the way code was *stored* > on GitHub but in your dev environment, everything resides in the image... > Too late : I had lost him solely based on the impression that he was entering > into a code management nightmare worse than a thousand C header files! Which repo was that? Was it before/after Tonel? > In the current state of things, the whole Cuis/Pharo/Squeak world is a mess. > Newcomers looking for code end up having to pick between a myriad of links to > SqueakMap, catalogs, SqueakSource, SmalltalkHub, SS3, GitHub, sar files, mcz > files, fileOuts, etc. > Wouldn't it be nice to have a centralized server with Cuis, Pharo, Squeak > (and/or others such as VW, VAST, Dolphin) and share a common import/export > format (SIXX, Smalltalk Instance eXchange in XML, would be a good start and > would probably do a decent job) Yes, but please not XML. JSON like would be much nicer, where Tonel could be a good option. cheers -ben
