You will need to explain because I don't understand what you mean by centralized vs distributed , does not support working at the right granularity.
Influence the way Github goes is besides the point at this point since we dont have a better alternative and I will be a great oracle to predict , or not, that we wont have one in the next decade. Unless something extraordinary happens and Pharo goes super popular. Being a commercial application has not stopped tons of open source projects porting to it. But hey what do they know. I am not sure what you mean about sourceforge, I see still loads of open source project using it. The thing I see right now, is that I already use Github with Filetree and Monticello-GIT and it works. Can see the commits I made manually to git and create git commits. The only thing it does not do is push though thats also pretty much a matter of adding the code. So it looks like monticello is already there. It could be polished and sophisticated git interaction be integrated but I think with time we will see those things as well hopefully I can give a helping hand. And if Git is good enough to version control Linux source, I dont see why it would be a big problem to Pharo. But even if it is should not be faster if we make extensions to git via monticello to work around these potential problems instead of doing a huge project from scratch ? I will keep trying Monticello-GIT , if it works as well it seems to work I will probably stick with it. I would love also to extend it when I become familiar with its internals. Big thanks to people behind this. I think being against git is perfectly fine, wanting to trying your own thing is awesome, focusing on pharo specific solution is of course a good thing. But then not wanting to do that and use what is already out there can be as wise. On Sun, Nov 3, 2013 at 4:52 PM, Stephan Eggermont <step...@stack.nl> wrote: > Kilon wrote > >I take a look at previous experiments like squeaksource and I find little > justification to not support Github. But then I am not against Smalltalkhub > or other >repos being available to Pharo. The more the merrier. > > I see some very strong arguments against depending on github: > - it is centralized infrastructure, essentially unsuitable for use with a > distributed version control system; > - it doesn’t support working at the right granularity; > - the smalltalk community is too small to have any influence on the > directions github is taking. > It is a commercial organization that can decide to do something we don’t > like at any time. > It is free, so we are the product. Just take a look at sourceforge; > - we can do much better than github (but don’t have enough time). We > should be using a P2P, > bittorrent like system for version control. > > Stephan > > > >
