On Wed, Jan 30, 2019 at 01:33:48PM -0500, pmkellly(a)frontier.com wrote:
applications or for fedora infrastructure. To use Pull Requests you
have to get set up with GitHub and clone the fedora stuff on your
PC. Then you pick something to work on. When you're at a point where
you what to at least get some comments on what you've done, you
submit a Pull Request. If I have this wrong or incomplete please
point me to where I should read more.
That's essentially right, although the workflow is not limited to GitHub.
It's also used by Pagure (used by Fedora at https://pagure.io
) and GitLab (used for example by upstream
Then I got curious about infrastructure; so I started reading about
fedora infrastructure. From what I've read the infrastructure term
is used to refer to the servers, networks, and websites that all the
fedora teams use to accomplish their fedora related work. I also
thought this might include the various build, compose, test
procedures, and test software used, but that wasn't clear to me. If
I have this wrong or incomplete please point me to where I should
This is basically right too, although in Fedora it's complicated because
historically some bits of this were owned by Infrastructure and others by
Release Engineering. We're working on consolidating that all into one team.
Then I read some about Tickets. From what I read, Tickets are the
vehicle used for report infrastructure bugs, problems or suggestions
for enhancement. From the e'mails I have seen on this list they also
seem to be used by teams to act as reminders for team members to do
things. To write or edit a Ticket Pagure seems to be used. I browsed
the projects in Pagure and you really need to know exactly which
project to use before you go there. If I have this wrong or
incomplete please point me to where I should read more.
Yes, this is right too. Sorry -- it's a big project and so it's hard to
avoid there being lots of different parts.
Fedora Project Leader