Hey everyone,
I am trying to get a handle on the number of projects that we are actively working on for any given day of the week. Could I ask everybody to reply here with some information. At a minimum if you could share with me:
- Project you are actively working regularly on
- Link to the Landing Page / Tracker / Source / Docs / anything relevant really that might help me get a handle on the project
- Got a roadmap link? Or backlog link?
- Any upcoming release plans that you are aware of / have committed to?
- Anything else you think is worth sharing by all means include it
I want to try and get a picture of the landscape and to take all of that into account when we start looking at the upcoming priorities for the Red Hat team. I want to try paint a bigger picture of our current responsibilities and commitments to help us inform what our future commitments look like.
I intend to transpose this *somewhere* in due course, the Wiki might be a good starting point but for now I'm happy to take the details within this thread and I can follow up with another conversation as the information flows in.
Thanks, Leigh
On 29/01/19 14:14, Leigh Griffin wrote:
Hey everyone,
I am trying to get a handle on the number of projects that we are actively working on for any given day of the week. Could I ask everybody to reply here with some information. At a minimum if you could share with me:
- Project you are actively working regularly on
Anitya the-new-hotness
- Link to the Landing Page / Tracker / Source / Docs / anything
relevant really that might help me get a handle on the project
Anitya -------- Homepage: https://github.com/release-monitoring/anitya Where the project lives: release-monitoring.org Tracker: https://github.com/release-monitoring/anitya/issues Docs: https://anitya.readthedocs.io/en/latest/
the-new-hotness ---------------------- Homepage: https://github.com/fedora-infra/the-new-hotness Tracker: https://github.com/fedora-infra/the-new-hotness/issues Docs: https://the-new-hotness.readthedocs.io/en/stable/
- Got a roadmap link? Or backlog link?
I'm tracking all of my tasks also on my personal kanban (https://tree.taiga.io/project/zlopez-anitya/kanban), which I try to keep up to date.
- Any upcoming release plans that you are aware of / have committed to?
The future plans for the applications can be found here https://pagure.io/cpe-planning/issues?status=Open&assignee=zlopez&cl...
- Anything else you think is worth sharing by all means include it
There is plenty of code that needs refactoring, mainly in Anitya
I want to try and get a picture of the landscape and to take all of that into account when we start looking at the upcoming priorities for the Red Hat team. I want to try paint a bigger picture of our current responsibilities and commitments to help us inform what our future commitments look like.
I intend to transpose this *somewhere* in due course, the Wiki might be a good starting point but for now I'm happy to take the details within this thread and I can follow up with another conversation as the information flows in.
Thanks, Leigh
--
LEIGH GRIFFIN
ENGINEERING MANAGER,
Community Platform Engineering
Red Hat Ireland https://www.redhat.com/
Communications House, Cork Road
Waterford City, Ireland X91NY33
lgriffin@redhat.com mailto:lgriffin@redhat.com M: +353877545162 tel:+353877545162 IM: lgriffin
https://red.ht/sig TRIED. TESTED. TRUSTED. https://redhat.com/trusted
@redhatway https://twitter.com/redhatway @redhatinc https://instagram.com/redhatinc @redhatsnaps https://snapchat.com/add/redhatsnaps
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@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/infrastructure@lists.fedorapro...
On Tue, Jan 29, 2019 at 01:14:17PM +0000, Leigh Griffin wrote:
Hey everyone, I am trying to get a handle on the number of projects that we are actively working on for any given day of the week. Could I ask everybody to reply here with some information. At a minimum if you could share with me:
- Project you are actively working regularly on
- Link to the Landing Page / Tracker / Source / Docs / anything relevant
really that might help me get a handle on the project
- Got a roadmap link? Or backlog link?
- Any upcoming release plans that you are aware of / have committed to?
- Anything else you think is worth sharing by all means include it
Here we go:
* pagure - Landing Page: https://pagure.io/ - https://src.fedoraproject.org - Tracker: https://pagure.io/pagure/issues - Source: https://pagure.io/pagure/ - Docs: https://docs.pagure.org/pagure - Roadmap: https://pagure.io/pagure/roadmap - Upcoming release: https://pagure.io/pagure/roadmap/5.3/ (Fedb 7th) - Anything else: Ran by other companies
* fedocal - Landing Page: https://apps.fedoraproject.org/calendar/ - Tracker: https://pagure.io/fedocal/issues - Source: https://pagure.io/fedocal/ - Docs: https://fedocal.readthedocs.io/en/latest/ - Roadmap: - - Upcoming release: one needed to port to openshift, no ETA - Anything else: Ported to openshift in staging (login broken thus the need for a new release) Ported to python3 in git
* nuancier - Landing Page: https://apps.fedoraproject.org/nuancier/ - Tracker: https://pagure.io/nuancier/issues - Source: https://pagure.io/nuancier/ - Docs: - - Roadmap: - - Upcoming release: one needed to port to openshift, no ETA - Anything else: Ported to openshift in staging (login broken thus the need for a new release)
* elections - Landing Page: https://admin.fedoraproject.org/voting/ - Tracker: https://pagure.io/elections/issues - Source: https://pagure.io/elections/tree - Docs: - - Roadmap: - - Upcoming release: one needed to port to openshift, no ETA - Anything else: Ported to openshift in staging (login broken thus the need for a new release)
* mdapi - Landing Page: https://apps.fedoraproject.org/mdapi/ - Tracker: https://pagure.io/mdapi/issues - Source: https://pagure.io/mdapi/ - Docs: - - Roadmap: - - Upcoming release: none planned - Anything else: Ported to openshift in staging (cron job still needs to be fixed)
* fedmsg_meta_fedora_infrastructure - Landing Page: - - Tracker: https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/issues - Source: https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/ - Docs: - - Roadmap: - - Upcoming release: as needed - Anything else: Will be deprecated by the move to fedora-messaging
* fedora-gather-easyfix - Landing Page: http://fedoraproject.org/easyfix - Tracker: https://pagure.io/fedora-gather-easyfix/issues - Source: https://pagure.io/fedora-gather-easyfix - Docs: - - Roadmap: - - Upcoming release: none planned - Anything else: -
* is-it-in-rhel - Landing Page: - - Tracker: https://pagure.io/is-it-in-rhel/issues - Source: https://pagure.io/is-it-in-rhel - Docs: - - Roadmap: - - Upcoming release: none planned - Anything else: -
* simple-koji-ci - Landing Page: - - Tracker: https://pagure.io/simple-koji-ci/issues - Source: https://pagure.io/simple-koji-ci - Docs: - - Roadmap: - - Upcoming release: none planned - Anything else: -
* pkgdb-cli - Landing Page: - - Tracker: https://pagure.io/pkgdb-cli/issues - Source: https://pagure.io/pkgdb-cli - Docs: - - Roadmap: - - Upcoming release: none planned - Anything else: -
* rdbsync - Landing Page: - - Tracker: https://github.com/fedora-infra/rdbsync/issues - Source: https://github.com/fedora-infra/rdbsync - Docs: - - Roadmap: - - Upcoming release: none planned - Anything else: -
* fedora-active-user - Landing Page: - - Tracker: https://github.com/pypingou/fedora-active-user/issues - Source: https://github.com/pypingou/fedora-active-user - Docs: - - Roadmap: - - Upcoming release: none planned - Anything else: -
Side-projects: * pag-off - Source: https://pagure.io/pag-off * r2spec - Source: https://pagure.io/r2spec * gitsync - Source: https://github.com/pypingou/gitsync
Hoping this helps,
Pierre
Wow, that's an impressive list !
Mine is much shorter:
- Pagure (see above)
- Fedora CI (gating) https://fedoraproject.org/wiki/CI
- package maintenance, i.e. vim, libcap, ed, .... Add tests and enable gating
Similar to smooge, I'm on the ops side primarily, but I do bounce around and try to be flexible when needed.
Notable things over the last few months: - Lots of newcloud work with Kevin, Jim, and Patrick - Maintained and deployed the websites -- at least enough to get them updated -- for the last few releases. - Lots of on-call (especially the last few weeks while people were travelling) - Lots of proxy rebuilding (tag-teamed these with Kevin to get them updated to a non-EOL Fedora) - Got our S3/cloudfront mirror sync working (though it has some issues and is WIP) - Focused and presented on some ideas for retaining contributors and making infrastructure onboarding more interactive and appealing to people. WIP. - Calling in drives/problems to vendors and working with dcops to get them taken care of. - Maintain our modernpaste pastebin (which I'll have more to say about at the next infra meeting) - Maintain the (external) da.gd URL shortener, which Fedora uses in a fair number of places nowadays - Package maintenance, though I've been trying to do less of this.
More recent one-off type things, to give an idea of my quotidian work: - Fixed our robots.txt in staging to make the wiki not be crawlable - While doing that, discovered that for "reasons" our prod robots.txt had a lotus-organizer mimetype. Fixed. - Our GeoDNS stopped working due to GeoIP format change. Wrote a script to parse and process the new format, and made it a bit better than the old setup by adding ipv6.
Upcoming-ish plans: - Experiment and help with eventual migration to RHEL8 by looking at RHEL8-beta in various places and seeing how much pain getting our ansible setup to work on it will be. - Work with smooge(?) on getting some proxies in AWS/EC2. - Websites work for F30/F31 releases - Getting more apps in OpenShift
Random/outside of Fedora: - I have a deep passion for statically typed functional programming/type theory, and most of my non-Fedora FOSS contributions are in that space. - Relatedly, I'm a volunteer on the haskell.org infrastructure team, though less active nowadays. - I've taken to playing with various backend networking protocols (bgp/igp, ospf, etc.) to learn about them with some friends using gre tunnels. - I play a few instruments with varying degrees of success. - I swing dance, DJ swing dances, and run sound systems for live-band swing dances - I'm finishing my undergraduate degree (CS/Math dual major, Linguistics minor); should be graduating in May. - I have a dog, she keeps me busy.
Rick
On Thu, Jan 31, 2019 at 9:46 AM Karsten Hopp karsten@fedoraproject.org wrote:
Wow, that's an impressive list !
Mine is much shorter:
Pagure (see above)
Fedora CI (gating) https://fedoraproject.org/wiki/CI
package maintenance, i.e. vim, libcap, ed, .... Add tests and enable gating
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@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/infrastructure@lists.fedorapro...
On Thu, Jan 31, 2019 at 10:45 AM Karsten Hopp karsten@fedoraproject.org wrote:
Wow, that's an impressive list !
Mine is much shorter:
- Pagure (see above)
Well, I work on Pagure too. I'm the maintainer for Pagure in Fedora and EPEL now, as well as in Mageia and openSUSE. Mainly I fix things related to making Pagure work on these distributions.
Fedora CI (gating) https://fedoraproject.org/wiki/CI
package maintenance, i.e. vim, libcap, ed, .... Add tests and enable gating
And of course, I'm a packager. :)
-- 真実はいつも一つ！/ Always, there's only one truth!
Hey Leigh!
- Project you are actively working regularly on
- Fedora Messaging - Bodhi
- Link to the Landing Page / Tracker / Source / Docs / anything relevant
really that might help me get a handle on the project
Fedora Messaging: - https://fedora-messaging.readthedocs.io/en/stable/ - https://github.com/fedora-infra/fedora-messaging
Bodhi: https://github.com/fedora-infra/bodhi/
- Got a roadmap link? Or backlog link?
Fedora Messaging: no roadmap at the moment, the focus is on migrating apps to the recently published library and making minor fixes in the process (and add a couple features to adjust for what we may have missed during initial development).
Bodhi's high level tasks: https://github.com/fedora-infra/bodhi/projects
- Any upcoming release plans that you are aware of / have committed to?
Fedora Messaging: the releases are driven by our porting needs at the moment. Bodhi: Version 4.0: https://github.com/fedora-infra/bodhi/projects/6
- Anything else you think is worth sharing by all means include it
I'm also working on Mailman3 / HyperKitty / Postorius, but not regularly (more a sort of bugfix mode + infrastructure requests). I had started to work on FPDC with Clément but got sidetracked by other projects, so I'm not contributing much to that these days, but it's the sort of tech I know and could be working on when other things clear up.
Cheers!
Aurélien
On Tue, 29 Jan 2019 at 14:29, Leigh Griffin lgriffin@redhat.com wrote:
Hey everyone,
I am trying to get a handle on the number of projects that we are actively working on for any given day of the week. Could I ask everybody to reply here with some information. At a minimum if you could share with me:
- Project you are actively working regularly on
- OSBS ( OpenShift Build Service ) :
This is the service we are using to build layered image containers (not the fedora base image yet) in Fedora. I mostly make sure that the service is available and running, I also maintain the packages in Fedora. The project is actively develop by the OSBS team at Red Hat, on my side I now mostly do sysadmin tasks.
OSBS is composed of https://github.com/projectatomic/atomic-reactor https://github.com/projectatomic/osbs-client https://github.com/release-engineering/koji-containerbuild
More documentation of the Build system https://docs.pagure.org/releng/layered_image_build_service.html
Backlog: - Support for aarch64 build in production (currently available in staging) - https://pagure.io/cpe-planning/issue/7 - https://pagure.io/ContainerSIG/container-sig/issues
- Fedora Container SIG and Release :
I started the Fedora Container SIG ( https://pagure.io/projects/ContainerSIG/%2A) and host our fortnightly meeting. I make sure the fedora base container image release happen (released on dockerhub, quay.io, registry.fp.o), I am also the default assignee for all the bugzilla assinged to the "Fedora Container Images" product.
Backlog: - Build the container base image in OSBS - https://pagure.io/cpe-planning/issue/36
- FPDC (Fedora Product Definition Center) ( https://fpdc.fedoraproject.org/api/v1/)
This is aimed to replace PDC (https://pdc.fedoraproject.org/) to give a central place to query information about component built in Fedora and the life-cycle of these.
https://github.com/fedora-infra/fpdc https://github.com/fedora-infra/fpdc-client
Backlog: https://github.com/fedora-infra/fpdc/issues
Initial design document: https://docs.google.com/document/d/1F5OEyAM22Jcsa4H5JoQ97PE39lBi5LPpxbSHabCm... (only available by Red Hat employee) If needed I am happy to move it on a public shared platform :)
- fedora-packages (https://apps.fedoraproject.org/packages/) :
This is the google of Fedora packages, it helps people searching for packages in Fedora and provides all kind of useful information for a package. The code base starts to be quite old and I started to work on a potential replacement for it (https://github.com/fedora-infra/fedora-search ).
Backlog: https://github.com/fedora-infra/fedora-packages/issues
Hope that helps :)
- Link to the Landing Page / Tracker / Source / Docs / anything relevant
really that might help me get a handle on the project
Got a roadmap link? Or backlog link?
Any upcoming release plans that you are aware of / have committed to?
Anything else you think is worth sharing by all means include it
I want to try and get a picture of the landscape and to take all of that into account when we start looking at the upcoming priorities for the Red Hat team. I want to try paint a bigger picture of our current responsibilities and commitments to help us inform what our future commitments look like.
I intend to transpose this *somewhere* in due course, the Wiki might be a good starting point but for now I'm happy to take the details within this thread and I can follow up with another conversation as the information flows in.
Thanks, Leigh
--
LEIGH GRIFFIN
ENGINEERING MANAGER,
Community Platform Engineering
Red Hat Ireland https://www.redhat.com/
Communications House, Cork Road
Waterford City, Ireland X91NY33
lgriffin@redhat.com M: +353877545162 IM: lgriffin https://red.ht/sig TRIED. TESTED. TRUSTED. https://redhat.com/trusted
@redhatway https://twitter.com/redhatway @redhatinc https://instagram.com/redhatinc @redhatsnaps https://snapchat.com/add/redhatsnaps _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@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/infrastructure@lists.fedorapro...
On Tue, 29 Jan 2019 at 08:18, Leigh Griffin lgriffin@redhat.com wrote:
Hey everyone,
I am trying to get a handle on the number of projects that we are actively working on for any given day of the week. Could I ask everybody to reply here with some information. At a minimum if you could share with me:
I am mostly on the ops side so not sure how to handle this.. I have put items I deal with regularly but not sure if that meets it.
- Project you are actively working regularly on
Fedora Infrastructure https://pagure.io/fedora-infrastructure EPEL https://pagure.io/epel Nagios https://nagios.fedoraproject.org Various data-analysis https://data-analysis.fedoraproject.org (behind limited login)
- Link to the Landing Page / Tracker / Source / Docs / anything relevant
really that might help me get a handle on the project
- Got a roadmap link? Or backlog link?
What exactly does that mean?
- Any upcoming release plans that you are aware of / have committed to?
EPEL-8 beta by March Sensu evaluation by April data-analysis updates by April keep the plates spinning.
- Anything else you think is worth sharing by all means include it
I want to try and get a picture of the landscape and to take all of that into account when we start looking at the upcoming priorities for the Red Hat team. I want to try paint a bigger picture of our current responsibilities and commitments to help us inform what our future commitments look like.
I intend to transpose this *somewhere* in due course, the Wiki might be a good starting point but for now I'm happy to take the details within this thread and I can follow up with another conversation as the information flows in.
Thanks to those that responded, if you haven't had a chance with travel / busy things going on, it would be really appreciated if you could take 5 minutes and give an overview.
To clarify by backlog / roadmap, I mean do you have future plans to do certain things so that the Community can have an insight into what's coming next and / or want to help you out on that. Obviously for unplanned Ops style work it's harder to quantify that but you might, for example, have plans to expand monitoring to A B or C....or automate all of the things. I hope that makes sense?
Leigh
On Wed, Jan 30, 2019 at 7:41 PM Stephen John Smoogen smooge@gmail.com wrote:
On Tue, 29 Jan 2019 at 08:18, Leigh Griffin lgriffin@redhat.com wrote:
Hey everyone,
I am trying to get a handle on the number of projects that we are actively working on for any given day of the week. Could I ask everybody to reply here with some information. At a minimum if you could share with me:
I am mostly on the ops side so not sure how to handle this.. I have put items I deal with regularly but not sure if that meets it.
- Project you are actively working regularly on
Fedora Infrastructure https://pagure.io/fedora-infrastructure EPEL https://pagure.io/epel Nagios https://nagios.fedoraproject.org Various data-analysis https://data-analysis.fedoraproject.org (behind limited login)
- Link to the Landing Page / Tracker / Source / Docs / anything relevant
really that might help me get a handle on the project
- Got a roadmap link? Or backlog link?
What exactly does that mean?
- Any upcoming release plans that you are aware of / have committed to?
EPEL-8 beta by March Sensu evaluation by April data-analysis updates by April keep the plates spinning.
- Anything else you think is worth sharing by all means include it
I want to try and get a picture of the landscape and to take all of that into account when we start looking at the upcoming priorities for the Red Hat team. I want to try paint a bigger picture of our current responsibilities and commitments to help us inform what our future commitments look like.
I intend to transpose this *somewhere* in due course, the Wiki might be a good starting point but for now I'm happy to take the details within this thread and I can follow up with another conversation as the information flows in.
-- Stephen J Smoogen.
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@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/infrastructure@lists.fedorapro...
On Wed, Jan 30, 2019 at 5:07 PM Leigh Griffin lgriffin@redhat.com wrote:
Hey everyone,
I am trying to get a handle on the number of projects that we are actively working on for any given day of the week. Could I ask everybody to reply here with some information. At a minimum if you could share with me:
I'm not a Red Hatter, but it's probably useful for other people to know what I'm doing...
- Project you are actively working regularly on
The main thing I'm working on is porting infrastructure software to Python 3 and/or DNF, or pushing forward other efforts to do so.
I also develop/maintain several projects:
- livecd-tools: https://github.com/livecd-tools/livecd-tools - appliance-tools: https://pagure.io/appliance-tools - rpmlint: https://github.com/rpm-software-management/rpmlint - rpmdevtools: https://pagure.io/rpmdevtools - FedoraReview: https://pagure.io/FedoraReview
- Link to the Landing Page / Tracker / Source / Docs / anything relevant
really that might help me get a handle on the project
I don't have a specific "page" about the porting stuff, but I'm currently tracking and reviewing the following efforts:
- Porting Koji to Python 3 and DNF - https://pagure.io/koji/pull-request/1117 - https://pagure.io/koji/pull-request/921 - https://pagure.io/koji/pull-request/891 - Porting urlgrabber to Python 3 - https://github.com/rpm-software-management/urlgrabber/pull/8 - Porting Ipsilon to Python 3 - https://pagure.io/ipsilon/pull-request/313
- Got a roadmap link? Or backlog link?
Sorry, most of my stuff is ad-hoc, given that I'm doing all of this in my free time. Help would be appreciated, though. 😊
If can get to it, I'm planning on working a bit on the following efforts:
- Porting FedoraReview to Python 3 - Porting Spacewalk to DNF and Python 3 - Porting Cobbler to DNF and Python 3
- Any upcoming release plans that you are aware of / have committed to?
In no particular order:
- Fedora 30 release - Mageia 7 release - openSUSE Leap 15.1 release - RHEL 8 release
- Anything else you think is worth sharing by all means include it
If I can manage to squeeze it in somehow, I want to try to address the issue of module repository metadata being YAML instead of XML. This is a major problem for third-party consumers of RPM repodata when trying to parse the various extensions of rpm-md repodata.
The GitHub issue for this: https://github.com/fedora-modularity/libmodulemd/issues/101
Without fixing this, I'm basically stuck in terms of being able to support some way of parsing modules properly, if we're going to be stuck with this approach for modularity.
I want to try and get a picture of the landscape and to take all of that into account when we start looking at the upcoming priorities for the Red Hat team. I want to try paint a bigger picture of our current responsibilities and commitments to help us inform what our future commitments look like.
I intend to transpose this *somewhere* in due course, the Wiki might be a good starting point but for now I'm happy to take the details within this thread and I can follow up with another conversation as the information flows in.
I don't know how much bigger you want to go here... And I don't know if
there's much care by anyone about the stuff I'm looking at now...
On 1/29/19 5:14 AM, Leigh Griffin wrote:
Hey everyone,
I am trying to get a handle on the number of projects that we are actively working on for any given day of the week. Could I ask everybody to reply here with some information. At a minimum if you could share with me:
Yeah, I am in the same boat that Smooge is (and Ricky), being on the ops side of things we don't have direct projects, just lots of misc things.
Project you are actively working regularly on
Link to the Landing Page / Tracker / Source / Docs / anything relevant
really that might help me get a handle on the project
Got a roadmap link? Or backlog link?
Any upcoming release plans that you are aware of / have committed to?
Anything else you think is worth sharing by all means include it
As noted our main ops/initial bugs tracker is https://pagure.io/fedora-infrastructure.
As for misc projects I am working on:
* Trying to get our buildvm-armv7 builders upgraded (they are Fedora 27 currently). This is blocked by bug https://bugzilla.redhat.com/show_bug.cgi?id=1576593
* Get our s390x buildvm's reinstalled as kvm guests. This is stalled on time from the mainframe admins.
* Retire cloud. Just started talking to copr folks and will be figuring out what we want to do moving forward.
* archive old koji content so we can reduce storage for active releases. This is waiting on some new hardware coming online.
* Get linux-system-roles setup to handle at least networking.
* repospanner for ansible repo, src.stg and finally src in prod. Will work on writing up the tasks left for this soon.
I think once we have a taiga we can track all these longer ops projects there. At least I hope so.
There's also a number of things we run that are projects that we are not upstream for. For example:
wiki (mediawiki) zodbot (Limnoria) koji nagios collectd magazine (wordpress) paste (modernpaste) mailman3 (hyperkitty/postorius)
Basically we just need to track these for issues and update/work with upstream.
Thanks for trying to bring order to our chaos Leigh!
kevin
infrastructure@lists.fedoraproject.org
-
Aurelien Bompard -
Clement Verna -
Karsten Hopp -
Kevin Fenzi -
Leigh Griffin -
Michal Konecny -
Neal Gompa -
Pierre-Yves Chibon -
Rick Elrod -
Stephen John Smoogen