[DRIVERS-116] Driver projects should have developer guides Created: 20/Aug/13  Updated: 15/Apr/19  Resolved: 22/Jun/16

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Bernie Hackett Assignee: Barrie Segal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on RUBY-684 Create a public developer guide Closed
depends on CXX-70 Update README and CONTRIBUTING.rst in... Closed
depends on MOTOR-50 Motor developer guide Closed
depends on CDRIVER-173 Support github contributing guidelines Closed
Related
related to PHPLIB-140 Missing CONTRIBUTING.md Closed
related to PYTHON-859 PyMongo developer guide Closed
Driver Compliance:
Key Status/Resolution FixVersion
RUBY-684 Done 2.0.0
MOTOR-50 Done
CXX-70 Done legacy-0.0-26compat-2.6.0-rc0
CDRIVER-173 Done 0.7

 Description   

A few of our driver projects have extensive documentation about getting started as a new developer (best practices, style guides, how to do code reviews, tools to use, etc.). All of the driver projects should have similar developer guides. This is important to not lose institutional knowledge when developers leave, and helps with interns and new grad engineering rotations.


Generated at Thu Feb 08 08:20:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.