If you really want to embrace Github , kill Smalltalkhub. Smalltalkhub should have been dead years ago. Its unmaintained anyway apart from when it crashes and Esteban fixes. Smalltalkhub has been a constant state from crashes since 2011 when I joined Pharo community.
Give people a month to move their projects in github and then kill it. At worst give only read access the same way squeakers made the old squeaksource read only. Another thing that must be fixed is the file format chosen for git, the idea to fragment source code to a billion diffirent source code files each one containing a method or class definition is problematic both for viewing those files offline and online. There is very little chance that if I give a link to my github repo to an outsider to take a look at my code that he will have the patience to navigate 10 files to read the code for 10 methods. Even the class comment is a separate file. I don't even have the patience to do that. Make an organisation for people to join, those are made inside github we have one for the books we have none for the community , this way we can gain easier visibility of source code and it will also make easier for people to contribute to third party code. Move the meta repos of Pharo to Github and remove "meta" from the name. Instead name them Pharo Packages Catalog as we do inside the image. One repo for all versions of Pharo. Branches can be used to separate versions. Add to Playground the ability to paste code directly to Gist. This is a low priority one but its a nice touch. A biggy one is the pharo repo of the pharo image on github. Its a mess. https://github.com/pharo-project/pharo-core/commits/6.0 seriously, Github makes us visible , this does not look good at all. If you do all the above you will have reduced the pain of working with Git by 80%. On Sun, Nov 6, 2016 at 4:37 PM stepharo <steph...@free.fr> wrote: > Dimitris > > better reread what I wrote because you missed it. > > My point is let us minimize the mess and act in a concerted way. Do you > think that we would pay 9 months of dev + esteban that will started to > push there too > > and base all our dev on it if we would not believe that moving to git is > stupid! > > Can you read what I write? > > Stef > > > Le 6/11/16 à 13:05, stepharo a écrit : > > Hi > > > > I would like that you think a bit about our community and that there > > is a value in using common tools > > > > to share and develop common libraries. Because to me it feels like we > > are getting balkanize. > > > > > > It may look super cool and be hyper trendy to use github (because like > > that you can say that you use latest hyper cool > > > > features), but I would like to ask especially people building > > libraries to pay attention that it is important > > > > that other people can contribute back easily and that there is an easy > > way to load/contribute. > > > > Today I experienced Bloc > > > > - I cannot load code and I cannot contribute. > > > > - I saw mdl with a mixture between smalltalkhub and github (sounds > > super hyper cool) and I saw paul not being able to contribute :( > > > > > > Yes you can say that monticello sucks yes it is terrible yes we all > > fell like Cobol programmers but at the end of the day. > > > > Yes the herb is always greener elsewhere. Yes yes yes. Let us take > > some facts. > > > > We managed pharo and moose with it over the last 8 years successfully > > and Pharo and moose are not 5 packages together from > > > > what I can see. So pay attention about the decision you take. > > > > Now we will provide git support (this is 8 months that nicolas is > > exclusively working/thinking/dreaming > > > > about that) and that we are doing experiments (Guille is managing the > > bootstrap in github). > > > > Now when everybody will have its own little project lost on github (I > > do not count the amount of time I do not find pillar on github because > > I forget > > > > that it is called pillar-markup), what will we do. > > > > So we need an infrastructure to handle this and christophe is working > > on this. > > > > I think that you should consider the accidental complexity as > > something that we can minimise by using patterns and common practices. > > > > Now you can think that I'm an idiot and that I have no vision (be my > > guest) but we should pay attention because we are a small community. > > > > Stef > > > > > > > > > > > > >
