Title: CVS Access
Last modified: August 18, 2016

---

# CVS Access

 *  [drummonds](https://wordpress.org/support/users/drummonds/)
 * (@drummonds)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/cvs-access/)
 * What is the policy for gaining CVS access (r/w access as a developer, not just
   anonymous CVS) to fix bugs? This morning I submitted what is undoubtedly a trivial
   bug (extra escaping of special characters) and I wonder if the developers would
   rather have someone that fixes things himself than just submit. I have the time
   to address some of the other smaller issues, too.
 * Given that there are so few developers on the project, something tells me the
   answer is _no_. But, hell, I thought I’d ask.
 * Scott

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [NuclearMoose](https://wordpress.org/support/users/nuclearmoose/)
 * (@nuclearmoose)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/cvs-access/#post-130375)
 * From the contact page:
    “If you’re interested in contributing your time to the
   project, be it through documentation, code, support, or evangalism, contact [helpout@wordpress.org](https://wordpress.org/support/topic/cvs-access/helpout@wordpress.org?output_format=md).”
 * Many coders have submitted proposed code fixes, usually in the form of patches,
   and they are evaluated and may be accepted and applied.
 *  [Mark (podz)](https://wordpress.org/support/users/podz/)
 * (@podz)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/cvs-access/#post-130376)
 * Try an email to m at this domain.
 *  [Kitten](https://wordpress.org/support/users/kitten/)
 * (@kitten)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/cvs-access/#post-130379)
 * Also, if you’re fixing something, there’s a good chance that you’re not the only
   one w/ the problem.
 * Check mosquito, and file a bug if it’s not been reported. Then upload your patch
   to the appropreate bug report so that devs and others can find it.
 * This is the best way, because not all the devs get the helpout@ emails, so if
   you’ve scratched someone’s itch, it’ll get committed straight from the bug report.
 *  Thread Starter [drummonds](https://wordpress.org/support/users/drummonds/)
 * (@drummonds)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/cvs-access/#post-130390)
 * Thanks to all! I think the patch/submit route is a great place to start.
 *  Moderator [Matt Mullenweg](https://wordpress.org/support/users/matt/)
 * (@matt)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/cvs-access/#post-130395)
 * For obvious reasons we try to keep the number of people with write access to 
   the repository to a minimum, but filing a bug report is probably the best way
   to go.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘CVS Access’ is closed to new replies.

 * In: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/)
 * 5 replies
 * 5 participants
 * Last reply from: [Matt Mullenweg](https://wordpress.org/support/users/matt/)
 * Last activity: [21 years, 7 months ago](https://wordpress.org/support/topic/cvs-access/#post-130395)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics