archive-org.com » ORG » M » MERPROJECT.ORG

Total: 820

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Revision history of "Nemo" - Mer Wiki
    09 27 August 2013 Mric Talk contribs 2 cur prev 20 37 27 August 2013 Mric Talk contribs 3 cur prev 20 34 27 August 2013 Mric Talk contribs 31 cur prev 14 03 1 August 2013 Faenil Talk contribs 0 Documentation cur prev 14 02 1 August 2013 Faenil Talk contribs 66 Documentation cur prev 23 02 30 July 2013 Leon Talk contribs 68 Status cur prev 17 57 23 July 2013 Qwazix Talk contribs 47 Documentation cur prev 10 14 19 July 2013 Netweaver Talk contribs 1 Documentation cur prev 10 14 19 July 2013 Netweaver Talk contribs m 69 Documentation cur prev 15 39 18 July 2013 Faenil Talk contribs 88 Documentation cur prev 05 21 11 July 2013 Sage Talk contribs 7 Documentation cur prev 09 51 3 June 2013 W00t Talk contribs 224 these are both out of date cur prev 10 30 17 May 2013 Sledge Talk contribs m 10 Communications cur prev 10 29 17 May 2013 Sledge Talk contribs m 2 Status cur prev 10 31 2 May 2013 Sledge Talk contribs m 2 Communications cur prev 10 31 2 May 2013 Sledge Talk contribs 8 Communications cur prev 09 58 2 May 2013 Sledge Talk contribs 60 Communications cur prev 09 56 2 May 2013 Sledge Talk contribs m 0 Communications cur prev 09 47 2 May 2013 Sledge Talk contribs 146 Communications cur prev 09 43 2 May 2013 Sledge Talk contribs m 0 Documentation cur prev 09 42 2 May 2013 Sledge Talk contribs 1 052 Source repositories MOVING out to Nemo Development cur prev 09 39 2 May 2013 Sledge Talk contribs m 2 Nemo Mobile cur prev 08 28 2 May 2013 Sage Talk contribs 576 Infrastructure cur prev 16 36 1 May 2013 Sledge Talk contribs

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Nemo&action=history (2016-02-01)
    Open archived version from archive

  • Log in - Mer Wiki
    to navigation search Log in This wiki uses accounts created on the Mer Bugzilla Please use your short username not your email address You must have cookies enabled to log in to Mer Wiki Username Password Your domain merproject org Remember my login on this browser for a maximum of 180 days Retrieved from https wiki merproject org wiki Special UserLogin Views Special page Personal tools 10 110 0 55

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Special:UserLogin&returnto=Nemo (2016-02-01)
    Open archived version from archive

  • Pages that link to "Nemo" - Mer Wiki
    File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Filters Hide transclusions Hide links Hide redirects The following pages link to Nemo View previous 50 next 50 20 50 100 250 500 Main Page links FAQ links Community Workspace links Nemo Installing links Adaptation N9 N950 Wayland links Nemo Installing old unmaintained qt4 x11 links View previous 50 next 50 20 50 100 250

    Original URL path: https://wiki.merproject.org/wiki/Special:WhatLinksHere/Nemo (2016-02-01)
    Open archived version from archive

  • Changes related to "Nemo" - Mer Wiki
    50 100 250 500 changes in last 1 3 7 14 30 days Hide minor edits Show bots Hide anonymous users Hide logged in users Hide my edits Show new changes starting from 16 43 1 February 2016 Namespace all Main Talk User User talk Mer Wiki Mer Wiki talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Invert selection Associated namespace Page

    Original URL path: https://wiki.merproject.org/wiki/Special:RecentChangesLinked/Nemo (2016-02-01)
    Open archived version from archive

  • Nemo - Mer Wiki
    style desktop Nemo N900 2012 08 31 Nemo N900 2012 07 02 Nemo N950 2013 06 24 See bugzilla for a list of known bugs Communications Ping us in this order IRC channels at freenode nemomobile Link Channel log webchat nemomobile porters device porting Link Channel log webchat mer core packages Link Channel log webchat Mailing list mer general lists merproject org Archive Nemo related topics should be prefixed with NEMO Twitter hashtag nemomobile List of tweets Twitter user nemomobile List of mentions Nemo Mobile discussion on maemo org Nemo Planet http planet devaamo fi nemo Meetings Nemo Contributor Meeting every Tuesday at 10 00 UTC 13 00 UTC 3 Finland at mer meeting Weekly error triage meeting every Monday at 7 00 UTC 10 00 UTC 3 Finland at mer meeting Installing Updating Visit Nemo Installing for a guide to install Nemo Mobile on your device This page also has information on how to set up a virtual machine with the Nemo x86 image enabling you to check out Nemo even if you don t own a device Supplementary install information and links are included in that page too Visit Nemo Updating for guide how to update existing installation of Nemo Mobile Infrastructure Releases Bugzilla OBS OBS Project structure Documentation Nemo Glacier Work in Progress Qt5 Nemo apps porting status DONE Contributing to Mer Guide for Development git trees code example git packaging etc Getting started in fixing bugs in existing software packages of Nemo Tips and tools for debugging Nemo Reporting bugs in Nemo USB Networking Visit Nemo Creating Releases for guide how Nemo Mobile releases are done Audio in Nemo Wayland Nemo VM Image current development status of the Wayland Nemo i486 image Migration tips N9xx Maemo Harmattan migration to Nemo tips Redesign Project Nemo redesign project

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Nemo&printable=yes (2016-02-01)
    Open archived version from archive

  • Quality/Test processes - Mer Wiki
    request notification from the Mer QA also sources of the changed packages Input Update changed packages to vendor OBS Output Repository where to find the packages Input List of changed packages and test stage Output Kickstart files list of needed packages for testing and test plans for the OTS Input Kickstart file and needed packages Output URL to image s Input Test plans and image locations Output The test results Returning regress improvement no change indicator to Mer QA Release testing Pre Release testing has two main test sets core and feature set Both sets are executed to every release Release testing can take more time than package testing and it should include non functional tests Core set The Core set contains set of tests that verify overall quality of the Mer Core release It has tests for all architecture domains and API tests Core set content is stable only minor changes are allowed between the releases Feature set Feature set includes tests for those packages that have changed from the previous release Basically feature set is set of package testing tests The feature set content changes to every release Manual testing QA Tools support manual testing When manual tests can be executed and how to report results What is the testing process in manual testing Reference QA processes MeeGo This is from the public side of the MeeGo No CI testing in place Only hourly nightly and release testing QA Reports was used to report test results QA Tools were OTS testrunner lite tdriver MCTS tests were used Maemo Please fix if you see mistakes here Active CI testing in place Test packaging was used the naming policy was strict Own dashboard for managing test packages Test package had in the Debian control file following parameters XB Maemo CI

    Original URL path: https://wiki.merproject.org/wiki/Quality/Test_processes (2016-02-01)
    Open archived version from archive

  • Contribution - Mer Wiki
    date or inaccurate report a bug against the Wiki component in bugzilla once fixed hope on mer freenode to get some review from the community before closing the bug There are also wiki pages used for brainstorming and collaborating for example Website Ideas where you can add your take suggestions and so forth Once you ve done so hop on mer freenode to let the rest of community know if it needs discussion or mail the mailing list for that High level testing As a user you are encouraged to use and end user product handset vertical and report back issues both to NemoMobile and Mer project as per the components affected If in doubt feel always welcome to hop on nemomobile freenode and ask around to know whom to contact about an issue You are encouraged as well to test Mer releases and report bugs accordingly You can find some insight into testing here If you like code packaging and are interested in contributing to the project code development take a look here to whet your appetite https bugs merproject org buglist cgi keywords easyFix resolution Issues tagged easyFix are those that should be relatively easy to fix and will get you up and running running with the contribution model and workflow This usually means proposing a patch to a package having it reviewed in the continues integration system and eventually have it accepted and built onto the package repository To get more details about code contributions read on as the next sections elaborate just on that If you can and are interested in both you re more than welcome to contribute to both as many times they harmonically coincide Contributing to packages NOTE If this sections feels a bit brief there s also a page which walks through the change submission process in greater detail Our repositories You can view our repositories at Mer gitlab Signed off by The Mer project uses the signed off by language and process used by the Linux kernel to give us a clear chain of trust for every patch received Linux Kernel Certificate of Origin v 1 1 By making a contribution to this project I certify that The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file or The contribution is based upon previous work that to the best of my knowledge is covered under an appropriate open source license and I have the right under that license to submit that work with modifications whether created in whole or in part by me under the same open source license unless I am permitted to submit under a different license as indicated in the file or The contribution was provided directly to me by some other person who certified a b or c and I have not modified it I understand and agree that this project and the contribution are public and that a

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Contribution&oldid=5483 (2016-02-01)
    Open archived version from archive

  • View source for Contribution - Mer Wiki
    get some review from the community before closing the bug There are also wiki pages used for brainstorming and collaborating for example https wiki merproject org wiki Website Ideas Website Ideas where you can add your take suggestions and so forth Once you ve done so hop on mer freenode to let the rest of community know if it needs discussion or mail the mailing list for that High level testing As a user you are encouraged to use and https wiki merproject org wiki Main Page End Users end user product handset vertical and report back issues both to NemoMobile and Mer project as per the components affected If in doubt feel always welcome to hop on nemomobile freenode and ask around to know whom to contact about an issue You are encouraged as well to test Mer releases and report bugs accordingly You can find some insight into testing https wiki merproject org wiki Quality Test processes here If you like code packaging and are interested in contributing to the project code development take a look here to whet your appetite https bugs merproject org buglist cgi keywords easyFix resolution Issues tagged easyFix are those that should be relatively easy to fix and will get you up and running running with the contribution model and workflow This usually means proposing a patch to a package having it reviewed in the http en wikipedia org wiki Continuous integration continues integration system and eventually have it accepted and built onto the package repository To get more details about code contributions read on as the next sections elaborate just on that If you can and are interested in both you re more than welcome to contribute to both as many times they harmonically coincide Contributing to packages NOTE If this sections feels a bit brief there s also a page which walks through Contribution in detail the change submission process in greater detail Our repositories You can view our repositories at http git merproject org Mer gitlab Signed off by The Mer project uses the signed off by language and process used by the Linux kernel to give us a clear chain of trust for every patch received pre Linux Kernel Certificate of Origin v 1 1 By making a contribution to this project I certify that The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file or The contribution is based upon previous work that to the best of my knowledge is covered under an appropriate open source license and I have the right under that license to submit that work with modifications whether created in whole or in part by me under the same open source license unless I am permitted to submit under a different license as indicated in the file or The contribution was provided directly to me by some other person who certified a b or c and

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Contribution&action=edit (2016-02-01)
    Open archived version from archive