docs.ubports.com icon indicating copy to clipboard operation
docs.ubports.com copied to clipboard

porting: finalize: add instructions for official UBports support

Open amartinz opened this issue 2 years ago • 6 comments

Requirements for a port to get officially supported by UBports.

amartinz avatar May 03 '22 09:05 amartinz

I am happy with the initial state, however there are some TODOs left and of course a proper review is needed as well :)

amartinz avatar May 03 '22 11:05 amartinz

Add "MUST be able to install OTAs" to requirements

amartinz avatar Jun 04 '22 09:06 amartinz

  • Changed emergency calling support from MUST to SHOULD, as not everyone has access to verifying such functionality.

  • Added Installer and Recovery sections.

Installer
---------
* Devices MUST support installation via `UBports Installer`_.

Recovery
--------

* Devices MUST support resetting to factory defaults.
* Devices MUST support updating via OTA.

amartinz avatar Jun 07 '22 13:06 amartinz

  • Added Documentation section to requirements:
Documentation
-------------

* The device MUST be listed at the `Ubuntu Touch device page`_; the device page needs to be kept up-to-date.
  • Added workflow for Submitting your port section, utilizing our new devrel team.
    • Including a brand new port submission template
  • Addressed all leftover TODOs

amartinz avatar Sep 08 '22 16:09 amartinz

Should be ready for review now.

I'd like this to get all approvals from the reviewers listed (at least, more are always welcome) before merging this. :smile:

amartinz avatar Sep 08 '22 16:09 amartinz

sorry, took me a while to get around to this. I'm very glad that we are moving forward in this area. I only have small mostly formatting/formulation remarks.

However, note that I only review clarity of language and presentation. I don't offer an opinion on the technical side. I think this should come from core developers, so I'd very much prefer another approval.

doniks avatar Sep 19 '22 14:09 doniks

Was this closed in mistake or?

JamiKettunen avatar Jan 05 '23 22:01 JamiKettunen

Was this closed in mistake or?

I do not have the time to further pursue this MR and do not want to be the blocker in case someone wants to pick this up :)

amartinz avatar Jan 06 '23 10:01 amartinz

Was this closed in mistake or?

I do not have the time to further pursue this MR and do not want to be the blocker in case someone wants to pick this up :)

I could pick up the leg work of writing, but I would need a core dev that reviews the content . Otherwise I just make up a process that only exists on paper. @amartinz any idea whom I might contact from the core team?

doniks avatar Jan 09 '23 08:01 doniks

I could pick up the leg work of writing, but I would need a core dev that reviews the content . Otherwise I just make up a process that only exists on paper. @amartinz any idea whom I might contact from the core team?

The reviewers added to this MR, i guess, as i think in this case it is more important to get feedback and input from the porting team rather than the platform team.

amartinz avatar Jan 09 '23 10:01 amartinz

Understood. Reopening this for now. Let's see how we get this over the finish line. Thanks for making the start @amartinz . Well find a way to wrap it up without taking more of your time

doniks avatar Jan 10 '23 11:01 doniks

trying again over here: https://github.com/ubports/docs.ubports.com/pull/540

doniks avatar Jan 10 '23 11:01 doniks

@doniks the problem is: Even if only a handful of people need to agree on this I do not want to push this entirely on my own and with Alex. I would have merged this already, but there is little interest in the porting corner to get this moving I guess. It is also unclear who are the stakeholders, and how we empower them to execute all of this.

If we get more restrictive then we should really be serious. It needs to be a logical step forward, but sometimes I have the feeling it is not what people want when saying "mobile freedom". Or idk.

Flohack74 avatar Jan 16 '23 19:01 Flohack74