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.

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

Create a "Developer Guidelines" section in wiki for code contributions #12

Open
frhino opened this issue Jan 12, 2019 · 2 comments
Open
Assignees
Labels
documentation help wanted Extra attention is needed

Comments

@frhino
Copy link
Collaborator

frhino commented Jan 12, 2019

No description provided.

@frhino
Copy link
Collaborator Author

frhino commented Jan 12, 2019

I'm sure there's a universe of considerations I'm not aware of, but I'm thinking along the lines of line indents, naming conventions for folders, files, functions and variable, max line length, comments requirements. What should new members know before making their first pull request? What should they expect in terms of code review process?

@frhino
Copy link
Collaborator Author

frhino commented Jan 12, 2019

There's great best-practices advice in this paper I'd like to see included for my own quick reference.

@frhino frhino added this to Documentation in Onboarding and Documentation Jan 12, 2019
@frhino frhino added the help wanted Extra attention is needed label Mar 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation help wanted Extra attention is needed
Projects
Development

No branches or pull requests

4 participants