Editing Talk:Git For Garage

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

== 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?--[[User:qgil|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.--[[User:feri|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.--[[User:qgil|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. --[[User:feri|feri]] 12:22, 1 December 2008 (UTC)
::::I imagine git.maemo.org similarly to http://git.collabora.co.uk/ , where the Maemo SW projects are identified as e.g. /nokia/whatever.git or something. If each project needs a garage project then I guess all code needs to be uploaded manually by each time in each location. Instead, what would happen if we would hav weekly bulks of the whole Maemo sources under development or something like that? There is something I don't see about the total subordination to Garag, which is that we have clear need for a git.maemo.org where Nokia and the community can share sources and contributions, and the need for garage projects is quite minor compared to this (in my humble opinion).--[[User:qgil|qgil]] 19:30, 3 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 [[User:timeless|timeless]] 12:44, 1 December 2008 (UTC)
:::::There is no such feature in GForge by default, but I could add it. --[[User:feri|feri]] 13:02, 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.--[[User:qgil|qgil]] 10:25, 1 December 2008 (UTC)

:Yes, it will be possible. --[[User:feri|feri]] 10:50, 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? ==

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.--[[User:qgil|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. --[[User:feri|feri]] 10:50, 1 December 2008 (UTC)

== SVN Supported ==

Is this opening up GIT for those who like GIT, but leaving SVN still fully supported for those who prefer SVN?   Or is the long term goals to depreciate SVN for GIT? --[[User:nathanael|nathanael]] 21:43, December 03, 2008 (UTC)

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "http://wiki.maemo.org/Talk:Git_For_Garage"

Personal tools

Navigation

Views

Editing Talk:Git For Garage

@@ Line 8: / Line 8: @@
 ::::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 [[User:timeless|timeless]] 12:44, 1 December 2008 (UTC)
 :::::There is no such feature in GForge by default, but I could add it. --[[User:feri|feri]] 13:02, 1 December 2008 (UTC)
-: Longer term could [http://gitorious.org gitorious.org] be integrated? Nokia/Qt already sponsors this and it provides really good team and ACL support. [[User:lbt|lbt]] 16:32, 3 June 2009 (UTC)
 == Centralized view of all the projects hosted in git.maemo.org ==
@@ Line 18: / Line 17: @@
 ::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
-like front page of git.kernel.org, git.freedesktop.org, git.debian.org, git.maemo.org should give a list of all git projects with gitweb (or cgit).
 == Any way to distinguish the Nokia projects? ==
@@ Line 30: / Line 27: @@
 Is this opening up GIT for those who like GIT, but leaving SVN still fully supported for those who prefer SVN?   Or is the long term goals to depreciate SVN for GIT? --[[User:nathanael|nathanael]] 21:43, December 03, 2008 (UTC)
-:This is just about adding git support.--[[User:qgil|qgil]] 21:00, 4 December 2008 (UTC)
-== Per-user git repositories ==
-Sure, branches on a project repository is nice and all, but alike launchpad, it could be nice for users to have a git repository of their own to post to, which could enable easier merging of patches from that users' branches. Is this something that could be considered? Would be very useful for Mer development, i suspect. Also, is the plan to have /project/<one or more repositories> ? or only one repository possible per project? --[[User:stskeeps|stskeeps]] 19:02, 9 December 2008 (UTC)