More maintainers

[Uriopass]

I am open to add more maintainers to this project (github & crates.io rights) that want to have the latest bindings so that it doesn't depend on a single person.

Ping @BeastLe9enD, @oisyn and @gents83 as you recently contributed new bindings/changes to meshopt

[BeastLe9enD]

Considering the fact that the crate on Github was last updated over a year ago (and November 2019 on crates.io), I think the is the best way to go. I would like to help as a maintainer!

[oisyn]

Same here!

[oisyn]

Have you tried reaching out to @gwihlidal to see if he was maybe interested in handing over the crates.io rights at least?

[BeastLe9enD]

good point, maybe we could try asking him on twitter (I think Github issues is not the best way to reach him)

[Uriopass]

You're right, I didn't think of that!

[Uriopass]

I'll send him a message on twitter

EDIT: Done

[Uriopass]

In the meantime, I have added you both to meshopt2 on crates.io too 👍

[BeastLe9enD]

@Uriopass Have you received an answer so far?

[Uriopass]

No answers :/

[gwihlidal]

Hey all,

Sorry I've been busy, but I'm definitely up for getting help maintaining this crate! I can add you all to this repo and also crates.io

I've been hoping to find some time again to resume crate dev, but getting your help will be awesome.

Thank you,
Graham

[Uriopass]

I can add you all to this repo and also crates.io

That would be great! Thank you

[JMS55]

Hi. I'm using meshopt in Bevy for meshlet generation. Currently, I'm using my own fork of meshopt that exposes some non-public fields and implements DecodePosition for an array of floats. In the future, I'm also going to need Traverse Research's fork that exposes simplifying meshes while locking edges (included in my branch atm, although I don't currently use it).

A prerequisite to being able to merge my code into Bevy is depending on a crates.io published crate, instead of a git fork. Would you be interested in merging my (small commits), and possibly Traverse Research's additional API, and then publishing a new crates.io release of meshopt2?

[Uriopass]

Absolutely open to that, these seem like good API changes!

It might be better to wait for @gwihlidal to give us maintaining control over the original crate though, as it'd be a bit less confusing

[oisyn]

Keep in mind that our fork (I work at Traverse 😉) is dependent on zeux/meshoptimizer#601 to be merged. We could of course opt to use the Traverse fork of the C++ library as basis in the mean time -- I would personally favor that as that would remove some patches in our Cargo.toml, but I'm a bit biased here 😄.

[gwihlidal]

I have added @Uriopass, @BeastLe9enD, @oisyn and @gents83 as maintainers to the meshopt repository, as well as crates.io - thank you very much for the help!