On Wed, Jan 30, 2019 at 5:07 PM Leigh Griffin <lgriffin(a)redhat.com> wrote:
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
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
tracking and reviewing the following efforts:
- Porting Koji to Python 3 and DNF
- Porting urlgrabber to Python 3
- Porting Ipsilon to Python 3
- 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:
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
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
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...
真実はいつも一つ！/ Always, there's only one truth!