Marketing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AutoSpider (talk | contribs) (Revert mailing list links: "lists.qt.io" -> "lists.qt-project.org") |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
=Warning, old content from 2012= | |||
==Scope== | |||
Still needs polishing: | Still needs polishing: | ||
* Website content, including news & | * Website content, including news & releases. | ||
* [[Events]] (participation, sponsorship, organization…). Including [[Qt Contributors Summit]] & | * [[Events]] (participation, sponsorship, organization…). Including [[Qt Contributors Summit]] & [[Qt Contributors Day|Qt Contributors Days]]. | ||
* Community engagement & | * Community engagement & contributions. | ||
* Qt advocacy & | * Qt advocacy & pride. See also [[Marketing/Materials]]. | ||
* Promoting Qt related projects & | * Promoting Qt related projects & organizations. | ||
Discuss at the [http://lists.qt. | Discuss at the [http://lists.qt-project.org/mailman/listinfo/marketing marketing list]! | ||
== Priorities == | == Priorities == | ||
| Line 15: | Line 19: | ||
There is no hard process to define priorities. You can list new tasks at the bottom of the list and discuss their priority at the Marketing list. Tasks taken seriously must have someone driving them and a link to a wiki page or bug report. You can join and push any task. | There is no hard process to define priorities. You can list new tasks at the bottom of the list and discuss their priority at the Marketing list. Tasks taken seriously must have someone driving them and a link to a wiki page or bug report. You can join and push any task. | ||
# Sort out the Qt Project [[Events]] strategy | |||
# Sort out the Qt Project [[Events]] strategy | |||
#* This is urgent for planning and budgeting purposes. The big venues and the Qt Contributors Summit haven't been agreed yet. | #* This is urgent for planning and budgeting purposes. The big venues and the Qt Contributors Summit haven't been agreed yet. | ||
# '''Bootstrap [[QtonPi|Qt 5 on Raspberry Pi]] project | |||
# '''Bootstrap [[QtonPi|Qt 5 on Raspberry Pi]] project | |||
#* Urgent because of the timing (boards available soon) and important because it sets a precedent for new projects joining the Qt Project. | #* Urgent because of the timing (boards available soon) and important because it sets a precedent for new projects joining the Qt Project. | ||
#* Select mentors and new board owners within the [[QtonPi/Device_program|Device program | #* Select mentors and new board owners within the [[QtonPi/Device_program|Device program]] | ||
#* Image and documentation to boot Qt 5 in the Raspberry Pi | #* Image and documentation to boot Qt 5 in the Raspberry Pi | ||
# '''Qt Roadmap''' | # '''Qt Roadmap''' | ||
#* The Qt roadmap and roadmapping process need to be documented. The information is out there but clear only to insiders. | #* The Qt roadmap and roadmapping process need to be documented. The information is out there but clear only to insiders. | ||
#* Many companies are confused about how to propose / push features and major changes. | #* Many companies are confused about how to propose / push features and major changes. | ||
#* Related: [[5.0 Feature Requirements]] | #* Related: [[5.0 Feature Requirements]] | ||
# '''Metrics''' | # '''Metrics''' | ||
#* Important to measure the progress of the project and the participation of diverse individuals and organizations. | #* Important to measure the progress of the project and the participation of diverse individuals and organizations. | ||
#* What metrics do we need? What are we measuring already? What can technically be measured? | #* What metrics do we need? What are we measuring already? What can technically be measured? | ||
#* The sooner we start (with something simple), the better we will track progress. | #* The sooner we start (with something simple), the better we will track progress. | ||
#* Who is directly involved & doing what. | |||
#* Who is directly involved & | |||
#* Product definition, key messages. | #* Product definition, key messages. | ||
#** We need an architecture overview. | #** We need an architecture overview. | ||
#* Unstable and final releases, launch activities. | #* Unstable and final releases, launch activities. | ||
#* How to get everybody involved spreading Qt 5. | #* How to get everybody involved spreading Qt 5. | ||
#* http://qt.io doesn't have a news section yet there are plenty of sources and channels for Qt news | #* http://qt.io doesn't have a news section yet there are plenty of sources and channels for Qt news | ||
#** we are building up a more comprehensive news section on http://qt.io/news which will grow over time | #** we are building up a more comprehensive news section on http://qt.io/news which will grow over time | ||
| Line 51: | Line 43: | ||
#** we suggest news worthy items to be sent to the marketing list and one of us turning it into a news item on the site for now, until we have better functionality in place | #** we suggest news worthy items to be sent to the marketing list and one of us turning it into a news item on the site for now, until we have better functionality in place | ||
#* the current idea is also to add a Planet feature to DevNet, this needs to be investigated further before we can go into more detail | #* the current idea is also to add a Planet feature to DevNet, this needs to be investigated further before we can go into more detail | ||
# '''Organize [[Qt local groups]]''' | |||
# '''Organize [[Qt local groups]]''' | |||
#* There are many Qt and Qt-like local groups in the World. How to articulate them around the Qt Project? | #* There are many Qt and Qt-like local groups in the World. How to articulate them around the Qt Project? | ||
#* This is important to organize locally many activities, and also to find good contacts at a regional / national level. | #* This is important to organize locally many activities, and also to find good contacts at a regional / national level. | ||
# '''Decide on a Qt [[Software Catalog]]''' | # '''Decide on a Qt [[Software Catalog]]''' | ||
#* Apps and software available is a key aspect for a technology selection nowadays, yet it's not easy to find out what is being developed with Qt. | #* Apps and software available is a key aspect for a technology selection nowadays, yet it's not easy to find out what is being developed with Qt. | ||
#* This would be a catalog of entries maintained by their own developers that could host packages organized by OS & | #* This would be a catalog of entries maintained by their own developers that could host packages organized by OS & form factor. | ||
# '''Collaboration with KDE''' | # '''Collaboration with KDE''' | ||
# '''Companies contributing to the Qt Project''' | |||
# '''Companies contributing to the Qt Project''' | |||
#* Currently companies aren't featured or even recognized at a Qt Project level. | #* Currently companies aren't featured or even recognized at a Qt Project level. | ||
#* We must understand better the needs and find solutions. | #* We must understand better the needs and find solutions. | ||
#* There have been vague discussions about the possibility of a body like the GNOME Foundation advisory board. | #* There have been vague discussions about the possibility of a body like the GNOME Foundation advisory board. | ||
#* There is still confusion and doubts about the long term commitment of Nokia in Qt. | #* There is still confusion and doubts about the long term commitment of Nokia in Qt. | ||
#* Easier to find the farther you go from the core group of Qt contributors. | #* Easier to find the farther you go from the core group of Qt contributors. | ||
#* A wiki page summarizing and linking to all the information available would help a lot already. | #* A wiki page summarizing and linking to all the information available would help a lot already. | ||
# '''University collaboration''' | # '''University collaboration''' | ||
#* There are lots of good quality materials and noticeable interest, but how to connect everything? | #* There are lots of good quality materials and noticeable interest, but how to connect everything? | ||
| Line 77: | Line 63: | ||
There is no official structure in place yet, but here goes a self-nominated list as a first approximation. Add yourself if you want to help or drive a task: | There is no official structure in place yet, but here goes a self-nominated list as a first approximation. Add yourself if you want to help or drive a task: | ||
Latest revision as of 02:41, 18 April 2015
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
Warning, old content from 2012
Scope
Still needs polishing:
- Website content, including news & releases.
- Events (participation, sponsorship, organization…). Including Qt Contributors Summit & Qt Contributors Days.
- Community engagement & contributions.
- Qt advocacy & pride. See also Marketing/Materials.
- Promoting Qt related projects & organizations.
Discuss at the marketing list!
Priorities
There is no hard process to define priorities. You can list new tasks at the bottom of the list and discuss their priority at the Marketing list. Tasks taken seriously must have someone driving them and a link to a wiki page or bug report. You can join and push any task.
- Sort out the Qt Project Events strategy
- This is urgent for planning and budgeting purposes. The big venues and the Qt Contributors Summit haven't been agreed yet.
- Bootstrap Qt 5 on Raspberry Pi project
- Urgent because of the timing (boards available soon) and important because it sets a precedent for new projects joining the Qt Project.
- Select mentors and new board owners within the Device program
- Image and documentation to boot Qt 5 in the Raspberry Pi
- Qt Roadmap
- The Qt roadmap and roadmapping process need to be documented. The information is out there but clear only to insiders.
- Many companies are confused about how to propose / push features and major changes.
- Related: 5.0 Feature Requirements
- Metrics
- Important to measure the progress of the project and the participation of diverse individuals and organizations.
- What metrics do we need? What are we measuring already? What can technically be measured?
- The sooner we start (with something simple), the better we will track progress.
- Who is directly involved & doing what.
- Product definition, key messages.
- We need an architecture overview.
- Unstable and final releases, launch activities.
- How to get everybody involved spreading Qt 5.
- http://qt.io doesn't have a news section yet there are plenty of sources and channels for Qt news
- we are building up a more comprehensive news section on http://qt.io/news which will grow over time
- the section is meant to collect very short news items that link to more comprehensive blogs, announcements, etc.
- we suggest news worthy items to be sent to the marketing list and one of us turning it into a news item on the site for now, until we have better functionality in place
- the current idea is also to add a Planet feature to DevNet, this needs to be investigated further before we can go into more detail
- Organize Qt local groups
- There are many Qt and Qt-like local groups in the World. How to articulate them around the Qt Project?
- This is important to organize locally many activities, and also to find good contacts at a regional / national level.
- Decide on a Qt Software Catalog
- Apps and software available is a key aspect for a technology selection nowadays, yet it's not easy to find out what is being developed with Qt.
- This would be a catalog of entries maintained by their own developers that could host packages organized by OS & form factor.
- Collaboration with KDE
- Companies contributing to the Qt Project
- Currently companies aren't featured or even recognized at a Qt Project level.
- We must understand better the needs and find solutions.
- There have been vague discussions about the possibility of a body like the GNOME Foundation advisory board.
- There is still confusion and doubts about the long term commitment of Nokia in Qt.
- Easier to find the farther you go from the core group of Qt contributors.
- A wiki page summarizing and linking to all the information available would help a lot already.
- University collaboration
- There are lots of good quality materials and noticeable interest, but how to connect everything?
People
There is no official structure in place yet, but here goes a self-nominated list as a first approximation. Add yourself if you want to help or drive a task: