Thank you for sharing your feedback and ideas,
The point is, for a newcomer is a little bit hard to understand how
when to use many different tools (Pagure, Bugzilla, Bodhi, IRC, etc, etc).
I agree, I once was faced by a similar situation to learn how to use
Pagure, Bugzilla, Bodhi, IRC, etc.
We at Join SiG are planning the following Classrooms in the near future for:
- `Git 101 with Pagure` to help newcomers understand how Git works and how
to interact with Pagure and sync SSH keys.
- IRC 101, as we've seen newcomers are not much familiar with how IRC works
and how to communicate on IRC.
Other than that,
- For Bodhi, on the packages testing side, Fedora QA did an awesome job by
organizing an onboarding call and recorded it, to help newcomers
understand how Bodhi and karma works and how packages get pushed.
- Bugzilla would be an interesting one to look for as Bugzilla is huge and
have different use cases within Fedora, we can have a 2 part classroom on
For Packaging Classrooms, we can have an onboarding call like we have in
Fedora QA that can serve as a way to help newcomers to know about How RPM
packaging works and how packages are maintained in Fedora and details about
the sponsorship Model and a tutorial to package a simple app and references
if someone would like to get started with Packaging.
Thank You for sharing the links for previous workshops and docs Ankur.
Have a Good Day,
Nasir Hussain (He/Him/His)
On Tue, Jun 23, 2020 at 10:07 PM Ankur Sinha <sanjay.ankur(a)gmail.com> wrote:
On Tue, Jun 23, 2020 14:56:29 +0200, Christiano Anderson wrote:
> Hi Nasir,
Thanks Christiano, that's most useful.
> This classroom for newcomers is a great idea.
> I guess it should start with a very introductory one, how to get started
> have the hands dirty very fast, I mean, with real examples.
> The point is, for a newcomer is a little bit hard to understand how and
> to use many different tools (Pagure, Bugzilla, Bodhi, IRC, etc, etc).
> A real world example would be great, for instance, how to fix a bug into
> project, let's take DNF as example:
An unfortunate property of a volunteer driven community is that it's
quite fluid and does not have the strict structure that one would see at
corporations. So, when people come together to work on something, they
decide what platforms/services they want to use. As an example, lots of
tools in Fedora use Pagure, fedora-review for example:
but dnf uses GitHub:
This is compounded by the fact that Fedora as a Linux distribution is
"downstream", so the packages we include can come from literally
anywhere on the internet. It's up to the developers to decide on a
So instead of trying to teach newcomers all of this, we've got the
"Welcome-to-Fedora" process. It helps people learn the
tools/platforms/skills they are interested in:
I do agree that a packaging classroom would be very useful. We've had
them in the past, and we're looking at organising another one. In the
meantime, please use these recordings of past packaging workshops:
- Advanced RPM packaging: https://youtu.be/vdWnyIbN8uw
There were some introductory posts on the Fedora magazine related to RPM
sometime ago also:
- RPM packages explained:
- The SPEC file:
- The SRPM:
I'll see if links to these can be added to the packaging docs on Fedora
Ankur Sinha "FranciscoD" (He / Him / His) |
Time zone: Europe/London
fedora-join mailing list -- fedora-join(a)lists.fedoraproject.org
To unsubscribe send an email to fedora-join-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines