Just to make sure this reaches all interested parties, we have some important discussions about Modularity going on in Pagure tickets:
Distribution Upgrades (reaching decision) — Handling modules, streams, and defaults during major distribution upgrades. * Tracker: https://tree.taiga.io/project/modularity-wg/epic/27 * Discussion: https://pagure.io/modularity/issue/108 Module Lifecycles in General (proposal) — The general concept of defining and managing module lifecycles. * Tracker: https://tree.taiga.io/project/modularity-wg/epic/3 * Discussion: https://pagure.io/modularity/issue/112 Defaults & Fedora Changes (proposal) — Communicating major changes in the distribution introduced by new module stream defaults. * Tracker: https://tree.taiga.io/project/modularity-wg/epic/35 * Discussion: https://pagure.io/modularity/issue/114 Branch Ownership (proposal) — Making sure that package and module owners are clearly defined and relevant processes are in place. * Tracker: https://tree.taiga.io/project/modularity-wg/epic/4 * Discussion: https://pagure.io/modularity/issue/115 Cheers! Adam -- Adam Šamalík --------------------------- Software Engineer Red Hat
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
