Software Developing: SnipSnap, SnipIt and SnipSnip 
It has been a while since I write something regarding
SnipSnap or SnipIt - readers interested in SnipIt should read
Software_Developing:_SnipSnap_and_Snip_It. Today I'll be writing about a new project called
SnipSnip.

As I already wrote - see
SnipSnap_Developing:_Planning_a_fork - SnipSnap development has ceased. Besides the announcement made in Stephen's personal blog a
public announcement in snipsnap.org was made.
Even though snipSnap users aren't as many as the ones in popular blog platforms such as
wordpress they all know the great potential SnipSnap has. That lead to some of the users - including me - suggesting that the development should be brought to the community. Among those users was Angelo Schneider (
aos at snipsnap) who after the announcement created a project on sourceforge called SnipSnip.
Currently SnipSnip, for what I know, only contains the latest snipsnap source code, which in my opinion is lacking some essential features for nowadays blogging. I've already sent an email to Angelo and posted on snipsnip's forum showing my interest in contributing with my fork to the project - yes I'm suggesting a merge. Until the moment I've not received any reply from the current snipsnip team.
Thinking in a possible merge leaves a question, what will happen to SnipIt. Most probably I'll keep developing in SnipSnip instead, unless there's some conflict of interests between the way I see SnipIt - a blog tool with wiki capabilities - and the way the snipsnip team sees their project.
I also take the chance to say that I've been doing a few more modifications in SnipIt code, mostly regarding integration with other web applications such as
feedburner,
google webmasters,
google analytics and support for configure which
social web sites (del.icio.us, digg, dzone, etc) are available in blog posts.
My contribution roadmap - in SnipIt or SnipSnip - is mostly described in
my_snipsnap_fork_feature_list with the addition of a few other ideas, such as, the possibility of creating more than two portlets or having support for access control based on user groups besides user roles.
I suggest you join.Best regards,
Paulo
- Set up a project (the name SnipSnap is still available on java.net - no need to deal with angel-o-sphere regarding the sourceforge project) and configure the project tools
- Add sources: We should start with your fork
- There should be an initial release containing your improvements. The improvements should be documented and outlined
- We should come up with a road map - this should attract developer and a community (it shows that the project is going to get up to speed).
- Look for references to SnipSnap on snipsnap.org and elsewhere and tell people that they already missed the project re-launch

I'm not only interested in SnipSnap as an application but I would like to gain more experience in running a community project. This will probably some contrast to the professional projects I'm involved withAlso any of you know anyone else interested? I also need to document every feature I've added, need to check all my logs but that won't be hard to do.It seems we are putting up a team to make SnipSnap start from its ashes, let's see if this time works… I think your suggestions regarding the initial work are good so, shall we go for it?
- Code related
Obviously this will be your part mostly - you have the code and you know it (at least better than anyone else currently involved).- We should bring the latest "official" sources of SnipSnap to our repository.
- We add your modifications
- Project related
In my professional projects I deal a lot with build infrastructure (e.g. Maven). Therefore I will take care of this. This will include setting up the project at java.net, create a subversion repository, bug tracker, mailing list etc.I would like to emphasize that we should only advertise for the project once we have things up and running. At least you and I will have to spend some time to get this work done. I have to admit that I don't know the time frame of this initial work but would expect it to be about 1-2 months (this is a leisure activity, not a full-time job).I will prepare the project set-up and then come back to you.AxelBefore you start getting the code to built we should be sure about the version of the code. I would start from one of the last "official" releases (probably 1.0b3-uttoxeter). Is this the version of the source code you have?Axel
I'll be replying all previous posts in one, hope you don't mind.Couldn't agree more the 1st version should be uttoxeter. I've done the same thing on my private SVN, so it won't be a problem neither having the "official" source not committing a patch.Regarding the build infrastructure you think it's an improvement changing from ant to maven. If so, could you please elaborate a bit on why? In all the projects I work I use ant, except when I need to build
- right click on project and select properties
- Select java build path on the right menu
- select Libraries
- Remove all the libraries listed there (except the JRE System Library)
- Select add Jars and browse into the SnipSnap's lib directory and add them all
You should be set to compile it in eclipse if you want.I've forked SnipSnap 1.0b3-uttoxeter.The data schema is still the same. I had that concern because, since I knew data migrations would just make people unease to change to my fork- Nick.
PS: should we take this to the code.google.com mailing list?Thanks for all the source digging Nick!
Well I'm gonna join java.net and put in also a request to join snipsnap.