Skip to content
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.

Sign up for GitHub

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

Jump to bottom

No credits for people not writing code #25

Open
GoogleCodeExporter opened this issue Apr 8, 2015 · 1 comment
Open

No credits for people not writing code #25

GoogleCodeExporter opened this issue Apr 8, 2015 · 1 comment
Labels
Area-Process Priority-P3 Type-Bug

Comments

@GoogleCodeExporter
Copy link
Contributor 

What steps will reproduce the problem?
People who are investigating and reporting problems don't get attribution in 
Python development.

What is the expected output? What do you see instead?

1. Expected to adopt Subversion community guide for crediting 
http://subversion.apache.org/docs/community-guide/conventions.html#crediting
2. Perhaps provide convenient tools for crediting process if it places too much 
burden on committers

Original issue reported on code.google.com by [email protected] on 13 Nov 2012 at 3:02
@GoogleCodeExporter
Copy link
Contributor Author

Original comment by [email protected] on 13 Nov 2012 at 3:02

  • Added labels: Area-Process

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Process Priority-P3 Type-Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@techtonik @GoogleCodeExporter