I'm happy to see interest from others on contributing to this library and helping Marc alone keeping up with maintenance on SPServices. Sounds like we are really going to see FOSS at work here... :)
Re: Codeplex -vs- Github
My opinion here will be bias... I started using Github less than 1 year ago and am really liking it - mainly (as @marktiderman mentioned above) because the workflow there is very good... note that it has nothing to do with GIT itself, but rather the workfow that github has built around git itself. That being said, I am opened to using GIT here in codeplex... (does anyone know if mentions of issue items in commits automatically update the issue itself?)...
I also agree with @Rainer and @tstojecki on KISS... As the size/functionality grows, simplicity will need to be maintained with the help of scripts/build tools (take a look at the jQuery grunt file). Example, most of my build scripts do at a minimum the following:
And lastly... @sympmarc : I would not dismiss your statement above "You're all going to be helping much more with SPServices" - That was my intent on initiating this threat... its a calling to the community to participate and contribute... in my opinion, given the quick responses received thus far, I say we may be up to a good start. At some point, you may really want to put this to the test by drafting a plan (I can help) and come up with a list of tasks that should be done in order to setup all of this... let's highlight the areas we (the community) can help with and see how many answer the calling...
One last word on my personal usage of git... I do, from time to time, use it from the command line, but have found that most of the common tasks are done just fine using a GUI (I use aptana for eclipse, which includes a GUI for it, as well as a command line shell).
Paul.
Re: Codeplex -vs- Github
My opinion here will be bias... I started using Github less than 1 year ago and am really liking it - mainly (as @marktiderman mentioned above) because the workflow there is very good... note that it has nothing to do with GIT itself, but rather the workfow that github has built around git itself. That being said, I am opened to using GIT here in codeplex... (does anyone know if mentions of issue items in commits automatically update the issue itself?)...
I also agree with @Rainer and @tstojecki on KISS... As the size/functionality grows, simplicity will need to be maintained with the help of scripts/build tools (take a look at the jQuery grunt file). Example, most of my build scripts do at a minimum the following:
- Generate developer jsDocs (javadoc type of stuff)
- Generate user documentation (I used to do it with NaturalDocs, I now use Markdown)...
- Create minified version of library file(s)
-
Create a distribution package (zip file with source, documentation and minified versions)
And lastly... @sympmarc : I would not dismiss your statement above "You're all going to be helping much more with SPServices" - That was my intent on initiating this threat... its a calling to the community to participate and contribute... in my opinion, given the quick responses received thus far, I say we may be up to a good start. At some point, you may really want to put this to the test by drafting a plan (I can help) and come up with a list of tasks that should be done in order to setup all of this... let's highlight the areas we (the community) can help with and see how many answer the calling...
One last word on my personal usage of git... I do, from time to time, use it from the command line, but have found that most of the common tasks are done just fine using a GUI (I use aptana for eclipse, which includes a GUI for it, as well as a command line shell).
Paul.