Term no longer in use, because it was confusing. See TWikiTerminology for correct terms
TWiki currently only has one official package, the
TWikiRelease at TWiki.org. TWiki is used now more and more in areas originally not anticipated. The installation process is complex and error prone, and has been responsible for putting off a lot of potential users. The
one package approach does not fit the bill anymore.
The official
TWikiRelease serves as a base to build TWiki distribution specific packages. This base is the
TWikiKernel, composed of the core code (scripts and libs),
TWiki docs, and several Plugins and Skins.
This page links distribution specific packages of TWiki that are available for different platforms.
Only distribution specific packages that are generated according to the process described in ProcessForBuildingTWikiDistributions are listed here.
In addition to the Platform (Distribution) specific packages.
TWikiPackages are also being built to meet the needs of all the areas where TWiki is a viable solution.
IntranetTWiki
InternetTWiki
EcommerceTWiki
(among several others to be listed soon)
(some summary of the concept needed here)
something like this maybe?
"In order to make your experience with TWiki as easy and as productive as possible we are in the process of building [have prepared] prepackaged "distros" of TWiki software taylored to your needs, Be it Internet or Intranet, Social or Scientific, for and Individual or a team, our goal is to provide the right mix of Plugins and Ad-ons along with the TWiki core engine all in a single package that "just works" for
your needs."
--
TravisBarker - 11 Apr 2005
(list of the most common problems twiki is often employed to solve)
All of these would be TWiki, but packaged with all the pieces needed to address the specific application domain.
--
CrawfordCurrie
--
TravisBarker - 11 Apr 2005
TODO List
(list of things we need to do to make this happen)
- Define what Distros should be built
- Decide what plugins and add-ons should be included in each Distro
- create an organized method of building and listing distros
- design forms for classify plugins, their usage etc
- Related Topics List needs to be populated.
Topic Meta Discussion area
(where we can hash our our differences of opinion as to how we should move forward)
This Should be enough to get started down the road. Now all we have to do is ...well,
do it
--
TravisBarker - 11 Apr 2005
here are some terms which could be used:
TWikiKernel,
TWikiCore,
TWikiDistribution,
TWikiPackage,
TWikiBundle,
TWikiPort,
TWikiModule,
TWikiExtension,
TWikiRelease,
TWikiPreConfiguration,
TWikiAppliance
--
WillNorris - 17 Jun 2005
This seems to have stalled, simply because of terminology. Here are the terms we should move ahead with:
| TWikiCore |
The core components, not including any Contrib or Plugin modules. |
| TWikiPackage |
TWikiCore + plugins, skins, themes, documentation etc. |
| TWikiRelease |
A TWikiPackage identified as a "mainstream release" of TWiki |
| TWikiDistribution |
A zip, rpm, tar, whatever of a TWikiPackage made to address a single platform |
| TWikiApplication |
A set of plugins, contribs, add-ons, and topics, that when layered onto a TWikiPackage adds value. |
The existing terms
TWikiPlugin,
TWikiAddOn,
TWikiContrib retain their existing semantics.
Example: let's say I wanted to build a
TWikiAppliance for Linuxen equivalent to Mediawiki i.e. minimalist, supports login/logout, one-touch install, targeted at internet use.
- I would start with the TWikiCore
- I would add WysiwygPlugin, SessionPlugin and AuthPagePlugin, but no other plugins
- I would add MediaSkin (
)
- I would preconfigure an install on my Linux box
- I would buid a .tgz
--
CrawfordCurrie - 26 Jun 2005
| TWikiKernel |
The core components, not including any Contrib or Plugin modules |
| TWikiPackage |
a collection of TWikiExtensions (plugins, skins, themes, etc), documentation, etc. |
| TWikiDistribution |
TWikiCore + plugins, skins, themes, documentation, etc. |
| TWikiRelease |
A TWikiPackage identified as a "mainstream release" of TWiki (a TWikiRelease is also a TWikiDistribution) |
| TWikiPort |
A zip, rpm, tar, whatever of a TWikiDistribution made to address a single platform |
| TWikiApplication |
A set of plugins, contribs, add-ons, and topics, that when layered onto a TWikiDistribution adds value |
| TWikiAppliance |
an installation CD (or netboot image, etc.) which is used to install a complete OS + TWiki + other applications onto a bare box |
The existing terms
TWikiExtension (
TWikiPlugin,
TWikiAddOn,
TWikiContrib) retain their existing semantics.
Example: let's say I wanted to build a
TWikiAppliance equivalent to
MediaWiki (i.e., minimalist, supports login/logout, one-touch install, targeted at internet use)
- I would start with the TWikiKernel
- I would add WysiwygPlugin, SessionPlugin and AuthPagePlugin, but no other plugins
- I would add MediaSkin (
)
- I would preconfigure an install on my Linux box
- I would buid a .tgz
- I would combine with a (Linux) distribution, and add my TWikiDistribution as part of the list of things to (automatically) install
- I have created such automatic systems installs from RedHat 9, though in the future, i'd prefer to make them Debian-based instead.
i'm still (of course) open to working out this terminology; however, i will say that i
much prefer
TWikiPort to mean a port to a specific platform, and
TWikiDistribution to mean TWiki plus a set of bundled plugins, addons, skins, etc.
--
WillNorris - 26 Jun 2005
I don't really care; I just want this closed. I am conscious that "distribution" means something specific to Linux users, though, and we should probably reflect that. People will continue to refer to what you call a
TWikiPort as "distributions" (you can lead a horse to water etc....) so my feeling is that we might as well go with the flow.
I'm not mad about the term
TWikiPort either. It makes me think of port numbers before target platforms.
In your list above, how is a
TWikiPackage different to a
TWikiApplication? In that is doesn't add value?
Proposal:
TWikiFor is more intention-revealing - for example,
TWikiForRedHatEnterprise25,
TWikiForWindowsXP,
TWikiForPalmPilot. It lets us be as specific or as general as required: from
TWikiForTheInternet all the way to
TWikiForWidgetDesignersOnMacOS10X. It lets us work with fewer terms as well, as a
TWikiDistribution is a
TWikiFor (otherwise why are you doing it?) and so is a
TWikiPort.
| TWikiCore |
The core components, not including any Contrib or Plugin modules |
| TWikiFor |
TWikiCore + plugins, skins, themes, documentation, etc. |
| TWikiRelease |
A TWikiFor identified as a "mainstream release" of TWiki (a TWikiRelease is a TWikiForGeneralUse) |
| TWikiApplication |
A set of plugins, contribs, add-ons, and topics, that when layered onto a TWikiDistribution adds value |
| TWikiAppliance |
an installation CD (or netboot image, etc.) which is used to install a complete OS + TWiki + other applications onto a bare box |
--
CrawfordCurrie - 28 Jun 2005
THIS DISCUSSION HAS NOW BEEN PUT TO BED - see
TWikiTerminology.
--
CrawfordCurrie - 28 Jun 2005