Initial Ecosystem WG Readme

[KodrAus]

No description provided.

[aturon]

LGTM! I might add something about discoverability also (e.g. cookbook).

[vitiral]

👍 I think the focus on tooling is especially important.

[KodrAus]

@vitiral do you think we should call out supporting/discussing tools that are typically used in Rust maintenance more?

[vitiral]

When you say "we" do you mean the ecosystem-wg or the rust community in general?

I think that cross platform distribution/testing and unifying the workflow for major rust projects (bors, travis, appveyor, github) is extremely important and there isn't a great unified guide for doing so.

I've also found compiling on some platforms to be challenging when there are non-rust dependencies, which is why I'm investigating Nix. However, I think this might be too big an issue for this year (maybe next year), although I am far from an official voice here.

I think @matthiasbeyer or @P-E-Meunier probably has the most experience with rust+nix itself, but I don't know their viewpoints of rust+nix combined with the entire ecosystem a-la tooling at this moment.

[vitiral]

this issue is probably related to this WG: https://github.com/rust-lang-nursery/cli-wg/issues/8

[KodrAus]

When you say "we" do you mean the ecosystem-wg or the rust community in general?

I would say both :)

I think that cross platform distribution/testing and unifying the workflow for major rust projects (bors, travis, appveyor, github) is extremely important and there isn't a great unified guide for doing so.

I totally agree! I think some part of our maintainership guidelines should touch on this. There tend to be a lot of moving parts in a cross-platform, open-source project.

There are also other handy process bots like highfive and rfcbot that I think deserve some attention.

I'll add a note about tools explicitly to the readme.