The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)

Community Workspace

From Mer Wiki
(Difference between revisions)
Jump to: navigation, search
m (→‎Device Adaptations)
m (→‎Community Resources)
Line 9: Line 9:
 
== Community Resources ==
 
== Community Resources ==
  
−
* MeeGo Porting Guide - http://wiki.meego.com/MeeGo_Porting_Guide <span style="color:red;">[DEAD LINK]</span> possibly refer instead to [[Nemo/Porting]] or [[Adaptations]]
+
* MeeGo Porting Guide - http://wiki.meego.com/MeeGo_Porting_Guide <span style="color:red;">[DEAD LINK]</span> possibly refer instead to [[Adaptation_Guide]] or [[Nemo/Porting]]
 
* MeeGo Image Creator Guide - http://wiki.meego.com/Image_Creation <span style="color:red;">[DEAD LINK]</span> possibly refer instead to  [[Image_Creation]]
 
* MeeGo Image Creator Guide - http://wiki.meego.com/Image_Creation <span style="color:red;">[DEAD LINK]</span> possibly refer instead to  [[Image_Creation]]
 
* MeeGo OBS (opensuse build server) - http://wiki.meego.com/OBS <span style="color:red;">[DEAD LINK]</span> possibly refer instead to [[Building_against_Mer_in_COBS]]
 
* MeeGo OBS (opensuse build server) - http://wiki.meego.com/OBS <span style="color:red;">[DEAD LINK]</span> possibly refer instead to [[Building_against_Mer_in_COBS]]

Revision as of 20:00, 8 January 2014

Two quotes from the 'MeeGo Reconstructed' email (http://lists.meego.com/pipermail/meego-dev/2011-October/484215.html) [DEAD LINK] describe what can find here.

  • 'Initially the project will be developing a Core for basing products on and will split UX and hardware adaptations out into separate projects within the community surrounding the Core'
  • 'We will continue to welcome contribution and participation from the hacker community - in fact we aim to make it so easy to port to a new vendor device that a single hacker could do it for their device'

Some of the information is taken from the MeeGo project with which we share a number of tools and processes.

Community Resources

Device Adaptations

See also Adaptations

Adaptations available under obs (https://build.merproject.org/project/list_public) are typically (but not consistently) named hw:vendor:processor:sbc, e.g., hw:ti:omap4:pandaboard. (see also OBS_architecture_naming) The items below are typically listed by a common device or sbc (single board computer) name, which is not necessarily unique; e.g., Google Nexus 7 2012 is nv:tegra3:nexus7, Google Nexus 7 2013 might rather be qualcomm:s4pro:nexus7, and would likely share very little in common with nv:tegra3:nexus7.

To estimate the level of activity in an adaptation project on obs, you might look at the kernel adaptation package, and check the top line of the "changes" file, e.g., kernel-adaptation-pandaboard.changes to see the kernel version and/or date of recent patches. Many of the adaptations listed below are outdated, one-time, "proof-of-concept" activities, rather than useful, active hardware ports. There might also be adaptations hosted completely externally to the obs that are not documented here.

User Experience UX

Retrieved from "https://wiki.merproject.org/wiki/index.php?title=Community_Workspace&oldid=4295"
Personal tools