GitLab AMA Topic Follow Up: Namespace & Issue Tracking
# GitLab AMA Session Topic - Namespace & Issue Tracking Hi everyone, Thanks again for your involvement in the GitLab AMA session on IRC in September. This email discussion thread is on Namespace & Issue Tracking. I have pulled the relevant questions and answers from the original hackmd doc into one email and if you would like to discuss this topic specifically, here might be a good place to do so so your conversations don't go down a 'rabbit hole' :) Here are some links to resources as well: * Questions and Answers hackmd link https://hackmd.io/RW8HahOeR7OJPON1dwuo3w * Chat log from session https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/ama_session_with_gitlab.2020-09-10-13.31.log.html * AMA Blog post https://communityblog.fedoraproject.org/gitlab-ama-follow-up/#more-9346 * Here is this email in hackmd if you wish to view it there: https://hackmd.io/oZrDwbSeSWO-l_X65A1ndg?view ## Namespace & Issue Tracking - Question: Currently dist-git in Fedora has several namespaces: rpms, modules, containers, tests... All namespaces but the ``tests`` namespace have their issue tracker in bugzilla. Would this work in gitlab? Can we selectively enable/disable issue tracking per namespace for the entire instance? (ie: w/o giving the possibility to ``owner`` or ``maintainer`` to toggle that setting.) - Answer: It may need to be checked again, but it appears you can turn on/off the issue tracker at the project level. - Question: Currently dist-git in Fedora has several namespaces: rpms, modules, containers, tests... All namespaces but the ``tests`` namespace have their issue tracker in bugzilla. Would this work in gitlab? Can we selectively enable/disable issue tracking per namespace for the entire instance? (ie: w/o giving the possibility to ``owner`` or ``maintainer`` to toggle that setting.) - Answer: You can turn the GitLab issue tracker on and off by project. See https://docs.gitlab.com/ee/user/project/settings/#sharing-and-permissions Namespaces map to “group” in GitLab. Here’s more info about them: https://docs.gitlab.com/ee/api/namespaces.html - Question: Fedora, as far as I understand, still plan on using bugzilla as issue tracker. Currently default assignee and the CC are gathered using the ``main admin`` (ie: the ``owner`` for GitLab iiuc), the other maintainers (who did not ``unwatch issues`` in the project - mechanism for them to opt-out of being in the CC list) and the people having enabled ``Issue watching`` for the project (mechanism for them to opt-in into being in the CC list). Would this work in a GitLab world? - Answer: There are a number of options related to that. For one, users can control their notifications globally and by name space in a fine grained way (see GitLab Notification Emails). - Question: Fedora is part of GitLab’s Open Source program and we have a migration tracker issue that we are using to keep track of feature requests, bugs, etc that are important to Fedora. The Fedora migration team has been working with us at GitLab to maintain that and community members can add relevant issues there so we can track them. It’s also helpful for our product managers to hear about why particular issues are important for the Fedora use case, and to have upvotes, so doing that will help! Where can you submit requests/bugs/report issues? - Answer: Fedora Migration Tracker: https://gitlab.com/gitlab-org/gitlab/-/issues/217350 Feature template: https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Feature%20proposal Bug template: https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Bug Please do review the original questions doc in case I have missed any that relate to namespace and issue tracking and thank you again for your engagement with these emails! The next email topic will be on 'Branches'. Have a good week! Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Orphaned packages looking for new maintainers (hundreds of freshly orphaned F33FTBFS)
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Request package ownership via the *Take* button in he left column on https://src.fedoraproject.org/rpms/ Full report available at: https://churchyard.fedorapeople.org/orphans-2020-11-23.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager.fedorainfracloud.org/ For all orphaned packages, see https://packager.fedorainfracloud.org/orphan Package (co)maintainers Status Change Pencil2D lbazan, orphan 0 weeks ago RxCpp orphan 0 weeks ago ansible-collection-community- orphan 3 weeks ago general apivizlef, orphan 0 weeks ago apper kde-sig, orphan, rhughes 0 weeks ago bfast orphan 0 weeks ago biblesync cicku, orphan0 weeks ago bifcl orphan 0 weeks ago bmon orphan 0 weeks ago celt071 orphan 4 weeks ago colorhug-client orphan 1 weeks ago compat-guile18jskarvad, mlichvar, orphan, 3 weeks ago tkorbar cook orphan 0 weeks ago coolreaderorphan 0 weeks ago couchdb orphan 0 weeks ago cpulimit orphan 0 weeks ago cros-guest-tools orphan 1 weeks ago dc3dd maxamillion, orphan 0 weeks ago dep go-sig, orphan 0 weeks ago discord-irc orphan 3 weeks ago dnscaporphan 4 weeks ago dnsjava orphan 0 weeks ago dumb-init orphan 0 weeks ago dynaplugz orphan 0 weeks ago edb orphan 0 weeks ago elasticdump orphan 3 weeks ago electric blackfile, orphan0 weeks ago electrum orphan 4 weeks ago erlang-corba orphan 0 weeks ago erlang-lager bowlofeggs, orphan 0 weeks ago eyesight cicku, orphan, plfiorini 0 weeks ago fedora-developer-portal orphan 2 weeks ago fifechan orphan 0 weeks ago fillets-ngorphan, thias0 weeks ago flaconignatenkobrain, orphan 0 weeks ago fmpp orphan 0 weeks ago fossilorphan 0 weeks ago freetiger orphan 0 weeks ago gaupolmmraka, orphan 0 weeks ago ghc-pipes-safeorphan 3 weeks ago glyr orphan 0 weeks ago gmpc orphan 0 weeks ago gnome-code-assistance elad, orphan 0 weeks ago gnome-documents anujmore, cosimoc, gnome-sig,0 weeks ago orphan golang-contrib-opencensus-go-sig, orphan 0 weeks ago exporter-ocagent golang-github-casbin go-sig, orphan 0 weeks ago golang-github-cenkalti-backoffgo-sig, jchaloup, orphan 0 weeks ago
