Re-(re?)-starting the Fedora classrooms #338

Open
opened 2026-06-15 13:23:37 +00:00 by ankursinha · 7 comments
Owner

Here at Flock, we've received feedback that the classrooms would be good to:

  • restart
  • record/archive for later use

So, I'm just filing this here for us to look at. I think a call for participation to get more people helping here would be very useful. Perhaps another repository for Classrooms where we can archive materials/links would be useful to. If we have enough, it could even be made into a Docs sub-project and live on docs.fp.o

Please add ideas/comments/pain points here.

Here at Flock, we've received feedback that the classrooms would be good to: - restart - record/archive for later use So, I'm just filing this here for us to look at. I think a call for participation to get more people helping here would be very useful. Perhaps another repository for Classrooms where we can archive materials/links would be useful to. If we have enough, it could even be made into a Docs sub-project and live on docs.fp.o Please add ideas/comments/pain points here.
Member

yes, this is something which would be benefitial, we already have #304

i could take a look at making slides / working out what should we do for the hands on in the git classroom.

yes, this is something which would be benefitial, we already have https://forge.fedoraproject.org/join/Fedora-Join/issues/304 i could take a look at making slides / working out what should we do for the hands on in the git classroom.
Author
Owner

Thanks @smoliicek!

I was leaning towards following these curated sessions/curriculum, as they've been made by lots of experienced instructors:

https://software-carpentry.org/lessons/

It also means we don't have to prepare material---we can use these global ones. They also include lots of explanations, resources, and so on.

Thanks @smoliicek! I was leaning towards following these curated sessions/curriculum, as they've been made by lots of experienced instructors: https://software-carpentry.org/lessons/ It also means we don't have to prepare material---we can use these global ones. They also include lots of explanations, resources, and so on.
Owner

Using Software Carpentry is the way to go.
I fully support the idea, but am unable to work on any aspect of it at this time.

If we do it, we should contact marketting / socials / do some outreach / Magazine Article about it so we get some participants.

Using Software Carpentry is the way to go. I fully support the idea, but am unable to work on any aspect of it at this time. If we do it, we should contact marketting / socials / do some outreach / Magazine Article about it so we get some participants.
Author
Owner

I was wondering if I should do a new session on Git (see #304), using the software carpentry material---and we can perhaps record and archive that for people to follow at their own pace?

The question is:

  • do people want live sessions
  • do they want the recording to work on it themselves
  • do we try to do both

In the past, we've done both. Doing sessions regularly is a lot more work, of course, and I wouldn't recommend we go down this road if we don't have enough instructors to share the load. We could do a fresh classroom every year/2 years perhaps---that way it's more manageable, and the recordings remain up to date with changes in the tools etc.?

Here is an example of a packaging 101 session I'd done:

https://fedoramagazine.org/fedora-classroom-rpm-packaging-101/

youtube video

https://www.youtube.com/watch?v=woFtdIS6x0Q


A related bit is perhaps to have a place where we index archived sessions---add them to our join docs perhaps?

See more past classrooms here:

https://fedoramagazine.org/?s=classroom

I was wondering if I should do a new session on Git (see #304), using the software carpentry material---and we can perhaps record and archive that for people to follow at their own pace? The question is: - do people want live sessions - do they want the recording to work on it themselves - do we try to do both In the past, we've done both. Doing sessions regularly is a lot more work, of course, and I wouldn't recommend we go down this road if we don't have enough instructors to share the load. We could do a fresh classroom every year/2 years perhaps---that way it's more manageable, and the recordings remain up to date with changes in the tools etc.? Here is an example of a packaging 101 session I'd done: https://fedoramagazine.org/fedora-classroom-rpm-packaging-101/ youtube video https://www.youtube.com/watch?v=woFtdIS6x0Q --- A related bit is perhaps to have a place where we index archived sessions---add them to our join docs perhaps? See more past classrooms here: https://fedoramagazine.org/?s=classroom
Owner

You should record the sessions.
We have had people come and Join due to watching Cornelius' Docs Worshops.
People do look at Fedora You Tube content, and appreciate it.

Minimise the work, set the standard, and then let someone else run more sessions if they want to.

You should record the sessions. We have had people come and Join due to watching Cornelius' Docs Worshops. People do look at Fedora You Tube content, and appreciate it. Minimise the work, set the standard, and then let someone else run more sessions if they want to.

As someone just coming to the project I do like the idea of a series of lessons that would guide me through the processes involved.

I think a recorded session every release cycle would be adequate as that would give you the chance to update for any updated tooling, wouldn't be too much to commit to for an instructor and yet would appear incredibly welcoming and helpful to any new starters.

Any follow up questions can be dealt with in a chat and if a docs project is included we can update the docs as questions are asked and produce a truly comprehensive set of docs that would end up covering pretty much every eventually, reducing the load on volunteers having to answer all the questions

As someone just coming to the project I do like the idea of a series of lessons that would guide me through the processes involved. I think a recorded session every release cycle would be adequate as that would give you the chance to update for any updated tooling, wouldn't be too much to commit to for an instructor and yet would appear incredibly welcoming and helpful to any new starters. Any follow up questions can be dealt with in a chat and if a docs project is included we can update the docs as questions are asked and produce a truly comprehensive set of docs that would end up covering pretty much every eventually, reducing the load on volunteers having to answer all the questions
Author
Owner

An idea that @robinsheps and I had while discussing in the chat is to go hybrid:

  • use the software carpentries material for 101 (general intro to git): do a session, record it
  • do a 102 session for "git with fedora forge" for people that have done the 101 session where we quickly walk through using the forge---any material for this will be short, and specific to the forge.

that way, we don't end up duplicating what the carpentries (and others) do, but we also have a specific session for people that focuses on the tools we use?

For fedora specific things like packaging, we'll have to do it of course---but the materials for those already exists in the packaging guidelines and so on.

An idea that @robinsheps and I had while discussing in the chat is to go hybrid: - use the software carpentries material for 101 (general intro to git): do a session, record it - do a 102 session for "git with fedora forge" *for people that have done the 101* session where we quickly walk through using the forge---any material for this will be short, and specific to the forge. that way, we don't end up duplicating what the carpentries (and others) do, but we also have a specific session for people that focuses on the tools we use? For fedora specific things like packaging, we'll have to do it of course---but the materials for those already exists in the packaging guidelines and so on.
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
join/Fedora-Join#338
No description provided.