subversive

(adjective)

Intending to subvert, overturn or undermine a government or authority

Related Terms

Examples of subversive in the following topics:

  • Example Instructions for Reporting Bugs

    • This is a lightly-edited copy of the Subversion project's online instructions to new users on how to report bugs.
    • * If the bug is in Subversion itself, send mail to users@subversion.tigris.org.
    • Subversion, right?
    • * The version of Berkeley DB you're running Subversion with, if any
    • That is, say how you expected Subversion to behave, and contrast that with how it actually behaved.

  • Sources

    • Much of the raw material for the first edition of this book came from five years of working with the Subversion project (subversion.tigris.org).
    • Subversion is an open source version control system, written from scratch, and intended to replace CVS as the de facto version control system of choice in the open source community.
    • Subversion is in many ways a classic example of an open source project, and I ended up drawing on it more heavily than I originally expected.
    • This was partly a matter of convenience: whenever I needed an example of a particular phenomenon, I could usually call one up from Subversion right off the top of my head.
    • If someone were to try that with Subversion, I knew, she'd be right about half the time and wrong the other half.

  • Choosing a Version Control System

    • Two other reasonable choices of version control system are Mercurial and Subversion.
    • Mercurial and Git are both decentralized systems, whereas Subversion is centralized.
    • If you find yourself using something other than Git, Mercurial, or Subversion, ask yourself why — because whatever that other version control system is, most other developers won't be familiar with it, and it likely has a smaller and less stable community of support around it than the big three do.

  • Money Can't Buy You Love

    • A perfect example of this came up early in the Subversion project.
    • Subversion was started in 2000 by CollabNet, which has been the project's primary funder since its inception, paying the salaries of several developers (disclaimer: I'm one of them).
    • Although Subversion was still very much in the early stages, it already had a development community with a set of basic ground rules.
    • Subversion already had a policy about how a new developer gets commit access.
    • CollabNet had hired Mike specifically to work on Subversion.

  • Case Study

    • I would say that five of these people are contributing to Subversion hitting 1.0 in the near future.
    • I would also say that one of these people is consistently drawing time and energy from the other 5, not to mention the list as a whole, thus (albeit unintentionally) slowing the development of Subversion.
    • I did not do a threaded analysis, but vgrepping my Subversion mail spool tells me that every mail from this person is responded to at least once by at least 2 of the other 5 people on the above list.
    • dev@subversion is a mailing list to facilitate development of a version control system, not a group therapy session.

  • Introduction to Setting the Tone

    • I chose these particular examples because they came up in the Subversion project (subversion.apache.org), which I participated in and observed from its very beginning.
    • But they're not unique to Subversion; situations like these will come up in most open source projects, and should be seen as opportunities to start things off on the right foot.

  • Mechanics of Release Branches

    • While I can't show the exact commands for every version control system, I'll give examples in CVS and Subversion and hope that the corresponding commands in other systems can be deduced from those two.)

  • Free Version Control Systems

    • The ones I use on a regular basis are Subversion and Git, and I have used Bazaar and CVS extensively as well.
    • One of Subversion's goals is for people already accustomed to CVS to find the transition to Subversion relatively smooth.
    • [Disclaimer: I am involved in Subversion development, and it is the only one of these systems that I use on a regular basis.]
    • Although it is built on top of Subversion, SVK probably resembles some of the decentralized systems below more than it does Subversion.
    • [Disclaimer: I was active in CVS development for about five years, before helping to start the Subversion project to replace it.]

  • Avoid Mystery

    • In the Subversion project, we put this information right in the developer guidelines document, since the people most likely to be interested in how commit access is granted are those thinking of contributing code to the project.

  • Acknowledgments

    • Thanks to Greg Stein not only for friendship and well-timed encouragement, but for showing the Subversion project how important regular code review is in building a programming community.
    • The entire Subversion development team has been an inspiration for the past five years, and much of what is in this book I learned from working with them.
    • I won't thank them all by name here, because there are too many, but I implore any reader who runs into a Subversion committer to immediately buy that committer the drink of his choice—I certainly plan to.