First, I'm sure we're extremely grateful to all the great folks that
have stepped forward to instruct classroom sessions.
I think we now have enough to plan a schedule and get the sessions
started. Here's a draft plan and schedule. Please weigh in so that we
can maybe start in two weeks time?
SOP (standard operating procedure) draft:
Week: -2 (2 weeks before a session)
- Instructor picks a time and day of the week
- A wrangler updates the calendar on fedocal
- A wrangler drafts a post for both the fedora magazine (target
audience - end users) and the community blog (target audience -
community people) and submits it for review to CommOps
- A wrangler drafts a general announcement for the "announce" mailing
Week: -1 (1 week before a session)
- Both magazine and commblog posts to go live (CommOps will do this)
- A wrangler sends out mail to "announce" mailing list
- A wrangler begins to work on the *next* session.
Week: 0 (Day or two before the session)
- Reminders over social media etc.
Week: 0 (Day or two after the session)
- Instructor publishes report + logs. (What channel do we use for
- Instructor uploads/documents post class "study material" - A Pagure
and so we keep rolling. How does that sound? The pagure repo can be
used for general organisation too via tickets if this is ever required.
I think the wiki works for the time being,
Proposed class schedule
We have the following classes available:
- Packaging 101 (FranciscoD)
- QA 101, 102 (Sumantro)
- Git 101 (FranciscoD)
- Emacs 101(Sachin)
- Magazine 101 (Eduard)
- Vim 101 (Eduard/FranciscoD)
- Command line 101 (FranciscoD/?)
So we have 6 classes. I'm also going to go look for someone who can
take a "Free software 101" class. Personally, I'd like it to be a
regular class that is repeated every few months where we can discuss
Fedora's role in the Free software movement. (Maybe I can ask one of
the seasoned contributors from the Council to help with this?)
The order I propose:
- The one that doesn't require much technical knowledge
* Magazine 101
* Then a quick introduction to the Linux command line and utilities:
- Command line 101
- Then the text editors
* Vim 101
* Emacs 101
- Then slightly more technical
* QA 101
- Then even more technical and more software focussed
* Git 101
- Then the process that uses a lot of the afore-learned skills:
* Packaging 101
How does that sound?
I'm hoping we'll get more community members involved once the sessions
start. We can use more wranglers, (and instructors, of course). When
you speak to people at meetings and so on, please drop in a word to let
people know. :)
Ankur Sinha "FranciscoD"
I have kinda prepared what we will be giving out as a part of Fedora QA classroom session.
The topics covered will be:
1. Working with Fedora
2. Installing on VM(s)
3. Configuring and Installing fedora
4. Fedora Release Cycle
5. Live boot and Fedora Media Writer
6. Setting up accounts
7. Types of testing
8. Finding Test Cases
9. Writing Test Cases for Packages
12. Release Validation Testing
13. Update Testing
14. Manual Testing
14.1 Release validation
14.2 Update Testing
A small post where I have attached an reference guide to getting started for attendees to have a look after the sessions are over
I would like to know if everyone is okay with fixing a time to sync up and discuss?
I want to offer my help in the classroom with 2 ideas for a classroom and
also to publicize the classroom in the magazine.
- Magazine Workflow: How to contribute with the magazine? What is a pitch,
a draft and other statuses?
- ViM for human beings: Installing, configuring and using ViM without quit
in the first hour.
GNU/Linux User #589060
Ubuntu User #8749
Fedora Ambassador Latam