Re: Unresponsive maintainer procedure for tuxbrewr

2016-01-15 Thread Kevin Kofler
Christian Dersch wrote: > I tried to contact tuxbrewr some weeks ago (due to quassel bug fixes and > maintainance), without any response. Does anybody know how to contact > him? I already tried smparr...@gmail.com without success. FYI, it's been a long long time since we last heard from tuxbrewr

Re: Unresponsive maintainer procedure for tuxbrewr

2016-01-12 Thread Michael Schwendt
On Mon, 11 Jan 2016 21:48:25 +0100, Christian Dersch wrote: > Hi all, > > I tried to contact tuxbrewr some weeks ago (due to quassel bug fixes and > maintainance), without any response. Does anybody know how to contact > him? I already tried smparr...@gmail.com without success. > > Info:

Re: Unresponsive maintainer procedure for tuxbrewr

2016-01-12 Thread Sven Lankes
On Tue, Jan 12, 2016 at 01:30:27PM +0100, Michael Schwendt wrote: > Isn't that tedious, inefficient and a waste of time? As all of the unresponsive maintainer procedure. Could we adjust the tooling so that a request for commit access is automatically granted if it isn't answered within three

Re: Unresponsive maintainer procedure for tuxbrewr

2016-01-12 Thread Michael Schwendt
On Tue, 12 Jan 2016 16:27:03 +0100, Sven Lankes wrote: > As I understand it, your sponsor is supposed to look after your commits. Not forever, though. Sponsorship is not a life-time duty, and monitoring git commits isn't either. It's not even mentioned as a responsibility. There are sponsors who

Re: Unresponsive maintainer procedure for tuxbrewr

2016-01-12 Thread Christian Dersch
On 01/12/2016 10:00 AM, Michael Schwendt wrote: > The same procedure has been started a few times, at least > > https://bugzilla.redhat.com/736874 > https://bugzilla.redhat.com/963890 > > Requesting co-maintainer access would be a way to solve such > isues. > -- > I requested it in pkgdb

Re: Unresponsive maintainer procedure for tuxbrewr

2016-01-12 Thread Michael Schwendt
On Tue, 12 Jan 2016 11:17:37 +0100, Christian Dersch wrote: > > The same procedure has been started a few times, at least > > > > https://bugzilla.redhat.com/736874 > > https://bugzilla.redhat.com/963890 > > > > Requesting co-maintainer access would be a way to solve such > > isues. > > > I

Re: Unresponsive maintainer procedure for tuxbrewr

2016-01-12 Thread Sven Lankes
On Tue, Jan 12, 2016 at 10:06:40AM -0500, Nico Kadel-Garcia wrote: >> Could we adjust the tooling so that a request for commit access is >> automatically granted if it isn't answered within three months? > That's a potential security problem. If I, for example, can get > commit access to any

Re: Unresponsive maintainer procedure for tuxbrewr

2016-01-12 Thread Nico Kadel-Garcia
On Tue, Jan 12, 2016 at 9:31 AM, Sven Lankes wrote: > On Tue, Jan 12, 2016 at 01:30:27PM +0100, Michael Schwendt wrote: > >> Isn't that tedious, inefficient and a waste of time? > > As all of the unresponsive maintainer procedure. > > Could we adjust the tooling so that a request

Unresponsive maintainer procedure for tuxbrewr

2016-01-11 Thread Christian Dersch
Hi all, I tried to contact tuxbrewr some weeks ago (due to quassel bug fixes and maintainance), without any response. Does anybody know how to contact him? I already tried smparr...@gmail.com without success. Info: https://bugzilla.redhat.com/show_bug.cgi?id=1294472 Greetings, Christian --