History: Software_Project
Preview of version: 18
A software project profile is a high priority as it could help attract programmers to our project.
As an example, let's look at the Open Moko project, which uses several applications to manage its community.
They appear to have used the "best of breed" strategy when picking applications. More about this at http://marclaporte.com/TikiSucks
However, now, it must be quite a challenge to integrate these various applications. Pretty much all this functionality could have been handled by a single all-in-one application like TikiWiki or with a framework/CMS with additional modules (like Drupal, Joomla!, Plone, Xoops, etc).
The following profile is to meet this use case. Open Moko is a fairly large project though so let's keep in mind that most projects are much smaller.
In using TikiWiki instead of the above combination:
The "bad"
The "good"
In this profile, we need
Things we should improve to make Tiki an even more compelling software collaboration tool:
We'll start below
As an example, let's look at the Open Moko project, which uses several applications to manage its community.
- MediaWiki for the main site
- Not one but two instances of Trac for bug tracking, and more (they migrated from Bugzilla)
- Planet for RSS aggregation
- Gforge for project management
- Mailman for the mailing lists/forums
They appear to have used the "best of breed" strategy when picking applications. More about this at http://marclaporte.com/TikiSucks
However, now, it must be quite a challenge to integrate these various applications. Pretty much all this functionality could have been handled by a single all-in-one application like TikiWiki or with a framework/CMS with additional modules (like Drupal, Joomla!, Plone, Xoops, etc).
The following profile is to meet this use case. Open Moko is a fairly large project though so let's keep in mind that most projects are much smaller.
In using TikiWiki instead of the above combination:
The "bad"
- not everything is done exactly the same.
- Tiki forums are not the same as mailman mailing lists, and Open Moko wiki cleverly notes that "Apparently, there are two groups of people: one group does not like Web forums; the other group prefers Web forums" so we should set-up the Forum and List Synchronization
- Project management would be the TikiWiki way and not the gforge way.
- not all features are necesarily as advanced.
- Some feature are just missing.
The "good"
- Tiki does have features that they may want.
- For example, blogs and news articles. It would be even worse if they installed a WordPress blog on top of what they have.
- Surveys
- Etc.
- Tiki would offer
- Single Sign On (single user system, groups & permissions)
- Global search engine
- Consistent look & feel
- Tighter integration permits better internal linking
In this profile, we need
- Wiki
- Forums
- Improve the Bug_Tracker profile
- RSS aggregator
- Categories
- Source browser
- etc
Things we should improve to make Tiki an even more compelling software collaboration tool:
- http://blog.lphuberdeau.com/wordpress/2009/01/25/adding-collaboration-and-durability-to-code-reviews/
We'll start below
Permissions
Uses: Community_PermissionsYAML
dependencies: - $profiles.tikiwiki.org:Community_Permissions:Community_Permissions
History
Current Profiles
Latest Changes
- How to Create Profiles
- Profiles_in_Wizard
- Test_All_Plugins
- Testing_Aggestor
- JonnyBs_Luxury_Tiki_Setup
- Collaborative_Multilingual_Terminology
- Profile_Test_all_Modules_Test_all_Modules_page
- Revision Approval (ISO9001)
- WantedPages
- Kanban_Board_26
- Kanban Profile Menu
- Kanban-Board-26
- Logging in at this site
- Bug_Tracker_16
- Profile_Work_Custom_Pricing_menupage_include
- Bug_Tracker_16
- Customer_Relationship_Management
- Currency Tracker
- Welcome to Tiki Profiles
- Markdown_Settings