Software Developing: SnipSnap, SnipIt and SnipSnip

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.