[Development] Maintainership of QtNetwork

[Peter Hartmann]

Hello,

I also think having 2 maintainers versus 1 maintainer for QtNetwork will 
not matter much in practice; but if people demand to have one single 
go-to person I am also fine with either of us taking that role.

Peter


On 11/04/2013 09:38 PM, Richard Moore wrote:
> Hi All,
>
> I think there's a valid question in who gets to be the arbiter should
> Peter and I disagree on something, however between Peter, Shane and I
> we've been working with pretty much this model anyway - I can't
> imagine that any of us would allow something through that one of the
> others disagreed with. In a situation like this, then we always have
> Lars as a tie breaker with his chief maintainer hat on.
>
> I'd guess that any likely tie in this situation would be more along
> the lines of /should/ we support a feature rather than how the feature
> is supported. I don't see this being a problem based on the way we've
> managed to run stuff for the last couple of years, but if we really
> need a designated QtNetwork tie breaker, then really either of us
> could be that person. It seems a but academic to me since Peter, Shane
> and I have been collaborating on the network stack since opengov
> started, so this isn't a new team or any kind of dramatic change.
>
> I don't mind how people want this to be handled. Joint maintainership
> or a designated tie breaker is fine with me.
>
> Cheers
>
> Rich.
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.