• 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.


Viewing 5 replies - 1 through 5 (of 5 total)
  • 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.”

    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)


    Support Maven

    Try an email to m at this domain.

    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.

    Thanks to all! I think the patch/submit route is a great place to start.

    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.