Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC for moving cross to its own organisation #590
RFC for moving cross to its own organisation #590
Changes from 1 commit
e6dc25e
32c479d
07af85f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any work needed to be done before transferring?
I can imagine cutting out some mentions of the Tools Team/EWG in various parts.
Should authors in cargo manifest still mentions EWG? Or can the full field be dropped? (the field is optional in newer rust)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we should update the README to indicate that while the project used to be maintained by the WG, it no longer is. I don't mind about the
authors
field, perhaps simplest to remove it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What role is a
maintainer
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean people with access to merge PRs into the repo, and perform other maintenance tasks like labelling and closing issues etc. Perhaps it should also include publishing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some volunteers [...] could be added [...] and eventually
what does this mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, it's quite vaguely worded because I don't know exactly how we'd want this to look. I expect we'd initially add some volunteers from that call-for-help thread (after chatting to them of course) who could review and merge PRs, and possibly also publish to crates.io, and then over time expect to grant org ownership too once it's had more time to settle down.