Establish some written governance

[google]

Establish some written governance

[benbrittain]

Thanks for writing this up @raggi. I'm planning on taking some time and going through the existing issues/README in the near future and making it clear we are trending in this direction. We should have clear governance and mechanisms for contributing to Argh :)

I want argh to be maximally useful for everyone.

[sourcefrog]

It would be great to have some clarity on which features are in principle acceptable.

I think it's a real strength of Argh that it is opinionated and does not support every weird grammar, and the API is cleaner than structopt/Clap. But, in my opinion, it would be nice to support idiomatic Rust command lines as seen in Cargo.

#78, distinguishing arguments after --, is a good example of something that's common in Rust programs. (I don't know about Fuschia.)

If Argh wants to stick strictly to what is needed in Fuschia and no more, then perhaps there's room for a friendly fork that adds a few more features. On the other hand if you make clear that things like #78 are in principle acceptable and will get a reasonably timely review & release, people could help here.

[dschuyler]

Just making a +1 note to "Fuchsia command spec is not immovable, but it has its own governance model" (above).