Following up on this subject,
It’s a very good idea to make a (curated?) list of haxe extensions! But am not sure it’s the best option to try to put everything in the same GitHub team (of course it’s fine if some people want to, but for instance, I don’t want to, even if I am happy to contribute extensions).
I believe a simple repo like Awesome Snowkit listing every extensions (and some other resources) would be much straighforward to do, wouldn’t create any concern about ownership (everybody is free to keep his repo where he want’s etc…) and in general would be as useful.
Oh, it seems that there is already an Awesome Haxe repo by @nadako (but it didn’t get updated for 2 years ; I guess it would need an “active and regular curator” to make it useful)
Regarding Haxe extensions themselves, I am currently working on iOS/Android extensions for our own Haxe game engine (not openfl-based) but still trying to see how to make them compatible with OpenFL as well. My recent work on an Automatic iOS/Android bindings generator is some part of this effort.
About standards and how to build an extension, I found the linc initiative to work very well for us on Haxe/C++ target. It makes it easy to make and use native extensions without worrying about having precompiled binaries etc… It just build with the rest of the codebase and plays well with compilation cache. This obviously only solve the C++ part (that is why I am working on a binding utility for iOS/Android as a complement of this), but I think it’s a good step forward.
I should have some extensions ready in the coming weeks/months and will be happy to share these to the community when they are ready, but not by moving them to another Github team, sorry. Let me know if you think there can be any other way to contibute extensions though! (Of course haxelib itself is still a valid way to contribute anyway)!