Repos
    Proj1
        trunk
            lib
            t
        tags
        branches
    Proj2
        trunk
            lib
            t
        tags
        branches
  ...

[download]

This is how I structure my CPAN stuff, what OpenJSAN has migrated to (at my request), and how my employer structures both our OSS and work repositories. It's simply the easiest layout to work with, imho. Even if you never branch in most projects, you'll branch in one and you'll be happy for the consistent layout. Tagging should be done early and often, especially as tagging is O(1) in SVN. I generally tag every 4-10 commits in my CPAN projects. Anything more than that and you are probably looking at a complete rewrite, not a point release.

As for migration - that's a non-issue. SVN can migrate to and from nearly every major SCM out there. Plus, how often are you really migrating from one SCM to another - isn't this just a straw man?

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: How to structure your svn/svk repository by dragonchild
in thread How to structure your svn/svk repository by badaiaqrandista

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.