Consolidate predicate efforts?

[epage]

I've created some predicates for assert_cli and expect to be creating more.

I'm wondering if you want to join efforts in providing general predicates implementations for exposure in APIs like hamcrest.

• Would you be interested in moving to the new assert.rs org with the intent of having others help support you in maintaining this crate?
• How amenable are you to the API evolving to support additional or different needs? For example, making the system more pluggable with traits or renaming / re-arranging our predicates are exposed?
  • I'm not sure how strict ports of hamcrest are to the original style and can understand not joining efforts due to needing to follow a specific style that a general predicate crate might move away from and the cost of maintaining vocabulary adapters would be
  • No concrete examples atm, just trying to explore areas of concern in joining efforts.

RE consolidating on orgs, I'm inspired by killercups #rust2018 post:

There is no reason why so many popular crates should live in user-repos instead of in community-managed organizations (speaking in Github terms). Writing and then publishing a bunch of code as a crate one thing, but maintaining it, fixing bugs, replying to issues and pull requests, that takes up a lot of time as well. Time, that a lot of developers don't have, or don't want to invest. cargo-edit, for example, which lives under my Github username, has two wonderful maintainers, who are more active than I am. But should I create a cargo-edit organization and move the repo there? If there was a good and definitive answer, which would neither make me deal with the organizational aspects not result in accumulating lot of junk code, I'd be really happy.

https://deterministic.space/rust-2018.html#aim-for-long-term-stability-of-the-library-ecosystem

[epage]

Also brought this up with predicate-rs

See assert-rs/predicates-rs#5