Talk:Git For Garage
(→git.maemo.org without garage project) |
(→Centralized view of all the projects hosted in git.maemo.org) |
||
| Line 15: | Line 15: | ||
::MXR supports git, so it can index git repos just as easily as it indexes svn repos ([http://mxr.maemo.org/garage mxr]). the only issue is again knowing when new gits (or svns) are created. [[User:timeless|timeless]] 12:41, 1 December 2008 (UTC) | ::MXR supports git, so it can index git repos just as easily as it indexes svn repos ([http://mxr.maemo.org/garage mxr]). the only issue is again knowing when new gits (or svns) are created. [[User:timeless|timeless]] 12:41, 1 December 2008 (UTC) | ||
| + | :::Create an interface and GForge will send the info whenever such event is triggered. --[[User:feri|feri]] 13:03, 1 December 2008 (UTC)feri | ||
== Any way to distinguish the Nokia projects? == | == Any way to distinguish the Nokia projects? == | ||
Revision as of 13:03, 1 December 2008
git.maemo.org without garage project
A project should be able to use git.maemo.org without having to create a garage project. This is specially true for the Nokia teams and releases. For instance, some teams might think of using git.maemo.org as default platform for development and send the packages to the Maemo SW integration from there. Having a maemo.org account (= "garage account") is fine. Is this possibility being contemplated?--qgil 10:25, 1 December 2008 (UTC)
- Yes, it is possible. However the starting point for creating a git repository was planned to be at garage. I have to re-think the setup if a project does not need to have a garage entry first. We should remember that having a garage project does not mean that we have to utilize all the GForge features. Every project can disable any GForge module, so a Nokia project may just use garage for account management and SCM (source code management) purposes. All other modules, like tracker, forum, lists would be disabled.--feri 10:50, 1 December 2008 (UTC)
- Still, if we are talking about hundreds of components in the Maemo platform... There is really no point opening hundreds of garage projects because of that.--qgil 12:14, 1 December 2008 (UTC)
- How would those projects like to handle the account management? Garage offers the framework. If we go to a custom solution then we will end up where we started in 2005 with the subversion repositories. The solution for adding new users and granting access to repositories for svn still works today, so nothing against it, but it is more difficult to maintain then garage. Garage can easily handle a few hundred more projects. We may move the stuff to one or more dedicated server once, but this move should be anyway done next year. --feri 12:22, 1 December 2008 (UTC)
- Can a garage project inherit permissions from another garage project? If I run 10 projects, I don't want to have to grant the same permissions to each one, and it's likely that I could run projects in such a configuration (10 distinct things that should be tracked, but the same engineers working across them). I've seen people try to use trac for this purpose, and it's pretty much a disaster timeless 12:44, 1 December 2008 (UTC)
- There is no such feature in GForge by default, but I could add it. --feri 13:02, 1 December 2008 (UTC)
- Can a garage project inherit permissions from another garage project? If I run 10 projects, I don't want to have to grant the same permissions to each one, and it's likely that I could run projects in such a configuration (10 distinct things that should be tracked, but the same engineers working across them). I've seen people try to use trac for this purpose, and it's pretty much a disaster timeless 12:44, 1 December 2008 (UTC)
- How would those projects like to handle the account management? Garage offers the framework. If we go to a custom solution then we will end up where we started in 2005 with the subversion repositories. The solution for adding new users and granting access to repositories for svn still works today, so nothing against it, but it is more difficult to maintain then garage. Garage can easily handle a few hundred more projects. We may move the stuff to one or more dedicated server once, but this move should be anyway done next year. --feri 12:22, 1 December 2008 (UTC)
- Still, if we are talking about hundreds of components in the Maemo platform... There is really no point opening hundreds of garage projects because of that.--qgil 12:14, 1 December 2008 (UTC)
Centralized view of all the projects hosted in git.maemo.org
Just to make sure: will it be possible to browse all the projects hosted in git.maemo.org from a centralized location? A problem with svn at garage is that you have to go project by project to know what is in there.--qgil 10:25, 1 December 2008 (UTC)
- Yes, it will be possible. --feri 10:50, 1 December 2008 (UTC)
- MXR supports git, so it can index git repos just as easily as it indexes svn repos (mxr). the only issue is again knowing when new gits (or svns) are created. timeless 12:41, 1 December 2008 (UTC)
- Create an interface and GForge will send the info whenever such event is triggered. --feri 13:03, 1 December 2008 (UTC)feri
- MXR supports git, so it can index git repos just as easily as it indexes svn repos (mxr). the only issue is again knowing when new gits (or svns) are created. timeless 12:41, 1 December 2008 (UTC)
Any way to distinguish the Nokia projects?
Would it be a way to easily distinguish the Nokia projects from the rest? I'm not even sure this is needed or useful, but it might be a useful detail. In the worst case we could create a plain HTML/wiki index somewhere and link the relevant projects from there.--qgil 10:25, 1 December 2008 (UTC)
- At "registration" time (let it be on garage or elsewhere) we can certainly ask a checkbox to be ticked in case of a Nokia project, but the question is where to store this info and how to re-use. If we had the garage entry only than it would not be a problem, since we have this feature already. --feri 10:50, 1 December 2008 (UTC)