project-chip / rs-matter

Rust implementation of the Matter protocol. Status: Experimental
Apache License 2.0
328 stars 45 forks source link

Add pipeline for upload matter-rs crates to crates.io #56

Open Neirth opened 1 year ago

Neirth commented 1 year ago

I hope this message finds you well. I am reaching out to kindly request the upload of the matter-rs packages to crates.io in order to facilitate their usage in our projects.

We have been eagerly following the development of matter-rs and are impressed by its features and potential benefits for our projects. However, we have encountered difficulty in accessing the crates through crates.io, which is the primary repository for Rust packages.

To ensure seamless integration and compatibility within our projects, we kindly request that you consider publishing the matter-rs packages to crates.io. This will enable us and other members of the Rust community to easily include and utilize this valuable resource in our development workflows.

We understand the effort and dedication required to maintain and distribute crates, and we truly appreciate your contribution to the Rust ecosystem. By making the matter-rs packages available on crates.io, you would greatly enhance their accessibility and encourage wider adoption among developers.

Thank you for your time and consideration. We look forward to your positive response and eagerly anticipate the availability of the matter-rs packages on crates.io.

kedars commented 1 year ago

Yes, this will happen soon enough. Depending upon the crypto, both the mbedtls and openssl, couldn't be run out of the box using their respective crates and required some patches in the Git repos. But the rust-crypto is cleaner.

ivmarkov commented 1 year ago

@kedars This means a decision needs to be taken as to what would be the name under which the matter crate in the matter-rs workspace will be published/known in crates.io. To remind us about the status quo:

In any case, and whatever name you pick, ideally we need to rename the matter crate in the matter-rs workspace to a new name, so that the crate name in the workspace and its crates.io name do match. While not strictly required, I think keeping two different names is confusing. For one, the examples would refer to the workspace crate name, while users would need to use the crates.io name and just copy-pasting the examples won't work 1:1 (in that users would either need to rename the crates.io crate name in Cargo.toml's [dependencies] section back to matter for the examples to work out of the box, or they'll need to adjust the use statement when pasting the example code. Both things quite annoying).