On Mi 14 Jan 2015 20:12:51 UTC, Mihai Moldovan wrote:
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 [email protected] +bugs.x2go.org [email protected] git.x2go.org [email protected] -debbugs [email protected] -not-a-bug [email protected] +debbugs [email protected] +not-a-bug [email protected] wiki.x2go.org [email protected] lists.x2go.org [email protected] -jenkins.x2go.org [email protected] -packages.x2go.org [email protected] -launchpad.net [email protected] +jenkins.x2go.org [email protected] +packages.x2go.org [email protected] +launchpad.net [email protected] + Request for feedback, ideas, comments!You don't want to pollute the x2go-dev mailing list, but still set debbugs and not-a-bug to x2go-dev?
debbug:The debbugs code is code and requires devs to look after it. There also could be a mail address (e.g. [email protected], which is already an existing address) that will be forward to the X2Go BTS maintainer. If this is settled, then this address could be a valid replacment for x2go-dev.
not-a-bug:I invented this pseudo-package for all bugs that are bugs, but not related to X2Go directly (better name: not-an-X2Go-bug). Also something that is interesting for devs, only, I fear.
Or do you mean all the x2go-project assignments, which would have otherwise went to x2go-dev? That's reasonable then, though.
Exactly! That was my idead.
What about a bug-admin address? That may however not make sense if
Ooops... yeah. See above ([email protected]).
debbugs (debian bug reports?) isn't to be handled by the bug admin
debbugs is the software name behind X2Go BTS. The Debian project runs the same software (and has brought it into being).
directly (x)or by multiple people.
Maintaining bugs in Debian is not for X2Go upstream devs. I (as the co-maintainer of X2Go software in Debian) use Debian BTS for communication with other teams in Debian (e.g. the release team). Don't copy upstream bugs into Debian BTS.
The same goes for jenkins and packages. Maybe we need build-admin, too? Probably not, though.
Maybe yes. Maybe not. The idea of piping messages/bugs about those systems to x2go-project is that people reading x2go-project can read that certain parts of the X2Go infrastructure have problems (which then some time later get resolved).
Otherwise it all sounds sane.
:-) Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: [email protected], http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgpyz03vqLpX8.pgp
Description: Digitale PGP-Signatur
_______________________________________________ x2go-project mailing list [email protected] http://lists.x2go.org/listinfo/x2go-project
