Some rubyforge projects release more than one sequence of gems. The gems might be related in operation or purpose, but
not related in implementation, so it is awkward to have only one git repos for the project. An alternative is to use
github, but rubyforge's scm pages don't have a way to explain to the user where to go to find these other scms.

IMO the best solution, if it is not too hard, would be to allow several git repos per project. Otherwise, it would be
nice at least to be able to list on the SCM page the other repos urls.

Thanks!

Date: 2009-09-16 13:19
Sender: Tom Copeland

Some more discussion btwn me and 7rans:

==========
From example.conf in the gitosis repo:

 [group quux]
 members = jdoe wsmith @anothergroup
 writable = foo bar baz/thud
 readonly = xyzzy

And further down:

 [repo foo]
 gitweb = yes
 description = blah blah
 owner = John Doe
 daemon = yes

I don't know very much about gitosis but if I were to hanker
a guess:

 [group actiontimer]
 writable = actiontimer/actiontimer actiontimer/foopackage
 members = spox@rubyforge.org

or

 [group actiontimer]
 writable = actiontimer actiontimer-foopackage
 members = spox@rubyforge.org

The former is probably better, but means current git addresses
might
change. While the later preserves current addresses, but you
have to
deal with "-" separation and exception for the main
repo. But then
again I could be totally wrong about this since I'm not exactly
sure
how all this (GForge + Gitosis) fits together.

I take it though that you'd tie in this configuration to the
File
package section of the site? Ie. adding a package, adds
a "writable"?

Perhaps there is a gitosis forum you can drop the question on.
==========

Date: 2009-08-17 14:35
Sender: 7rans 

One thought... Make each subproject it's own git repo inside
a master directory which is also a git repo. Git ignores the
.git directory in subdirs (you can not add these files even if
you try explicitly). But we could trick it, if we rename the
.git directory. So we would have:

  superproj/
    .git/
    subproj1/
      .gitsub
    subproj2/
      .gitsub

When working on a subproject, we first rename .gitsub to .git,
do our work and then when finished rename it back so the master
git repo with track it. It's an added step but could work.

At the top level we just mass commit the whole as needed. I know
it seems crazy to double track the repos, but I don't see another
way.

Perhaps some porcelain could be made to automate this procedure?

Thoughts?

Date: 2009-08-06 13:57
Sender: Tom Copeland

Hi Joel -

Thanks for the feedback.  Yeah, that would be handy... although,
do you know if gitosis supports multiple git repos per project?
I can dig around a bit.

Also, I'm kind of tied up in the RubyForge REST API stuff at
the moment:

http://rubyforge.org/forum/forum.php?thread_id=45101&forum_id
=32738

But let's definitely keep this on the TODO list.

Yours,

tom