Hi Michelle,

Michelle O'Brien wrote:
> On 23/02/11 04:19, Dave Neary wrote:
>> Note that the tablet UX still doesn't have a code-centric project home
>> page yet. I think it would be hugely useful for someone to start a Wiki
>> page for the tablet UX, linking to the various Git modules, documenting
>> how to build&  run the bleeding edge, and collecting the names of the
>> development team for each module. This would enable people interested to
>> start following along with development&  start developing new features
>> straight away, instead of waiting for the next release.
>>
>> Nice community task for someone?
> 
> I'd offer - but have no idea where to start.

You could create the page at http://wiki.meego.com/Tablet_UX

A page for a code project should contain, at a minimum:

* A description of the project
* A direct link to the mailing list for its developers (looks like
there's nothing more specific than meego-dev or meego-touch-dev at this
point, although there is a Tablet forum for users - perhaps tablet devs
could tell us where they hang out)
* A link to a list of bugs against the module(s) (it doesn't look like
the tablet UX has a Bugzilla product yet, though, it will be in the
"MeeGo Platform" classification when it's created, I imagine)
* A link to the source code of the module(s), and instructions on how to
get & build it (I don't see anything promising on
http://meego.gitorious.org/ - can someone in the know tell me where the
tablet is being developed, please?)
* A link to a .tar.gz of the latest release
* Ideally a roadmap showing the important short-term features & bugs,
and also the medium & long term direction, and the project's goals & vision

Everything there does not need specific technical skills or knowledge of
the project, apart from the roadmap.

So I guess the first step is to know which git modules are being used
for the development of the tablet UX. I made such a list for the netbook
UX a few weeks ago - perhaps someone involved in the tablet development
could do the same for the tablet UX, please? Once we have that, the rest
should fall into place.

Cheers,
Dave.

-- 
Email: [email protected]
Jabber: [email protected]

_______________________________________________
MeeGo-community mailing list
[email protected]
http://lists.meego.com/listinfo/meego-community
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to