-------------------------------------------------------------------
[I've changed this to go to maemo-developers, where I think it is more
appropriate to be discussed, follow-ups there please]
-------------------------------------------------------------------


On Wed, Apr 21, 2010 at 14:09,  <jarmo.ti...@nokia.com> wrote:
>From: Andrew Flegg <and...@bleb.org>
>>
>> One thing I'd like to see is a *definitive* Maemo reference library.
>> Currently, we have docs spread over Forum Nokia, Info Center, the
>> maemo.org wiki - and then there's the docs that are *duplicated* (with
>> slightly different versions) between the various places.
>
> This new Maemo Info Center library is planned to be THE place to look for
> official Maemo documentation (and Maemo.org wiki will continue to be
> THE place to look for unofficial docs :).

Yeah, and this is the problem. See below...

> I do nto think we have much documentation in Forum Nokia exception
> being some training slideware and Hildon 2.2. UI guides. I have now
> converted all those 4 Hildon 2.2. UI guides into laTex and I will
> publish them shortly in Maemo Info Centeras official documents
> (they will also be available as PDF/HTML downloadables as all
> other Latex docs).

Cool, thanks.

> I was planning to update and release pyMameo documentation in Info Center
> but it was decided last summer (2009) by our product management that we
> do not release Python (pyMaemo) documentation as official documentation.
> So I cannot add Python documents (and I have not even verified do we
> have updated pyMaemo docs for Fremantle available).

This continued separation between "official" and "unofficial" (and
"open"/"closed") doesn't help developers AT ALL.

Why does a developer need to know, or care, whether the framework they
are using is "officially" sanctioned by Nokia, or whether - like
PyMaemo - it's come from a third-party (though one whose bills are
paid for by Nokia)?!

I want to have a single place that I can refer to broad, deep, Maemo
developer documentation. It seems that the Info Center is NOT it,
solely due to the decisions of your product management. So, for me,
it'd be better if someone in the community mirrored its content and
combined it with the documentation for all the other parts of the real
world Maemo development ecosystem.

If you're able, I would strongly encourage you to try and persuade
your product management into changing their mind on this.
Alternatively, if you'd like me - as a representative of the Maemo
community - to talk to them directly, let me know who to chat to.

Thanks in advance,

Andrew

-- 
Andrew Flegg -- mailto:and...@bleb.org  |  http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Reply via email to