From Fedora Project Wiki
(Created page with '{{admon/note | Feel free to edit anything under this proposal, we are working on it as draft.}} = Objectives = * Getting people (mostly beginners) acquainted with using Version...')
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{admon/note | Feel free to edit anything under this proposal, we are working on it as draft.}}
{{admon/note | Feel free to edit anything under this proposal, we are working on it as draft | This is a draft for the mentioned Fedora Classroom '11 topic: Version Control Systems. You can see drafts for other topics, choose to prepare a draft on one of the topic or suggest a class [[Classroom#Suggest_a_class | here]]. }}


= Objectives =
= Objectives =
Line 39: Line 39:
== Tasks by levels ==
== Tasks by levels ==


{{admon/tip|This classroom topic needs teachers|We really do. Add your name below to take up this topic (Only if you are well acquainted with git and other Version Control Systems)}}
{{admon/tip|This classroom topic needs teachers|We really do. Add your name below to take up this topic (Only if you are well acquainted with git and other Version Control Systems (Because I am not)) Feel free to add/remove any topics you feel. This is just a draft.}}
 
== Tools and process ==
== Tools and process ==


[[Category:Draft]]
[[Category:Draft]]
[[Category:Fedora_School]]
[[Category:Fedora_School]]

Latest revision as of 06:33, 23 January 2011

Feel free to edit anything under this proposal, we are working on it as draft
This is a draft for the mentioned Fedora Classroom '11 topic: Version Control Systems. You can see drafts for other topics, choose to prepare a draft on one of the topic or suggest a class here.

Objectives

  • Getting people (mostly beginners) acquainted with using Version Control Systems like git.
  • Get them to work together into learning and meet each other, sharing more ideas to work in Fedora.

Schedule proposed

These could be the tasks for a first introductory crash course

Introduction to Verson Control Systems

Everyone should be able to make changes to a software (using git) in a maximum time of a week.

Prerrequisite: A Fedora system with git installed. Setting up a fedorapeople space

  • Need for Version Control System
    1. Backup and Restore
    2. Synchronization
    3. Short-term undo
    4. Long-term undo
    5. Track Changes
    6. Track Ownership
    7. Sandboxing
    8. Branching and merging
  • Terminology used frequently (Repo, Trunk/Main, Head, Diff etc)
  • Checkins and checkouts
  • Branching/Merging
  • Tagging
  • Source control using IDEs

Meetings

I really don't know what to put in here.

Tasks by levels

This classroom topic needs teachers
We really do. Add your name below to take up this topic (Only if you are well acquainted with git and other Version Control Systems (Because I am not)) Feel free to add/remove any topics you feel. This is just a draft.

Tools and process