Jump to content

Core Contributors Meetings

From postmarketOS Wiki
Revision as of 09:14, 24 November 2020 by Ollieparanoid (talk | contribs) (add notes from 2020-11-23)

Monthly meeting of the Core Team to move postmarketOS forward. Important discussion results are written down in this wiki page.

2020-11-23

  • We talked about when/if features should be backported to stable. Backporting every feature 5 days after it was merged to edge is too much effort. The solution we came up with is creating a monthly dot release with interesting features backported. All backports in one merge request, test them together, then merge. We'll do the merge request for these dot releases at the beginning of each team meeting, and if somebody wants to suggest something to backport just let us know in the chat or issues.
  • pinetab will be moved to device/community
  • pinephone will be moved to device/main

2020-10-26

  • We're going to use the CODEOWNERS feature of Gitlab on demand, e.g. for shared kernels or specific packages a user is interested in
  • We're changing how we approve MR's, see the updated rules page
  • New features to edge that should also appear on the master branch will be backported after a week or so, at least 5 days

2020-09-24

  • To move a device to the community directory will require it to run a close to mainline kernel just as with the main directory
  • The PinePhone will use a forked version of Megi's branch. We won't use p-boot though
  • We're going to have minimal kernel configs in pmaports.git and use shared fragments pmb#1824
  • sxmo will be backported to the stable branch
  • Megapixels will be the default photo taking app in Phosh

2020-08-25

  • Write down results of this meeting and future meetings in this public wiki page.
  • Decide on principles of postmarketOS: about postmarketOS#Principles
  • Decide first iteration of guidelines for packaging patches
    • Apply GTK+ patches to master too (pmaports#690). Most importantly, because stable should be a snapshot of master.
  • Do not merge back libhybris/Halium related patches as they cost us significant maintenance effort without benefit. If somebody wants to have it, they should create their own aports repository (and binary packages if desired), like Sxmo is doing it currently. We would also accept some integration into pmbootstrap, like an additional question in "pmbootstrap init" that makes it easy to use this 3rd party repository.
  • Mastodon: PureTryOut got access to the account, in order to make it more active (see Infrastructure Maintainers)
  • We discussed if we want to keep the "two approvals before merge" rule (see Team guidelines). We do want to keep it, the benefits of better review are worth the increased time until a MR gets merged.
  • Get all devices from community into stable -> new issue: pmaports#724