Code of Conduct: Open Source

Posted by omarshammas on Monday December 10, 2012 @04:52PM
from the mahdiyusuf.com dept.

( 4 comments | 15 points | on HN )

Re:Code of Conduct: Open Source by talmirza on Monday December 10, 2012 @05:04PM (#4901764)

I have written a lot of code for OS that doesn't get committed into master.

I was wondering what I could do to improve my code written to code committed ratio.

Still open to suggestions.

[ Parent | on HN ]

Re:Code of Conduct: Open Source by jff on Monday December 10, 2012 @05:27PM (#4901863)

Write highly detailed commit messages.

Email the owner to discuss what you're adding and why, especially if it's a big thing.

Keep your commits small--nothing worse than a mega-commit which fixes 3 different bugs and updates the formatting for 10 files.

Make sure to follow the project's formatting and naming conventions.

[ Parent | on HN ]

Re:Code of Conduct: Open Source by jeremyjh on Monday December 10, 2012 @05:39PM (#4901911)

Also make sure you update and add relevant tests and documentation.

[ Parent | on HN ]

Re:Code of Conduct: Open Source by jonchang on Monday December 10, 2012 @05:15PM (#4901817)

The pull request referenced in the post can be seen here: https://github.com/twitter/bootstrap/pull/6127

[ Parent | on HN ]