-
Notifications
You must be signed in to change notification settings - Fork 3
Öykü Yılmaz Repository Exploration
oykuyilmaz1 edited this page Feb 19, 2020
·
2 revisions
Here, you can find the repositories I find useful and the brief descriptions taken from their GitHub pages.
"These pages are primarily intended for those who wish to contribute to the VS Code project by submitting bug reports, suggesting new features, building extensions, commenting on new ideas, or even by submitting pull requests."
- In the
READ ME
file you can find the description of the repository, how to contribute, how to give feedback - shortly everything you can ask. - In their wiki page, everything is categorized and well explained.
- Also they have 258 labels that can categorize their issues.
"This is the core repository of the Open edX software. It includes the LMS (student-facing, delivering courseware), and Studio (course authoring) components."
- This repository has also a webpage, so it refers to that in the
READ ME
file. The file also contains help for downloading the software. Just reading this file gives you an idea of the repository. - Their wiki page has moved to another website but you can see the old files uploaded there. Everything is also categorized and they have a page called 'FAQ' which can be really useful.
"This is a series of books diving deep into the core mechanisms of the JavaScript language."
- Since this repository is a book in the first place, you can find the titles in the
READ ME
file. This helps a lot if you are not sure whether this is the book you are looking for. - What I do not like about it is they do not have a proper wiki page. If it did, it can be used as a proper forum and they could have added a FAQ part to gather questions of the learners.
"A practical security guide for web developers"
- Their
READ ME
file is crystal clear, you can find out what this repository is, who are running it, and the contents. - They also does not have a wiki page you feel like they used the
READ ME
file as wiki.
- Requirements
- Workspace Creation Scenario
- Application to a Workspace Scenario
- Follow Mechanism Scenario
- Design Documents
- Plan Documents
- Milestone Reports
- API Documentation
- Manuals
- Burak Ömür
- Halil Umut Özdemir
- Hasan Ramazan Yurt
- Öykü Yılmaz (Communicator)
- Ahmet Dadak
- Ertuğrul Bülbül
- Alperen Divriklioğlu
- Burhan Can Akkuş
- Hüseyin Can Bölükbaş
- Hilal Demir
- Umutcan Uvut
- Orkan Akisu
- Frontend Meeting #7 (19.01.2021)
- Frontend Meeting #6 (12.01.2021)
- Android Meeting #5 (08.01.2021)
- Frontend Meeting #5 (05.01.2021)
- Backend Meeting #6 (30.12.2020)
- Meeting #26 (29.12.2020)
- Meeting #25 (28.12.2020)
- Backend Meeting #5 (23.12.2020)
- Frontend Meeting #4 (21.12.2020)
- Android Meeting #4 (18.12.2020)
- Backend Meeting #4 (16.12.2020)
- Meeting #24 (15.12.2020)
- Meeting #23 (09.12.2020)
- Frontend Meeting #3 (10.12.2020)
- Android Meeting #3 (09.12.2020)
- Backend Meeting #3 (09.12.2020)
- Frontend Meeting #2 (08.12.2020)
- Android Meeting #2 (07.12.2020)
- Frontend Meeting #1 (03.12.2020)
- Android Meeting #1 (02.12.2020)
- Backend Meeting #2 (02.12.2020)
- Meeting #22 (25.11.2020)
- Meeting #21 (21.11.2020)
- Backend Meeting #1 (18.11.2020)
- Meeting #20 (17.11.2020)
- Meeting #19 (10.11.2020)
- Meeting #18 (30.10.2020)
- Meeting #17 (27.10.2020)
- Meeting #16 (24.05.2020)
- Meeting #15 (13.05.2020)
- Meeting #14 (10.05.2020)
- Meeting #13 (07.05.2020)
- Meeting #12 (30.04.2020)
- Meeting #11 (23.04.2020)
- Meeting #10 (17.04.2020)
- Meeting #9 (16.04.2020)
- Meeting #8 (09.04.2020)
- Meeting #7 (22.03.2020)
- Meeting #6 (12.03.2020)
- Meeting #5 (05.03.2020)
- Meeting #4 (28.02.2020)
- Customer Meeting #1 (28.02.2020)
- Meeting #3 (27.02.2020)
- Meeting #2 (20.02.2020)
- Meeting #1 (13.02.2020)
- Meeting Notes Template