I'm interested in your most highly recommended service provider for a hosted Revision Control System, Considering the age, and size of my local Subversion repository, and my adequate proficiency with Subversion, I believe it's most sensible for me if I find a service provider which supports Subversion. I have used GIT-- for Windows, i think-- but only for some unremarkable export / checkout operations.

As the reader might suspect, I'm familiar with SourceForge, GITHub, and during a cursory perusal of G-results (for "hosted revision control system"), I found this summary article effectively provides insight into seven ( 7 ) Revision Control System software options (including CVS, Subversion and GIT). From there, I glanced at Beanstalk.

I have experience with hosted version control from ActiveState Firefly. I'd still be there, but it seems to have vanished, without notice, and without a trace. firefly.activestate.com, the commercial / no-cost (with restrictions) service was-- like SourceForge-- powered by Trac (tweaked with ActiveState branding). I expect a Trac-based, Subversion provider might present the least pain in transition.

Obviously, it's a lot to digest. Pondering, “... where can I get quality advice about hosted version control!?...”, it occurred to me-- I haven't been to phpbuilder.com in a long while! I figure there are users here who have experience with hosted revision control.

What have you to say about this topic?

    ATS16805 wrote:

    Considering the age, and size of my local Subversion repository, and my adequate proficiency with Subversion, I believe it's most sensible for me if I find a service provider which supports Subversion.

    Proficiency with Subversion is certainly a factor to consider. The fact that you have an existing Subversion repository is also important, but only if you intend to replicate this repository to the host. If you are starting a new project with no history, or if you are not going to port over the history to the host, then this is a moot point.

    You might also want to tell us if this repository needs to be private, and if you are working on it alone, with another person, or with several other developers. Their own knowledge and preferences should also be taken into account.

    ATS16805 wrote:

    I have used GIT-- for Windows, i think-- but only for some unremarkable export / checkout operations.

    As the reader might suspect, I'm familiar with SourceForge, GITHub

    My preference is for distributed version control. The access to full version control functionality even when offline or when it is inconvenient to access the main repository appeals to me. My personal preference is Bazaar, but as you have experience with git I would urge you to consider git. (Though in my opinion a transition from Subversion to Bazaar is likely to be easier if your experience with git is really minimal.) GitHub should be acceptable... what do you find lacking that made you consider other options?

      a month later

      Hi, laserlight. It's a pleasure to communicate with you again. Thank you for your input on this topic.

      I didn't just fire off a reply here because, as concise as it is, laserlight's skillful reply contains several points of interest for me, where i'd like to present further inquiry-- but, i'd better concede and just reply while i'm here!

      hmm.... trying to remember how it's done; to figure a way of outlining my reply... and, i've been away from forums such as this for quite a while. (i.e. please forgive the chiken-scratch)

      1. laserlight <> “...port over the history...”
        ats16805 <> I'm not sure what it means to "port over the history". Using my own vocabulary, and extrapolating, ('cause i ain't hip to no smooth jive, turkey!) i'm guessing it's as to synchronize my repo, and the various revisions, from my local store to the service providers storage?

      2. laserlight <> “If you are starting a new project with no history, or if you are not going to port over the history”.
        ats16805 <> I can't get my head around precisely why such a circumstance would render moot, the issue of version-control service providers. Can you help me with that? (i.e. i didn't do that with ActiveState Firefly, i don't think, yet I still found familiarity at the Subversion-level to be helpful... e.g. i knew i needed to commit new "finished" code, vs... say import, or "add" it...)
        I'm pretty sure i Didn't copy my local repo to Firefly-- just merely "imported" it, as to recursively copy the contents of a singular container (i.e. upload the folder / contents of whatever is my source code [e.g. where wordpress == ./wp ./wp/wp-admin ./wp/wp-plugins ./wp/wp-etc] ) ... i forget the SVN command wait-- svnsync? hmmm...

        SVNSYNC -- i didn't look-it-up-- because i can't-- but this has jogged-the-memory: I recall an initial process now... i recall it seemed like nothing happened, but something to sort-of format, or initialize my so-called Project space there, for using Subversion, etc. I don't think any files were transferred-- because i wasn't ready for that, at the time.

        I definitely recall, among the very first actions i did w/ SVN at Firefly, there was a one-time use of an SVN cmd unfamiliar to me at that time; outside of the common-to-me cmd's, like update, commit, etc.

      3. laserlight <>laserlight “if this repository needs to be private...other developers' preferences taken into account”
        This doesn't really apply to me at all. I'm glad you brought it up, however, as it adds value to this thread as a resource on the topic of hosted version control (it's unfortunate, however, my poor forum skills do as much to diminish it)

      Before closing, let me address another dynamic of of Hosted Version Control:
      Laserlight summarizes, expressing an affinity for Distributed Version control, for having the ability to access “full version control functionality”. This pretty much just blows my mind-- i mean, i think my inexperience with Version Control altogether is made more clear by my reaction to this concept. I think i'd need to examine some diagrams, and actually involve myself, for example, with some example repo mgt with GIT / GIThub (if i understand it's a Distributed type), if i'm to understand this concept. Trying to do so, from my current point of view-- i just feel really stupid-- i'm wearing a rubber helmet, repelling all intelligent concepts...

      [font=smaller]I apologize for such delay in my own reply. I composed a draft in reply-- honest-- but must have shut-down the browser, restarted the sys, or... murphey's law, inevitably. [/font]

        ATS16805 wrote:

        I'm not sure what it means to "port over the history". Using my own vocabulary, and extrapolating, ('cause i ain't hip to no smooth jive, turkey!) i'm guessing it's as to synchronize my repo, and the various revisions, from my local store to the service providers storage?

        No, I mean that you currently have a Subversion repository. Now, you want to use Bazaar or some other version control system besides Subversion, while copying as much of your existing history from your Subversion repository as possible into your new Bazaar/etc repository.

        ATS16805 wrote:

        I can't get my head around precisely why such a circumstance would render moot, the issue of version-control service providers. Can you help me with that?

        Such a circumstance would not render moot "the issue of version-control service providers". It would render moot the fact that you currently have a Subversion repository with history.

        ATS16805 wrote:

        I definitely recall, among the very first actions i did w/ SVN at Firefly, there was a one-time use of an SVN cmd unfamiliar to me at that time; outside of the common-to-me cmd's, like update, commit, etc.

        You probably initialised the repository.

        ATS16805 wrote:

        Laserlight summarizes, expressing an affinity for Distributed Version control, for having the ability to access &#8220;full version control functionality&#8221;. This pretty much just blows my mind-- i mean, i think my inexperience with Version Control altogether is made more clear by my reaction to this concept. I think i'd need to examine some diagrams, and actually involve myself, for example, with some example repo mgt with GIT / GIThub (if i understand it's a Distributed type), if i'm to understand this concept. Trying to do so, from my current point of view-- i just feel really stupid-- i'm wearing a rubber helmet, repelling all intelligent concepts...

        You could browse through the Bazaar user guide.

          Write a Reply...