Assemble a team of maintainers

[carllerche]

Relates to #190

Nix has a vast scope, bigger than I can manage on my own. I am constantly a blocker for getting PRs merged and issues looked at. I need help!

Given that nix covers many facets of APIs on _nix systems, it should be plausible to officially split responsibility based on that. Eventually, these difference facets will be moved into nix-_ libs and iterate versions independently.

If you want to help out, jump in here and let me know which bits you want to own!

[kamalmarhubi]

I've become a huge fan of nix so I'd definitely love to help out! I've mostly been working with process stuff in unistd, sched (Linux only though), and a bit of mount.

[fiveop]

My current private project involves a lot of work with signals. I would therefore offer to look after anything singals related.

[carllerche]

@kamalmarhubi @fiveop Thanks! I added you as collaborators.

@posborne I added you since you have way more ioctl knowledge than I do.

@utkarshkukreti I've added you as you have many good commits :)

I created an IRC channel on the mozilla IRC server (irc.mozilla.org). The channel is #nix. It would be good to chat a bit to coordinate. I would like to move #190 forward at some point. Aka, come up w/ a style guide, move all FFI definitions to libc and try to split up nix into sub crates that represent categories of *nix APIs. This way versions can float independently. The nix crate can be an aggregation of all the sub crates.

[posborne]

Sounds good to me.

[kamalmarhubi]

After a small IRC chat with @carllerche, I've created the nix-rust org, and nix will be moving there soon! I added everyone mentioned here, as well as @arcnmx as members of the org.

[kamalmarhubi]

I'm closing this for now. We've got at least a few people who can r+ things now!!

[kamalmarhubi]

@posborne somehow I missed you in this. Sorry!

[posborne]

@kamalmarhubi No problem. I haven't been too active recently but I'm sure that will change. Great work pushing this stuff forward.