platform-owner: bring text up to date

- remove refrences to old tools (Jira)
- remove references to D61

Signed-off-by: Gerwin Klein <[email protected]>

projects/sel4/platf-owner.md

@@ -9,6 +9,7 @@ Below are the guidelines defined by the [Technical Steering Committee
 (TSC)](https://sel4.systems/Foundation/TSC/) to become a *platform owner*.
 
 This assumes that:
+
 * the platform that you are after is not listed on the [Supported Platforms
   page](/Hardware/);
 * from your available [options](/Hardware/index.html#not-in-the-lists-below),
@@ -18,6 +19,7 @@ This assumes that:
   [Platform Porting guide](/projects/sel4/porting).
 
 > A platform owner:
+>
 > * is the maintainer of platform specific kernel and library code for that
 >   platform
 > * is the “driver” for that platform (setting the direction where things are
@@ -30,18 +32,15 @@ This assumes that:
 >     documentation for the platform,
 > * help to keep the verification passing for verified configurations (only
 >   relevant for a few platforms, but might increase in the future)
-> * handle bug reports for that platform on github and devel mailing list (has
->   access to github issues and/or the new sel4 Jira at sel4.atlassian.net for
->   this if desired)
+> * handle bug reports for that platform on GitHub and devel mailing list
 > * handle support requests/questions for that platform (if low-key, ideally
 >   publicly on the mailing list, but also paid support etc for bigger things)
 > * review and help merge PRs for that platform (relevant PRs should have one
 >   approving review from the platform owner if possible)
 > * providing binaries for bootloader and load instructions would be desirable
-> * if other development on the master branch has platform impact (from
->   contributions or D61), it should preferably include relevant platform code
->   updates already, but might need consultation with the platform owner to get
->   done, i.e. the basic expectation would be “you break it, you fix it”, but
->   people sometimes might need help.
+> * if other development on the master branch has platform impact, it should
+>   preferably include relevant platform code updates already, but might need
+>   consultation with the platform owner to get done, i.e. the basic expectation
+>   would be “you break it, you fix it”, but people sometimes might need help.
 > * the foundation advertises platform owners on the website, and platform owners
 >   would link back to the foundation.