Hi, > On 5 Oct 2018, at 19:03, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > > Hi monty > > I ****really**** think that we should move to github. > I mean really. Let us use a pro VCS - I do not like much git but > Iceberg improves the > feeling.
It is not just that is a modern vcs tool. I already talked a lot about the technical advantages of using git. But let me put the accent now in some “non technical” reasons: - Imagine if we migrate to github all the projects at sthub, ss, ss3, etc… There are thousands of projects there (yes, many od them are dead code, but is the same about most of the projects on GitHub too): we will be making something to help re-place Smalltalk in the map (is not of course ensured, but is a small contribution to gain a visibility we do not have now. - you know a lot of companies look at the GitHub profiles of applicants these days, to see how they work on open source projects, etc. Which means having GitHub exposure will also help people willing to start with Pharo (or Smalltalk in general) and do not do it because that will not help them to get a job. One important reason why we selected GitHub and not another provider (personally I prefer GitLab, for example) is precisely that: increase visibility and lower the artificial barriers to adopt Pharo.And of course, this is just a small thing among the huge amount of things to do, but that does not means is not an important one. Esteban > > Stef > On Wed, Oct 3, 2018 at 8:28 AM monty <mon...@programmer.net> wrote: >> >> It would also prefer an SS3-based STHub, at least as an alternative to >> GitHub. >> ___ >> montyos.wordpress.com >> >> >>> Sent: Saturday, September 29, 2018 at 6:43 AM >>> From: "Stephane Ducasse" <stepharo.s...@gmail.com> >>> To: "Pharo Development List" <pharo-dev@lists.pharo.org> >>> Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ >>> >>> Hi Sven >>> >>> SmalltalkHub is dying. And we will turn it readonly by January. >>> Esteban has something else to do that to take care of it. It is a legacy. >>> We are about to announce that we cannot create account and projects anymore. >>> We are waiting to do that after the mooc. >>> Now you want to use Squeaksource or SS3 I do not want. >>> I want to use github and I guess that I do not have to explain why for real. >>> >>> Stef >>> >>> On Sat, Sep 29, 2018 at 11:27 AM Sven Van Caekenberghe <s...@stfx.eu> wrote: >>>> >>>> I think that would be monty, email addresses (CC-ed) >>>> >>>> mon...@programmer.net >>>> >>>> I should note that he has been very good at maintaining the XML packages >>>> (the specs of which are super complex), and as far as I know, the code >>>> works under Pharo 7 ... >>>> >>>> What does not work for you ? >>>> >>>> Sven >>>> >>>>> On 29 Sep 2018, at 10:38, Stephane Ducasse <stepharo.s...@gmail.com> >>>>> wrote: >>>>> >>>>> Hi >>>>> >>>>> I contacted the maintainer (but I'm not sure in fact who it is :) ) >>>>> about the XML related packages in Pharo extras. >>>>> >>>>> XMLParser >>>>> XMLParserHTML >>>>> XMLParserStAX >>>>> XMLSupport >>>>> XMLWriter >>>>> XPath >>>>> >>>>> I did not get any answer so may be I sent a mail to the wrong email >>>>> address. >>>>> Probably. >>>>> Now the question still remains: who is planning to migrate the XML >>>>> packages. >>>>> I was planning to do it but I will not consider history because I do >>>>> not know how to do it and I do not have the time to do it (sorry). And >>>>> yes I work the weekends and this is bad and this is not even on Pharo. >>>>> >>>>> I was planning to spend some time on the baseline and making sure that >>>>> we can load everything and run the tests. >>>>> So let me know. >>>>> >>>>> Stef >>>>> >>>> >>>> >>> >>> >> >
