2005-01-20 #1

Sorry, but i can't edit or comment the feature requests snip nor my personal page rbtst. Please, why?

So what is going to appear on snipforge.org? At present there's just a logo.

A site for snipsnap development and plugins. A place for new developments.

Any timeline?

The ratio of announcements to actual delivery is very discouraging.

unfortunately, I have to concur …

What would be the appropriate forum for we, the users, to decide which features are critical to the SnipSnap Core? I think many of us are eager to see ACL, but that's coming Any Day Now.

Virtually everything else I have come up with is addressable with plugins. Which is why I'd like to see the FIRST guys keep their focus on wrapping up 1.0 with permissions, rather than getting distracted with things like SnipForge and macros for graphing and UML.

I think the next priority for the core should be a robust UI for installing and configuring plugins, alá Confluence. This is critical for a healthy plugin ecosystem.

I've created SNIPSNAP-413 to track this.

Looks like if I want to really use SnipSnap I am going to have to learn how to patch things in Java.

ThoMo has some patches on his page to fix bugs that look like they have been available for 3+ months but were not incorporated into the newest beta build?? I don't get it. Broken things, like the AtoZ lister for Labels are not fixed?

I like SnipSnap - so I guess I will have to learn to Patch.

Even if you are willing to start writing Java code, it's not going to be easy. I would like to work on SnipSnap, but the new architecture (in particular, using Java properties instead of config files) is making it virtually impossible to develop on the same machine on which I already have a "real" SnipSnap installation. This is a problem for those of us who have only one computer, or who are using SnipSnap as a "log book" and therefore want to have it running locally. It's also a pain to set it up as a project in Eclipse and run it under Eclipse's debugger. All of those container libraries -- Pico, Nanning, etc. -- SnipSnap uses these days sound really cool and "in the moment", but from my viewpoint (which I admit is not that of an active developer) they only further complicated figuring out what is going on.

In addition, the web site has almost died. That's never a good sign for an open-source project, if you intend to have an active community of contributors.

The java properties api is not very successful and I think I will remove it. It is only found in the main server loader and not anywhere in the war, so it should not be too bad.