[Development] Orphan modules

[Edward Welbourne]

Tor Arne Vestbø (12 September 2018 10:25)
> I think the qtmacextras module should be maintained by the same
> [maintainer] as macOS, Morten.

That would depend on - Morten: are you willing to take it on ?

As long as Tor Arne and Morten are watching the module, Samuel could
gain some experience as a Maintainer, after all.

> 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.

Indeed, I'm always wary of extras, util, misc and similar names, that
have no boundary on their scope to keep clutter from being dumped in.
I've found too much misplaced junk in such-named things over the years.

> 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.

Sounds promising.

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

Use of passive voice - "should be" - perhaps a better plan would be to
actively submit the patches to make it happen, or file a task in Jira
for it.  Even if there's no release branch ready for them, having
patches on dev gives relevant folk notice of your intent; and it might
give a focus for like-minded folk to co-ordinate the pre-requisites of
that change,

	Eddy.