Talk:Git For Garage - Revision history

imported_>sixwheeledbeast: Reverted edits by 178.214.173.123 (Talk) to last revision by lbt

2022-10-24T16:28:25Z

Reverted edits by 178.214.173.123 (Talk) to last revision by lbt

← Older revision		Revision as of 16:28, 24 October 2022
Line 35:		Line 35:

	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)		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)

	~~== где можно встретить новый год в ейске ==~~

	~~анекдоты про гагауз. Взять <a href=https://wm-lend.ru>займ webmoney</a>. видео конверер для lg kp500~~

178.214.173.123: /* где можно встретить новый год в ейске */ new section

2022-10-24T11:26:50Z

где можно встретить новый год в ейске: new section

← Older revision		Revision as of 11:26, 24 October 2022
Line 35:		Line 35:

	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)		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)

			== где можно встретить новый год в ейске ==

			анекдоты про гагауз. Взять <a href=https://wm-lend.ru>займ webmoney</a>. видео конверер для lg kp500

imported_>lbt: /* git.maemo.org without garage project */

2009-06-03T16:32:29Z

git.maemo.org without garage project

← Older revision		Revision as of 16:32, 3 June 2009
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)		::::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)		:::::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 ==		== Centralized view of all the projects hosted in git.maemo.org ==

imported_>suihkulokki: /* Centralized view of all the projects hosted in git.maemo.org */

2009-02-20T12:53:51Z

Centralized view of all the projects hosted in git.maemo.org

← Older revision		Revision as of 12:53, 20 February 2009
Line 17:		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)		::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		:::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? ==		== Any way to distinguish the Nokia projects? ==

imported_>stskeeps at 19:02, 9 December 2008

2008-12-09T19:02:49Z

← Older revision		Revision as of 19:02, 9 December 2008
Line 28:		Line 28:
	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)		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)		: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)

imported_>qgil: /* SVN Supported */

2008-12-04T21:00:05Z

SVN Supported

← Older revision		Revision as of 21:00, 4 December 2008
Line 27:		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)		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)

imported_>nathanael at 21:45, 3 December 2008

2008-12-03T21:45:01Z

← Older revision		Revision as of 21:45, 3 December 2008
Line 23:		Line 23:

	: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)		: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)

imported_>qgil: /* git.maemo.org without garage project */

2008-12-03T19:30:15Z

git.maemo.org without garage project

← Older revision		Revision as of 19:30, 3 December 2008
Line 5:		Line 5:
	::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)		::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)		:::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)		::::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)		:::::There is no such feature in GForge by default, but I could add it. --[[User:feri\|feri]] 13:02, 1 December 2008 (UTC)

imported_>feri: /* Centralized view of all the projects hosted in git.maemo.org */

2008-12-01T13:03:19Z

Centralized view of all the projects hosted in git.maemo.org

← Older revision		Revision as of 13:03, 1 December 2008
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? ==

imported_>feri: /* git.maemo.org without garage project */

2008-12-01T13:02:30Z

git.maemo.org without garage project

← Older revision		Revision as of 13:02, 1 December 2008
Line 2:		Line 2:

	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)		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.		: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)
	--[[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)		::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)		:::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)

← Older revision		Revision as of 19:30, 3 December 2008
Line 5:		Line 5:
	::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)		::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)		:::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)		::::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)		:::::There is no such feature in GForge by default, but I could add it. --[[User:feri\|feri]] 13:02, 1 December 2008 (UTC)

← Older revision		Revision as of 13:02, 1 December 2008
Line 2:		Line 2:

	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)		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.		: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)
	--[[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)		::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)		:::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)