-
Notifications
You must be signed in to change notification settings - Fork 1.3k
How should we list contributors in Cargo.toml(s)? #1094
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
Comments
As I wrote a fairly large portion of the code, I don't mind being put as author. I prefer however something like rustpython team or something like that. Is this possible? |
As package names I would prefer this:
|
I propose to release rustpython-parser as the first package, since this is the least changing one. |
I think we could, maybe something like: authors = ["RustPython contributors <github.com/RustPython/RustPython/contributors>"] |
I propose: authors = ["RustPython Team"] |
Sounds good to me! |
I'll make a PR for this. |
Unscribe me
…On Wed, Jul 3, 2019, 12:48 PM coolreader18 ***@***.***> wrote:
Closed #1094 <#1094>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1094?email_source=notifications&email_token=AMLSORXQ7WOLXBVZZKQQFJTP5TJ5ZA5CNFSM4H4NT5R2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSKCU3EI#event-2458209681>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMLSORQTFDUUWTCNVCOU7FLP5TJ5ZANCNFSM4H4NT5RQ>
.
|
There's a link at the bottom of this email for you to unsubscribe, I'll put it right here too: https://github.com/notifications/unsubscribe-auth/AMLSORQTFDUUWTCNVCOU7FLP5TJ5ZANCNFSM4H4NT5RQ. |
Now that we're going to start publishing our crates (#838), how what should we put for
authors
in theCargo
s.toml
? All the crates have different authors listed, usually just whoever first created that package. What should we change them to to keep them consistent across everything? Relevant section in cargo docsThe text was updated successfully, but these errors were encountered: