Quote: rdalverny wrote on Fri, 25 March 2011 10:53

> You can't force a maintainer to do something you want and that she
> judges not right for her set of packages.

We seem to be having a communication issue. Where did I force a maintainer
to do anything?

I asked if there is any COMPELLING reason for me not to reenable
qt3-devel.
If there isn't, then of course I will reenable it.

It wasn't me who then started a long off-topic discussion about imagined or
otherwise risks of TDE.

> If you can't work here by that, or if you are not happy with how
> things go here, you are free to discuss this openly with members of
> the council or of the board to sort it out.

Is there a procedure for that somewhere?
I would think such discussions are supposed to happen on the MLs (rather
than in private) and given that board/council members posted in this
thread I would assume that this discussion is happening here.

Are you saying that the members of the council that posted here in this
thread would give a different answer if I contacted them formally (how?)
as members of the council?

TBH I didn't even want any grand discussion, to repeat myself I was just
trying to find out if there is anything blocking the reenabling of
qt3-devel.
(I hope this point is finally clear enough by now)

> So why all the fuss? Take the maintainance of the package, make your
> changes, submit it and here you are.

If you re-read the thread you will find that I didn't start "the fuss", in
fact it was started by people expressing fears about TDE and some
board/council members putting preemptive vetos on TDE.

I have no problem co-maintaining the package (with regards to the devel
side of it) but I'm not aware of any formal procedure to take maintenance
of a package.
Is there such a procedure formalized somewhere?

-- 
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/

Reply via email to