From laforge at gnumonks.org Fri Feb 5 16:10:54 2016 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 5 Feb 2016 17:10:54 +0100 Subject: Moving from trac to a single redmine In-Reply-To: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> References: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> Message-ID: <20160205161054.GE10932@nataraja> Hi Holger, On Thu, Feb 04, 2016 at 08:12:19AM +0100, Holger Freyther wrote: > I think some of us would like to move to redmine and start using > public tickets more frequently. So in case we move there are some > topics to be discussed and I would like to start with a couple of them > right now. Thanks for getting the public discussion about this started. To give some more background to the mailing list: * The trac installations at osmocom.org are pretty much underused/dormant. The only part that's used is the Wiki. * Osmocom started when a single project (OpenBSC) got a sister project (OsmocomBB) and has grown into many projects. Running a single trac instance for each project on a separate dns hostname is overkill. Also, as code is shifted around between libraries and programs, we'd appreciate some flexibility. * at sysmocom internally we have successfully used redmine for dozens of different projects. The project hierarchy can be changed as needed on the fly, and issues can relate to issues of other projects, shifted from project to project, etc. * Quite a bit of the work we do at sysmocom on the Osmocom software should have the issue tracker for bugs and features in the public, but as our internal redmine is so much easier than the public trac setup, we kept using the internal redmine. So my plan moving forward is to migrate all Osmocom projects (initially those related to GSM) to a public redmine, and then keep all issues updated there. This would give more visibility into the work we're doing, such as the EDGE PCU, the 3G NITB + SGSN, the HNB-GW, etc. > Redmine has a global linear sequence of ticket numbers. If we move > from many tracs to a single redmine we can either: > > * not import tickets > * only import from one project > * deal with changing ticket numbers I think not importing tickets or dealing wih changing numbers is the way to go. > In terms of installations the GMR trac is broken in regard to tickets, > there are some for SDR that are probably not being fixed anytime soon, > baseband might be relevant and OpenBSC is unlikely to be relevant. I > don't think we have ever used ticket reference in OpenBSC commit > messages so in terms of OpenBSC having changing ticket numbers would > not be a big deal. E.g. we could add a custom field with the old trac > number? If there is automatic import/conversion available, I'd prefer to import the OsmocomBB, SIMtrace, (non-spam) Security and OpenBSC tickets, even though most of them are probably stale and outdated for years. They're still part of the history. Changing the numbers doesn't matter, as we don't refer to them. > We have external references that should be redirected to the new > place. Is there any way besides maintaining a list in the > apache2/nginx configuration and making redirects as we find broken > references? Can we proactively manage this? Is anybody willing to come > up with a script and nginx configuration for doing this? I'm not aware of any tools that might be able to help here. Indeed, it would be great if anyone would volunteer to generate a script to generate the redirects. I guess the old format is e.g. http://openbsc.osmocom.org/trac/wiki/nanoBTS/Internals and the new URL would be something like http://projects.osmocom.org/redmine/openbsc/wiki/nanoBTS/Internals Or should we strip even the redmine from the URL? And should we have a rewrite for http://openbsc.osmocom.org/redmine to http://projects.osmocom.org/redmine/openbsc ? Any ideas? Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From 246tnt at gmail.com Fri Feb 5 20:57:12 2016 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 5 Feb 2016 21:57:12 +0100 Subject: Moving from trac to a single redmine In-Reply-To: <20160205161054.GE10932@nataraja> References: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> <20160205161054.GE10932@nataraja> Message-ID: Hi, >> I think some of us would like to move to redmine and start using >> public tickets more frequently. So in case we move there are some >> topics to be discussed and I would like to start with a couple of them >> right now. +1 for redmine. >> In terms of installations the GMR trac is broken in regard to tickets, >> there are some for SDR that are probably not being fixed anytime soon, >> baseband might be relevant and OpenBSC is unlikely to be relevant. I >> don't think we have ever used ticket reference in OpenBSC commit >> messages so in terms of OpenBSC having changing ticket numbers would >> not be a big deal. E.g. we could add a custom field with the old trac >> number? > > If there is automatic import/conversion available, I'd prefer to import > the OsmocomBB, SIMtrace, (non-spam) Security and OpenBSC tickets, even > though most of them are probably stale and outdated for years. They're > still part of the history. Changing the numbers doesn't matter, as we > don't refer to them. - OsmocomBB never used tickets AFAIK. - OsmocomGMR definitely never used them - OsmocomSDR ... don't think it's worth importing. - Security ... yeah maybe, although not really sure anyone is really using this. >> We have external references that should be redirected to the new >> place. Is there any way besides maintaining a list in the >> apache2/nginx configuration and making redirects as we find broken >> references? Can we proactively manage this? Is anybody willing to come >> up with a script and nginx configuration for doing this? > > I'm not aware of any tools that might be able to help here. > > Indeed, it would be great if anyone would volunteer to generate a script > to generate the redirects. script ? The page names should be the same, so it should pretty much be just a few redirects per project with regexp to redirect properly. Shouldn't be too hard once we settled for a URL scheme. Any reason not to go for just http://osmocom.org/ as a base ? We have nothing really in the front page and we could just let redmine handle it too. Then just http://osmocom.org/projectname/wiki/page/name looks good to me if doable. Cheers, Sylvain From laforge at gnumonks.org Fri Feb 5 23:54:33 2016 From: laforge at gnumonks.org (Harald Welte) Date: Sat, 6 Feb 2016 00:54:33 +0100 Subject: OsmoDevCon 2016 planning / wiki page In-Reply-To: <20160113133526.GO9964@nataraja> References: <20160112151200.GP1762@nataraja> <20160113133526.GO9964@nataraja> Message-ID: <20160205235433.GP10932@nataraja> Hi all, I've just created the template wiki page for OsmoDevCon2016 at http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2016 please add your name to the list if you're interested to attend (and qualify as somebody who contributed to Osmocom projects). Please also add any talks or workshops that you'd like to either a) hold yourself, or b) would want somebody else to talk about Looking forward to meeting you all again. It will already be the fifth OsmoDevCon, so we might consider a small birthday celebration :) Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Sun Feb 28 09:59:40 2016 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 28 Feb 2016 10:59:40 +0100 Subject: OsmoDevCon 2016 planning / wiki page In-Reply-To: <20160205235433.GP10932@nataraja> References: <20160112151200.GP1762@nataraja> <20160113133526.GO9964@nataraja> <20160205235433.GP10932@nataraja> Message-ID: <20160228095940.GC23371@nataraja> Dear all, On Sat, Feb 06, 2016 at 12:54:33AM +0100, Harald Welte wrote: > I've just created the template wiki page for OsmoDevCon2016 at > > http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2016 > > please add your name to the list if you're interested to attend (and > qualify as somebody who contributed to Osmocom projects). We have meanwhile migrated this to the new redmine installation at http://projects.osmocom.org/projects/openbsc/wiki/OsmoDevCon2016 As today is February 28 (indicated as the last day for registration), please let me know if you still have not added your name but are an existing Osmocom developer/contributor and would like to attend. Please also feel free to suggest further talks / discusison topics, either about which you would like to talk, or about which you would like to hear others talk. Also, the current list of topics is merely a suggestion. Please share openly if you think you don't want to hear about one of the topics :) Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)