Where are we?
Started to implement in CVS. Here are the steps (as I see them):
- Change tiki.sql and tiki_1.7to1.8.sql to initialize all the rows in tiki_preferences - done
- Change dev docs to have new records for tiki_preferences put into the .sql files instead of tiki-setup
- Create / document dump scripts - done
- Create some sample configs - done
- Add code to tiki-install.php to select and run the profiles - done
- Test, test, test - in process
Where do we want to be?
A profile is a collection of Tiki configuration data, including
- which features are selected
- which groups are set up
- which permissions a group has
Profiles can be chosen at initial setup
- At the beginning of the webbased part of the installation process, the admin can choose what profile to install with
- examples could be "minimal", "standard news portal", "full fledged monster"
- There is a link "download more profiles" (like with themes or extensions in mozillafirebird)
- after choosing initial profile, the admin can finetune to her needs
Example: Profile "Tiki for a music band"
- uses features calendar, CMS, Wiki, Forum
- uses groups Band, Booking, Venues, Fans
- permissions so that Band sees more than Fans etc.
- a musicians magazine could provide a version of Tiki that loads with the "Music Band" profile by default. The whole thing just looks like designed ONLY for musicians.
Profiles are mergable
- Suppose I already have a running and configured Tiki, but I want to add all the functionality of profile "Band", then I can merge that into the current instance
- Wherever this is possible without conflicts, Groups and permissions are just automatically added
- Admin can choose what to do in conflicts
Profiles are dumpable
- Suppose some band is quite happy with their configuration after some tweaking.
- Then they just click "dump profile", set the appropiate checkboxes on which part of the configuration to dump (export) and contribute the resulting profile to tikiwiki.org, where others can download it.
Profiles mix well with Content Packs
- see ContentPacksDev for more information
TikiTeam
Currently recruiting members!
Dennis Heltzel
Dennis Daniels for testing
chibaguy aka Gary
Trackers
- Bugs
- RFEs
- tech support
- patches
Competition and standards
List of other products with similar/interesting/related features.
Here I would like to see some "editorial" content. How do our features compare to others?
CVS Doc section
This is where new features being developed and only in CVS are documented. When the CVS becomes RC/official release, the info in the CVS docs is transferred to update the official docs TikiProfilesDoc.
How to create a new profile for Tiki
Supported Profiles
Discussion
- Initially, the profiles will only support MySQL
- The process of creating new profiles is very simple (and hopefully soon, well documented) so that we can provide many different profiles out of othe box.
- Profiles will not be mergable or dumpable, and won't be accessible at all except at inmitial creation. Some of this can be done from the command line, but not via the web interface. If someone wants to add this on later, fine, but IMO, it's not very important, and possibly dangerous.
to be removed from profiles
Server name (for absolute URIs)
Sender Email
LDAP/CAS/PAM settings
Meta tags
Admin dsn
webmail
Mail notifications
to be added
tracker definitions (but not data)
Site identity
forums, but no messages?
newsletter already setup?
menu
unsure
content templates
reminders
Keep binairies stored to DB
;){kind=link}
;){kind=link}