-
Notifications
You must be signed in to change notification settings - Fork 22
Home
Mihai Coslet edited this page Feb 12, 2018
·
22 revisions
-
C++
average to strong background - Spoken and Written English
- Event-driven programming (message-oriented)
- API
- Windows applications development
- Version Control Systems (
git
) - Code style
- Debugging
- Virtual machine
- 3-tier architecture
- Testing
Laboratory work follow rules that where public when submission was done. If you'll do a submission after rules change, your submission will fall under new rules.
You can foresee your marks by following this.
In order to pass this course you have to submit all you laboratory works. For details view this page.
First check issues page and closed issues page. Then check the facebook group.
If your question is still unanswered then:
- if your question is about schedule, classroom, some events, some deadlines or anything else that is specific for your group, ask it on facebook page
- otherwise ask questions about laboratory works by opening new issues
In order to receive changes on repository or on its wiki, there is a watching button on top of repository page.
To edit laboratory works descriptions or samples do a pull request to WP repository with your proposals/changes/typo fixes.
To edit/create a wiki page do:
- Manually create a fork of the WP wiki on your GitHub account:
- Create a new repository on your GitHub account. Let's call it "WP-Wiki"
- Clone the WP wiki repo to your local machine somewhere:
git clone [email protected]:TUM-FAF/WP.wiki.git
- Remove the original "origin" remote and add your github repo as new "origin"
git remote rm origin
andgit remote add origin [email protected]:<your username>/WP.wiki.git
- Make your proposed changes locally, then push them to your github account:
-
git push -u origin master
('-u origin master' only required the first time; afterwards just do git push)
-
- Submit a ticket to the WP issue tracker requesting me to review your changes and merge them in. Please be sure to include a link to your repo and describe what you've changed.