[PySide] Additional pyside reviewers

[lndn]

>  Would it be possible to get some rights so that I could change tickets?

I don't know the answer, but it's a good question.  My guess is that you
would need to become an Approver.  According to the Qt Governance Model (
http://qt-project.org/wiki/The_Qt_Governance_Model), an existing Approver
must nominate you and another to second that nomination.  But I don't know
if there are any Approvers left in the project for this to happen.  I think
Lars Knoll may be the only one who can do this (according to his email).
 If so, you have my vote of support.




On Tue, Mar 19, 2013 at 4:24 AM, Sébastien Sablé <
sable at users.sourceforge.net> wrote:

> Hi,
>
> I got a couple bug fixes for shiboken merged into PySide the last few
> weeks; I have a few more in the pipe.
>
> I am too new on the project to be a code reviewer, however I also think
> there is a lot of work needed on the issue tracker side:
> https://bugreports.qt-project.org/browse/PYSIDE
> There are 111 tickets that not been evaluated at all.
>
> Would it be possible to get some rights so that I could change tickets?
>
> I would like to start prioritizing them, possibly closing the one which do
> not provide enough information to reproduce or that may be deprecated and
> writing unit tests for those which have enough details.
> Then I will try to fix one ticket per week depending on how much available
> time I have.
>
> best regards
>
> Sébastien
>
>
>
>
> 2013/3/19 lndn <lndndev at gmail.com>
>
>> Great news, just heard back from Lars Knoll regarding how to add new
>> maintainers, see his email reply below.
>>
>>
>> On Tue, Mar 19, 2013 at 3:22 AM, Knoll Lars <Lars.Knoll at digia.com> wrote:
>>
>>> Hi,
>>>
>>> yes, I'm in the position to add new maintainers. I'd say we follow the
>>> process we have on qt-project for this as well.
>>>
>>> Ideally, Hugo proposes a successor on the pyside mailing list. If he
>>> doesn't do it, I would propose to initiate a discussion about the best
>>> candidate on the ML. Please put me on CC, so I can follow the thread. If
>>> the person gets support on the ML, I'll give him formal maintainer status
>>> a little later.
>>>
>>> Cheers,
>>> Lars
>>>
>>> On 3/19/13 12:18 AM, "LNDN" wrote:
>>>
>>> >Hi Lars,
>>>
>>> >Are you in a position to add new maintainers to the PySide project?
>>>  And if so, what
>>> >do we need to do on our side to do this?
>>> >
>>> >
>>> >Thank you,
>>> >LNDN
>>> >
>>>
>>
>>
>> On Mon, Mar 18, 2013 at 9:49 PM, Matti Airas <mairas at iki.fi> wrote:
>>
>>>
>>> On 18 Mar 2013 23:53, "Hugo Parente Lima" <hugo.lima at openbossa.org>
>>> wrote:
>>> > Yes, I want to step down as maintainer, I'm no longer working on
>>> PySide and
>>> > the code base in fading out from my memory month after month, the main
>>> problem
>>> > now is that I don't know who on Qt-Project is responsible for
>>> add/remove
>>> > approvers/maintainers.
>>>
>>> I'd like to thank on my behalf for the awesome contribution you've done
>>> for PySide over the past years. It's been quite incredible!
>>>
>>> The different roles and nomination process are described here:
>>>
>>> http://qt-project.org/wiki/The_Qt_Governance_Model
>>>
>>> Basically, you, Hugo, should just send an email your proposal to
>>> development at qt-project.org mailing list. A cc to Lars probably won't
>>> harm, but the reasoning should be in public.
>>>
>>> http://lists.qt-project.org/mailman/listinfo/development
>>>
>>> Nominating a bunch of new approvers at the same time probably wouldn't
>>> harm, either... :-)
>>>
>>> Cheers,
>>>
>>> ma.
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>>
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/7c63333c/attachment.html>