KDE Community Wiki - Recent changes [en]

Promo/Material

Nightrose — Sun, 22 Nov 2009 23:32:44 GMT

sceleton for material page - more content as soon as i can upload files

New page

= Social Media =

a general intro to [http://blog.lydiapintscher.de/2009/08/16/social-media-guide-for-free-software-projects/ social media for free software projects]

== microblogging ==

Promo

Nightrose — Sun, 22 Nov 2009 23:20:33 GMT

add promo material page

← Older revision		Revision as of 23:20, 22 November 2009
Line 7:		Line 7:
	* [[Promo/Branding\|Branding]]		* [[Promo/Branding\|Branding]]
	* [[Promo/Strategy\|Strategy]]		* [[Promo/Strategy\|Strategy]]
		+	* [[Promo/Material\|Material]]

	== Ideas ==		== Ideas ==

Sysadmin

Toma — Sun, 22 Nov 2009 18:53:19 GMT

New page

The KDE sysadmins consist of a group of contributors which maintain the KDE infrastructure.

To organise the work, they use a special section of bugzilla. You can report issues to them at the following special page: https://bugs.kde.org/enter_sysadmin_request.cgi

At that page you can request:
* @kdemail.net e-mail addresses
* mailinglists
* bugzilla assistance
* reviewboard extentions
* additional karma for svn

Also, please report not working parts of the infrastructure. Don't just assume someone else has done it!

If you want to request a subversion account, you need a different form, it can be reached via http://techbase.kde.org/Contribute/Get_a_SVN_Account

Main Page

Toma — Sun, 22 Nov 2009 18:44:48 GMT

← Older revision		Revision as of 18:44, 22 November 2009
(One intermediate revision not shown)
Line 16:		Line 16:
	* [[Promo\|KDE Promo]]		* [[Promo\|KDE Promo]]
	* [[KDE Women]]		* [[KDE Women]]
		+	* [[Sysadmin\|KDE Sysadmin]]

User:Toma

84.53.90.221 — Sun, 22 Nov 2009 18:42:09 GMT

created new account User:Toma

New page

KDE Women

Nightrose — Sun, 22 Nov 2009 16:17:51 GMT

create KDE Women page

New page

KDE Women is a group of women in the KDE community. We are here to help increase the number of women in Open Source and to support each other. KDE is a friendly and open community and one of the Open Source projects with the highest rate of female contributors. It strives through its diversity.

Some of the things we do:
* help women find the right place to contribute
* encourage women to give talks at conferences such as Akademy, the annual KDE conference
* provide mutual support
and most importantly we make KDE rock more each day ;-)

To contact us please join our [http://mail.kde.org/mailman/listinfo/kde-women mailing list].

Read our blogs on [http://planet.kde.org PlanetKDE] to find out what some of us are doing in KDE.

Main Page

Nightrose — Sun, 22 Nov 2009 16:11:54 GMT

add KDE Women and sort alphabetically

← Older revision		Revision as of 16:11, 22 November 2009
Line 12:		Line 12:

	* [[KDE e.V.]]		* [[KDE e.V.]]
		+	* [[KDE Edu]]
	* [[KDE PIM]]		* [[KDE PIM]]
	* [[Promo\|KDE Promo]]		* [[Promo\|KDE Promo]]
-	* [[KDE ~~Edu~~]]	+	* [[KDE Women]]

Promo/Branding/Rebranding KDE v1.1.0

Stu — Sun, 22 Nov 2009 13:37:00 GMT

← Older revision		Revision as of 13:37, 22 November 2009
Line 109:		Line 109:
	The following would need to happen to implement this proposal:		The following would need to happen to implement this proposal:

-	*Start to use the KDE brand and the chosen workspace sub-brand actively in our	+	*Start to use the KDE brand and the chosen workspace sub-brand actively in our communications, making sure to distinguish between them in a natural way, and start treating the workspace as "just another product" in these communications. Special focus is on the new brands “KDE Software Compilation”, “KDE Platform”, and “Plasma Desktop”.
-	communications, making sure to distinguish between them in a natural way, and	+	*Perform a press release noting the repositioning of the KDE brand to be more inclusive of all platforms and of all efforts (not just coding), and that as such it has been decided to brand KDE as the entire community effort, instead of just the workspace efforts.
-	start treating the workspace as "just another product" in these communications.	+
-	Special focus is on the new brands “KDE Software Compilation”, “KDE Platform”,	+
-	and “Plasma Desktop”.	+
-	*Perform a press release noting the repositioning of the KDE brand to be more	+
-	inclusive of all platforms and of all efforts (not just coding), and that as such it has been decided to brand KDE as the entire community effort, instead of just the workspace efforts.	+
	*Rewrite key areas of the kde.org web site to reflect the new brand; reveal these changes with release of 4.4.		*Rewrite key areas of the kde.org web site to reflect the new brand; reveal these changes with release of 4.4.

Promo/Branding/Rebranding KDE

Stu — Sun, 22 Nov 2009 13:30:59 GMT

Point to rebranding proposal imported in to wiki

← Older revision		Revision as of 13:30, 22 November 2009
Line 3:		Line 3:
	There is a detailed proposal about the rebranding effort, which has been discussed over the last months and has gained broad acceptance in all parts of the community.		There is a detailed proposal about the rebranding effort, which has been discussed over the last months and has gained broad acceptance in all parts of the community.

-	* [http://~~cornelius-schumacher~~.~~de/repositioning-the-~~kde~~-brand~~.~~pdf~~ KDE Rebranding Proposal v1.1.0]	+	* [http://community.kde.org/Promo/Branding/Rebranding_KDE_v1.1.0 KDE Rebranding Proposal v1.1.0]
-	* [http://markmail.org/message/ruajryjfbfdmgccl KDE Rebranding Proposal v1.0.2]	+	* [http://markmail.org/message/ruajryjfbfdmgccl KDE Rebranding Proposal v1.0.2] (Old version on a mailing list)

Promo/Branding/Rebranding KDE v1.1.0

Stu — Sun, 22 Nov 2009 13:29:16 GMT

Tidying up PDF import

New page

=Repositioning the KDE brand=
'''Draft 1.1.0, Nov 14, 2009'''

''This document has been created by the KDE Marketing Team. It's maintained by Cornelius Schumacher <schumacher@kde.org>. Please do not modify this page without agreement on KDE-Promo mailing list.''

==Introduction==
The past years have seen pervasive developments in the KDE universe. The application framework has grown, matured and gone cross-platform, as have the applications. Strong growth in our community has created an increasingly diverse and large set of high-quality applications.

In the process, KDE's identity has shifted from being simply a desktop environment to representing a global community that creates a remarkably rich body of free software targeted for use by people everywhere.

'''KDE is no longer software created by people, but people who create software.
'''

To be able to communicate this clearly in our messaging, it is necessary to reposition the KDE brand so that it reflects this evolution and stands for the community, our international team of talented developers, artists, usability specialists, translators and other contributors who make the project what it is today. This way the KDE brand will become the umbrella brand for the technology we create together. The workspace, the desktop itself, will get its distinctive "KDE Workspace" brand to give it its own identity which can't be confused with KDE as umbrella for platform and applications.

==Proposal==

#Retire the term "K Desktop Environment". Replace it by "KDE".
#Use the term "KDE" exclusively in two meanings:
#*(a)KDE, the community, which creates free software for end users.
#*(b)As an umbrella brand for the technology created by the KDE community.
#Create distinct brands for the software that was previously referred to generically as “KDE”, such as the desktop workspace.

==Details==

===Retiring the term "K Desktop Environment"===

The expanded term "K Desktop Environment" has become misleading, ambiguous, and
obsolete. Settling on "KDE" as a self-contained term makes it clear that we have made the shift from a limited set of software components to a community providing an ecosystem of free software applications and platforms for the end user on the desktop, mobile devices, and more.

The term "K Desktop Environment" can be accurately and completely replaced by "KDE Community", "KDE Platform", "KDE Applications" or specific KDE application names, depending on what is actually meant.

We may even want to stop talking about “desktop environment” at all. For the desktop itself we will have the clearer "KDE Workspace" brand, and the huge set of KDE applications can be put under the KDE umbrella brand using more specific brands for individual applications or application suites. The confusion about what a desktop environment is and implies can be avoided by using clearer terms in this manner.

===Use the term "KDE" exclusively in two meanings===

====KDE, the community====

The main feature of KDE is the community. That's the ground on which everything we do is based. This includes the KDE culture, the KDE values and the KDE mission. The community is also what ties us together and gives us an identity. This identity is KDE. So it seems very obvious and natural that the brand and term "KDE" stands first and foremost for the community.

Sometimes we use the term "KDE project" as a weak way to say "KDE community". We have grown far beyond the situation where you could refer to KDE as a “project”. It is not a limited effort to solve the problem of having a desktop GUI for Linux anymore. It has evolved into a thriving community of people continuously working on creating and improving free software for end users based on specific values, ideals and goals.

The KDE brand transports the values of the KDE community, such as freedom, technical excellence, beauty, pragmatism, portability, open standards, international collaboration, professionalism, respect, and great teamwork.

====KDE, the umbrella brand====

In the context of software KDE acts as an umbrella brand for the software created by the KDE community and software using the KDE platform. This includes the KDE platform itself, the KDE software compilation, and all other KDE applications.

=====The KDE Platform=====

The platform consists of shared libraries and a runtime base. The libraries include:

*Qt, the core and UI toolkit.
*The KDE libraries containing Qt extensions and the framework to integrate with the desktop and use desktop services in a standard way.
*Bindings for various programming languages.

Technically Qt is not released as part of KDE, but it is the most essential component of the platform and is developed closely together with the KDE platform. As such it can be considered part of the platform.

The primary goal of the KDE libraries is to provide integration and cooperation across applications based on standards while making development easy. This means providing integration layers with underlying technologies such as D-Bus, HAL, kioslaves, multimedia backends, PIM storage, search and semantic data engines or standard file formats like ODF. This is all based on standards specified by general standard bodies, freedesktop.org or KDE itself.

The runtime base includes:

* Tools required to run desktop applications like control modules or help center.
* Required data like localization information and icons.

The runtime base provides the non-library infrastructure to run fully functional and integrated desktop applications.

The KDE platform is required to run KDE applications. Together with some additional development data and tools it provides the KDE development platform, which is used by core and third-party developers to create KDE applications.

Some specific parts of the KDE platform are referred to as pillars of KDE.

=====KDE Software Compilation=====

The KDE Software Compilation is a collection of basic components and applications which are released together as a coordinated effort. This compilation represents the core set of applications which provide a clean, basic desktop experience. The KDE Softw are Compilation is divided into thematic modules including:

* workspace (Plasma, KWin, System Settings...)
* base applications (Konqueror, Dolphin, Konsole, Kwrite, ...)
* personal information management, or PIM (Kontact)
* games, education, networking, graphics, multimedia, administration, ...

Applications that make up the KDE Software Compilation may be run independently of each other and additional applications can be added without problems. These applications can be freely mixed with applications using other frameworks and run in whatever desktop environment one may choose.

=====KDE Applications=====

KDE applications use the KDE platform as a toolkit and to integrate with desktop standards, so they can be run on various desktop implementations, be it GNOME, Windows, or MacOS. They can be freely mixed with other desktop applications independent of the toolkit or framework with which they are written (e.g. Firefox, OpenOffice, etc.).

In addition to the applications released as part of the core KDE software compilation there are thousands of additional KDE applications. Some are large, sophisticated products in their own right such as KOffice and Amarok, while others are smaller like many apps on kde-apps.org. They all use the KDE platform to integrate with the desktop and in some cases use KDE development infrastructure, such as the KDE Extragear source code repository. They may be released independently or aligned with KDE Software Compilation releases.

All these applications are part of KDE, but also have their own identities. Being part of KDE means that they are developed by members of the KDE community and that they use KDE technology. It does not mean that they are tied to certain desktop implementations or can only be run in combination with other KDE applications. For the end user this choice in underlying technology is transparent. A KDE application should provide a great experience because it's based on great technology and is created by people sharing the KDE values,
not because it runs only in a specific desktop environment.

===Create distinct brands for the software that was previously referred to generically as “KDE”, such as the desktop workspace===

Calling the workspace "KDE" is misleading and might create the impression that it is a requirement for running KDE applications. So branding the workspace under a separate brand makes it align on the same level with all the other KDE applications which are a part of KDE, taking into account that KDE applications run just as well on any other workspace implementation, Linux, BSD, Solaris, Windows or MacOS.

The KDE workspace consists of the components which make up the desktop itself, which is contained in the kdebase-workspace module. This includes KWin, KDM, Plasma desktop shell, KRunner, System Settings, KSysGuard, etc.

By separating KDE-the-workspace from KDE as a whole, we can make it attractive to be more closely associated with the KDE brand, as the message becomes clear that KDE is not a desktop environment but rather provides one as a product.
It also gives the workspace components more freedom to be marketed independent of KDE as a whole, just as all other KDE applications are. Users of other desktops can run their applications together with KWin, KDM or the Plasma desktop shell just as they can run other KDE applications and vice versa. The workspace is a component like other KDE applications are as well.

The workspace comes in different flavors addressing the needs of specific groups of users and hardware platform constraints. The following brands are to be used:

*“KDE Plasma Desktop” for the traditional workspace
*“KDE Plasma Netbook” for the Netbook form-factor devices
*“KDE Plasma Mobile” for the workspace on phones and similar devices

==Implementation==

The following would need to happen to implement this proposal:

*Start to use the KDE brand and the chosen workspace sub-brand actively in our
communications, making sure to distinguish between them in a natural way, and
start treating the workspace as "just another product" in these communications.
Special focus is on the new brands “KDE Software Compilation”, “KDE Platform”,
and “Plasma Desktop”.
*Perform a press release noting the repositioning of the KDE brand to be more
inclusive of all platforms and of all efforts (not just coding), and that as such it has been decided to brand KDE as the entire community effort, instead of just the workspace efforts.
*Rewrite key areas of the kde.org web site to reflect the new brand; reveal these changes with release of 4.4.

==Time line==

The marketing team would like to see these changes begin to happen by the release of 4.4. We would like them to be complete by the release of 4.5.

User:Stu

94.195.5.14 — Sun, 22 Nov 2009 12:50:09 GMT

created new account User:Stu

New page

KDEEdu/Meeting20091119IRC

Frederik — Thu, 19 Nov 2009 23:40:27 GMT

Other Discussion:

← Older revision		Revision as of 23:40, 19 November 2009
Line 43:		Line 43:
	== Other Discussion ==		== Other Discussion ==

-	* sabineller has asked ~~Eugune~~ for a mascot	+	* sabineller has asked Eugene for a mascot

	* apol notes that in terms of promotion, we need to define what kdeedu is.		* apol notes that in terms of promotion, we need to define what kdeedu is.

KDEEdu/Meeting20091119IRC

Nightrose — Thu, 19 Nov 2009 22:44:22 GMT

Action to be taken: expand and clarify

← Older revision		Revision as of 22:44, 19 November 2009
Line 94:		Line 94:
	* Scout for volunteers for apps on the watch-list, using blogs, mailing lists, and klassroom.		* Scout for volunteers for apps on the watch-list, using blogs, mailing lists, and klassroom.
	** For kalgebra-meets-kmplot, apol will talk to aucuhuasi about it.		** For kalgebra-meets-kmplot, apol will talk to aucuhuasi about it.
-	** ~~Also include~~ kstars ~~(due~~ to kstar~~'s busyness.)~~	+	** kstars promo to be taken care of by kstar
		+	** Kiten promo to be taken care of by ?
		+	** KBruch promo to be taken care of by ?
		+	** KMPlot promo to be taken care of by ?
		+	** KTouch promo to be taken care of by ?
		+	** Step to be taken care of by ?
	* Possibility of using the 'fan' mechanism on Facebook, as currently done for amarok. Nightrose can create fan pages on demand for peoples' applications.		* Possibility of using the 'fan' mechanism on Facebook, as currently done for amarok. Nightrose can create fan pages on demand for peoples' applications.
	* Create some junior jobs for unmaintained apps.		* Create some junior jobs for unmaintained apps.
	* Find Klassroom mentors.		* Find Klassroom mentors.
-	* Create YouTube introduction videos for apps.	+	* Create YouTube introduction videos for apps. (Nightrose)
	* Write for the website explaining what kdeedu is about.		* Write for the website explaining what kdeedu is about.
-	* Ask teachers for their three pet problems with kdeedu apps (perhaps for conversion into junior jobs.)	+	* Ask teachers for their three pet problems with kdeedu apps (perhaps for conversion into junior jobs.) (Nightrose will do the survey part - who does the junior jobs conversion?)
	* Look for someone to help make the kdeedu apps feel more integrated.		* Look for someone to help make the kdeedu apps feel more integrated.
	* Document 'how to start changing stuff' + meta packages for distros etc.		* Document 'how to start changing stuff' + meta packages for distros etc.
	* Decide tasks for organising EDU meeting.		* Decide tasks for organising EDU meeting.
	* doodle.com poll for when people want the meeting (owner: sabineller.)		* doodle.com poll for when people want the meeting (owner: sabineller.)
-	* Poll to arrange follow-up IRC meeting in 2 or 3 weeks (owner: Nightrose.)	+	* Poll to arrange follow-up IRC meeting in 2 or 3 weeks (owner: Nightrose - done)
	* Ask annma to explain the issues surrounding GHNS, perhaps at next meeting.		* Ask annma to explain the issues surrounding GHNS, perhaps at next meeting.

User:Nightrose

92.200.81.152 — Thu, 19 Nov 2009 22:29:45 GMT

created new account User:Nightrose

New page

KDEEdu/Meeting20091119IRC

Frederik — Thu, 19 Nov 2009 22:14:29 GMT

← Older revision		Revision as of 22:14, 19 November 2009
Line 6:		Line 6:
	* KHangman: annma		* KHangman: annma
	* KLettres: annma		* KLettres: annma
-	* KWordQuis: ~~peter (a.k. peah)~~	+	* KWordQuis: Peter Hedlund
-	* Parley: ~~dani_l (who protests at such)~~	+	* Parley: Frederik, Daniel
	* KAlgebra: apol		* KAlgebra: apol
	* Kig: pino, who adds 'kig is okay'		* Kig: pino, who adds 'kig is okay'
Line 88:		Line 88:
	** Mario can handle local arrangements, but would need help from the team. Claudia?		** Mario can handle local arrangements, but would need help from the team. Claudia?
	** Duration - fregl suggests long weekend? Spring?		** Duration - fregl suggests long weekend? Spring?
-	** ~~Fregle~~ suggests inviting 1 marketing + args guy if possible? Apol suggests teachers?	+	** Fregl suggests inviting 1 marketing + args guy if possible? Apol suggests teachers?

	== Action to be taken ==		== Action to be taken ==

User:Frederik

84.57.130.241 — Thu, 19 Nov 2009 22:12:55 GMT

created new account User:Frederik

New page

KDEEdu/Meeting20091119IRC

86.25.217.110 — Thu, 19 Nov 2009 21:50:53 GMT

Added minutes for tonight's meeting

New page

== Discussion of who is maintaining what ==

'''In top-down order from edu.kde.org:'''

* KAnagram: jpwhiting (though not overly)
* KHangman: annma
* KLettres: annma
* KWordQuis: peter (a.k. peah)
* Parley: dani_l (who protests at such)
* KAlgebra: apol
* Kig: pino, who adds 'kig is okay'
* Blinken: tsdgeos
* KGeography: tsdgeos
* KTurtle: piacentini, Niels, cies.
* Kalzium
** To quote Carsen, ''Kalzium is maintained as in "it works". Currently I have 0.0 time for coding, the little coding I do is job related. I would love to see fresh blood in Kalzium but we all would, right? Perhaps I will find time to work on Kalzium of christmas but I doubt it because I am now a father and need time-off with my family.''
* KStars: jason, kstar, some others
* Marble: fine
* Cantor: arieder, new for 4.4

'''Not on edu.kde.org:'''

* Rocs: not on the list, but is fine.

'''Watch list:'''

* Kiten: Kiruwa (8 commits this year) ?
* KBruch: 25 commits this year, not sure if UNESP team from Barzil are active.
* KMPlot: 13 commits this year, though no one responds to apol's emails.
* KTouch: 28 commits this year, none from a recognisable maintainer.
* Step: Needs help.

== Discussion about the Watch List ==

* Given the apps work, removal is not on the agenda.
* piacentini raised the possibility of merging kmplot with kalgebra, as it almost supercedes its functionality at present. apol notes that the key feature in KMPlot missing from KAlgebra is implicit plotting, and (even better) suggests he could perhaps get it done for KAlgebra in KDE 4.5.
* Nightrose enquires about scouting for volunteers. For kalgebra-meets-kmplot, apol will talk to aucuhuasi about it as he also has pending patches. jpwhiting offers to blog about ktouch.
* Nightrose discusses issues in not wanting to scare people off by handing them maintainership, by beginning with reviewed patches. apol proposes using junior jobs for this, and fregl inadvertently offers to mentor.

== Other Discussion ==

* sabineller has asked Eugune for a mascot

* apol notes that in terms of promotion, we need to define what kdeedu is.
** we have apps for parents, young students, not-so-young-students, teachers etc.
** No segmentation in the KDEEDU module.
** 'Right now, kdeedu is just for students, not for teachers+students+fathers+etc.'.
** '...except for rocs.'

* fregl notes it would be great to work with teachers on generating content, especially if it could be made easier.
** piacentini notes there is an active (if small) community, but not many speak English.
** jpwhiting suggests they could get a translator?
** apol has tried to get teachers involved, but found it hard to get much feedback.
** Nighrose suggests being specific, and asking for three pet problems. apol points out they are a potential source of junior jobs, and tsdgeos agrees that fixing three bugs per app would be well received.
** fregl pontificates further on why kdeedu has limited contact with Linux school projects (e.g. scoelinux, edubuntu et al), which contact real teachers and students, and could provide feedback.
** Nightrose suggests the short to medium term emphasis should be on attainable goals - feedback rather than conferences.

* Easy installation for Windows is a hurdle at moment:
** jpwhiting suggests an installer that makes it as easy 'as firefox'?
** fregl mentions having discussed MSI packages.
** puchrojo notes that at present running Parley on windows takes a lot of disk space and uses considerable bandwidth.

* Apol notes consistency between kdeedu applications' user interfaces is weak.
** Fregl agrees that a similar workflow would be good, although must avoid causing re-learning where possible.
** Brand colours for kdeedu? e.g. KDevelop is green instead of blue.
** kdegames did well with the Egyptian theme, motivates similar idea for kdeedu?

* Addressing the issue that people think they must use the KDE workspace to use kdeedu:
** Nightrose notes that it is a problem for amarok also, and the promo folk are working on it.
** Stress in the intro on edu.kde.org?
** dani_l mentions the promo sprint, starting a new kde.org website that will (hopefully) contain pages for all applications.
** as fregl puts it, promote that 'you don't need the plasma desktop in order to run kalzium etc.'
** marketing spring was comparatively recently, so this aligns with general KDE attention at the moment.

* kstar will be busy over the next couple of years, so wants an active feature contributor for kstars; though he can do routine maintenance himself.

* Lowering the bar for what is needed to get started in kde development:
** cmake complains about missing package, user gives up?
** Cornelius's SDK ( [http://blog.cornelius-schumacher.de/2009/07/creating-kde-sdk.html] ), though he is short of time.
** Pluggable applications, and hence python rather than C++?

* EDU Meeting
** Invite from Mario Fuchs to Switzerland.
** Nightrose raises issue of an organiser. Kenny busy with akademy?
** Mario can handle local arrangements, but would need help from the team. Claudia?
** Duration - fregl suggests long weekend? Spring?
** Fregle suggests inviting 1 marketing + args guy if possible? Apol suggests teachers?

== Action to be taken ==

* Scout for volunteers for apps on the watch-list, using blogs, mailing lists, and klassroom.
** For kalgebra-meets-kmplot, apol will talk to aucuhuasi about it.
** Also include kstars (due to kstar's busyness.)
* Possibility of using the 'fan' mechanism on Facebook, as currently done for amarok. Nightrose can create fan pages on demand for peoples' applications.
* Create some junior jobs for unmaintained apps.
* Find Klassroom mentors.
* Create YouTube introduction videos for apps.
* Write for the website explaining what kdeedu is about.
* Ask teachers for their three pet problems with kdeedu apps (perhaps for conversion into junior jobs.)
* Look for someone to help make the kdeedu apps feel more integrated.
* Document 'how to start changing stuff' + meta packages for distros etc.
* Decide tasks for organising EDU meeting.
* doodle.com poll for when people want the meeting (owner: sabineller.)
* Poll to arrange follow-up IRC meeting in 2 or 3 weeks (owner: Nightrose.)
* Ask annma to explain the issues surrounding GHNS, perhaps at next meeting.

KDE Edu

86.25.217.110 — Thu, 19 Nov 2009 21:40:19 GMT

Added skeleton page containing link to minutes from today's IRC meeting

New page

== Minutes from IRC Meetings ==

[[KDEEdu/Meeting20091119IRC|Meeting on IRC, Thursday the 19th of November, 2009]]

Main Page

86.25.217.110 — Thu, 19 Nov 2009 21:35:12 GMT

Added link to new KDE Edu sub-project

← Older revision		Revision as of 21:35, 19 November 2009
Line 14:		Line 14:
	* [[KDE PIM]]		* [[KDE PIM]]
	* [[Promo\|KDE Promo]]		* [[Promo\|KDE Promo]]
		+	* [[KDE Edu]]

Promo/Strategy

66.183.103.183 — Thu, 19 Nov 2009 17:38:29 GMT

← Older revision		Revision as of 17:38, 19 November 2009
Line 1:		Line 1:
-	=~~Goal~~=	+	=Strategies=

-	~~This page lists~~ specific subjects people might have trouble understanding or which are otherwise sensitive. What these things are exactly should be on ~~userbase~~ and ~~techbase~~, but our communication around them is defined here.	+	==The Promo Cycle==
		+	Currently, we have a fixed 6 month cycle for the KDE software compilation. Our promo cycle is designed to keep pace with that development rhythm. For each 4.x release, the promotional messaging will roughly meet up with the development cycle in this manner (times are relative to the release date):
		+
		+	* <b>-2 months</b>: Promo team gathers key talking points for promo around the release. Feature freeze should be around this time, so it's a good opportunity to start rounding up the interesting features and improvements. Work begins on thematic messaging. Publicity levels are lowered slightly to provide a "pause" between the current release and the next one to avoid overexposure or confusing mingling of "now" and "coming" messaging.
		+	* <b>-1 month</b>: betas and release candidates are being released at this point and we release our first "why you're going to love this next release" articles, interviews, etc. The drum banging begins! During this time, the release announcement, feature tours, screencasts, etc. are readied.
		+	* <b>Release month!</b> Press releases and supporting promo assets are sent out and we spread the word far and wide. Getting our "good answers for hot topics" points out amongst the community is a focus.
		+	* <b>Months +1-3</b>: each month, a new "patch level" release is made and we continue to focus on the current release in our interviews and articles. Questions about the next release(s) should be met with positive and curiosity-inducing answers, but should not be allowed to become the focus of any articles or interviews during this time period. Focus on the now is most important to get people trying this release instead of waiting for the next.
		+
		+	As can be seen, the promo cycle is offset by two months as compared to the KDE Software Compilation cycle.
		+
		+	==Hot Topics, Good Answers==
		+	Below is a list of specific subjects people might have trouble understanding or which are otherwise sensitive. What these things are exactly should be on Userbase and Techbase, but our communication strategy around them is defined here.

	* [[Promo/Strategy/Semantik_Desktop\|Semantik_Desktop]]		* [[Promo/Strategy/Semantik_Desktop\|Semantik_Desktop]]

User:Einar

93.34.51.5 — Thu, 19 Nov 2009 17:30:26 GMT

created new account User:Einar

New page

Promo/Strategy/Semantik Desktop

66.183.103.183 — Thu, 19 Nov 2009 17:23:40 GMT

← Older revision		Revision as of 17:23, 19 November 2009
(One intermediate revision not shown)
Line 1:		Line 1:
	=Semantic Desktop communication strategy=		=Semantic Desktop communication strategy=

-		+	Positioning the semantic desktop is not easy. It's a big topic with all kinds
-	Positioning the semantic desktop is not easy. it's a big topic with all kinds	+	of potential but it takes a while to explain all the benefits. Making it more challenging yet, we still don't know what all the benefits will end up
-	of potential but it takes a while to explain all the benefits. ~~And, to be~~	+
-	~~honest with ourselves~~, we still don't know what all the benefits will end up	+
	being, either.		being, either.

-	~~I see a lot of scepticism~~ being voiced in ~~various web boards every time~~ the	+	This leads to understandable skepticism often being voiced in reader comments when the semantic desktop comes up due to this. By providing updated information on resource usage, offering "poster boy" examples of Nepomuk in action and showing how we will be using Nepomuk to do things we already do now (only better) we can turn this around.
-	semantic desktop comes up due to this. ~~Unless the average joe/jane gains some~~	+
-	~~moderate visionary capability~~, ~~i don~~'~~t see this changing~~.	+
		+	==Poster Boy Features==
		+
		+	===Meme===
		+	There are fun and useful things you can do with Nepomuk today.
		+
		+	===Purpose===
		+	Spread awareness of how Nepomuk is actually useful to people in their day-to-day lives, justifying it's existence on their computers.

-	~~The strategy is twofold:~~	+	===Implementation Strategy===
		+	Use a set of "poster boy" features for the semantic desktop as examples whenever discussing Nepomuk and repeat them in every interview / article we do where the semantic desktop comes up. We should have three good examples of new such features for each major KDE release.

-	~~0. identify a set of "poster boy" features for~~ the ~~semantic~~ desktop.	+	===Talking Points===
		+	* If you tag an image in your image viewer, the tag becomes visible in your desktop search. That's how it should be, right?

-	~~1. start a "you won't even know you're using it" meme~~

-	~~Post Boy Features~~	+	==You Won't Even Know Your Using It==
-	~~--------------------------~~	+
-	~~These should be easy and fun or useful things that people can start doing in~~	+
-	~~4.4. we should keep repeating them in every interview / article we do where~~	+
-	~~the semantic desktop comes up. we can pick some new ones for 4.5 to keep it~~	+
-	~~fresh, but we will need to repeat it a lot.~~	+

-	~~Sebas has got us off to a good start with the 'If you tag an image in your~~	+	===Meme===
-	~~image viewer~~, the ~~tag becomes visible in your desktop search~~. ~~That~~'~~s how~~ it	+	Nepomuk bring not only new features, it is also helping improve things we already use and rely on all the time as a "behind the scenes" technology. Often you won't even know you're using it, other than it making the software experience better.
-	~~should be~~, ~~right?' line~~.	+

-	~~we should have 1-2 more such examples, perhaps one including krunner and one~~	+	===Purpose===
-	~~that doesn~~'t ~~include a file manager~~, ~~a desktop search tool or a run command~~	+	The goal is to provide counterpoints to "I don't want to tag all my stuff
-	~~window~~. ~~any ideas?~~	+	manually" and "I don't care for this new fancy stuff, I am happy with
		+	the current functionality I have as it is".

		+	===Talking Points===
		+	* Akonadi is using Nepomuk to power search and information retrieval features we take for granted such as contact lists. When Kontact is fully Akonadi powered,, you'll end up using the semantic desktop tools without even knowing it whenever you use Kontact. The result is your email/contacts/calendaring system will work better, thanks in part to the semantic desktop framework.

-	~~You Won't Even Know Your Using It~~
-	~~------------------------------------------------~~
-	~~one of the common counterpoints made is "i don't want to tag all my stuff~~
-	~~manually"; another is "i don't care for this new fancy stuff, i am happy with~~
-	~~my current sets of functionality".~~

-	~~something that would be good to spread is the message that nepomuk is not just~~	+	==Functionality Challenges Are Being Addressed==
-	~~"another set of exposed features" but is also an integrated framework that~~	+
-	~~will be sitting just under the surface of things we use all the time already,~~	+
-	~~right now.~~	+

-	~~for instance, our groupware system (akonadi) is using it now to power its~~	+	===Meme===
-	~~search and information retrieval. which means that if you use kontact, you'll~~	+	The foundations of Nepomuk are maturing.
-	~~end up using the semantic desktop without even knowing it. you'll just find~~	+
-	~~your email/contacts/calendaring system to work better, thanks in part to the~~	+
-	~~semantic desktop framework~~.	+

-	~~there~~ are ~~similar stories for things like plasma activities~~, and ~~i'm sure~~ we	+	===Purpose===
-	can ~~find other good, approachable examples~~.	+	As a new technology, Nepomuk has been shipped in various broken states by some of our downstreams and has historically used technologies that are new and even immature. This is improving, and we need to spread the word so that Nepomuk's reputation can be rid of these "early days" hiccups.

		+	===Talking Points===
		+	* Due to being a new kind of technology being brought into mainstream use for the first time, tools for the technologies that underpin Nepomuk were few and mostly academic in nature: they worked, but performance was not a goal. Nepomuk is using more and more infrastructure that has been written with production use and performance in mind. The new Virtuoso storage backend is an important step in this.

-	~~Implementation~~	+	* As a new kind of technology, KDE packagers were not familiar with it or all the techniques to deliver it in a well functioning manner to their (and our) users. As packagers are gaining experience with Nepomuk, the quality of system integration is improving and a higher quality user experience is resulting due to improved packaging and out-of-the-box configuration.
-	~~---------------------~~	+
-	~~if there's consensus on~~ the ~~above strategy~~, ~~then we just need~~ to ~~form up~~ the	+
-	~~few talking points we need and then repeat them in enough places often enough~~	+
-	~~until other people start repeating them for us~~. ~~(that's how this works :)~~	+

Promo/Strategy

Jospoortvliet — Thu, 19 Nov 2009 13:12:59 GMT

← Older revision		Revision as of 13:12, 19 November 2009
Line 6:		Line 6:
	* [[Promo/Strategy/Akonadi\|Akonadi]]		* [[Promo/Strategy/Akonadi\|Akonadi]]
	* [[Promo/Strategy/Plasma\|Plasma]]		* [[Promo/Strategy/Plasma\|Plasma]]
-	* [[Promo~~/Strategy~~/Branding\|Branding]]	+	* [[Promo/Branding\|Branding]]

Promo/Strategy/Branding

Jospoortvliet — Thu, 19 Nov 2009 13:12:38 GMT

Blanked the page

New page

Promo/Strategy

Jospoortvliet — Thu, 19 Nov 2009 13:05:41 GMT

← Older revision		Revision as of 13:05, 19 November 2009
Line 6:		Line 6:
	* [[Promo/Strategy/Akonadi\|Akonadi]]		* [[Promo/Strategy/Akonadi\|Akonadi]]
	* [[Promo/Strategy/Plasma\|Plasma]]		* [[Promo/Strategy/Plasma\|Plasma]]
		+	* [[Promo/Strategy/Branding\|Branding]]

Promo/Strategy/Plasma

Jospoortvliet — Thu, 19 Nov 2009 13:03:07 GMT

Created page with '(this page currently only has a few notes) Relationship between widgets, gadgets, applets and plasmoids: All items on the plasma canvas are named "Widgets". Subsets of widgets ...'

New page

(this page currently only has a few notes)

Relationship between widgets, gadgets, applets and plasmoids:

All items on the plasma canvas are named "Widgets". Subsets of widgets would be Plasmoids (native plasma widgets), Google Gadgets, Apple Widgets etcetera.

Promo/Strategy

Jospoortvliet — Thu, 19 Nov 2009 13:01:53 GMT

← Older revision		Revision as of 13:01, 19 November 2009
(One intermediate revision not shown)
Line 3:		Line 3:
	This page lists specific subjects people might have trouble understanding or which are otherwise sensitive. What these things are exactly should be on userbase and techbase, but our communication around them is defined here.		This page lists specific subjects people might have trouble understanding or which are otherwise sensitive. What these things are exactly should be on userbase and techbase, but our communication around them is defined here.

-	* [[Promo/~~Topics~~/~~Nepomuk~~\|~~Nepomuk~~]]	+	* [[Promo/Strategy/Semantik_Desktop\|Semantik_Desktop]]
-	* [[Promo/~~Topics~~/Akonadi\|~~Topics~~]]	+	* [[Promo/Strategy/Akonadi\|Akonadi]]
-	* [[Promo/~~Topics~~/Plasma\|~~Topics~~]]	+	* [[Promo/Strategy/Plasma\|Plasma]]

Promo/Strategy/Semantik Desktop

Jospoortvliet — Thu, 19 Nov 2009 12:41:03 GMT

← Older revision		Revision as of 12:41, 19 November 2009
Line 1:		Line 1:
-	=~~Nepomuk~~ communication strategy=	+	=Semantic Desktop communication strategy=

Promo/Strategy/Nepomuk

Jospoortvliet — Thu, 19 Nov 2009 12:40:40 GMT

moved [[Promo/Strategy/Nepomuk]] to [[Promo/Strategy/Semantik Desktop]]

New page

Promo

Jospoortvliet — Thu, 19 Nov 2009 12:37:57 GMT

← Older revision		Revision as of 12:37, 19 November 2009
Line 16:		Line 16:
	* List of [[Promo/Events\|Events]] KDE will visit.		* List of [[Promo/Events\|Events]] KDE will visit.
	* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.		* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.
-	* ~~List of~~ [[Promo/~~Topics~~\|~~Topics~~]] ~~people might have questions about like Nepomuk and Akonadi~~, ~~and our communication strategy around~~ those.	+	* The communcation [[Promo/Strategy\|Strategy]] can be found here. It lists specific topics which are hard to communicate or controversial. When writing or talking, look at those.

Promo/Topics/Nepomuk

Jospoortvliet — Thu, 19 Nov 2009 12:37:00 GMT

moved [[Promo/Topics/Nepomuk]] to [[Promo/Strategy/Nepomuk]] as discussed

New page

Promo/Topics

Jospoortvliet — Thu, 19 Nov 2009 12:36:39 GMT

moved [[Promo/Topics]] to [[Promo/Strategy]]

New page

Promo/Topics/Nepomuk

Jospoortvliet — Thu, 19 Nov 2009 12:34:37 GMT

first version based on email by Aaron

New page

=Nepomuk communication strategy=

Positioning the semantic desktop is not easy. it's a big topic with all kinds
of potential but it takes a while to explain all the benefits. And, to be
honest with ourselves, we still don't know what all the benefits will end up
being, either.

I see a lot of scepticism being voiced in various web boards every time the
semantic desktop comes up due to this. Unless the average joe/jane gains some
moderate visionary capability, i don't see this changing.

The strategy is twofold:

0. identify a set of "poster boy" features for the semantic desktop.

1. start a "you won't even know you're using it" meme

Post Boy Features
--------------------------
These should be easy and fun or useful things that people can start doing in
4.4. we should keep repeating them in every interview / article we do where
the semantic desktop comes up. we can pick some new ones for 4.5 to keep it
fresh, but we will need to repeat it a lot.

Sebas has got us off to a good start with the 'If you tag an image in your
image viewer, the tag becomes visible in your desktop search. That's how it
should be, right?' line.

we should have 1-2 more such examples, perhaps one including krunner and one
that doesn't include a file manager, a desktop search tool or a run command
window. any ideas?

You Won't Even Know Your Using It
------------------------------------------------
one of the common counterpoints made is "i don't want to tag all my stuff
manually"; another is "i don't care for this new fancy stuff, i am happy with
my current sets of functionality".

something that would be good to spread is the message that nepomuk is not just
"another set of exposed features" but is also an integrated framework that
will be sitting just under the surface of things we use all the time already,
right now.

for instance, our groupware system (akonadi) is using it now to power its
search and information retrieval. which means that if you use kontact, you'll
end up using the semantic desktop without even knowing it. you'll just find
your email/contacts/calendaring system to work better, thanks in part to the
semantic desktop framework.

there are similar stories for things like plasma activities, and i'm sure we
can find other good, approachable examples.

Implementation
---------------------
if there's consensus on the above strategy, then we just need to form up the
few talking points we need and then repeat them in enough places often enough
until other people start repeating them for us. (that's how this works :)

Promo/Topics

Jospoortvliet — Thu, 19 Nov 2009 12:33:08 GMT

first page

New page

=Goal=

This page lists specific subjects people might have trouble understanding or which are otherwise sensitive. What these things are exactly should be on userbase and techbase, but our communication around them is defined here.

* [[Promo/Topics/Nepomuk|Nepomuk]]
* [[Promo/Topics/Akonadi|Topics]]
* [[Promo/Topics/Plasma|Topics]]

Promo

Jospoortvliet — Thu, 19 Nov 2009 12:31:25 GMT

adding some new pages

← Older revision		Revision as of 12:31, 19 November 2009
Line 13:		Line 13:

	* List of [[Promo/DotIdeas\|Ideas]] for DOT articles.		* List of [[Promo/DotIdeas\|Ideas]] for DOT articles.
		+	* List of [[Promo/Tasks\|Tasks]] we have - and progress on them.
	* List of [[Promo/Events\|Events]] KDE will visit.		* List of [[Promo/Events\|Events]] KDE will visit.
	* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.		* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.
		+	* List of [[Promo/Topics\|Topics]] people might have questions about like Nepomuk and Akonadi, and our communication strategy around those.

Promo/Branding/Rebranding KDE

Cornelius — Wed, 18 Nov 2009 23:58:00 GMT

← Older revision		Revision as of 23:58, 18 November 2009
Line 3:		Line 3:
	There is a detailed proposal about the rebranding effort, which has been discussed over the last months and has gained broad acceptance in all parts of the community.		There is a detailed proposal about the rebranding effort, which has been discussed over the last months and has gained broad acceptance in all parts of the community.

		+	* [http://cornelius-schumacher.de/repositioning-the-kde-brand.pdf KDE Rebranding Proposal v1.1.0]
	* [http://markmail.org/message/ruajryjfbfdmgccl KDE Rebranding Proposal v1.0.2]		* [http://markmail.org/message/ruajryjfbfdmgccl KDE Rebranding Proposal v1.0.2]

Promo

Cornelius — Wed, 18 Nov 2009 23:35:29 GMT

← Older revision		Revision as of 23:35, 18 November 2009
Line 1:		Line 1:
-	Marketing and Promotion	+	= Marketing and Promotion =

-	The marketing and promo team in KDE attends trade fairs and conferences, informing visitors using a booth and giving talks. We also write news articles, work on release announcements and other content for our webpages. If you're interested what we are doing, contact us by sending an email to kde-promo@kde.org!	+	The marketing and promo team in KDE attends trade fairs and conferences, informing visitors using a booth and giving talks. We also write news articles, work on release announcements and other content for our webpages. If you're interested what we are doing, contact us by sending an email to [mailto:kde-promo@kde.org kde-promo@kde.org]!

-	~~Just putting some ideas in here~~:	+	More info:

		+	* [[Promo/Branding\|Branding]]
		+	* [[Promo/Strategy\|Strategy]]

-	~~List of [[Promo/DotIdeas\|~~Ideas~~]] for DOT articles.~~	+	== Ideas ==

-	~~List of [[Promo/Events\|Events]] KDE will visit.~~	+	Just putting some ideas in here:

-	List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.	+	* List of [[Promo/DotIdeas\|Ideas]] for DOT articles.
		+	* List of [[Promo/Events\|Events]] KDE will visit.
		+	* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.

Promo/Branding/Software Label

Cornelius — Wed, 18 Nov 2009 23:30:58 GMT

Created page with '= KDE Software Label = For giving application developers, and in particular 3rd party developers, a way to identify themselves with KDE and label their software as belonging to ...'

New page

= KDE Software Label =

For giving application developers, and in particular 3rd party developers, a way to identify themselves with KDE and label their software as belonging to KDE we provide a standard KDE software label. This can be used to communicate that developers feel as part of the KDE community or that they use the KDE platform. It can be used for example on application web sites, in the about dialog of applications or in general communication about applications, especially in cases where it's not obvious that an application is part of KDE or making use of KDE technology.

Candidates for the label:

* Made with KDE technology
* Powered by KDE
* Free Software by KDE
* Built on the KDE platform
* Part of the KDE family

We'll perform a poll on kde-apps to get feedback from the people who are supposed to use this label and then decide about what to use. We might end up with more than one label. When we have decided about the label, we'll get some graphics, banners, etc. done ready to use for people who want to associate their software with KDE.

Promo/Branding

Cornelius — Wed, 18 Nov 2009 23:30:01 GMT

← Older revision		Revision as of 23:30, 18 November 2009
(One intermediate revision not shown)
Line 3:		Line 3:
	* [[Promo/Branding/Rebranding KDE\|Rebranding KDE]]		* [[Promo/Branding/Rebranding KDE\|Rebranding KDE]]
	* [[Promo/Branding/Map\|Brand Map]]		* [[Promo/Branding/Map\|Brand Map]]
		+	* [[Promo/Branding/Software Label\|KDE Software Label]]

Promo/Branding/Map

Cornelius — Wed, 18 Nov 2009 23:29:09 GMT

Created page with '= KDE Brand Map = This document describes the various brands used by the KDE community. It outlines the relationship of the brands and gives some guidance how to use them. These...'

New page

= KDE Brand Map =

This document describes the various brands used by the KDE community. It outlines the relationship of the brands and gives some guidance how to use them. These brands are meant for communication to users. They are not necessarily related to names of SVN modules, package names, or how application names are used internally by the contributors community.

== Umbrella brand ==

The brand "KDE" stands for the KDE community, also used as "KDE Community" or "KDE Team". It acts as umbrella brand for the sub brands used for naming applications, application suites, or sub communities. KDE as a brand transports the KDE values such as freedom, technical excellence, beauty, pragmatism, portability, open standards, international collaboration, professionalism, respect, and great teamwork.

== Products ==

Software created by the KDE community is branded on its own under the umbrella brand of KDE. Use of "KDE" in the product name is optional and depending on the context. Especially for the names which are not recognizable as KDE applications because they don't use a K as prefix in their name it's recommended to use "KDE" in the product name.

=== KDE Applications ===

KDE applications make up the breadth and richness of the KDE universe. They are solutions to specific use cases. KDE applications can run independently of the KDE workspace and can freely be mixed with applications based on other platforms and toolkits.

* "Okular" or "KDE Okular"
* "Dolphin" or "KDE Dolphin"
* "Amarok"
* "Krita" or "KDE Krita"
* "KWord"
* "KPresenter"
* "KDE Kontact" or "Kontact"
* "KDevelop"
* "Plasmate" or "KDE Plasmate"
* "KSysguard"
* "K3B"
* ...

=== KDE Application Suites ===

There are a couple of brands which are used to identify application suites built up from several applications. These can be used just like application names when referring to a set of related applications as bundled under the application suite brand. Those brands are sometimes also used to refer to a subcommunity.

* "KOffice" (KWord, Krita, ...)
* "KDE Kontact" or "Kontact" (KMail, KOrganizer, KAddressbook, ...)
* "KDE Edu"

=== KDE Workspaces ===

KDE provides workspaces. These provide the environment for running and managing applications and integrate interaction of applications. The workspaces are designed as generic environment for all kind of desktop applications, not only applications built on the KDE platform. They integrate best with applications following the standards used by the KDE platform. There are different flavors of the workspace to address the needs of specific groups of users or adapt to specific hardware platforms.

* "Plasma Desktop" or "KDE Plasma Desktop". This is the workspace for desktop computers. It's built on the classical paradigm of a "desktop environment". Its components are KWin, KDM, Plasma desktop shell, KSysguard and System Settings. The components are not marketed to end users.
* "Plasma Netbook" or "KDE Plasma Netbook". This is the workspace for computers with a small display, e.g. Netbooks.
* "Plasma Mobile" or "KDE Plasma Mobile". This is the workspace for small devices, e.g. phones, which also provide a special environment like touch screens.

=== KDE Platform ===

KDE Software is based on the "KDE Platform", the base of libraries and services which are needed to run KDE applications. Especially when including development frameworks and tools it is referred to as "KDE Development Platform". It's built on a number of Pillars (Akonadi, Solid, Nepomuk, Phonon, Plasma, ...), distinct parts of the development platform. The pillars are not marketed to end users.

=== KDE Software Compilation ===

The KDE community does regular releases of a core set of KDE software components. These releases are called "KDE Software Compilation" and tagged with a version number, e.g. "The KDE community is releasing the KDE Software Compilation 4.4".

== People ==

The KDE community consists of several sub communities, teams working on a specific part of KDE software. They use names which partly also have a unique identity as a brand. Some of the teams share the name with the application or the application suite they work on. These names are important for keeping the identity of the teams, but they are not marketed to end users.

* KDE Bug Squad
* KDE Promo
* KDE PIM
* KOffice
* Amarok Team
* KDE Edu
* ...

Promo/Branding/Rebranding KDE

Cornelius — Wed, 18 Nov 2009 23:25:15 GMT

New page

We want to reposition the brand "KDE" and move it from standing for the desktop to standing for the community. This reflects the growth and development of the community and the software KDE creates. It also aims at eliminating the misconception that KDE software is only running on a KDE desktop and the KDE desktop can only run KDE software.

There is a detailed proposal about the rebranding effort, which has been discussed over the last months and has gained broad acceptance in all parts of the community.

* [http://markmail.org/message/ruajryjfbfdmgccl KDE Rebranding Proposal v1.0.2]

Promo/Branding

Cornelius — Wed, 18 Nov 2009 23:13:04 GMT

Created page with 'Overview of KDE branding. * Rebranding KDE * Brand Map'

New page

Overview of KDE branding.

* [[Promo/Branding/Rebranding KDE|Rebranding KDE]]
* [[Promo/Branding/Map|Brand Map]]

← Older revision		Revision as of 13:12, 19 November 2009
Line 6:		Line 6:
	* [[Promo/Strategy/Akonadi\|Akonadi]]		* [[Promo/Strategy/Akonadi\|Akonadi]]
	* [[Promo/Strategy/Plasma\|Plasma]]		* [[Promo/Strategy/Plasma\|Plasma]]
-	* [[Promo~~/Strategy~~/Branding\|Branding]]	+	* [[Promo/Branding\|Branding]]

← Older revision		Revision as of 13:05, 19 November 2009
Line 6:		Line 6:
	* [[Promo/Strategy/Akonadi\|Akonadi]]		* [[Promo/Strategy/Akonadi\|Akonadi]]
	* [[Promo/Strategy/Plasma\|Plasma]]		* [[Promo/Strategy/Plasma\|Plasma]]
		+	* [[Promo/Strategy/Branding\|Branding]]

← Older revision		Revision as of 12:37, 19 November 2009
Line 16:		Line 16:
	* List of [[Promo/Events\|Events]] KDE will visit.		* List of [[Promo/Events\|Events]] KDE will visit.
	* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.		* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.
-	* ~~List of~~ [[Promo/~~Topics~~\|~~Topics~~]] ~~people might have questions about like Nepomuk and Akonadi~~, ~~and our communication strategy around~~ those.	+	* The communcation [[Promo/Strategy\|Strategy]] can be found here. It lists specific topics which are hard to communicate or controversial. When writing or talking, look at those.

← Older revision		Revision as of 12:31, 19 November 2009
Line 13:		Line 13:

	* List of [[Promo/DotIdeas\|Ideas]] for DOT articles.		* List of [[Promo/DotIdeas\|Ideas]] for DOT articles.
		+	* List of [[Promo/Tasks\|Tasks]] we have - and progress on them.
	* List of [[Promo/Events\|Events]] KDE will visit.		* List of [[Promo/Events\|Events]] KDE will visit.
	* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.		* List of [[Promo/Events/Speakers\|Speakers]] available for talks about KDE related topics.
		+	* List of [[Promo/Topics\|Topics]] people might have questions about like Nepomuk and Akonadi, and our communication strategy around those.