Hey,

Nothing against your competence Samuel, but I think the qtmacextras module 
should be maintained by the same maintained as macOS, Morten.

I also think that the extras modules have a risk of ending up as dumping 
grounds for platform specific APIs we never really got around to integrating 
with Qt in a cross platform way, or that didn’t really need a Qt api in the 
first place, such as wrapping simple objective-c functions.

With the proposed solution of making platform plugins libraries with their own 
private headers, we can have these apis closer to the platform code, and 
without lots of plumbing and indirection.

I think the qtmacextras module in particular should be deprecated ASAP, and 
will strongly oppose any new APIs added to it.

- Tor Arne

> On 12 Sep 2018, at 00:00, Samuel Gaist <samuel.ga...@idiap.ch> wrote:
> 
> Hi Eddy,
> 
> If you guys think my competences fill the bill, I can take on the qtmacextras
> module maintenance.
> 
> Best regards
> 
> Samuel
> 
>> On 30 Aug 2018, at 15:27, Edward Welbourne <edward.welbou...@qt.io> wrote:
>> 
>> I notice, as part of seeking folk to look at API reviews, that we have
>> several modules with no Maintainer: qtandroidextras, qtgraphicaleffects,
>> qtmacextras, qtquick1, qtquickcontrols, qtsvg, qtwinextras and (the one
>> that brought this to my attention) qtxmlpatterns, according to [0].
>> 
>> * [0] https://wiki.qt.io/Maintainers
>> 
>> (There's also qtdoc, with no person as maintainer, but with "Norway" in
>> the Country column, which I interpret as the doc-team here in Oslo; and
>> there's qtfeedback, which is unsupported; two other unsupported modules
>> do in fact have Maintainers.)
>> 
>> If anyone out there feels an urge to volunteer to adopt one of these
>> orphans, it'd be worth speaking up,
>> 
>>    Eddy.
>> _______________________________________________
>> Development mailing list
>> Development@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
> 
> 
> 
> _______________________________________________
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to