Slashdot Mirror

← Back to Stories (view on slashdot.org)

One Approach To Open Source Code Contribution and Testing

Posted by timothy on from the treat-warnings-as-errors dept.

An anonymous reader writes "Brian Aker, one of the core developers of MySQL, has written up a lengthy blog on how the Drizzle fork is handling both its code contributions and its testing. He has listed the tools they use and how they work with their processes. He also makes an interesting statement about the signing of corporate code-contribution agreements and how there are some, including Rasmus (creator of PHP), who refuse to sign them."

2 of 83 comments (clear)

  1. Re:Here's my approach by Vuojo · · Score: 0, Offtopic

    And closed source code is always perfect?

  2. Re:Here's my approach by protologix · · Score: 0, Offtopic

    Too true. Of course, the biggest difference is that the open shit doesn't try to sue you.