I would think forks with pull requests would be quite sufficient to maintain such a "core" repository. Alternatively, you could create a "dirty" branch, but then the problem still remains how to propagate commits (without adding tons of collaborators).
And really, there's very little "inefficiency" in forking a repo on Github. It's practically trivial, compared to saurian VCSes such as SVN and CVS (shudder). It really doesn't get any simpler than forks and pull requests (for both you and the contributors). ~ Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
