JSPWiki at http://jspwiki.org/:
JSPWiki is a WikiWiki engine built around the standard J2EE components (Java, servlets, JSP). This site serves as the general discussion area, bug report system, idea bin, and source repository.
JSPWiki doesn't seem to have a management structure. See http://jspwiki.org/wiki/SupportJSPWiki.
It's a natural consequence of growth that once a team reaches a certain size the need for organization and management tends to surface.
There is no marketing department, nor even a management team here. We're so busy developing that we don't really even have the time to help organize those people who are interested in helping. If you have a natural talent in working with people and like to organize people, documentation your help would be kindly welcomed.
JSPWiki was founded by Janne Jalkanen, not in his role as a senior technology manager at Nokia. (See http://www.ecyrd.com/ButtUgly/wiki/JanneJalkanen.
I currently work as a Senior Technology Manager at Nokia. However, I am writing as a private person, and nothing written on this blog should be considered an official opinion of the company. I represent myself, not the corporation. (And please don't bother them about me, either. ;-)
It is licensed as on the Lesser GPL, as described at http://www.ecyrd.com/ButtUgly/Wiki.jsp?page=Main_blogentry_010303_1.
BTW, I am changing the JSPWiki license to the Lesser GPL, so that people can more easily embed JSPWiki code into their own things. It's a sort of a compromise between the forced sharing of GPL, and the free-for-all attitude of the Apache License - I want JSPWiki to be useful to people, but I also do feel that the Free Software Foundation does have the right idea. Yes, this is very wishy-washy :-).
Wiki Central → Instawiki → Wiki Central v2
A history is available at http://w3.webahead.ibm.com/prototype/wiki.htm.
How did this all begin (btw, when you hit the wiki help page, you'll see the text again)
- We started with a Single instance of a Wiki . Single instance meaning, no Access Control Lists (ACLs) - and all of the pages were in a single space. This wiki was basically shared by everyone and can be found at WikiCentral.
- Then we moved into a Multiple wiki instances environment. People could create more of a community editing environment, added control, as well as privay. This was hosted at InstaWiki.
- Now we have the new wiki WikiCentral v2 . Instawiki was plagued by a bunch of bugs. User feedback let us know that it was also missing a important features such as Such as restoring the history version of pages and managing attachments (specifically, people wanted the power to delete them!). Users found it hard to configure their ACLs, and when they figured it out, it was too easy to screw it up. You can find Wiki CentralV2 here: http://w3ki.webahead.ibm.com.
This new wiki engine is based on the commercial product Confluence while those two previous versions of wiki were based on JSPWiki. Confluence not only addresses the bugs and feature requests demanded by the users, but also adds a few extras:
- Team blogs are enabled.
- Now, when you hit the wiki dashboard, you only see what you have access to. Nothing is more annoying than seeing a link, clicking on it, and receiving the error "access denied" - this won't happen!
- Comments are also enabled
- you can create a PDF file from your wiki pages
- and you can "watch this space" (get email notifications of major wiki page/space changes)
Confluence, from Atlassian
- Enterprise security
- Simple installation and management
- Attractive, user-friendly WYSIWYG interface
- Powerful tools for structuring and searching your wiki
- Professional features such as PDF export and automated refactoring
- An open API for extension and integration
- Atlassian's Legendary Service
From "10 Reasons to Use Confluence" at http://www.atlassian.com/software/confluence/learn/10reasons.jsp, there's technology considerations, with Java:
8. Integrated with your existing systems.
In addition to the extension possibilities, which allow bidirectional information flow with your existing systems, Confluence also has other integration features:
- Confluence is developed using HTML standards and is tested with all major browsers.
- RSS and email allow you to interact with Confluence from your daily work tools.
- RPC plugins allow you to deploy SOAP or XML-RPC services within Confluence.
- Themes allow you to skin Confluence to match your look and feel!
- Java Servlets can be deployed directly onto the Confluence server, dynamically!
- Hook into Confluence's event-driven architecture to drive other applications or systems from Confluence activity.
9. Confluence runs everywhere.
Confluence will run on your existing hardware and software platform. It runs on all operating systems which have a JDK, with almost all JDBC compliant databases.
Confluence has been run on hardware from a Compaq iPAQ to an IBM AS400 and everything in between.
Confluence isn't a very expensive software product, and it's not open source, as explained at http://www.atlassian.com/software/confluence/licensing-faq.jsp#open_source:
1.1. Are your products Open Source software applications?
No, Atlassian products are proprietary software applications.
Atlassian commercial licensees do however receive the full source code to the software (under a developer source license), allowing for in-house customizations and modifications. Atlassian's software is still very flexible and customisable; source modifications are required only in the most complex setups.
Note: Atlassian does offer free licenses for official Open Source Projects and non-profit organisations - it's our way of giving something back :) . In addition, Atlassian actively supports a large number of Open Source projects and groups, such as Apache, Codehaus, OpenSymphony, WebWork and XDoclet.
SNAPPS QWiki, and Quickr (Quickplace v8)
On December 6, 2006, SNAPPS, an IBM Design Partner for Quickplace, made a template available for Quickplace v7 on the forum at http://www.snapps.com/qforum.nsf/WebBoardMainCategorized?OpenView&RestrictToCategory=QWiki&ExpandSection=11:
12-06-2006 15:52 - QWiki
QWiki is an advanced template for QuickPlace that enables you to maintain a Wiki site in the familiar QuickPlace environment. Some of its features:
"Web 2.0" look and feel, accomplished in part with the open-source Dojo toolkit for Ajax
- Rich text editing (better than most wikis!) including links and images
- Dynamic link and image procurement and placement
- Revision history of each and every document, with the ability to comment on the change(s)
- A clean, streamlined, uncluttered UI
QWiki is implemented as a placetype for QuickPlace. It is usable as is, or you can take it apart and add Wiki featuers to your existing places - for instance, in a room. Like all of our free templates, QWiki leverages the open-source Dojo toolkit (IBM is a supporter of the Dojo foundation) to provide an updated, modern user experience.
These templates were announced as open source at http://www.snapps.com/SNAWEB.NSF/0/44CD269257591E7B86257226006E6786:
SNAPPS is pleased to offer IBM Lotus QuickPlace™ customers a series of free, open-source templates for QuickPlace 7! In our role as the official IBM Design Partner for QuickPlace, we have worked closely with IBM to provide you with an enhanced experience, new Web 2.0 functionality, and immediate benefits for new and existing QuickPlace installations.
Our first three offerings are outlined below. More will follow as we approach the debut of QuickPlace 8.0 from IBM!
There's are review of the templates by Christian at http://chris.brandlehner.at/Brandlehner/cab_blog.nsf/d6plinks/CBRR-6YJE7K:
SNAPPS did a great job with this free IBM Lotus QuickPlace PlaceType!
This could potentially be licensed by, IBM, and presumably would be included in Quickr (Quickplace v8)