Hi,
we previously used Subversion where it was common to put all
subprojects in the same repository because you could easily checkout
subtrees with only that subproject you were working on.
With Git, the common workflow is slightly different as Git doesn't
really allow so called "narrow" clones and you always need to checkout
the whole project.
If I look at
https://github.com/amora/amora as well as
https://github.com/amora/amora/tree/master/amora-server and
https://github.com/amora/amora/tree/master/amora-client we do have
between three and five sub projects:
* artwork
* amora-client
+ maemo
+ pys60
* amora-server
+ amora-applet
+ amora-cli
Adenilson also talked about clients for further platforms. (And I'd be
happy to see a SailfishOS client for my Jolla. :-)
From my gut feeling, I'd say amora-client's subsubprojects don't have
much in common (except maybe artwork) while amora-server's
subsubprojects do have quite a lot in common. So I'd split up the
former, but keep the latter together.
To split the repos up, I'd keep the full history and then remove
anything no more needed for each repo and move the according
subdirectory's contents to the root directory.
Splitting up into separate repositories though raises the question of
how split up the issues at
https://github.com/amora/amora/issues
I still have one of my export tries as github repos which has the full
set of issues, too. So we could misuse that, force-push the current
git repo and use that for e.g. amora-server while we rename amora to
amora-client.
artwork probably doesn't have any issues and could be pushed into a
new separate repo.
What's your opinion on that? Does that make sense? Or do you rather
think it rather makes stuff more complicated?
Kind regards, Axel
--
/~\ Plain Text Ribbon Campaign | Axel Beckert
\ / Say No to HTML in E-Mail and News |
a...@deuxchevaux.org (Mail)
X See
http://www.nonhtmlmail.org/campaign.html |
a...@noone.org (Mail+Jabber)
/ \ I love long mails:
http://email.is-not-s.ms/ |
http://abe.noone.org/ (Web)