Em 02-05-2011 06:24, Christian Johansen escreveu:

    Hi, I think I'll start to have some free time at night and on
    weekends. I'd love to help since I would love to have both
    Gitorious and Redmine/ChiliProject running on Rails 3. Actually I
    would like both to be mountable apps so that I could use Redmine
    or ChiliProject as issue management integrated to Gitorious, but
    before moving to Rails 3.1, we should better go against 3.0 first.
    Baby steps. Or should I say child steps? ;)

    So, it would be great if we could set some way that we could
    contribute to each other while converting Gitorious to Rails 3.
    Any guidelines?


Rodrigo,

This is awesome news! I suggest that we create an official Rails 3 branch under the Gitorious mainline repo, and you can clone that (in fact, I already did: https://gitorious.org/gitorious/mainline/commits/rails-3.0). The biggest challenge will be porting the routing, but this may be possible to simplify. For instance, today we serve group repositories over URLs like /+group/project/repository. In the future, this link should probably still resolve, but for generating links on Gitorious, /project/repository will be sufficient. Not having to generate links to e.g. group repositories might make the routing porting simpler.

Great! I'll understand this better when I start working on it ;) For me it is just all news at the mean time.
August Lilleaas started work on this when Rails 3.0 was still in beta. You can review his work here: https://gitorious.org/gitorious/mainline/commits/rails3 (I'll rename this branch later to avoid confusion). As per August himself, this is a good reference for the porting job, but due to the ever-changing Rails (at the time) it is probably not a project to continue working on - the branch is also not at all in sync with master. But I think you should find some help for the routing stuff there.

Ok, I'll take a look on this commits as I advance on the refactoring.

Best regards,

Rodrigo.

--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

Reply via email to