I'm not sure how the risk here is worse than the risk of using any cloud service at all. If some attacker steals your password, they can destroy your picasaweb photos, your docs within Google Docs, delete your gmails, delete your g-calendar appointments, etc.
And the risk isn't specific to cloud services either. Even if you set up your own private server in a datacenter, an attacker could still hack the system and erase the machine. So the recommendation to 'back up' is a universal one: if you have valuable data, it's your responsibility to make sure it exists in more than one place. For subversion in particular, you can create a local mirror of a server's repository using the 'svnsync' tool. Just run svnsync every day to keep the mirror up to date. On Mon, Nov 15, 2010 at 3:32 PM, calin <[email protected]> wrote: > nobody during google lifetime would have the right to delete a project > > owner may close project > > if storage is a burden the last committed version is archived > > a closed project gets renamed and original name is free for other > owner to claim > > this setup would remove a taunting thought > > committing code to googlecode would be considered a backup > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
