Latest revision as of 17:16, 8 March 2016

Proposed for Deletion
This page has been proposed for deletion for the following reason: it has been moved to community.kde.org

This face-to-face meeting focuses on KDE Wikis. It's supported by KDE e.V.

Date

Sunday, June 28th, to Monday 29th 2009

Location

Nokia Qt Software Office, Berlin Adlershof

Goals

Migrate obsolete web content to userbase and techbase (e.g. pim.kde.org and kontact.kde.org)
Find a place and a structure for community content (see techbase/Projects and the ideas around communitybase.kde.org)
Improve Wiki style, so it handles our needs, e.g. in terms of program code, better.
Implement common login for techbase and userbase
Implement template for applications on userbase
Find solution for wiki.kde.org (this is a follow up)?
Write down a clear definition of what content should go where, and what purpose the different Wikis have
...

Past wiki meetings

Meeting during KDE PIM Meeting 2009

ToDo

how do we handle different languages (this is a follow-up)?

At the moment, all is a mess. If I do a search in a pure english installation, I may get russian results, I do not like this. This could be easily solved with namespaces.

- possible solution: mediawiki namespaces

tstaerk's favorite solution, yet to be tested. Problem: How do we adapt the name spaces to be searched by default? Maybe so?

- possible solution: subdomains

Frederic Sheedy <[email protected]> has an interest in developing this area. we have already discussed it in broad terms. annew

rating system wanted?
what about breadcrumb navigation?

jstaniek is going to do this for userbase. annew

how do we make openid work in the sense of one login for both userbase and techbase sites?
what about the community web site described at Osnabrueck_7?
- we want two pages: one for users and one for developers. The developers' page will focus on community and technology. If we make a separate page for the community, we will run into definition problems: E.g. what about projects? Do they belong to community or to technology?
  - tstaerk
- we want three pages: userbase, techbase and community
- we want four pages: userbase, techbase, community and projects
can't we show "this site has been visited X times" below an article?
can we all get a Unix user for immanuel? Is it all running on immanuel?

@@ Line 1: / Line 1: @@
-This meeting focuses on KDE wikis.
+{{Proposed_deletion|reason=it has been moved to community.kde.org}}
-= date =
+This face-to-face meeting focuses on KDE Wikis. It's supported by [http://ev.kde.org KDE e.V.]
-See http://www.doodle.com/z2ukyr3nxx8k6bc2 for a vote.
-= past wiki meetings =
+= Date =
-* [[PIM/Meetings/Osnabrueck_7#Web_Site_Meeting]]
+Sunday, June 28th, to Monday 29th 2009
+= Location =
+Nokia Qt Software Office, Berlin Adlershof
+= Goals =
+* Migrate obsolete web content to userbase and techbase (e.g. pim.kde.org and kontact.kde.org)
+* Find a place and a structure for community content (see techbase/Projects and the ideas around communitybase.kde.org)
+* Improve Wiki style, so it handles our needs, e.g. in terms of program code, better.
+* Implement common login for techbase and userbase
+* Implement template for applications on userbase
+* Find solution for wiki.kde.org (this is a [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_7#redirects follow up])?
+* Write down a clear definition of what content should go where, and what purpose the different Wikis have
+* ...
+= Past wiki meetings =
+* [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_7#Web_Site_Meeting Meeting during KDE PIM Meeting 2009]
 = ToDo =
-* how do we handle different languages (this is a [http://techbase.kde.org/Projects/PIM/Meetings/Osnabrueck_7#translations follow-up])?
+* how do we handle different languages (this is a [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_7#translations follow-up])?
 : At the moment, all is a mess. If I do a search in a pure english installation, I may get russian results, [[User:Tstaerk|I]] do not like this. This could be easily solved with namespaces.
 ** possible solution: mediawiki namespaces
-::: tstaerk's favorite solution, yet to be tested
+::: tstaerk's favorite solution, yet to be tested. Problem: How do we adapt the [http://www.mediawiki.org/wiki/Manual:$wgNamespacesToBeSearchedDefault name spaces to be searched by default]? Maybe [http://www.tutorialized.com/view/tutorial/Redirect-Visitors-by-Browser-Language/10157 so]?
 ** possible solution: subdomains
 ::: Frederic Sheedy <[email protected]> has an interest in developing this area.  we have already discussed it in broad terms. annew
-* what about wiki.kde.org (this is a [http://techbase.kde.org/Projects/PIM/Meetings/Osnabrueck_7#redirects follow up])?
 * rating system wanted?
 * what about breadcrumb navigation?
 ::: jstaniek is going to do this for userbase. annew
 * how do we make openid work in the sense of one login for both userbase and techbase sites?
+* what about the community web site described at [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_7 Osnabrueck_7]?
+** we want '''two pages''': one for users and one for developers. The developers' page will focus on community and technology. If we make a separate page for the community, we will run into definition problems: E.g. what about projects? Do they belong to community or to technology?
+*** tstaerk
+** we want '''three pages''': userbase, techbase and community
+** we want '''four pages''': userbase, techbase, community and projects
 * can't we show "this site has been visited X times" below an article?
+* can we all get a Unix user for immanuel? Is it all running on immanuel?