Inside Paulo Abrantes' head
[ start | index | login or register ]
start > 2007-04-07 > 1

SnipSnap Developing: Planning a fork

Created by pabrantes. Last edited by pabrantes, 3 years and 149 days ago. Viewed 3,005 times. #5
[diff] [history] [edit] [rdf]
labels
attachments

SnipSnap Developing: Planning a fork

Like the title is saying I'm planning to go for a fork.
There are various reasons for doing such move, but here are a few (and probably also the strongest ones):
  1. The development is stopped;
  2. The SVN is dead;
  3. Stephan as >>announced is retirement from snipsnap;
  4. SnipSnap as been my pet-project for more than a year;
  5. I think I can do a good job.
Currently I have no name for the fork, snipsnapNG - where NG stands for Next Generation - just sounds too lame… Any suggestions for the name?

I've already started a >>SVN repository, the code is being released under GPL. Since it supports anonymous read access, anyone interested can download my snipsnap version from there. Besides all the modifications I've been mentioning in my posts, I felt like giving some goodies for this first SVN release, so the additional features are:

  • Security Fix against XSS on the Search Macro
  • Security Fix regarding config snip (which can be accessed via diff or version servlets by anyone)
  • Integration of Digg It feature
  • Integration of Del.icio.us feature
  • Integration of RSS comments for each snip features
  • Configurability of the last three points, the user can select if it's interested or not to have each feature.
The digg it, delicious and rss comment features can be now seen in my blog, at the upper right corner of each snip, or posts in case of displaying a weblog snip. To add or remove each one of them is so simple has toggle a feature on config snip to true or false.

I'm planning not only in deliver more features but also refactor some code that I've already seen. Not that I think Stephan and Leo didn't do things good, but mostly because I want things on my way.

Features to be implemented include:

  • Configurable snapPreview integration
  • Configurable meta-information
  • Configurable Access Control for each snip
  • Configurable secure login and register
  • Better CATPCHA Support (that includes sound support)
  • Many other, keep tuned to know about them.
If anyone has any suggestions to improve this version of snipsnap, please comment!
67 comments (by pabrantes, AdaHsu, derjohn) | post comment
Who am I?
paulo-roca2My name is Paulo Abrantes AKA pabrantes and I'm a software developer. I'm currently employed at >>CIIST working as a Java developer in >>FenixEDU.

This blog is mostly about Java programming, domain driven design and snipsnap bliki developing. Everything written in this blog is my personal opinion and it may not reflect the opinions of my employer and co-workers.


Blog subscription
subscribe by rss subscribe by email

Links
>> Home
>> Paulo's Profile
>> Post History
>> Add to Technorati Favorites
>> Paulo's Photo Gallery
>> WishList
>> Posting without Login

Search Blog
Fellow Bloggers

Recent Posts

Blog: Almost an year since last post
Java Programming: Bytecode Injection
Intermission: Sorry For Downtime
Software Developing: Studying The Bliki Domain Model
SnipSnap Developing: Trying to settle a roadmap
System Administration: Load Balancing with Apache
Blogging: Two years have passed
Software Developing: The SnipSnap Saga
Java Programming: Getting your code spicy with Groovy
Software Developing: Fluent Interfaces
Software Developing: Implementing a ShoutBox on SnipsSnip
Software Developing: SnipSnap, SnipIt and SnipSnip
Java Programming: Proxies and Access Control
Java Programming: Proxies and References
Java Programming: References' Package

For older posts, please refer to post-history for a complete Post History

Logged in Users: (0)
… and 3 Guests.
This is a modified version of snipsnap.org created by >>Paulo Abrantes