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

7 of 83 comments (clear)

  1. If this is not the first post... by Anonymous Coward · · Score: -1, Offtopic

    I will smear honey about my asshole and testicles and roll around on a fire-ants' nest. As always, links to pictures would be posted!

  2. News: David Carradine alive and well! Hoax death. by Anonymous Coward · · Score: -1, Offtopic

    Apparently Carradine was eaten by wolves on the Connecticut turn-pike. All reports say he was delicious.

  3. fst pst by Anonymous Coward · · Score: -1, Offtopic

    hihi

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

    And closed source code is always perfect?

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

  6. Re:all-your-code-is-ours by Anonymous Coward · · Score: -1, Offtopic

    By reading this post you hereby agree that all code written by you from now until the year 20009 belongs to me.

  7. OI thank you for your time by Anonymous Coward · · Score: -1, Offtopic

    goiNg to continUe,