On 14.01.2015 10:29 AM, Mike Gabriel wrote:
The git-admin has been me for the last years.
@Heinz, if not done already: git-admin@x2go.org -> git-admin -> Mihai Moldovan
Yeah, that would be great, thanks.
For sharing the workload on other issues, I recommend this new assignment model for X2Go BTS:
""" bugs.x2go.org x2go-project@lists.x2go.org (NEW) debbugs x2go-dev@lists.x2go.org (NEW) not-a-bug x2go-dev@lists.x2go.org (NEW) wiki.x2go.org wiki-admin@x2go.org lists.x2go.org listadmins@x2go.org jenkins.x2go.org x2go-project@lists.x2go.org (NEW) packages.x2go.org x2go-project@lists.x2go.org (NEW) launchpad.net x2go-project@lists.x2go.org (NEW) """
This also allows people to track issues with X2Go infrastructure via the X2Go project ML.
I'd also love not to have those infrastructural issues "pollute" the x2go-dev mailing list.
So, I am proposing the changes as seen in the below diff.
--- pseudo-packages.maintainers 2014-11-05 12:22:02.000000000 +0100 +++ pseudo-packages.maintainers.proposal 2015-01-14 10:21:58.000000000 +0100 @@ -1,9 +1,10 @@ -bugs.x2go.org git-admin@x2go.org +bugs.x2go.org x2go-project@lists.x2go.org git.x2go.org git-admin@x2go.org -debbugs git-admin@x2go.org -not-a-bug git-admin@x2go.org +debbugs x2go-dev@lists.x2go.org +not-a-bug x2go-dev@lists.x2go.org wiki.x2go.org wiki-admin@x2go.org lists.x2go.org listadmins@x2go.org -jenkins.x2go.org git-admin@x2go.org -packages.x2go.org git-admin@x2go.org -launchpad.net git-admin@x2go.org +jenkins.x2go.org x2go-project@lists.x2go.org +packages.x2go.org x2go-project@lists.x2go.org +launchpad.net x2go-project@lists.x2go.org +
Request for feedback, ideas, comments!
What is this I don't even. You don't want to pollute the x2go-dev mailing list, but still set debbugs and not-a-bug to x2go-dev? Or do you mean all the x2go-project assignments, which would have otherwise went to x2go-dev? That's reasonable then, though. What about a bug-admin address? That may however not make sense if debbugs (debian bug reports?) isn't to be handled by the bug admin directly (x)or by multiple people. The same goes for jenkins and packages. Maybe we need build-admin, too? Probably not, though. Otherwise it all sounds sane. Mihai