+ [2014-07-10T23:11:34Z] VxJasonxV wikis are descendents of main repositories
+ [2014-07-10T23:48:25Z] jxport hey
+ [2014-07-10T23:49:07Z] jxport I'm looking to apply SemVer to a new project I'm starting. It seems that with every change though, I'm going to eventually get 0.9001.0 - how can I avoid this?
+ [2014-07-10T23:49:48Z] jxport Without lumping lots of changes into big, irregular releases, it seems as though the minor version will go through the roof pretty quickly, in this early stage of development
+ [2014-07-10T23:54:42Z] andyleap Question, would a repo that has a license that doesn't allow redistribution of the compiled source code still qualify as a repo that is allowed to be forked?

message no. 28638

Posted by andyleap in #github at 2014-07-10T23:54:42Z

Question, would a repo that has a license that doesn't allow redistribution of the compiled source code still qualify as a repo that is allowed to be forked?
+ [2014-07-11T00:01:16Z] VxJasonxV jxport: git shas
+ [2014-07-11T00:01:32Z] VxJasonxV version numbers are for releases, git shas are for changes
+ [2014-07-11T00:01:38Z] VxJasonxV don't marry the two
+ [2014-07-11T00:02:00Z] VxJasonxV andyleap: are the repository's contents compiled source code?
+ [2014-07-11T00:02:26Z] VxJasonxV jxport: to expand on that thought. if you're going to get to release version 0.9001, you shouldn't be releasing