Meego Wiki
Views

Developer engagement

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Who?)
(change preformatted text to lists)
 
(4 intermediate revisions not shown)
Line 18: Line 18:
Or, in a word: Mentoring.
Or, in a word: Mentoring.
-
- Helping new developers find their feet
+
* Helping new developers find their feet
-
- Teaching developers new tricks
+
* Teaching developers new tricks
-
- Exchanging knowledge throughout the community to ensure equal footing
+
* Exchanging knowledge throughout the community to ensure equal footing
A simple summary would be that *no* application developer should feel alone, or be confused. ;)
A simple summary would be that *no* application developer should feel alone, or be confused. ;)
Line 28: Line 28:
== How? ==
== How? ==
Tutorials
Tutorials
-
- Wiki based
+
* Wiki based
-
- Forum threads for feedback and questions
+
* Forum threads for feedback and questions
Classes
Classes
-
- On IRC
+
* On IRC
-
- Covering tutorial material and topics which don't quite fit into a tutorial, e.g. "how to write responsive UI"
+
* Covering tutorial material and topics which don't quite fit into a tutorial, e.g. "how to write responsive UI"
-
- Possibly split out into a tutorial *after* each class, if the topic is self-contained enough
+
* Possibly split out into a tutorial *after* each class, if the topic is self-contained enough
   
   
Mentoring
Mentoring
-
- A 'buddy' type system. Skilled developers offer to take on an eager trainee or two (or three or four) and 'show them the ropes'.
+
* A 'buddy' type system. Skilled developers offer to take on an eager trainee or two (or three or four) and 'show them the ropes'. It might be as simple as asking them how their project is going, and where they're getting stuck - from time to time - or as difficult as actually pitching in and helping them hack. Not really a role I want to define in terms beyond something like a 'big geeky brother'. :)
-
  It might be as simple as asking them how their project is going, and where they're getting stuck - from time to time - or as
+
-
  difficult as actually pitching in and helping them hack. Not really a role I want to define in terms beyond something like a
+
-
  'big geeky brother'. :)
+
== Who? ==
== Who? ==
Line 47: Line 44:
*  [http://meego.com/users/w00t Robin Burchell] - coordination, tutorials, classes, mentoring - Python, C++, Qt, git, misc.
*  [http://meego.com/users/w00t Robin Burchell] - coordination, tutorials, classes, mentoring - Python, C++, Qt, git, misc.
*  [http://meego.com/users/digitalsurgeon Ahmad Mushtaq] - classes, C++, Qt, git, QML/QtQuick.
*  [http://meego.com/users/digitalsurgeon Ahmad Mushtaq] - classes, C++, Qt, git, QML/QtQuick.
-
*  [http://meego.com/users/venemo Timur Kristóf] - C++ and SVN, Qt basics, helping .NET developers to get started with Qt.
+
*  [http://meego.com/users/venemo Timur Kristóf] - C++ and SVN, Qt basics, OOP, UI design, C#/.NET + helping .NET developers to get started with Qt.
*  [http://meego.com/users/jflatt Jason Flatt] - tutorials, classes, mentoring - C++, Qt, OOP
*  [http://meego.com/users/jflatt Jason Flatt] - tutorials, classes, mentoring - C++, Qt, OOP
*  [http://meego.com/users/weggi Veikko Tapaninen] - tutorials, classes - Qt, Qt Mobility API
*  [http://meego.com/users/weggi Veikko Tapaninen] - tutorials, classes - Qt, Qt Mobility API
Line 57: Line 54:
*  [http://meego.com/users/epage Ed Page] - tutorial, mentoring  - C++, Python, (Py)Qt, GIT, Portable UIs also
*  [http://meego.com/users/epage Ed Page] - tutorial, mentoring  - C++, Python, (Py)Qt, GIT, Portable UIs also
*  [http://meego.com/users/thp Thomas Perl] - mentoring - Python, C, (Py)GTK, (Py)Qt, Git, UX, WebKit
*  [http://meego.com/users/thp Thomas Perl] - mentoring - Python, C, (Py)GTK, (Py)Qt, Git, UX, WebKit
 +
 +
== Another language version of this page (Simplified Chinese - 简体中文)==
 +
 +
[[DeveloperEngagement chinese|Simplified Chinese - 简体中文]]

Latest revision as of 13:36, 21 March 2011

Contents

MeeGo Application Developer Engagement

This is mostly targetted at existing application developer-type people, especially those with Qt knowledge, although all are welcome to participate in some way or another.

Some background: We have a lot of highly productive developers that are not sure how their skills will remain relevant in a MeeGo context. We can't afford to lose them through neglect. There are also even more developers not familiar with MeeGo. When they find us, we have to grab them and keep them.

Basically, we can't afford to lose our developers, and we need to gain more. I need help. I've written tutorials and helped a lot of people in the past, but frankly, it is not enough. We need to do more. The hands of many lighten that load.


What?

The success of a platform is usually directly linked to its support and nurturing of developer talent. Great platforms have often withered without developer attention, and bad platforms have survived technical flaws thanks to high developer engagement and retention.

I think we need this around MeeGo, and our related platform - Qt.

Specifically, we need to provide education, support (moral and technical), and a feedback cycle - for application developers.

Or, in a word: Mentoring.

  • Helping new developers find their feet
  • Teaching developers new tricks
  • Exchanging knowledge throughout the community to ensure equal footing

A simple summary would be that *no* application developer should feel alone, or be confused. ;)

As an added benefit, rough edges and other nasties become more obvious, and can (hopefully) be addressed instead of falling to the wayside, and losing valuable developers as a consequence.

How?

Tutorials

  • Wiki based
  • Forum threads for feedback and questions

Classes

  • On IRC
  • Covering tutorial material and topics which don't quite fit into a tutorial, e.g. "how to write responsive UI"
  • Possibly split out into a tutorial *after* each class, if the topic is self-contained enough

Mentoring

  • A 'buddy' type system. Skilled developers offer to take on an eager trainee or two (or three or four) and 'show them the ropes'. It might be as simple as asking them how their project is going, and where they're getting stuck - from time to time - or as difficult as actually pitching in and helping them hack. Not really a role I want to define in terms beyond something like a 'big geeky brother'. :)

Who?

If you're interested in helping out, please note the areas (tutorials, classes, mentoring) that you're willing to help out with - and a (very) brief rundown on your skills.

  • Robin Burchell - coordination, tutorials, classes, mentoring - Python, C++, Qt, git, misc.
  • Ahmad Mushtaq - classes, C++, Qt, git, QML/QtQuick.
  • Timur Kristóf - C++ and SVN, Qt basics, OOP, UI design, C#/.NET + helping .NET developers to get started with Qt.
  • Jason Flatt - tutorials, classes, mentoring - C++, Qt, OOP
  • Veikko Tapaninen - tutorials, classes - Qt, Qt Mobility API
  • Felipe Crochik - tutorials, mentoring - OOP (C++, JAVA, C#), Qt/Qt Mobility (maemo)
  • Timo Härkönen - tutorials, mentoring - OOP, C++, Qt
  • Tyler Starke - mentoring - Python, PyQt4 (Portable UI's with PyQt and Python)
  • Robbie Newman - tutorials, mentoring, classes - C++, QT, QT Mobility, OOP
  • Nicola De Filippo - tutorials, mentoring - OOP, C++, Qt, Qt/Qt Mobility (maemo)
  • Ed Page - tutorial, mentoring - C++, Python, (Py)Qt, GIT, Portable UIs also
  • Thomas Perl - mentoring - Python, C, (Py)GTK, (Py)Qt, Git, UX, WebKit

Another language version of this page (Simplified Chinese - 简体中文)

Simplified Chinese - 简体中文

Personal tools