History: Using profiles to replace mods
Preview of version: 1
- «
- »
This is brainstorming about if/how/when mods should be deprecated, in favor of profiles.
Status as of 2012
- Mods is code in SVN: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/mods/trunk/
- Most of the mods are abandonware but there are a handful of useful/maintained mods but
- They are not in core because of licensing
- mods can't deal with versioning
- mods can't deal with translations
- The mods installer hasn't been improved in years and it's unlikely someone will step up.
- Mods installer can't work in some places because of file permissions
Idea
- Mods is a packaging/distribution tool for files managed in a SCM (SVN)
- Instead, profiles could be used to deploy and wiki pages could become the SCM, with a nice Web-based source code editor
Benefits
- The license of the content can be GPL because the user installs themselves
- Contributors can contribute via the browser (especially interesting for translators)
Challenges
- How to sync svn with the wiki?
- tw:Translation branching strategy
- How to deal with binairies?
- Profiles could be improved to handle binairies
- mods has an installer
- * PluginArchiveBuilder can generate the zip on demand of a bunch of files and we let people install themselves if file permissions are an issue
Long term
- We could imagine moving translations completely to this, but we would need to upgrade our scripts