Planet maemo: category "feed:a7ebd5f9cfd7ca3830cb6317611d7f18"

Randall Arnold

Akademy 2010: Day 2

2010-07-04 13:30 UTC  by  Randall Arnold
0
0

I just sat through a talk by Aaron Seigo where he outlined the challenges for KDE.  Very stimulating discussion.

As a newcomer to KDE I was struck by the singular fact that nothing he said was new per se.  When he kidded the community for falling short with documentation and global teaming I was put in mind of our similar struggles in Maemo.  So in one sense it was refreshing that that we weren’t the only ones to battle managerial sort of demons and in another frustrating in that his points appear to reinforce the idea that open source communities can’t establish the same degree of discipline as corporate efforts.

This is something we encountered at maemo.org when attempting to implement a usable software quality assurance process.  We were looking for balance between chaos and clampdown and stymied by the fact that contributions tried to pull the dialog kicking and screaming into one or another corner (as an aside, it was this very experience that led to our feedback project for MeeGo).

Aaron explained to his audience here that consensus doesn’t always mean 100% agreement and he is correct.  A manager of mine once explained that I didn’t have to agree with him, but I had to align.  When I understood what he meant I saw the beauty in that statement.  His point of course was that ultimately someone had to break logjams and naturally that’s the guy in charge.

But in open governance models there’s very often a public perception that there is no one in charge– indeed, the sense is that there shouldn’t be anyone in charge.  Yet how successful is any project erected in anarchy?  I know of none.  Yes, “anarchy” is often a necessary early component of brainstorming but even that process is supposed to eventually lead to norming and performing.

As KDE grows it will need to at least borrow elements of governance and coordination from corporate models.  But at the same time, I think we all understand that even corporations have not managed to perfect that model and that bureaucracy (clampdown) is a common consequence of corporate management run amok.

Aaron wrapped up by challenging the KDE community to adopt elegance as its mantra, in recognition of the success companies like Apple have enjoyed with high visual appeal in their user experience.  The designer in me concedes the point, and hopes KDE finds its way to an acceptable elegance.  At the same time, the engineer in me has a bottom line desire for performance, and I will gladly sacrifice some eye candy for quick click-throughs.  But I am an atypical user and what KDE needs to achieve here is general consensus.  Hopefully they will find it.


Filed under: Delivering Quality, Great Governance, Mentioning Maemo, Mentioning MeeGo, The Write Stuff, Views and Reviews Tagged: 2010, Aaron Seigo, Akademy, Finland, KDE, Tampere
Categories: Delivering Quality
Randall Arnold

Akademy 2010: Day 1

2010-07-03 16:10 UTC  by  Randall Arnold
0
0

I’m typing this up toward the end of Akademy 2010‘s day 1 in beautiful Tampere, Finland, so please forgive any signs of weariness.

The day began with Valtteri Halla promoting Meego and demonstrating how the project has already benefitted KDE, Akademy’s coordinating organization, with upstream development for KOffice and other applications.  From there came talks along the tracks of community and mobility, including mine on user engagement (presentation to come soon; project site here).  Even Maemo was mentioned!

I was nervous about my talk but while it didn’t go as smoothly as I would have liked, it wasn’t the disaster I feared either.  I’ll take that.  ;)

I was encouraged by Henri Bergius’ presentation on GeoClue, a  low-level MeeGo architecture component supporting location services by a variety of means.  Since part of the MeeGo User Engagement Framework (MUEF) wishes for location-sensitive feedback and input mechanisms for mobile devices, seeing that this was already embedded into MeeGo offers some hope.  I’ll update our wiki appropriately soon.

But back to my speech.  There was only one question afterward, which I hope was not an indication of the interest level.  The gentleman asked if we were constructing an ontology for feedback, and what about the repercussions of that.

Wikipedia defines ontology thus:

In computer science and information science, an ontology is a formal representation of the knowledge by a set of concepts within a domain and the relationships between those concepts. It is used to reason about the properties of that domain, and may be used to describe the domain.

This was a good question.  I don’t know if I answered well enough at the time so I want to expand here.

Right now we’re not as much concerned with ontologies as we are with enabling them.  Specifically, we want to promote the creation and improvement of feedback mechanisms first.  There are already ontologies in place, i.e., the designs behind metadata implementations, and the plan is to eventually leverage and perhaps expand those.  So maybe that manifests in a meta-ontology that pulls currently disparate parts into a whole.  But not yet.

And it’s possible I misled the questioner, because I did touch on the topic when I mentioned ratings systems.  There is a great need for consistency within any feedback ecosystem, so there’s the value of having an ontology in place.

But again, first the functional framework parts, then of course domains and relationships.

Tomorrow, Sebastian Kügler of Project Silk gives a presentation, and there’s one on the open gaming project Gluon as well from Dan Leinir Turthra Jensen.  We see synergies between MUEF and these efforts so I am eager to learn more!


Filed under: Econometrics and Analytics, Mentioning Maemo, Mentioning MeeGo, The Cat Corral Tagged: 2010, Akademy, feedback, Finland, KDE, MeeGo, Tampere
Categories: Econometrics and Analytics
Randall Arnold

An Open Letter to Nokia for 2010

2010-06-27 23:29 UTC  by  Randall Arnold
0
0

Dear Nokia,

Click to read 2434 more words
Categories: Addressing Retention
Randall Arnold

Maemo Missteps for 2010

2010-06-10 19:40 UTC  by  Randall Arnold
0
0

The release of MeeGo 1.0 was accompanied by some resolution to Maemo, not all of it with positive consequences.  The long-awaited PR1.2 update was officially released at around the same time, which was a welcome relief, but excitement over the improvements it brought were tempered by less-than-genius developments.

Click to read 2466 more words
Categories: Mentioning Maemo
Randall Arnold

The seeds of a feedback ecosystem

2010-05-26 06:43 UTC  by  Randall Arnold
0
0

A few posts ago I kicked off a series of talks here on the subject of a feedback ecosystem and how such a thing could enhance user engagement, particularly on mobile devices.

Click to read 1894 more words
Categories: Addressing Retention
Randall Arnold

America Offline: fall of a walled gardener

2010-05-16 00:11 UTC  by  Randall Arnold
0
0

This is a Tale of Two Internets, with a vivid beginning but no clear ending yet.

Click to read 2796 more words
Categories: Inviting Change
Randall Arnold

Will 2011 be make-or-break for Nokia?

2010-05-12 03:58 UTC  by  Randall Arnold
0
0

As many know I was recently privileged to attend the Linux Foundation Collaboration Summit 2010 in San Francisco, California.  After running out of juice trying to maintain community enthusiasm at maemo.org while simultaneously whipping it up for MeeGo, I was reinvigorated by the fresh energy permeating the conference.  Seeing old acquaintances again, finally greeting others in person for the time and making new friends always helps… as did the endless talks at various pubs and eateries about MeeGo’s future.

Click to read 1504 more words
Categories: Inviting Change
Randall Arnold

Input on a feedback ecosystem

2010-05-10 18:26 UTC  by  Randall Arnold
0
0

Click to read 1502 more words
Categories: Addressing Retention
Randall Arnold

Apple vs Adobe: a messy divorce

2010-04-11 04:12 UTC  by  Randall Arnold
0
0

Click to read 1340 more words
Categories: Mentioning Maemo
Randall Arnold

Why the first MeeGo device needs to launch BIG

2010-04-09 06:04 UTC  by  Randall Arnold
0
0

With each major variant in the Maemo Device line, Nokia enjoyed incrementally increasing success.  Its conservative “test the waters cautiously with a toe tip” approach cultivated a small but determined community eager to demonstrate that mobility and open source were a match made in electronic heaven.

Click to read 1138 more words
Categories: Mentioning Maemo
Randall Arnold

Geography Lesson for US Tech Bloggers

2010-04-06 21:29 UTC  by  Randall Arnold
0
0
Since the dawn of civilization, defining the center of the world has been a Very Important Activity.  Great wars were fought to stick a flag in this spot, where ever that turned out to be at any given time.  Ghengis Khan, Alexander the Great and former US president George Bush all had different opinions on the L10N.  Various indigenous peoples have paid for its ever-changing identification by loss of land and gain of child-labored textile mills.

So given the constant confusion around this nebulous spot it’s no wonder many technically-oriented blog sites get lost… especially those in the United States suffering from a gross misconception of world view.

Click to read 776 more words
Categories: Econometrics and Analytics
Randall Arnold

MeeGo and Pandora: a nice match?

2010-03-21 23:04 UTC  by  Randall Arnold
0
0

maemo.org members have been long interested in the open Linux device project Pandora, both seriously and in lovingly jesting fashion.

Now some are asking if MeeGo might look good sitting on a Pandora device, and I have to admit the thought is intriguing.  There shouldn’t be any insurmountable technical hurdles, and each open project could reinforce the legitimacy of the other.

But why not take that a step further?

Since MeeGo will be an open source solution freely available to any device or class of device, what would keep the Linux Foundation from broadening the scope of sponsorship?  Why not partner very closely with the Pandora project in every aspect?  The Foundation could even bring Pandora under its wing as the hardware sibling to MeeGo.

Of course that gets into a sticky area.  Hardware-driven sponsors like Nokia, which will be of course producing its own devices to run MeeGo, might balk at providing partial funding to the Linux Foundation if it got too deeply into open source hardware.  Then again, think of such a venture more as open source research and development rather than simple competition, and even Nokia may see a benefit.  Just as MeeGo drives down its software overhead, so could a sponsored Pandora do the same for hardware.

The value for Nokia and other corporate interests in such a scenario is that the attention on the mundane is diminished and differentiation becomes an even larger, more visible part of revenue contributions– and that is where companies need to focus their bottom line to improve margins anyway.

Naturally, such a scenario relies on all parties seeing a win-win, and Pandora’s leadership may not.  In addition, the Linux Foundation could not be faulted for focusing exclusively on the softer side of this equation and avoiding meddling with hardware.  Perhaps Pandora could instead evolve into the same sort of organization, ultimately gaining sponsorship from Nokia and others.  In that alternative, the Pandora organization and the Linux Foundation could form a partnership of mutual interest without any sort of actual merger.

Personally I find this potentially exciting and believe that sooner or later it’s inevitable… but as always, I’m highly interested in the opinions of readers.  Well?


Filed under: Inviting Change, Mentioning Maemo, Mentioning MeeGo, Out There, The Write Stuff Tagged: LinkedIn, Linux Foundation, MeeGo, Nokia, Pandora
Categories: Inviting Change