2011/12/21 Garrett Serack <garre...@microsoft.com>: > So the consensus is to take snapshots, not import history. > I'm really good with that.
Yes. Just maintain snapshots of packaged project + history of CoApp-specific changes. > (since it really means that anything > we're dealing with is 1 fork = (1 snapshot of a foreign source > tree/tag/branch). By default, it single fork in https://github.com/coapp-packages will be used, indeed. So, upstream of shall forks lives in coapp-packages Obviously, everyone can fork such shallow fork and experiment more with a package Then send pull request to submit changes into the shallow fork upstream Best regards, -- Mateusz Loskot, http://mateusz.loskot.net _______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
