Conversation:
Notices
-
@roland I've made sure it has a working repository listed. Not sure what more I can do besides mailing them.
@aqeel - as "con"? What does that mean and how do we fix it? :)
-
I don't like #GitHub. And now that I read about their take on Git 2.3 I notice interesting comments: "Your server will contain a .git directory containing the entire history of your project. You probably want to make extra sure that it cannot be served to users!". Bah! And their site encourages people to share code? Given the #AGPL license of !gnusocial for example we…
-
https://gitorious.org/ - even licensed AGPL and hosting several large projects already :)
Since git is decentralized, the least people can do is to start a mirror repository on another server. In !gnusocial's case @mattl has set up a mirror on #github but our main repo (where merge requests are accepted) is on #Gitorious.
-
I'm not a huge fan of it myself. Two things are true though: people look at GitHub for code, and GitHub makes it easy to see dev progress.
-
I'm not sure why https://www.openhub.net/p/gnusocial has stopped updating (since they stopped being ohloh.net). That's otherwise a pretty neat development visualizer.
-
@aqeel Oh wait you meant the #GitHub statement. Yeah, that "the entire history is available" is apparently a "con" according to those secrecy lovers even though just about everyone who uses their servers are encouraged to publish projects with forkable licenses. But obviously not because it's a good and obvious thing - only because they want to hog all the FLOSS developers.