Posted by Damon Young
Thu, 10 Apr 2008 22:37:00 GMT
We love feedback.
So much so, we even have an e-mail address soley dedicated to receiving the thoughts of our clients, called, unsurprisingly, feedback@projectlocker.com.
At this moment in particular, we would love to hear from all of our current clients with your thoughts on our hosted Subversion service. What do you love? What do you love less? What would you like to see changed?
Send us an e-mail. Let us know what you think.
Tags clients, control, current, hosted, SCM, source, subversion, SVN, version | 3 comments
Posted by Damon Young
Thu, 10 Apr 2008 19:08:00 GMT
While we're very big proponents of Subversion here at ProjectLocker, we also recognize that even the best tools and, consequently, the teams that use them can be crippled by the wrong development processes. With that in mind, here is an excellent article by Henrik Kniberg, a Certified Scrum Master with Crisp, a Stockholm-based Agile consulting firm. In it, he proposes a methodology to most effectively make use of your version control tool when applying Agile best practices in an environment with multiple & distinct teams working from common code base. Notice that he never mentions a specific version control tool, just a set of procedures and team protocols to help optimize the process. More details at the link below:
"Version Control for Multiple Agile Teams"
Watch this blog for more posts in the future on best practices and other development resources we think will help you build better software.
Tags agile, best, development, hosted, lifecycle, practices, scrum, software, subversion, SVN | no comments | no trackbacks
Posted by Damon Young
Mon, 17 Mar 2008 16:45:00 GMT
A recent entry at O'Reilly's OnLamp blog, entitled "Subversion for BSD With All the Bells and Whistles" described the time and effort that an experienced system administrator like Jeff Palmer had to take to install and configure a local instance of Subversion from scratch. In speaking with Jeff, he told me that it took up 2 days to make that first install, although now, he's probably cut the process down to 1.5 to 2 hours. In addition, he spends roughly an hour a week on maintanence.
A time savings, to be sure. But, a developer team could have access to a comparable instance of Subversion literally within moments of signing up from our website.
In addition to near instantaneous provisioning for most clients, ProjectLocker's user interfaces simplify the process of team and user management to such a degree that, for many of our clients, those tasks can be assigned to non-technical managers, freeing your more technical team members to concentrate on your most stubborn technical challenges.
It also doesn't take into account the time & materials required to both implement and maintain a backup & recovery strategy comparable to the one provided by ProjectLocker for all of our services.
Or the time saved on your development efforts by the speed of a ProjectLocker restore should such a disaster occur.
Or the flexibility of downloading backups on demand.
Or the convenience of receiving commit notifications in either Twitter or Jabber.
Or ProjectLocker's proprietary Subversion enhancements, like our Analytics tool.
In short, the time and expense your system administrators can save every day by choosing ProjectLocker is just the tip of our software quality iceberg.
Just something to consider.
Tags control, hosting, LAMP, O, Reilly, SCM, source, subversion, SVN, version | no comments | no trackbacks
