View Single Post
Old 10-31-2013, 06:01 PM   #18
knc1
Embedded Cheerleader
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,523
Karma: 5840130
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by eureka View Post
Version control is useful anyway, even if you're developing you project alone. In this case, Github or Bitbucket is just a public backup of your personal repository. If development will stall or you will lose interest in development (it happens), someone will be able to take this backup and continue development history. And if you'll continue development infinitely, public repository will serve as entry point to contributing (though it never happens ) with well-known and convenient workflow (opposing to attachment hell).




To the topic: did I ever recommend something inherently wrong?
Both systems allow you to mark the repository as 'private'

Then it is mostly just a backup of your local work in case you "twobob" your local disk drive. [**]

Ah - I think that both systems allow you to "share" access to your private repositories to a small group of people.

[**] will be teaching about RAID arrays in next semester's course materials.
knc1 is offline   Reply With Quote