|
|
| Line 9: |
Line 9: |
| | ** Might grow very big | | ** Might grow very big |
| | ** Requires namespaces | | ** Requires namespaces |
| | + | ** No obvious structure |
| | + | ** No homogenous target audience |
| | + | |
| | + | Unattractive for subprojects |
| | | | |
| | === n /wiki per site === | | === n /wiki per site === |
| Line 37: |
Line 41: |
| | | | |
| | * Investigate OpenID | | * Investigate OpenID |
| | + | * Investigate which target audiences we/the projects want |
| | + | * Talk to subprojects |
| | + | ** What solution do they prefer? |
| | + | ** To what extend would they go with whatever we do? |
| | + | ** Whats the additional value for them to join the effort? |
| | + | * How and where to migrate the contents of the current wikis? |
Revision as of 19:07, 2 July 2007
Possible Scenarios for future Wiki use on *.kde.org
wiki.kde.org with namespaces
- Cons
- Might grow very big
- Requires namespaces
- No obvious structure
- No homogenous target audience
Unattractive for subprojects
n /wiki per site
- Pros
- Very flexible for projects
- Cons
- Sharing templates impossible
- Sharing files quite hard
- Interwiki-Links are of limited use
- n databases
n role-based wiki sites
Possible compromise between the two suggestions above.
- Pros
- Less wiki instances than one per site
- Cons
- Sharing templates impossible
- Sharing files quite hard
- Interwiki-Links are of limited use
- n databases
Action items
- Investigate OpenID
- Investigate which target audiences we/the projects want
- Talk to subprojects
- What solution do they prefer?
- To what extend would they go with whatever we do?
- Whats the additional value for them to join the effort?
- How and where to migrate the contents of the current wikis?
KDE TechBase 