[opensuse-buildservice] technical reorganisation svn->git and administrator mailing lists ?
Hello, I would like to propose two changes in our development enviroments. svn to gitorious ================ openSUSE is currently consolidating its svn/git/... systems to gitorious. I would like to propose that we move the entire openSUSE svn from forge.novell.com, including the Build Service also to this place. http://gitorious.org/opensuse/ As a side effect, this would be a switch from subversion to git. git is more feature rich, but less obvious to use. Also the account at gitorious will not be the same as in the rest in the infrastructure. So it will be a bit harder to verify if user X at gitorious is really user Y in bugzilla/OBS/.... Are there concerns in doing this ? Mailing list re-org =================== We have basically two mailing lists regarding OBS atm. One is this opensuse-buildservice ml, which is intended for developer questions and for reporting issues with the opensuse.org instance. opensuse-packaging is intended for topics how to use the OBS and general packaging questions. I would like to propose another buildservice-admin mailing list, esp. for people who run a build service instance. An open question is, if we should make the -admin ml world readable or a closed and invatation only ml. The later would have the advantage that we could use it also as reporting address for potential security issues. What are your opinions about this ? Background information: http://en.opensuse.org/Build_Service/Support bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Oct 12, Adrian Schröter wrote:
Mailing list re-org ===================
We have basically two mailing lists regarding OBS atm. One is this opensuse-buildservice ml, which is intended for developer questions and for reporting issues with the opensuse.org instance.
opensuse-packaging is intended for topics how to use the OBS and general packaging questions.
I would like to propose another buildservice-admin mailing list, esp. for people who run a build service instance.
An open question is, if we should make the -admin ml world readable or a closed and invatation only ml. The later would have the advantage that we could use it also as reporting address for potential security issues.
What are your opinions about this ?
I'm always against creating more lists, I'm more the "consolidation" guy... ;-) More lists result in more confusion (IMHO).
Background information: http://en.opensuse.org/Build_Service/Support
bye adrian
--
Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- With best regards, Carsten Hoeger
On 2009-10-12 12:05:28 +0200, Adrian Schröter wrote:
I would like to propose two changes in our development enviroments.
svn to gitorious ================
openSUSE is currently consolidating its svn/git/... systems to gitorious. I would like to propose that we move the entire openSUSE svn from forge.novell.com, including the Build Service also to this place.
http://gitorious.org/opensuse/
As a side effect, this would be a switch from subversion to git. git is more feature rich, but less obvious to use. Also the account at gitorious will not be the same as in the rest in the infrastructure. So it will be a bit harder to verify if user X at gitorious is really user Y in bugzilla/OBS/....
Are there concerns in doing this ?
i would rather maintain our own svn instead of switching to git. but that might be just me.
Mailing list re-org ===================
We have basically two mailing lists regarding OBS atm. One is this opensuse-buildservice ml, which is intended for developer questions and for reporting issues with the opensuse.org instance.
opensuse-packaging is intended for topics how to use the OBS and general packaging questions.
I would like to propose another buildservice-admin mailing list, esp. for people who run a build service instance.
An open question is, if we should make the -admin ml world readable or a closed and invatation only ml. The later would have the advantage that we could use it also as reporting address for potential security issues.
What are your opinions about this ?
not more mailinglists. if you want to make this list more focused on development and less using the obs. thats fine. but please not yet another list -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Marcus Rueckert wrote:
On 2009-10-12 12:05:28 +0200, Adrian Schröter wrote:
I would like to propose two changes in our development enviroments.
svn to gitorious ================
openSUSE is currently consolidating its svn/git/... systems to gitorious. I would like to propose that we move the entire openSUSE svn from forge.novell.com, including the Build Service also to this place.
http://gitorious.org/opensuse/
As a side effect, this would be a switch from subversion to git. git is more feature rich, but less obvious to use. Also the account at gitorious will not be the same as in the rest in the infrastructure. So it will be a bit harder to verify if user X at gitorious is really user Y in bugzilla/OBS/....
Are there concerns in doing this ?
i would rather maintain our own svn instead of switching to git. but that might be just me.
If you want an improvement, break up the source in https://forgesvn1.novell.com/svn/opensuse/trunk/. OBS, the server, and osc, and other clients are all under the same 'trunk', but are released on different schedules. It would make more sense to move the 'trunk' under each individual rpm's source. That could also eliminate the packaging of osc, which is under https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/clientlib/p..., into the OBS server tarball, which is rooted at https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/. For our internal OBS instance I have two copies of osc since one is under obs-server and one under osc as it's easier to do vendor drops with osc having its own trunk and branches.
Mailing list re-org ===================
We have basically two mailing lists regarding OBS atm. One is this opensuse-buildservice ml, which is intended for developer questions and for reporting issues with the opensuse.org instance.
opensuse-packaging is intended for topics how to use the OBS and general packaging questions.
I would like to propose another buildservice-admin mailing list, esp. for people who run a build service instance.
An open question is, if we should make the -admin ml world readable or a closed and invatation only ml. The later would have the advantage that we could use it also as reporting address for potential security issues.
What are your opinions about this ?
not more mailinglists. if you want to make this list more focused on development and less using the obs. thats fine.
but please not yet another list
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Dne 12.10.2009 20:36, Luke Imhoff napsal(a):
Marcus Rueckert wrote:
On 2009-10-12 12:05:28 +0200, Adrian Schröter wrote:
As a side effect, this would be a switch from subversion to git. git is more feature rich, but less obvious to use. Also the account at gitorious will not be the same as in the rest in the infrastructure. So it will be a bit harder to verify if user X at gitorious is really user Y in bugzilla/OBS/....
Are there concerns in doing this ?
i would rather maintain our own svn instead of switching to git. but that might be just me.
If you want an improvement, break up the source in https://forgesvn1.novell.com/svn/opensuse/trunk/. OBS, the server, and osc, and other clients are all under the same 'trunk', but are released on different schedules. It would make more sense to move the 'trunk' under each individual rpm's source. That could also eliminate the packaging of osc, which is under
I think that splitting the repository into smaller parts is a prerequisite to switching to git (I wouldn't want to clone all of backend, frontend, webclient, qt client and whatnot to just hack on osc), so a repository reorg is IMO needed anyway, whether are the developers going to switch to git or to keep their own svn. Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 13. Oktober 2009 13:13:53 schrieb Michal Marek:
Dne 12.10.2009 20:36, Luke Imhoff napsal(a):
Marcus Rueckert wrote:
On 2009-10-12 12:05:28 +0200, Adrian Schröter wrote:
As a side effect, this would be a switch from subversion to git. git is more feature rich, but less obvious to use. Also the account at gitorious will not be the same as in the rest in the infrastructure. So it will be a bit harder to verify if user X at gitorious is really user Y in bugzilla/OBS/....
Are there concerns in doing this ?
i would rather maintain our own svn instead of switching to git. but that might be just me.
If you want an improvement, break up the source in https://forgesvn1.novell.com/svn/opensuse/trunk/. OBS, the server, and osc, and other clients are all under the same 'trunk', but are released on different schedules. It would make more sense to move the 'trunk' under each individual rpm's source. That could also eliminate the packaging of osc, which is under
I think that splitting the repository into smaller parts is a prerequisite to switching to git (I wouldn't want to clone all of backend, frontend, webclient, qt client and whatnot to just hack on osc), so a repository reorg is IMO needed anyway, whether are the developers going to switch to git or to keep their own svn.
yes, we will do so during the move. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 12 Oct 2009, Adrian Schröter wrote:
svn to gitorious ================
openSUSE is currently consolidating its svn/git/... systems to gitorious. I would like to propose that we move the entire openSUSE svn from forge.novell.com, including the Build Service also to this place.
http://gitorious.org/opensuse/
As a side effect, this would be a switch from subversion to git. git is more feature rich, but less obvious to use. Also the account at gitorious will not be the same as in the rest in the infrastructure. So it will be a bit harder to verify if user X at gitorious is really user Y in bugzilla/OBS/....
Are there concerns in doing this ?
I really like this. I am very much for it.
Mailing list re-org ===================
We have basically two mailing lists regarding OBS atm. One is this opensuse-buildservice ml, which is intended for developer questions and for reporting issues with the opensuse.org instance.
opensuse-packaging is intended for topics how to use the OBS and general packaging questions.
I would like to propose another buildservice-admin mailing list, esp. for people who run a build service instance.
An open question is, if we should make the -admin ml world readable or a closed and invatation only ml. The later would have the advantage that we could use it also as reporting address for potential security issues.
What are your opinions about this ?
Background information: http://en.opensuse.org/Build_Service/Support
I would rather not have an other mail list. -- Boyd Gerber <gerberb@zenez.com> 801 849-0213 ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (6)
-
Adrian Schröter -
Boyd Lynn Gerber -
Carsten Hoeger -
Luke Imhoff -
Marcus Rueckert -
Michal Marek