Skip to content
This repository has been archived by the owner on Jul 10, 2021. It is now read-only.

Tracker document to record status of repo audits, contact responses, and migrations so that move to rust-lang org can be completed #30

Closed
valgrimm opened this issue Dec 3, 2019 · 8 comments
Labels
C-Tracking Tracking on a specific topic

Comments

@valgrimm
Copy link
Contributor

valgrimm commented Dec 3, 2019

META
Originating issue: #4
Orginating meeting: https://hackmd.io/T-KVGkNfQpipFmTUiwS8tQ?both
HackMD: https://hackmd.io/wdJIYSUCTCWKoAfu3y8Q0w?both

@XAMPPRocky XAMPPRocky added Infrastructure C-Tracking Tracking on a specific topic labels Dec 4, 2019
@valgrimm
Copy link
Contributor Author

valgrimm commented Dec 4, 2019

Document complete and ready for use.

@XAMPPRocky
Copy link
Member

Thank you, this is great! @nikomatsakis What do you think about, we send all those repos with one more ping, and after the next meeting (~2 weeks) we transfer whatever ones are remaining?

@valgrimm
Copy link
Contributor Author

valgrimm commented Dec 6, 2019

@XAMPPRocky @nikomatsakis Hi, do you need any help updating the document? If you need to you can forward a bunch of the email responses you receive my way and I can update the document accordingly.

@XAMPPRocky
Copy link
Member

@valgrimm Hey, I haven't gotten around this yet. What I'll do is make time to create similar issue for working groups to the team tracking issue rust-lang/team#146 and then ping the remaining teams and then use your document to track the responses. Since we could get responses from GitHub, email, discord, or some other service.

@valgrimm
Copy link
Contributor Author

valgrimm commented Dec 6, 2019

@XAMPPRocky Ah ok, good to know. I could help create issues and, if it would be ok, track the responses on Github. Would that be helpful? I'd have volunteered to do more earlier, but I was trying to identify a gap where I could contribute, as I know this is a situation where known people need to do the actual notifying.

@XAMPPRocky
Copy link
Member

XAMPPRocky commented Dec 6, 2019

@valgrimm There's always more work, but you shouldn't feel any pressure to contribute more than you feel you're able to. You could go through the rust-lang-nursery and other organisations that we mentioned in the minutes and the issue. And make an issue for any that don't already have issues for them. All of the issues I created look like this with the same title so it should be easy to find an issue if it exists. rust-lang-nursery/rust-cookbook#558

@valgrimm
Copy link
Contributor Author

valgrimm commented Dec 6, 2019

Thank you @XAMPPRocky, for all of the above (: And I'll get to some of that creating issues this evening after work (CET), if there are any left.

@XAMPPRocky
Copy link
Member

Superceded by #50

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C-Tracking Tracking on a specific topic
Projects
None yet
Development

No branches or pull requests

2 participants