Adding TRANSFER.md instructions for transferring to the REC

[ryan-summers]

Fixes #23 by adding a new TRANSFER.md file.

[eldruin]

Thank you for writing this! There is one problem I have hit in the past with regard to publishing permissions, though:

In order to invite a team as an owner one must be a member of that team

So the process is slightly more complicated:

• If the person wants to join the r-e-c, that should be done first and then the transfer process is as detailed here.
• If the person does not want to join the r-e-c, crates.io publishing permission must be granted to an individual of the org (they are probably in contact with or know about someone already. Otherwise they can open an issue. Failing that they can contact me, for example).
  • This person can then grant publishing permission to the r-e-c/all team

I did not know you can transfer a repository to an org you do not belong to, though. The documentation seems a bit contradictory to me (you can transfer to anybody by writing their name and they get an email vs. you need permission to create repositories in the target org)

[jamesmunns]

@eldruin and @ryan-summers, is there anything we can do to get @eldruin's concerns addressed, and get this merged?

[ryan-summers]

Nope, I was out on vacation the last two weeks, which is why I wasn't touching it. Thanks for the reminder though, I'll review the requested changes and get this updated shortly.

[ryan-summers]

Alright, this should be ready for another read-through now. Thanks for the review (+ ping)!

[ryan-summers]

Sorry, there is a formatting mistake where the cargo owner command block is not properly closed due to it being from a review, where github apparently does not support triple quotes. Could you fix that manually?

Should be done. Interestingly, Github still rendered it properly with the formatting mistake. Thanks for pointing this out though, should be good now. Feel free to manually update the PR and merge if you'd like as well