Gotcha. I'll get with the plan. 4est
On Aug 26, 11:01 am, Josh Clayton <[EMAIL PROTECTED]> wrote: > 4est, > > Due to the open-source and collaborative nature of this project, > GitHub was decided upon to house the new repository to encourage > branching, collaboration, and development on BlueprintCSS, which was > previously stagnant for about six months. Again, seeing many other > fine open-source frameworks (such as Rails, Prototype, and Merb) and > the lack of decent branching/merging capabilities of Subversion caused > this change. > > Github makes it easier to see what development occurs by displaying a > list of commit messages as well as displays all branches/tags in a > concise manner. It provides much more to the end-user than SVN, which > has a higher learning curve (IMO) and doesn't allow for the > collaborative abilities (branching) without serious strain on the > developer. > > If you're struggling with Git, I suggest visitinghttp://git-scm.com/. > There are numerous resources that will help users unfamiliar with git > and it's presented in a friendly way. > > Cheers, > Josh > > On Aug 26, 10:30 am, 4est <[EMAIL PROTECTED]> wrote: > > > As a relatively inexperienced Blueprint user and definitely not super- > > savvy developer, I'm wondering why the Blueprint project is split > > among three (as I count) different development services. Can't > > everything reside at Google? Or SourceForge? Maybe I'm an idiot, but > > Github seems less friendly to this user. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Blueprint CSS" 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/blueprintcss?hl=en -~----------~----~----~----~------~----~------~--~---
