On Fri, Apr 20, 2012 at 1:30 AM, Dave Abrahams <dave@boostpro.com> wrote:
on Thu Apr 19 2012, Olaf van der Spek <ml-AT-vdspek.org> wrote:
On Thu, Apr 19, 2012 at 9:12 PM, Dave Abrahams <dave@boostpro.com> wrote:
I don't think anyone understands the question. What do you mean by "perform the move?"
Moving Trac from it's current host to OSUOSL. What's the plan? Who's going to execute it?
I don't understand; didn't you volunteer to make this happen? Presumably it would take cooperation between a Booster and sysadmins at both IUOSL and OSUOSL.
I did and still do. But I don't know what to do.
I can put you in touch with the IUOSL and OSUOSL people. A big part of this
Please do, let's get started.
job consists of "figuring out what to do," so you not knowing what to do is part of the game, so to speak.
I understand, but I need some starting pointers.
Who (from Boost) is dealing with IUOSL and OSUOSL?
A number of us deal with IUOSL from time to time. I think the OSUOSL interaction has mostly been me and Renée.
Who is managing the website
The website, meaning http://boost.org? It probably depends what you mean by "managing..." but in any case I don't think I know who's doing it, and I'm not sure it's relevant to the bug tracker migration.
Maybe not, I don't know whether the two are integrated or entirely separate.
and existing Trac instance?
The moderators and maybe a few others have admin privileges on the Trac instance via its web interface. For lower-level control, you have to deal with Dong-Inn Kim, the IUOSL sysadmin.
OK -- Olaf