https://wiki.cdot.senecacollege.ca/w/api.php?action=feedcontributions&user=Aushakou&feedformat=atomCDOT Wiki - User contributions [en]2024-03-28T16:56:47ZUser contributionsMediaWiki 1.30.0https://wiki.cdot.senecacollege.ca/w/index.php?title=OSD600_and_DPS909_Winter_2018_Lab_5&diff=133805OSD600 and DPS909 Winter 2018 Lab 52018-04-25T03:15:08Z<p>Aushakou: /* 2. Blog */</p>
<hr />
<div>=Mixing Open Data, Open Source, Open Assets=<br />
<br />
This week we're starting a case study looking at practical ways to use and mix open data sets, open source, and open assets. Along the way we're also exploring modern approaches to collaborative, modern JavaScript development.<br />
<br />
In this lab, you are asked to add a new feature to the project. The goals of the lab include:<br />
<br />
* Practice working on front-end JavaScript on GitHub<br />
* Gain experience using open source APIs and modules<br />
* Read and Write code written in modern JavaScript<br />
* Gain experience working with common collaborative tooling on GitHub<br />
<br />
==1. Feature Request==<br />
<br />
You are asked to implement a solution for the following Issue: https://github.com/humphd/bridge-troll/issues/6<br />
<br />
Please '''fork''' the https://github.com/humphd/bridge-troll repo and '''create a new branch''' named <code>issue-6</code>.<br />
<br />
Implement your fix on your <code>issue-6</code> branch, and then push to GitHub.<br />
<br />
==2. Blog==<br />
<br />
Write a blog post about your experience adding the feature. Here are some things to pay attention to as you work:<br />
<br />
* Did you run into any problems? How did you overcome them?<br />
* What did you need to learn in order to complete the work?<br />
* Talk about the technologies you used. What did you think of them? Were they easy to use? What did you like/dislike about them.<br />
* What does your fix look like (screenshots)?<br />
* What approach did you take to solving this?<br />
<br />
Please add a line for your blog and GitHub branch (with the commits for your fix) in the following table:<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! Git URL to Branch for Fix (URL)<br />
! Blog Post (URL)<br />
|-<br />
| 1<br />
| Woodson Delhia<br />
| https://github.com/Woody88/bridge-troll/tree/issue-6<br />
| https://woodsondelhia.wordpress.com/2018/04/24/lab-5-bridge-troll<br />
|-<br />
| 2<br />
| Liam Newell<br />
| https://github.com/hibyguy/bridge-troll<br />
| http://liamnewell.me/blog/bugs/Lab-5-bridge-troll/<br />
|-<br />
| 3<br />
| Matthew Quan<br />
| https://github.com/irrationalRock/bridge-troll/tree/addDayNight<br />
| https://mattprogrammingblog.wordpress.com/2018/03/20/osd600-lab-5-doing-a-feature-request/<br />
|-<br />
| 4<br />
| Alex Wang<br />
| https://github.com/AlexWang-16/bridge-troll/tree/issue-6<br />
| https://alexopensource.wordpress.com/2018/03/18/bridge-troll-project-implement-dark-mode/<br />
|-<br />
| 5<br />
| Zhihao Cai<br />
| https://github.com/josechoy/bridge-troll/tree/issue-6<br />
| https://choyzhihao.wordpress.com/2018/03/19/play-with-front-end-javascript/<br />
|-<br />
| 6<br />
| Kelvin Cho<br />
| https://github.com/TheKinshu/bridge-troll/tree/issue-6<br />
| https://klvincho.wordpress.com/2018/03/19/bridge-troll-dark-mode-feature/<br />
|-<br />
| 7<br />
|Qiliang Chen<br />
|https://github.com/KignorChan/bridge-troll/tree/issue-6<br />
|https://qchen102.blogspot.ca/2018/03/lab-5-add-feature-in-existing-object.html<br />
|-<br />
| 8<br />
| Hao Chen<br />
| https://github.com/haoRchen/bridge-troll/tree/issue6<br />
| https://medium.com/haorc/the-troll-under-the-bridge-cf9e24686fc1<br />
|-<br />
| 9<br />
| Lucas Verbeke<br />
| https://github.com/Micluc/bridge-troll/tree/issue-6<br />
| https://thelucasexcerpt.wordpress.com/2018/03/22/osd600-lab-5-lucas-verbeke<br />
|-<br />
| 10<br />
|Hongcheng Zhang<br />
|https://github.com/StevenZhang123/bridge-troll/tree/issue-6<br />
|https://hongcheng1993.wordpress.com/2018/03/22/lab5/<br />
|-<br />
| 11<br />
|Jafar Frotan<br />
|https://github.com/humphd/bridge-troll/pull/25<br />
|https://medium.com/@jaf.frotan/toggle-night-and-day-for-bridge-troll-repository-760931968fe3<br />
|-<br />
| 12<br />
|Justin Vuu<br />
|https://github.com/jevuu/bridge-troll/tree/issue-6<br />
|https://justosd.wordpress.com/2018/03/23/osd600-lab-5-the-bridge-troll/<br />
|-<br />
| 13<br />
| Joseph Pham<br />
| https://github.com/jpham14/bridge-troll<br />
| https://jpham14.wordpress.com/2018/03/16/lab-5-bridge-troll/<br />
|-<br />
| 14<br />
| Yalong Li<br />
| https://github.com/humphd/bridge-troll/pull/26<br />
| https://yalongxyz.blogspot.ca/2018/03/osd-lab5-add-light-dark-mode-switches.html<br />
|-<br />
| 15<br />
| Zukhruf Khan<br />
| https://github.com/zeddkay/bridge-troll/tree/issue6<br />
| https://zedsdps909blog.wordpress.com/2018/03/26/trying-to-fix-another-issue/<br />
|-<br />
| 16<br />
| Abdul Kabia<br />
| https://github.com/AbdulKabia/bridge-troll/tree/Lab5-Fix<br />
| https://akkabia.wordpress.com/2018/03/28/light-vs-dark-the-epic-battle/<br />
|-<br />
| 17<br />
| Owen Mak<br />
| https://github.com/Owen-Mak/bridge-troll/tree/issue6<br />
| https://makowen.wordpress.com/2018/03/28/trolls-and-sunshine/<br />
|-<br />
| 18<br />
| Vimal Raghubir<br />
| https://github.com/Vimal-Raghubir/bridge-troll/tree/issue-6<br />
| https://medium.com/@vraghubir/bridge-troll-feature-addition-bfee973b344b<br />
|-<br />
| 19<br />
| Oleh Hodovaniuk<br />
| https://github.com/ohodovaniuk1/bridge-troll/tree/issue6<br />
| https://ohodovaniuk.wordpress.com/2018/03/27/lab-5-2/<br />
|-<br />
| 20<br />
| Bakytzhan Apetov<br />
| https://github.com/humphd/bridge-troll/pull/28<br />
| https://bapetov.wordpress.com/2018/03/31/lab-5-adding-automatic-switch-for-light-and-dark-map-modes/<br />
|-<br />
| 21<br />
|Evan Davies<br />
|https://github.com/EmdaviesSeneca/bridge-troll/tree/issue-6<br />
|http://openthoughtsopensource.blogspot.ca/2018/04/the-difference-is-like-day-and-night.html<br />
|-<br />
| 22<br />
| Aleksey Glazkov<br />
| https://github.com/alexglazkov9/bridge-troll/tree/issue-6<br />
| https://aglazkovblog.wordpress.com/2018/04/05/a-friendly-troll-that-lives-under-ontarios-bridges/<br />
|-<br />
| 23<br />
|Abel Inocencio<br />
|https://github.com/simon-inoc/bridge-troll/tree/issue-6<br />
|<br />
|-<br />
| 24<br />
|Soutrik Barua<br />
|https://github.com/buttersnipps/bridge-troll/tree/mini-map<br />
|http://soutrikbarua.blogspot.ca/2018/04/utilizing-leaflet-mini-map-library-in.html<br />
|-<br />
| 25<br />
|Kevin Pham<br />
|https://github.com/kqpham/bridge-troll/tree/issue-6<br />
|http://kqpham2.blogspot.ca/2018/04/lab-5-bridge-troll.html<br />
|-<br />
| 26<br />
|Pranoy Santosh<br />
|https://github.com/pranoy10/bridge-troll/tree/issue5<br />
|http://pranoydps909.blogspot.ca/2018/04/implementing-daynight-mode-in-bridge.html<br />
|-<br />
| 27<br />
|Michael Fainshtein<br />
|https://github.com/mfainshtein2/bridge-troll/tree/issue-6<br />
|https://moderatelyokaydeveloper.wordpress.com/2018/04/21/let-there-be-night-mode/<br />
|-<br />
| 28<br />
|Aliaksandr Ushakou<br />
|https://github.com/aushakou/bridge-troll/tree/issue-6<br />
|https://aushakou.wordpress.com/2018/04/25/dark-mode-feature-request/<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD600_and_DPS909_Winter_2018_Lab_7&diff=133788OSD600 and DPS909 Winter 2018 Lab 72018-04-24T03:57:09Z<p>Aushakou: /* 8. Submission */</p>
<hr />
<div>=Traivs CI and Deployment to GH-Pages=<br />
<br />
This week we're looking at Continuous Integration with cloud services like Travis CI. We'll use Travis CI to setup automatic deployment of our Bridge Troll web app to GitHub's gh-pages hosting service.<br />
<br />
In this lab, you are asked to add automation and deployment configuration to your clone of bridge troll in order to learn how to use Travis CI for automatic deployment of code to the web. We'll also learn how to use GitHub for static hosting of web apps.<br />
<br />
==1. Update your Bridge Troll Fork==<br />
<br />
Make sure you're running the latest version of my repo. To do this, update your version like so:<br />
<br />
<code><br />
git fetch upstream<br />
git checkout -B master upstream/master<br />
</code><br />
<br />
This will download the latest commits from my upstream repo, and reset your <code>master</code> branch to be the same as mine.<br />
<br />
==2. Enable Traivs CI for your Fork==<br />
<br />
Everything you'll do in this lab will be done on your own personal fork (i.e., you aren't going to send me a pull request).<br />
<br />
First, login to travis-ci.org with your GitHub account.<br />
<br />
Second, enable your bridge-troll repo in the list of repos that Travis is connected to.<br />
<br />
==3. Add Deployment Step==<br />
<br />
In the <code>.travis.yml</code> file, you'll need to add steps for deployment to GH-Pages.<br />
<br />
Follow the instructions:<br />
<br />
* https://docs.travis-ci.com/user/deployment/<br />
* https://docs.travis-ci.com/user/deployment/pages/<br />
<br />
NOTE: you may need to alter the Travis build script in order to run <code>npm run build</code>. This creates the production <code>dist/</code> folder. For example, you might choose to do this during the [https://docs.travis-ci.com/user/customizing-the-build/#The-Build-Lifecycle before deploy] step.<br />
<br />
==4. Confirm Your Deploy==<br />
<br />
When you have successfully deployed to GH-Pages, you should be able to visit your gh-pages URL and see your code live on the web. See docs in https://help.github.com/categories/github-pages-basics/.<br />
<br />
==8. Submission==<br />
<br />
Submit a link to your forked repo's <code>.travis.yml</code> file, and also a link to your forked version of bridge troll running on gh-pages.<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! .travis.yml file (URL)<br />
! Bridge Troll on GH-Pages (URL)<br />
|-<br />
| 1<br />
| Hao Chen<br />
| https://github.com/haoRchen/bridge-troll/blob/master/.travis.yml<br />
| https://haorchen.github.io/bridge-troll/dist/index.html<br />
|-<br />
| 2<br />
| Owen Mak<br />
| https://github.com/Owen-Mak/bridge-troll/blob/gh-pages/.travis.yml <br />
| https://owen-mak.github.io/bridge-troll/dist/<br />
|-<br />
| 3<br />
|Hongcheng Zhang<br />
|https://github.com/StevenZhang123/bridge-troll/blob/gh-pages/.travis.yml<br />
|https://stevenzhang123.github.io/bridge-troll/dist/index.html<br />
|-<br />
| 4<br />
| Qiliang Chen<br />
| https://github.com/KignorChan/bridge-troll/blob/master/.travis.yml<br />
| https://kignorchan.github.io/bridge-troll/dist/<br />
|-<br />
| 5<br />
| Aaron Scott<br />
| https://github.com/ARDScott/bridge-troll/blob/master/.travis.yml<br />
| https://ardscott.github.io/bridge-troll/dist/<br />
|-<br />
| 6<br />
| Alex wang<br />
| https://github.com/AlexWang-16/bridge-troll/blob/gh-pages/.travis.yml<br />
| https://alexwang.ca/bridge-troll/dist/<br />
|-<br />
| 7<br />
| Lucas Verbeke<br />
| https://github.com/Micluc/bridge-troll/blob/master/.travis.yml<br />
| https://micluc.github.io/bridge-troll/dist/<br />
|-<br />
| 8<br />
| Yalong Li<br />
| https://github.com/yalooong/bridge-troll/blob/master/.travis.yml<br />
| https://yalooong.github.io/bridge-troll/dist/<br />
|-<br />
| 9<br />
| Matthew Quan<br />
| https://github.com/irrationalRock/bridge-troll/blob/master/.travis.yml<br />
| https://irrationalrock.github.io/bridge-troll/dist/<br />
|-<br />
| 10<br />
| Kelvin Cho<br />
| https://github.com/TheKinshu/bridge-troll/blob/master/.travis.yml<br />
| https://thekinshu.github.io/bridge-troll/dist/<br />
|-<br />
| 11<br />
| Vimal Raghubir<br />
| https://github.com/Vimal-Raghubir/bridge-troll/blob/master/.travis.yml<br />
| https://vimal-raghubir.github.io/bridge-troll/dist/<br />
|-<br />
| 12<br />
| Michael Fainshtein<br />
| https://github.com/mfainshtein2/bridge-troll/blob/master/.travis.yml<br />
| https://mfainshtein2.github.io/bridge-troll/dist/<br />
|-<br />
| 13<br />
| Aleksey Glazkov<br />
| https://github.com/alexglazkov9/bridge-troll/blob/master/.travis.yml<br />
| https://alexglazkov9.github.io/bridge-troll/dist/<br />
|-<br />
| 14<br />
| Zhihao Cai<br />
| https://github.com/josechoy/bridge-troll/blob/master/.travis.yml<br />
| https://josechoy.github.io/bridge-troll/dist/index.html<br />
|-<br />
| 15<br />
| Abdul Kabia<br />
| https://github.com/AbdulKabia/bridge-troll/blob/master/.travis.yml<br />
| https://abdulkabia.github.io/bridge-troll/dist/index.html<br />
|-<br />
| 16<br />
| Bakytzhan Apetov<br />
| https://github.com/apetov/bridge-troll/blob/master/.travis.yml<br />
| https://apetov.github.io/bridge-troll/dist/index.html<br />
|-<br />
| 17<br />
| Joseph Pham<br />
| https://github.com/jpham14/bridge-troll/blob/master/.travis.yml<br />
| https://jpham14.github.io/bridge-troll/dist/index.html<br />
|-<br />
| 18<br />
| Zukhruf Khan<br />
| https://github.com/zeddkay/bridge-troll/blob/master/.travis.yml<br />
| https://zeddkay.github.io/bridge-troll/dist/<br />
|-<br />
| 19<br />
|Soutrik Barua<br />
|https://github.com/buttersnipps/bridge-troll/blob/master/.travis.yml<br />
|https://buttersnipps.github.io/bridge-troll/dist/<br />
|-<br />
| 20<br />
|Woodson Delhia<br />
|https://github.com/Woody88/bridge-troll/blob/master/.travis.yml<br />
|https://Woody88.github.io/bridge-troll/dist<br />
|-<br />
| 21<br />
|Kevin Pham<br />
|https://github.com/kqpham/bridge-troll/blob/master/.travis.yml<br />
|https://kqpham.github.io/bridge-troll/dist/<br />
|-<br />
| 22<br />
|Pranoy Santosh<br />
|https://github.com/pranoy10/bridge-troll/blob/master/.travis.yml<br />
|https://pranoy10.github.io/bridge-troll/dist/<br />
|-<br />
| 23<br />
|Patrick Godbout<br />
|https://github.com/PatMB30/bridge-troll/blob/master/.travis.yml<br />
|https://patmb30.github.io/bridge-troll/dist/<br />
|-<br />
| 24<br />
|Oleh Hodovaniuk<br />
|https://github.com/ohodovaniuk1/bridge-troll/blob/master/.travis.yml<br />
|https://ohodovaniuk1.github.io/bridge-troll/dist/<br />
|-<br />
| 25<br />
|Evan Davies<br />
|https://github.com/EmdaviesSeneca/bridge-troll/blob/master/.travis.yml<br />
|https://emdaviesseneca.github.io/bridge-troll/dist/<br />
|-<br />
| 26<br />
|Aliaksandr Ushakou<br />
|https://github.com/aushakou/bridge-troll/blob/master/.travis.yml<br />
|https://aushakou.github.io/bridge-troll/dist/<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD600_and_DPS909_Winter_2018_Lab_5&diff=133787OSD600 and DPS909 Winter 2018 Lab 52018-04-24T03:44:23Z<p>Aushakou: /* 2. Blog */</p>
<hr />
<div>=Mixing Open Data, Open Source, Open Assets=<br />
<br />
This week we're starting a case study looking at practical ways to use and mix open data sets, open source, and open assets. Along the way we're also exploring modern approaches to collaborative, modern JavaScript development.<br />
<br />
In this lab, you are asked to add a new feature to the project. The goals of the lab include:<br />
<br />
* Practice working on front-end JavaScript on GitHub<br />
* Gain experience using open source APIs and modules<br />
* Read and Write code written in modern JavaScript<br />
* Gain experience working with common collaborative tooling on GitHub<br />
<br />
==1. Feature Request==<br />
<br />
You are asked to implement a solution for the following Issue: https://github.com/humphd/bridge-troll/issues/6<br />
<br />
Please '''fork''' the https://github.com/humphd/bridge-troll repo and '''create a new branch''' named <code>issue-6</code>.<br />
<br />
Implement your fix on your <code>issue-6</code> branch, and then push to GitHub.<br />
<br />
==2. Blog==<br />
<br />
Write a blog post about your experience adding the feature. Here are some things to pay attention to as you work:<br />
<br />
* Did you run into any problems? How did you overcome them?<br />
* What did you need to learn in order to complete the work?<br />
* Talk about the technologies you used. What did you think of them? Were they easy to use? What did you like/dislike about them.<br />
* What does your fix look like (screenshots)?<br />
* What approach did you take to solving this?<br />
<br />
Please add a line for your blog and GitHub branch (with the commits for your fix) in the following table:<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! Git URL to Branch for Fix (URL)<br />
! Blog Post (URL)<br />
|-<br />
| 1<br />
| Woodson Delhia<br />
| https://github.com/Woody88/bridge-troll/tree/issue-6<br />
|<br />
|-<br />
| 2<br />
| Liam Newell<br />
| https://github.com/hibyguy/bridge-troll<br />
| http://liamnewell.me/blog/bugs/Lab-5-bridge-troll/<br />
|-<br />
| 3<br />
| Matthew Quan<br />
| https://github.com/irrationalRock/bridge-troll/tree/addDayNight<br />
| https://mattprogrammingblog.wordpress.com/2018/03/20/osd600-lab-5-doing-a-feature-request/<br />
|-<br />
| 4<br />
| Alex Wang<br />
| https://github.com/AlexWang-16/bridge-troll/tree/issue-6<br />
| https://alexopensource.wordpress.com/2018/03/18/bridge-troll-project-implement-dark-mode/<br />
|-<br />
| 5<br />
| Zhihao Cai<br />
| https://github.com/josechoy/bridge-troll/tree/issue-6<br />
| https://choyzhihao.wordpress.com/2018/03/19/play-with-front-end-javascript/<br />
|-<br />
| 6<br />
| Kelvin Cho<br />
| https://github.com/TheKinshu/bridge-troll/tree/issue-6<br />
| https://klvincho.wordpress.com/2018/03/19/bridge-troll-dark-mode-feature/<br />
|-<br />
| 7<br />
|Qiliang Chen<br />
|https://github.com/KignorChan/bridge-troll/tree/issue-6<br />
|https://qchen102.blogspot.ca/2018/03/lab-5-add-feature-in-existing-object.html<br />
|-<br />
| 8<br />
| Hao Chen<br />
| https://github.com/haoRchen/bridge-troll/tree/issue6<br />
| https://medium.com/haorc/the-troll-under-the-bridge-cf9e24686fc1<br />
|-<br />
| 9<br />
| Lucas Verbeke<br />
| https://github.com/Micluc/bridge-troll/tree/issue-6<br />
| https://thelucasexcerpt.wordpress.com/2018/03/22/osd600-lab-5-lucas-verbeke<br />
|-<br />
| 10<br />
|Hongcheng Zhang<br />
|https://github.com/StevenZhang123/bridge-troll/tree/issue-6<br />
|https://hongcheng1993.wordpress.com/2018/03/22/lab5/<br />
|-<br />
| 11<br />
|Jafar Frotan<br />
|https://github.com/humphd/bridge-troll/pull/25<br />
|https://medium.com/@jaf.frotan/toggle-night-and-day-for-bridge-troll-repository-760931968fe3<br />
|-<br />
| 12<br />
|Justin Vuu<br />
|https://github.com/jevuu/bridge-troll/tree/issue-6<br />
|https://justosd.wordpress.com/2018/03/23/osd600-lab-5-the-bridge-troll/<br />
|-<br />
| 13<br />
| Joseph Pham<br />
| https://github.com/jpham14/bridge-troll<br />
| https://jpham14.wordpress.com/2018/03/16/lab-5-bridge-troll/<br />
|-<br />
| 14<br />
| Yalong Li<br />
| https://github.com/humphd/bridge-troll/pull/26<br />
| https://yalongxyz.blogspot.ca/2018/03/osd-lab5-add-light-dark-mode-switches.html<br />
|-<br />
| 15<br />
| Zukhruf Khan<br />
| https://github.com/zeddkay/bridge-troll/tree/issue6<br />
| https://zedsdps909blog.wordpress.com/2018/03/26/trying-to-fix-another-issue/<br />
|-<br />
| 16<br />
| Abdul Kabia<br />
| https://github.com/AbdulKabia/bridge-troll/tree/Lab5-Fix<br />
| https://akkabia.wordpress.com/2018/03/28/light-vs-dark-the-epic-battle/<br />
|-<br />
| 17<br />
| Owen Mak<br />
| https://github.com/Owen-Mak/bridge-troll/tree/issue6<br />
| https://makowen.wordpress.com/2018/03/28/trolls-and-sunshine/<br />
|-<br />
| 18<br />
| Vimal Raghubir<br />
| https://github.com/Vimal-Raghubir/bridge-troll/tree/issue-6<br />
| https://medium.com/@vraghubir/bridge-troll-feature-addition-bfee973b344b<br />
|-<br />
| 19<br />
| Oleh Hodovaniuk<br />
| https://github.com/ohodovaniuk1/bridge-troll/tree/issue6<br />
| https://ohodovaniuk.wordpress.com/2018/03/27/lab-5-2/<br />
|-<br />
| 20<br />
| Bakytzhan Apetov<br />
| https://github.com/humphd/bridge-troll/pull/28<br />
| https://bapetov.wordpress.com/2018/03/31/lab-5-adding-automatic-switch-for-light-and-dark-map-modes/<br />
|-<br />
| 21<br />
|Evan Davies<br />
|https://github.com/EmdaviesSeneca/bridge-troll/tree/issue-6<br />
|http://openthoughtsopensource.blogspot.ca/2018/04/the-difference-is-like-day-and-night.html<br />
|-<br />
| 22<br />
| Aleksey Glazkov<br />
| https://github.com/alexglazkov9/bridge-troll/tree/issue-6<br />
| https://aglazkovblog.wordpress.com/2018/04/05/a-friendly-troll-that-lives-under-ontarios-bridges/<br />
|-<br />
| 23<br />
|Abel Inocencio<br />
|https://github.com/simon-inoc/bridge-troll/tree/issue-6<br />
|<br />
|-<br />
| 24<br />
|Soutrik Barua<br />
|https://github.com/buttersnipps/bridge-troll/tree/mini-map<br />
|http://soutrikbarua.blogspot.ca/2018/04/utilizing-leaflet-mini-map-library-in.html<br />
|-<br />
| 25<br />
|Kevin Pham<br />
|https://github.com/kqpham/bridge-troll/tree/issue-6<br />
|http://kqpham2.blogspot.ca/2018/04/lab-5-bridge-troll.html<br />
|-<br />
| 26<br />
|Pranoy Santosh<br />
|https://github.com/pranoy10/bridge-troll/tree/issue5<br />
|http://pranoydps909.blogspot.ca/2018/04/implementing-daynight-mode-in-bridge.html<br />
|-<br />
| 27<br />
|Michael Fainshtein<br />
|https://github.com/mfainshtein2/bridge-troll/tree/issue-6<br />
|https://moderatelyokaydeveloper.wordpress.com/2018/04/21/let-there-be-night-mode/<br />
|-<br />
| 28<br />
|Aliaksandr Ushakou<br />
|https://github.com/aushakou/bridge-troll/tree/issue-6<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.3&diff=133775OSD & DPS909 Winter 2018 Release 0.32018-04-24T01:49:55Z<p>Aushakou: /* 6. Submission */</p>
<hr />
<div>=0.3 Release=<br />
<br />
In this release, you are asked to continue your work contributing to real open source projects, and show a degree of growth in your approach and effectiveness. This release is due the week of '''April 23'''.<br />
<br />
==1. Picking a Possible Project(s)==<br />
<br />
You are free to work on the same project as 0.2, or choose a new one. Ideally, the work you did in 0.2 can be leveraged in 0.3, since you shouldn't need to start at square-one. However, if your project choice in 0.2 was not ideal, picking a new one could be a good move.<br />
<br />
==2. Growth==<br />
<br />
One of the goals of this course is to help you grow as a developer, in your professional practice, and in your own confidence through gaining real-world experience. As such, you are asked to explicitly define a set of goals for yourself that will define "growth" to you. Some suggestions to consider:<br />
<br />
* to work on a larger type of bug (e.g, not a "good first bug")<br />
* to work on more bugs than last time (maybe you did 1 bug last time, and now you'll tackle 2 or 3)<br />
* to add a feature to a project<br />
* to work in a particular technology that interests you, or use some language/framework/tool<br />
* to build your experience with a particular type of programming (e.g., writing tests, automation, etc)<br />
* to gain more experience in different areas of contribution (e.g., docs vs. tests vs. code)<br />
<br />
Each student can define their growth differently; but all must have an overarching set of goals in this release.<br />
<br />
==3. Find some Bugs to Fix==<br />
<br />
Once you've decided on your project, and decided on your plan for growth, it's time to pick some bugs to work on. Look in the project's '''Issues''' and perhaps talk to them on Slack/IRC or wherever they work, and find some possible bugs.<br />
<br />
Pick bugs that align with your chosen growth strategy, and will help you achieve your goal(s). Also, try to pick a bug (or bugs) you can accomplish in the time you have available. For example, if a bug is really small, consider fixing more than one. If a bug is really huge (adding a new feature), consider whether it's reasonable to do this during this first release, or if you should wait for the next. You can talk to your professor to get help.<br />
<br />
You are encouraged to work on any/all of the following:<br />
<br />
* Fixing code bugs<br />
* Writing documentation<br />
* Automating processes (e.g., build system work)<br />
* Localization, translation<br />
* Writing tests<br />
<br />
When you've decided on bug(s) to work on, please leave a comment in the bug(s) asking if it's OK for you to do this. Someone else might be working on it, the bug might not exist anymore, or there might be a better bug you can work on. Communicate with the project's community before you spend hours working on the wrong thing.<br />
<br />
==4. Submit Pull Request(s) and Fix Review Comments==<br />
<br />
Submit one or more Pull Requests in order to fix your bug(s). Make sure you follow the project's instructions carefully for submitting work--every project does this slightly differently. When in doubt, go look at other closed pull requests to see how they did things.<br />
<br />
When you get feedback, make sure you respond, and push more commits to fix any problems pointed out by your reviewer.<br />
<br />
==6. Submission==<br />
<br />
Please fill out the table below with all relevant links, including:<br />
<br />
* Your name and the name of the open source project you're working on<br />
* Links to all Pull Requests you make to the project on GitHub.<br />
* A final blog post describing everything you did. Make sure to include your chosen growth goals in your post, and how you met them via your contributions. Please include links to bugs, pull requests, and discuss what your bug was about, how you fixed it, what you learned, etc. Feel free to include screenshots, screencasts, video, or anything else you need to properly describe your work.<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Open Source Project<br />
! style="font-weight: bold;" | Pull Request(s) (GitHub URLs)<br />
! style="font-weight: bold;" | Final Blog Post (URL)<br />
|-<br />
| 1<br />
| Matthew Quan<br />
| network-pulse, devtools-core, foundation.mozilla.org, Selenium, VSCode<br />
| https://github.com/mozilla/network-pulse/pull/942, https://github.com/devtools-html/devtools-core/pull/1019, https://github.com/mozilla/foundation.mozilla.org/pull/1359, https://github.com/SeleniumHQ/selenium/pull/5691, https://github.com/Microsoft/vscode/pull/48406<br />
| https://mattprogrammingblog.wordpress.com/2018/04/24/osd600-release-3-the-end-is-the-beginning/, https://mattprogrammingblog.wordpress.com/2018/04/24/osd600-release-3-growth-goals/<br />
|-<br />
| 2<br />
| Justin Vuu<br />
| Brave<br />
| https://github.com/brave/browser-laptop/pull/13890, https://github.com/brave/browser-laptop/pull/13892<br />
| https://justosd.wordpress.com/2018/04/23/osd600-release-0-3/<br />
|-<br />
| 3<br />
| Yalong Li<br />
| devtools-html/debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6052<br />
| https://yalongxyz.blogspot.ca/2018/04/osd-release-03-final-post.html<br />
|-<br />
| 4<br />
| Hongcheng Zhang<br />
| science.mozilla.org ; moz-corsica ; kitsune<br />
| https://github.com/mozilla/science.mozilla.org/pull/662 ; https://github.com/mozilla/moz-corsica/pull/120; https://github.com/mozilla/kitsune/pull/3199 <br />
|https://hongcheng1993.wordpress.com/2018/04/23/osd600-release-3/<br />
|-<br />
| 5<br />
| Kelvin Cho<br />
| Brave-Browser<br />
| https://github.com/brave/browser-laptop/pull/13873<br />
| https://klvincho.wordpress.com/2018/04/22/osd600-release-0-3/<br />
|-<br />
| 6<br />
| Soutrik Barua<br />
| devtools-html/debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6039<br />
| https://soutrikbarua.blogspot.ca/2018/04/understanding-debuggerhtml-codebase.html<br />
|-<br />
| 7<br />
| Zukhruf Khan<br />
| R for Data Science Online Learning Community<br />
| https://github.com/rfordatascience/website/pull/30, https://github.com/rfordatascience/website/pull/31<br />
| https://zedsdps909blog.wordpress.com/2018/04/22/release-0-3-more-bugs-to-fix/<br />
|-<br />
| 8<br />
| Alex Wang<br />
| devtools-html/debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6058<br />
| https://wp.me/p9ApzU-3r<br />
|-<br />
| 9<br />
| Woodson Delhia<br />
| https://github.com/dmjio/miso<br />
| https://github.com/dmjio/miso/pull/409<br />
| https://woodsondelhia.wordpress.com/2018/04/23/open-source-release-0-3-miso-haskell-function-helper<br />
|-<br />
| 10<br />
| Owen Mak<br />
| VSCode and Brave browser-laptop<br />
| https://github.com/Microsoft/vscode/pull/48349/files, https://github.com/Microsoft/vscode/pull/48326<br />
| https://makowen.wordpress.com/2018/04/23/final-boss-release-0-3/<br />
|-<br />
| 11<br />
| Vimal Raghubir<br />
| Kubernetes Website<br />
| https://github.com/kubernetes/website/pull/8111, https://github.com/kubernetes/website/pull/8131<br />
| https://medium.com/@vraghubir/fixing-bugs-in-kubernetes-website-8093da193899<br />
|-<br />
| 12<br />
| Oleh Hodovaniuk<br />
| Firefox Focus (Android)<br />
| https://github.com/mozilla-mobile/focus-android/pull/2502 <br />
| https://ohodovaniuk.wordpress.com/2018/04/12/osd600-release-3/<br />
|-<br />
| 13<br />
| Pranoy Santosh<br />
| debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6054<br />
| http://pranoydps909.blogspot.ca/2018/04/release-03-bug-fix.html<br />
|-<br />
| 14<br />
| Patrick Godbout<br />
| Brave browser-laptop<br />
| https://github.com/brave/browser-laptop/pull/13908<br />
| https://mb30myopensourceblog.blogspot.ca/2018/04/dps909-release-03-my-second-open-source.html<br />
|-<br />
| 15<br />
| Evan Davies<br />
| Debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6060<br />
|<br />
|-<br />
| 16<br />
|Jafar Frotan<br />
|Brave browser-laptop<br />
|https://github.com/brave/browser-laptop/pull/13888<br />
|https://medium.com/@jaf.frotan/release-0-3-17f744bb388f<br />
|-<br />
| 17<br />
| Abdul Kabia<br />
| fireside<br />
| https://github.com/marcobeltempo/fileside/pull/15<br />
| https://akkabia.wordpress.com/2018/04/23/on-the-fileside-of-things/<br />
|-<br />
| 18<br />
| Bakytzhan Apetov<br />
| devtools-html/perf.html<br />
| https://github.com/devtools-html/perf.html/pull/956<br />
|<br />
|-<br />
| 19<br />
| Joseph Pham<br />
| Firefox Screenshots<br />
| https://github.com/mozilla-services/screenshots/pull/4353, https://github.com/mozilla-services/screenshots/pull/4359<br />
| https://jpham14.wordpress.com/2018/04/23/osd600-final-release/<br />
|-<br />
| 20<br />
| Zhihao Cai<br />
| Mozilla<br />
| https://github.com/mozilla/blurts-server/pull/87, https://github.com/mozilla/kitsune/pull/3198, https://github.com/mozilla-services/screenshots/pull/4356<br />
|<br />
|-<br />
| 21<br />
| Qiliang Chen<br />
| Leafpic<br />
| https://github.com/HoraApps/LeafPic/pull/551<br />
|<br />
|-<br />
| 22<br />
| Aliaksandr Ushakou<br />
| Brave<br />
| https://github.com/brave/browser-laptop/pull/13915<br />
| https://aushakou.wordpress.com/2018/04/24/release-0-3/<br />
|-<br />
| 23<br />
| Kevin Pham<br />
| <br />
| http://kqpham2.blogspot.ca/2018/04/open-source-assignment-3.html<br />
|<br />
|-<br />
| 24<br />
| Hao Ran Chen<br />
| debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/5742, https://github.com/devtools-html/debugger.html/pull/6053<br />
| https://medium.com/haorc/default-behavior-6bd2f2ea2c0e, https://medium.com/haorc/tricky-javascript-with-a-sprinkle-of-react-12820e1d2fc6<br />
|-<br />
| 25<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 26<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.3&diff=133753OSD & DPS909 Winter 2018 Release 0.32018-04-24T00:16:24Z<p>Aushakou: /* 6. Submission */</p>
<hr />
<div>=0.3 Release=<br />
<br />
In this release, you are asked to continue your work contributing to real open source projects, and show a degree of growth in your approach and effectiveness. This release is due the week of '''April 23'''.<br />
<br />
==1. Picking a Possible Project(s)==<br />
<br />
You are free to work on the same project as 0.2, or choose a new one. Ideally, the work you did in 0.2 can be leveraged in 0.3, since you shouldn't need to start at square-one. However, if your project choice in 0.2 was not ideal, picking a new one could be a good move.<br />
<br />
==2. Growth==<br />
<br />
One of the goals of this course is to help you grow as a developer, in your professional practice, and in your own confidence through gaining real-world experience. As such, you are asked to explicitly define a set of goals for yourself that will define "growth" to you. Some suggestions to consider:<br />
<br />
* to work on a larger type of bug (e.g, not a "good first bug")<br />
* to work on more bugs than last time (maybe you did 1 bug last time, and now you'll tackle 2 or 3)<br />
* to add a feature to a project<br />
* to work in a particular technology that interests you, or use some language/framework/tool<br />
* to build your experience with a particular type of programming (e.g., writing tests, automation, etc)<br />
* to gain more experience in different areas of contribution (e.g., docs vs. tests vs. code)<br />
<br />
Each student can define their growth differently; but all must have an overarching set of goals in this release.<br />
<br />
==3. Find some Bugs to Fix==<br />
<br />
Once you've decided on your project, and decided on your plan for growth, it's time to pick some bugs to work on. Look in the project's '''Issues''' and perhaps talk to them on Slack/IRC or wherever they work, and find some possible bugs.<br />
<br />
Pick bugs that align with your chosen growth strategy, and will help you achieve your goal(s). Also, try to pick a bug (or bugs) you can accomplish in the time you have available. For example, if a bug is really small, consider fixing more than one. If a bug is really huge (adding a new feature), consider whether it's reasonable to do this during this first release, or if you should wait for the next. You can talk to your professor to get help.<br />
<br />
You are encouraged to work on any/all of the following:<br />
<br />
* Fixing code bugs<br />
* Writing documentation<br />
* Automating processes (e.g., build system work)<br />
* Localization, translation<br />
* Writing tests<br />
<br />
When you've decided on bug(s) to work on, please leave a comment in the bug(s) asking if it's OK for you to do this. Someone else might be working on it, the bug might not exist anymore, or there might be a better bug you can work on. Communicate with the project's community before you spend hours working on the wrong thing.<br />
<br />
==4. Submit Pull Request(s) and Fix Review Comments==<br />
<br />
Submit one or more Pull Requests in order to fix your bug(s). Make sure you follow the project's instructions carefully for submitting work--every project does this slightly differently. When in doubt, go look at other closed pull requests to see how they did things.<br />
<br />
When you get feedback, make sure you respond, and push more commits to fix any problems pointed out by your reviewer.<br />
<br />
==6. Submission==<br />
<br />
Please fill out the table below with all relevant links, including:<br />
<br />
* Your name and the name of the open source project you're working on<br />
* Links to all Pull Requests you make to the project on GitHub.<br />
* A final blog post describing everything you did. Make sure to include your chosen growth goals in your post, and how you met them via your contributions. Please include links to bugs, pull requests, and discuss what your bug was about, how you fixed it, what you learned, etc. Feel free to include screenshots, screencasts, video, or anything else you need to properly describe your work.<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Open Source Project<br />
! style="font-weight: bold;" | Pull Request(s) (GitHub URLs)<br />
! style="font-weight: bold;" | Final Blog Post (URL)<br />
|-<br />
| 1<br />
| Matthew Quan<br />
| network-pulse, devtools-core, foundation.mozilla.org, Selenium, VSCode<br />
| https://github.com/mozilla/network-pulse/pull/942, https://github.com/devtools-html/devtools-core/pull/1019, https://github.com/mozilla/foundation.mozilla.org/pull/1359, https://github.com/SeleniumHQ/selenium/pull/5691, https://github.com/Microsoft/vscode/pull/48406<br />
|<br />
|-<br />
| 2<br />
| Justin Vuu<br />
| Brave<br />
| https://github.com/brave/browser-laptop/pull/13890, https://github.com/brave/browser-laptop/pull/13892<br />
| https://justosd.wordpress.com/2018/04/23/osd600-release-0-3/<br />
|-<br />
| 3<br />
| Yalong Li<br />
| devtools-html/debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6052<br />
| https://yalongxyz.blogspot.ca/2018/04/osd-release-03-final-post.html<br />
|-<br />
| 4<br />
| Hongcheng Zhang<br />
| science.mozilla.org ; moz-corsica ; kitsune<br />
| https://github.com/mozilla/science.mozilla.org/pull/662 ; https://github.com/mozilla/moz-corsica/pull/120; https://github.com/mozilla/kitsune/pull/3199 <br />
|https://hongcheng1993.wordpress.com/2018/04/23/osd600-release-3/<br />
|-<br />
| 5<br />
| Kelvin Cho<br />
| Brave-Browser<br />
| https://github.com/brave/browser-laptop/pull/13873<br />
|<br />
|-<br />
| 6<br />
| Soutrik Barua<br />
| devtools-html/debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6039<br />
| https://soutrikbarua.blogspot.ca/2018/04/understanding-debuggerhtml-codebase.html<br />
|-<br />
| 7<br />
| Zukhruf Khan<br />
| R for Data Science Online Learning Community<br />
| https://github.com/rfordatascience/website/pull/30, https://github.com/rfordatascience/website/pull/31<br />
| https://zedsdps909blog.wordpress.com/2018/04/22/release-0-3-more-bugs-to-fix/<br />
|-<br />
| 8<br />
| Alex Wang<br />
| devtools-html/debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6058<br />
| https://wp.me/p9ApzU-3r<br />
|-<br />
| 9<br />
| Woodson Delhia<br />
| https://github.com/dmjio/miso<br />
| https://github.com/dmjio/miso/pull/409<br />
| https://woodsondelhia.wordpress.com/2018/04/23/open-source-release-0-3-miso-haskell-function-helper<br />
|-<br />
| 10<br />
| Owen Mak<br />
| VSCode and Brave browser-laptop<br />
| https://github.com/Microsoft/vscode/pull/48349/files, https://github.com/Microsoft/vscode/pull/48326<br />
| https://makowen.wordpress.com/2018/04/23/final-boss-release-0-3/<br />
|-<br />
| 11<br />
| Vimal Raghubir<br />
| Kubernetes Website<br />
| https://github.com/kubernetes/website/pull/8111, https://github.com/kubernetes/website/pull/8131<br />
| https://medium.com/@vraghubir/fixing-bugs-in-kubernetes-website-8093da193899<br />
|-<br />
| 12<br />
| Oleh Hodovaniuk<br />
| Firefox Focus (Android)<br />
| https://github.com/mozilla-mobile/focus-android/pull/2502 <br />
| https://ohodovaniuk.wordpress.com/2018/04/12/osd600-release-3/<br />
|-<br />
| 13<br />
| Pranoy Santosh<br />
| debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6054<br />
| http://pranoydps909.blogspot.ca/2018/04/release-03-bug-fix.html<br />
|-<br />
| 14<br />
| Patrick Godbout<br />
| Brave browser-laptop<br />
| https://github.com/brave/browser-laptop/pull/13908<br />
| https://mb30myopensourceblog.blogspot.ca/2018/04/dps909-release-03-my-second-open-source.html<br />
|-<br />
| 15<br />
| Evan Davies<br />
| Debugger.html<br />
| https://github.com/devtools-html/debugger.html/pull/6060<br />
|<br />
|-<br />
| 16<br />
|Jafar Frotan<br />
|Brave browser-laptop<br />
|https://github.com/brave/browser-laptop/pull/13888<br />
|https://medium.com/@jaf.frotan/release-0-3-17f744bb388f<br />
|-<br />
| 17<br />
| Abdul Kabia<br />
| fileside<br />
| https://github.com/marcobeltempo/fileside/pull/15<br />
| https://akkabia.wordpress.com/2018/04/23/on-the-fileside-of-things/<br />
|-<br />
| 18<br />
| Bakytzhan Apetov<br />
| devtools-html/perf.html<br />
| https://github.com/devtools-html/perf.html/pull/956<br />
|<br />
|-<br />
| 19<br />
| Joseph Pham<br />
| Firefox Screenshots<br />
| https://github.com/mozilla-services/screenshots/pull/4353, https://github.com/mozilla-services/screenshots/pull/4359<br />
| https://jpham14.wordpress.com/2018/04/23/osd600-final-release/<br />
|-<br />
| 20<br />
| Zhihao Cai<br />
| Mozilla<br />
| https://github.com/mozilla/blurts-server/pull/87, https://github.com/mozilla/kitsune/pull/3198, https://github.com/mozilla-services/screenshots/pull/4356<br />
|<br />
|-<br />
| 21<br />
| Qiliang Chen<br />
| Leafpic<br />
| https://github.com/HoraApps/LeafPic/pull/551<br />
|<br />
|-<br />
| 22<br />
| Aliaksandr Ushakou<br />
| Brave<br />
| https://github.com/brave/browser-laptop/pull/13915<br />
|<br />
|-<br />
| 23<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 24<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 25<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 26<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD600_and_DPS909_Winter_2018_Lab_4&diff=133708OSD600 and DPS909 Winter 2018 Lab 42018-04-23T05:25:51Z<p>Aushakou: /* 3. Blog */</p>
<hr />
<div>=Contributing to Open Standards=<br />
<br />
This week we're discussing open standards, and for our lab will try writing some tests for the JavaScript (ecmascript) standard.<br />
<br />
In order for implementors of the standard to know if they've got any bugs, a comprehensive set of tests are necessary. These tests should be something that can be run by any and all JavaScript implementations (i.e., we don't Microsoft to have their tests, Google to have their tests, Mozilla to have their tests, etc. and not share with each other). JavaScript should work the same everywhere, no matter which implementation you us.<br />
<br />
In this Lab you will gain experience doing the following:<br />
<br />
* reading a language standard<br />
* running a test suite<br />
* identifying testable aspects of the standard<br />
* writing tests<br />
* sharing work using gist.github.com<br />
<br />
==1. Running the Test Suite==<br />
<br />
The language is specified in https://tc39.github.io/ecma262/, and its test suite is available at https://github.com/tc39/test262.<br />
<br />
To run the tests on your computer using node.js, follow the steps listed in https://github.com/bterlson/test262-harness#test262-harness.<br />
<br />
When you run the tests, do all the tests pass or do any of them fail for you?<br />
<br />
==2. Become Familiar with Tests==<br />
<br />
Read the docs at https://github.com/tc39/test262/blob/master/CONTRIBUTING.md, which cover things like [https://github.com/tc39/test262/blob/master/CONTRIBUTING.md#test-case-names naming], [https://github.com/tc39/test262/blob/master/CONTRIBUTING.md#test-case-style general layout], [https://github.com/tc39/test262/blob/master/CONTRIBUTING.md#test-environment assertions], [https://github.com/tc39/test262/blob/master/CONTRIBUTING.md#handling-errors-and-negative-test-cases error handling], etc.<br />
<br />
Based on what you've just read, take a look at this test for [https://github.com/tc39/test262/blob/master/test/built-ins/String/prototype/toUpperCase/S15.5.4.18_A2_T1.js String.prototype.toUpperCase()]. See if you can make sense of the code and what it's testing.<br />
<br />
==3. Array.reverse==<br />
<br />
In JavaScript, Arrays can be reversed using the <code>reverse()</code> method. It is defined in the standard at https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.reverse. Begin by reading the definition of steps in the spec.<br />
<br />
What sort of things could you test with <code>Array.reverse</code>? Based on what you read above, what sort of things need to be true about how <code>Array.reverse</code> works? Try to write a few tests for things you just thought about, using what you learned in 2.<br />
<br />
To add a new test, you can create new <code>.js</code> files underneath <code>test/</code>.<br />
<br />
==4. Extending the Existing Tests== <br />
<br />
There are actually tests written now. You can see them in [https://github.com/tc39/test262/tree/a62da2b4997767a78bb2834c4fbf4e598b0fc241/test/built-ins/Array/prototype/reverse the Array.prototype.reverse() tests]<br />
<br />
There is a bug to improve these tests, based on things learned while writing the [https://github.com/tc39/test262/tree/a62da2b4997767a78bb2834c4fbf4e598b0fc241/test/built-ins/TypedArray/prototype/reverse TypedArray.prototype.reverse tests].<br />
<br />
Take a look at the code for the [https://github.com/tc39/test262/tree/a62da2b4997767a78bb2834c4fbf4e598b0fc241/test/built-ins/TypedArray/prototype/reverse TypedArray.prototype.reverse tests] and compare it to what is happening in the [https://github.com/tc39/test262/tree/a62da2b4997767a78bb2834c4fbf4e598b0fc241/test/built-ins/Array/prototype/reverse Array.prototype.reverse() tests].<br />
<br />
Can you figure out some things you could change (i.e., ideas to borrow from the other tests)? Try rewriting some of the tests for <code>Array.reverse</code> to do what you think might be better. <br />
<br />
NOTE: you do '''not''' need to submit your tests. This lab is only about reading the spec and existing tests, and understanding how they work.<br />
<br />
==3. Blog==<br />
<br />
Write a blog post about your experience reading the spec and tests and trying to write new tests. Put any code that you wrote into a [https://gist.github.com/ gist] on GitHub (i.e., you don't need to do a pull request or submit them anywhere).<br />
<br />
Please add a line for your blog in the following table:<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! Gist of test cases (URLs)<br />
! Blog Post (URL)<br />
|-<br />
| 1<br />
| Woodson Delhia<br />
| https://gist.github.com/Woody88/7295790410b01f6473f2e7ee502bc0c8<br />
|<br />
|-<br />
| 2<br />
| Hao Chen<br />
| https://gist.github.com/haoRchen/b3249dd14d7ced8fe11487304da335a8<br />
| https://medium.com/haorc/testing-with-javascript-3c6fe1b22d0d<br />
|-<br />
| 3<br />
| Matthew Quan<br />
| https://gist.github.com/irrationalRock/362826160d1646f69d274a3e729d5bb0#file-s15-4-4-8_a1_t1-js<br />
| https://mattprogrammingblog.wordpress.com/2018/03/13/osd600-lab4-looking-at-web-standards/<br />
|-<br />
| 4<br />
| Yuriy Kartuzov<br />
| https://gist.github.com/YuriyKartuzov/c195ed5cb2e09fdae4dfc2106995a604<br />
| https://yuriykartuzov.wordpress.com/2018/03/12/lab-4/<br />
|-<br />
| 5<br />
| Owen Mak<br />
| https://gist.github.com/Owen-Mak/569dd52440e48192a5edab013f0228e4<br />
| https://makowen.wordpress.com/2018/03/13/side-quest-2-ecma-and-unit-tests/<br />
|-<br />
| 6<br />
| Jafar Frotan<br />
| https://gist.github.com/a-one-d-one/913f5830b5bbfb1c7b6abf37eed79100<br />
| https://medium.com/@jaf.frotan/innovation-adhering-to-standards-and-diving-into-testing-bfcc9d8aa5b7<br />
|-<br />
| 7<br />
| Pranoy Santosh<br />
| https://gist.github.com/pranoy10/10fd4bbf04a7490567d527017c8d52df<br />
| http://pranoydps909.blogspot.ca/2018/04/ecma-script-testing.html<br />
|-<br />
| 8<br />
| Kevin Pham<br />
| https://gist.github.com/kqpham/65891808231e9bfb1d7182d5800b0002<br />
|<br />
|-<br />
| 9<br />
| Zhihao Cai<br />
| https://gist.github.com/josechoy/0b396ef5609ee2e13c4057f81eb5b9b2<br />
| https://choyzhihao.wordpress.com/2018/03/14/get-familiar-with-javascript-standard/<br />
|-<br />
| 10<br />
| Alex Wang<br />
| https://gist.github.com/AlexWang-16/5991e9e7cf9b526cd7cab0b4a069a36a<br />
| https://alexopensource.wordpress.com/2018/03/15/learning-and-working-with-emcascript-standardization-tests/<br />
|-<br />
| 11<br />
| Oleh Hodovaniuk<br />
| https://gist.github.com/ohodovaniuk1/f5f68bca012f9d3b222bd24f0b4252db<br />
| https://ohodovaniuk.wordpress.com/2018/03/13/osd600-lab-4/<br />
|-<br />
| 12<br />
| Qiliang Chen<br />
| https://gist.github.com/KignorChan/e82a9a597e2a02115238227e911ff1b5<br />
| https://qchen102.blogspot.ca/2018/03/studying-for-open-standard.html<br />
|-<br />
| 13<br />
| Bakytzhan Apetov<br />
| https://gist.github.com/apetov/bc60c73a584c2205cc498fe06f295ec3<br />
| https://bapetov.wordpress.com/2018/03/15/lab-4-running-tests/<br />
|-<br />
| 14<br />
| Hongcheng Zhang<br />
| https://gist.github.com/StevenZhang123/bd6697f51205954323895994927c7fd3<br />
| https://hongcheng1993.wordpress.com/2018/03/15/lab4-osd/<br />
|-<br />
| 15<br />
| Patrick Godbout<br />
| https://gist.github.com/PatMB30/7a483999a2986b8358c4155d74c587e8<br />
| https://mb30myopensourceblog.blogspot.ca/2018/03/running-test-suites-and-playing-with.html<br />
|-<br />
| 16<br />
| Justin Vuu<br />
| https://gist.github.com/jevuu/552694721103f4e39304fbd33e9f1287<br />
| https://justosd.wordpress.com/2018/03/16/osd600-lab-4-contributing-to-open-standards/<br />
|-<br />
| 17<br />
| Joseph Pham<br />
| https://gist.github.com/jpham14/24c5772b69e72dafadd1fb126031a739<br />
| https://jpham14.wordpress.com/2018/03/16/lab-4-contributing-to-open-standards/<br />
|-<br />
| 18<br />
| Yalong Li<br />
| https://gist.github.com/yalooong/16fd3eaa19584fe4ad13e1f241f1e3e0<br />
| https://yalongxyz.blogspot.ca/2018/03/ecmascript-test-suite-create-reverse.html<br />
|-<br />
| 19<br />
| Liam Newell<br />
| https://gist.github.com/hibyguy/836dd91212be43a73334a6d7d51eaca3<br />
| http://liamnewell.me/blog/bugs/Lab4/<br />
|-<br />
| 20<br />
| Aliaksandr Ushakou<br />
| https://gist.github.com/aushakou/9e35a93b20a82208c58aa12a3da71dd2<br />
| https://aushakou.wordpress.com/2018/04/23/a-first-glance-at-open-standards/<br />
|-<br />
| 21<br />
|Soutrik Barua<br />
|https://gist.github.com/buttersnipps/be6961429e8091b8e4af6c78a3d981a0<br />
|http://soutrikbarua.blogspot.ca/2018/03/testing-in-open-source-projects.html<br />
|-<br />
| 22<br />
|Abdul Kabia<br />
|https://gist.github.com/AbdulKabia/d5d9dddb14b9eb91cfb8e9af6b4c5afe<br />
|https://akkabia.wordpress.com/2018/03/24/play-that-ht-back/<br />
|-<br />
| 23<br />
|Lucas Verbeke<br />
|https://gist.github.com/Micluc/af61e5313e2521533f8c79c320f70898<br />
|https://thelucasexcerpt.wordpress.com/2018/03/25/osd600-lab-4-lucas-verbeke<br />
|-<br />
| 24<br />
|Kelvin Cho<br />
|https://gist.github.com/TheKinshu/abb1becaa1c4547b65f79e5244bfccbf<br />
|https://klvincho.wordpress.com/2018/03/25/lab4-messing-around-with-tests/<br />
|-<br />
| 25<br />
|Zukhruf Khan<br />
|https://gist.github.com/zeddkay/8de670467d3f4109d426424ee534a30d<br />
|https://zedsdps909blog.wordpress.com/2018/03/25/open-standards-and-tests/<br />
|-<br />
| 26<br />
|Abel Inocencio<br />
|https://gist.github.com/simon-inoc/8963b7d7372bef04651d4389ce1dfaf1<br />
|https://haxbyte.wordpress.com/2018/03/26/lab-4-getting-a-feel-of-testing/<br />
|-<br />
| 27<br />
|Vimal Raghubir<br />
|https://gist.github.com/Vimal-Raghubir/f1d1f512d1e81ed987e277ce388ceb76<br />
|https://medium.com/@vraghubir/ecmascript-and-test-suites-6c3c892e9341<br />
|-<br />
| 28<br />
|Evan Davies<br />
|https://gist.github.com/EmdaviesSeneca/f36f80958c3f24386f2d7d7a88036ca1<br />
|http://openthoughtsopensource.blogspot.ca/2018/03/testing-testing-123.html<br />
|-<br />
| 29<br />
|Aleksey Glazkov<br />
|https://gist.github.com/alexglazkov9/8a66907939cedf0e5365fe736210a919<br />
|https://aglazkovblog.wordpress.com/2018/04/12/open-standards-and-javascript-tests/<br />
|-<br />
| 30<br />
|Michael Fainshtein<br />
|https://gist.github.com/mfainshtein2/26651032e9d1938bc39e3ff6cebf1dfb<br />
|https://moderatelyokaydeveloper.wordpress.com/2018/04/21/standards-for-automated-testing/<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.2&diff=133365OSD & DPS909 Winter 2018 Release 0.22018-04-11T08:34:54Z<p>Aushakou: /* 6. Submission */</p>
<hr />
<div>=0.2 Release=<br />
<br />
In this release, you are asked to contribute to a real open source project. This release is due '''Monday March 26'''.<br />
<br />
Below you will find a suggested set of projects and tools to consider, as well as links to possible ''Good First Bugs''. You are free to work on other products/tools/bugs besides those listed below, as long as you talk to your professor first.<br />
<br />
Completing this release is a multi-step process, with various deliverables. Please read all instructions carefully so you don't miss any steps.<br />
<br />
==1. Pick a Possible Project(s)==<br />
<br />
Your first step is to research and find a suitable open source project on GitHub. Once you've chosen a project, add it to the table at the bottom, along with your name. This will help other students find you, if they are also working on the same code.<br />
<br />
Important things to consider:<br />
<br />
* Make sure the project is still active. Many projects on GitHub are no longer being developed.<br />
* Try to find larger projects with many contributors vs. small projects, or those with only a small number of contributors. It is difficult to get help, feedback, or traction in small projects.<br />
* Try to find a project with a wide variety of bugs to work on. Projects with only a few issues filed are less likely to be good places to find contributions.<br />
* Look for signals in <code>CONTRIBUTING.md</code> and <code>README.md</code> files that a project is open to contributors.<br />
* Pick a project that uses technologies you are interested in learning, or already know well. Don't pick a project that uses things you dislike.<br />
* Consider picking a project you use yourself, something you love, and/or something you would be proud to say you worked on.<br />
<br />
Here are some projects and areas to consider:<br />
<br />
* [https://github.com/trending GitHub's Trending projects] - you can see which projects are trending on GitHub, and maybe find one that would be interesting to you. Try limiting the language to one you want to work in (e.g., JavaScript).<br />
* [https://github.com/explore GitHub Explore] - list of many projects categorized into topics. Maybe you'll find one that you like there.<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction Mozilla] - you could work on Firefox or any number of other Mozilla projects. Mozilla uses C/C++, JS, HTML, Python, etc. There are literally thousands of ways to get involved.<br />
* [https://github.com/Microsoft/vscode Visual Studio Code] (Electron, TypeScrypt, JS, CSS, React)<br />
* [https://github.com/Brave Brave] - you could work on the Brave web browser for [https://github.com/brave/browser-laptop desktop], [https://github.com/brave/browser-android-tabs Android], or [https://github.com/brave/browser-ios iOS]<br />
* [https://datproject.org/ DAT Project] - p2p web technology, including the [https://beakerbrowser.com/ Beaker Browser]<br />
* [https://github.com/tensorflow/tensorflow Tensorflow] or [https://github.com/PAIR-code/deeplearnjs DeepLearn.js] or any number of other [https://github.com/topics/deep-learning Machine Learning/AI frameworks].<br />
* [https://github.com/topics/bitcoin Bitcoin] or [https://github.com/topics/etherium Etherium] or other [https://github.com/topics/cryptocurrency cryptocurrency/blockchain projects].<br />
* [https://github.com/topics/database Databases] - there are hundreds of open source database projects, libraries, and tools<br />
* [https://github.com/topics/docker Docker] and other container technology is hot right now<br />
* [https://github.com/topics/game-engine Game Engines] - many are open source and have ways to get involved<br />
* [https://github.com/topics/nodejs Node.js] is a huge ecosystem, with thousands of sub-projects, modules, and tools that need help.<br />
* [https://github.com/mozilla/activity-stream Firefox Activity Stream] (JS, CSS, React) [https://github.com/mozilla/activity-stream#for-developers dev docs] [https://github.com/mozilla/activity-stream/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+bug%22 "Good first bug"]<br />
* [http://firefox-dev.tools/debugger.html/ Firefox JavaScript Debugger] (React, JS) [https://t.co/4ewG5n9Q8D bugs], [https://t.co/LHCPAxhgVS more bugs].<br />
* [https://pontoon.mozilla.org/ Pontoon localization tool] (Python, JS, HTML5) [https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Pontoon&resolution=---&list_id=10786825 unedited bug list]<br />
* [https://www.rust-lang.org Rust] (programming language, sites, and project) [https://www.rust-lang.org/en-US/contribute.html contribute docs], [https://github.com/rust-lang/rust/labels/E-easy "easy" bugs], [https://github.com/rust-lang/crates.io/issues?q=is%3Aissue+is%3Aopen+label%3AE-easy Crates.io package manager "easy" bugs], [https://www.rustaceans.org/findwork other ideas for contributing to Rust and tooling]<br />
* [https://addons.mozilla.org/ Addons Server] (Python/Django Server and API) [https://github.com/mozilla/addons-server/labels/contrib%3A%20good%20first%20bug "good first bug"]<br />
<br />
Spend some time looking at these projects and find something that fits your skills, interests, and goals. Fixing bugs in a big project is hard, so it's wise to pick something you will enjoy and succeed at doing.<br />
<br />
==2. Subscribe to your chosen Project(s)==<br />
<br />
Once you've chosen a project or two, spend some time "lurking" in it so you can get a sense of how things work. Before you dive into picking and fixing bugs, it's a good idea to observe how the project works, what areas are being worked on, what the priorities are, which tools/workflows are being used, etc. Here are a few ways you can accomplish this:<br />
<br />
* '''Read''' the project's documentation (website, README, Contributing, Code of Conduct, etc)<br />
* '''Watch''' the [https://help.github.com/articles/watching-and-unwatching-repositories/#watching-a-single-repository project's repository on GitHub] to get email when people file/respond to bugs. NOTE: you might want to setup an inbox filter, as you'll likely get a lot of email when you do this.<br />
* '''Join''' the project's discussion channels. This might be Slack, IRC, or some other tool. It's normal to join channels and not say anything, just "listen," so don't feel weird doing it. You'll learn a lot by watching how they work. When you feel comfortable, introduce yourself and let them know you'd like to contribute.<br />
<br />
After you've spent some time doing this, '''write a blog post introducing the project'''. Here are things to cover:<br />
<br />
* What is the project about?<br />
* Where is the code located?<br />
* Where are their docs?<br />
* How can you get involved?<br />
* Where can you go to get help?<br />
* What are some interesting things you've learned while observing the project (e.g., pull requests fixing bugs, adding features, discussions)?<br />
<br />
==3. Find some Bugs to Fix==<br />
<br />
Once you've found a project you like, and are happy to get involved, it's time to find some bugs to work on. Look in their '''Issues''' and perhaps talk to them on Slack/IRC or wherever they work, and find some possible bugs. Consider looking for issues with labels like '''good-first-bug''', '''bug''', '''help wanted''', etc.<br />
<br />
Try to pick a bug (or bugs) you can accomplish in the time you have available. For example, if a bug is really small, consider fixing more than one. If a bug is really huge (adding a new feature), consider whether it's reasonable to do this during this first release, or if you should wait for the next. You can talk to your professor to get help.<br />
<br />
You are encouraged to work on any/all of the following:<br />
<br />
* Fixing code bugs<br />
* Writing documentation<br />
* Automating processes (e.g., build system work)<br />
* Localization, translation<br />
* Writing tests<br />
<br />
When you've decided on bug(s) to work on, please leave a comment in the bug(s) asking if it's OK for you to do this. Someone else might be working on it, the bug might not exist anymore, or there might be a better bug you can work on. Communicate with the project's community before you spend hours working on the wrong thing.<br />
<br />
==4. Submit Pull Request(s) and Fix Review Comments==<br />
<br />
Submit one or more Pull Requests in order to fix your bug(s). Make sure you follow the project's instructions carefully for submitting work--every project does this slightly differently. When in doubt, go look at other closed pull requests to see how they did things.<br />
<br />
When you get feedback, make sure you respond, and push more commits to fix any problems pointed out by your reviewer.<br />
<br />
==5. FAQ==<br />
<br />
* Can I start my own open source project and work on that? No. This project is about contributing to existing, large, open source projects, which involves learning many skills, tools, and processes that will be valuable to you in your career as a developer.<br />
<br />
* Can I work with a partner, or in a group? No. You can collaborate with others in the course on your bug(s), but you need to "own" your own bug, and do the work yourself. Having people give you advice or help, and doing the same for others, is fine. However, "help" doesn't mean one person does it all.<br />
<br />
* Can I work on something I don't know (e.g., Rust, Firefox, ...)? Yes. As long as you're willing to push yourself to learn what you need to know, you can do it. You have 4 weeks to accomplish this, which is lots of time to research, learn, fail, and succeed.<br />
<br />
* What if I write a fix and the project rejects it, will I still get marks? Yes. You will be marked on the process, how you work, and what you create. Mozilla will almost certainly reject your first attempt in code review, and offer comments on what to fix. It might take a few rounds of review/re-submission for you to get your bug(s) finished. That's normal.<br />
<br />
* When should I start working on my bug? Now. Fixing a bug in a large code base you don't know takes lots of time. You have lots of time (1 month), don't waste it. Work on your bug every few days for a short amount of time; don't leave it until a few days before it's due.<br />
<br />
* What do I do if someone else is already working on a bug? What if someone else also wants to work on a bug? You need to communicate your intent to work on something. Leave a comment in a bug, and let people know you are interested in working on it. If someone else is working on it, but hasn't made progress in a long time, you can leave a polite question asking if it's OK for you to take it over. If another student also wants to work on a bug, come see your professor for help finding another suitable issue.<br />
<br />
==6. Submission==<br />
<br />
Please fill out the table below with all relevant links, including:<br />
<br />
* Your name and the name of the open source project you're working on<br />
* An introductory blog post for your chosen project. See section 2. above for details.<br />
* Links to all Pull Requests you make to the project on GitHub.<br />
* A final blog post describing everything you did. Please include links to bugs, pull requests, and discuss what your bug was about, how you fixed it, what you learned, etc. Feel free to include screenshots, screencasts, video, or anything else you need to properly describe your work.<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Open Source Project<br />
! style="font-weight: bold;" | Project Intro Blog (URL)<br />
! style="font-weight: bold;" | Pull Request(s) (GitHub URLs)<br />
! style="font-weight: bold;" | Final Blog Post (URL)<br />
|-<br />
| 1<br />
| Matthew Quan<br />
| VSCode, Brave (browser-laptop), bridge-troll<br />
| https://mattprogrammingblog.wordpress.com/2018/03/09/osd600-release-0-2-part-1-working-with-vscode/<br />
| https://github.com/brave/browser-laptop/pull/13386, https://github.com/Microsoft/vscode/pull/43950, https://github.com/Microsoft/vscode-docs/pull/1487, https://github.com/humphd/bridge-troll/pull/22<br />
| https://mattprogrammingblog.wordpress.com/2018/03/24/release-0-2-part-2-working-with-brave/, https://mattprogrammingblog.wordpress.com/2018/03/27/osd600-release-2-part-3-working-with-bridge-troll/<br />
|-<br />
| 2<br />
| Yuriy Kartuzov<br />
| Tensorflow<br />
| 1. Learning Technology https://wp.me/p9B1Vb-1e<br />
|<br />
|<br />
|-<br />
| 3<br />
| Soutrik Barua<br />
|Debugger.html<br />
|https://soutrikbarua.blogspot.ca/2018/04/first-open-source-contribution.html<br />
|https://github.com/devtools-html/debugger.html/pull/5775 ,https://github.com/devtools-html/debugger.html/pull/5776<br />
|https://soutrikbarua.blogspot.ca/2018/04/fixing-issues-in-debuggerhtml.html<br />
|-<br />
| 4<br />
|Abel Inocencio<br />
|Brave Browser for Laptop<br />
|<br />
|<br />
|<br />
|-<br />
| 5<br />
|Hao Chen<br />
|Angularjs, Mozilla(Devtool/debugger.html)<br />
| https://medium.com/haorc/project-overview-for-open-source-contribution-2ef4e0f10253<br />
| https://github.com/angular/angular/pull/22431, https://github.com/devtools-html/debugger.html/pull/5619<br />
| https://medium.com/haorc/first-bug-in-open-source-cd3251a329cc, https://medium.com/haorc/bug-fix-in-debugger-html-9011499bf205<br />
|-<br />
| 6<br />
|Qiliang Chen<br />
|Brave browser for laptop (osx)<br />
|https://qchen102.blogspot.ca/2018/03/brave-browser-for-laptop.html<br />
|https://github.com/brave/browser-laptop/pull/13608<br />
|https://qchen102.blogspot.ca/2018/03/release-2-contribution-to-open-source.html<br />
|-<br />
| 7<br />
|Oleh Hodovaniuk<br />
|material-dialogs (Android), QKSMS <br />
|https://ohodovaniuk.wordpress.com/2018/03/13/release-2/<br />
|https://github.com/afollestad/material-dialogs/pull/1527, https://github.com/moezbhatti/qksms/pull/938<br />
|https://ohodovaniuk.wordpress.com/2018/03/18/release-2-process-and-results/<br />
|-<br />
| 8<br />
|Kelvin Cho<br />
|Brave/browser-laptop<br />
|https://klvincho.wordpress.com/2018/03/13/osd600-release-0-2-introduction/<br />
|https://github.com/vgstation-coders/vgstation13/pull/17940<br />
|https://klvincho.wordpress.com/2018/03/27/release-2-0-blog/<br />
|-<br />
| 9<br />
|Lucas Verbeke<br />
|Brave/browser-laptop, vgstation13<br />
|https://thelucasexcerpt.wordpress.com/2018/03/14/osd600-release-2-lucas-verbeke<br />
|https://github.com/vgstation-coders/vgstation13/pull/17938<br />
|https://thelucasexcerpt.wordpress.com/2018/03/27/osd600-release-0-2-lucas-verbeke<br />
|-<br />
| 10<br />
|Owen Mak<br />
|VSCode<br />
|https://makowen.wordpress.com/2018/03/25/merry-go-around-quest-for-finding-a-project-to-contribute/<br />
|https://github.com/Microsoft/vscode/pull/46466, https://github.com/humphd/bridge-troll/pull/15<br />
|https://makowen.wordpress.com/2018/03/26/vscode-titlebar-bug/<br />
|-<br />
| 11<br />
|Jafar Frotan <br />
|Mozilla addons-frontend<br />
|https://medium.com/@jaf.frotan/bugs-bugs-bugs-10c27f1530a7<br />
|https://github.com/mozilla/addons-frontend/pull/4702<br />
|https://medium.com/@jaf.frotan/release-0-2-a7d70fafdd7f<br />
|-<br />
| 12<br />
| Woodson Delhia<br />
| Haskell http-api-data<br />
| https://woodsondelhia.wordpress.com/2018/03/24/open-source-release-0-2-project-introduction/<br />
| https://github.com/fizruk/http-api-data/pull/74#pullrequestreview-104701255<br />
| https://woodsondelhia.wordpress.com/2018/03/26/open-source-release-0-2-http-api-data-bug-fix/<br />
|-<br />
| 13<br />
| Yalong Li<br />
| debugger.html<br />
| https://yalongxyz.blogspot.ca/2018/03/osd-release-02-intro-post.html<br />
| https://github.com/devtools-html/debugger.html/pull/5766<br />
| https://yalongxyz.blogspot.ca/2018/03/osd-release-02-final-post.html<br />
|-<br />
| 14<br />
| Aliaksandr Ushakou<br />
| Brave, VSCode<br />
| https://aushakou.wordpress.com/2018/04/09/introduction-to-brave/<br />
| https://github.com/Microsoft/vscode/pull/44006, https://github.com/brave/browser-laptop/pull/13774, https://github.com/brave/browser-laptop/pull/13775<br />
| https://aushakou.wordpress.com/2018/04/11/release-0-2/<br />
|-<br />
| 15<br />
| Abdul Kabia<br />
| Discord.js<br />
| https://akkabia.wordpress.com/2018/03/19/the-bots-are-taking-over/<br />
|<br />
|<br />
|-<br />
| 16<br />
| Alex Wang<br />
| Mozilla - devtools.html/debugger<br />
| https://alexopensource.wordpress.com/2018/03/24/mozilla-debugger-html/<br />
| https://github.com/devtools-html/debugger.html/pull/5750<br />
| https://wp.me/p9ApzU-1D<br />
|-<br />
| 17<br />
|Michael Kavidas<br />
|VSCode<br />
|<br />
|<br />
|<br />
|-<br />
| 18<br />
|Hongcheng Zhang<br />
|Mozilla-thimble,Android-alert-dialog<br />
|https://hongcheng1993.wordpress.com/2018/03/27/introduction-of-thimble-and-android-alert-dialog/<br />
|https://github.com/mozilla/thimble.mozilla.org/pull/2622, https://github.com/pedant/sweet-alert-dialog/pull/175<br />
|https://hongcheng1993.wordpress.com/2018/03/27/release2-final-post/<br />
|-<br />
| 19<br />
|Patrick Godbout<br />
|Brave/browser-laptop<br />
|https://mb30myopensourceblog.blogspot.ca/2018/03/dps909-release-02-my-first-open-source.html<br />
|https://github.com/brave/browser-laptop/pull/13769<br />
|https://mb30myopensourceblog.blogspot.ca/2018/03/dps909-release-02-my-first-open-source_25.html<br />
|-<br />
| 20<br />
| Zhihao Cai<br />
| Brave(browser-laptop), NextCloud(android)<br />
| https://choyzhihao.wordpress.com/2018/03/26/a-bit-intro-of-brave-browser/<br />
| https://www.transifex.com/user/profile/josechoy/, https://github.com/nextcloud/android/pull/2401<br />
| https://choyzhihao.wordpress.com/2018/03/25/contribute-to-open-source-as-a-translator/<br />
|-<br />
| 21<br />
| Evan Davies<br />
| Brave/browser-laptop<br />
|http://openthoughtsopensource.blogspot.ca/2018/03/brave-putting-browsing-power-back-in.html<br />
|https://github.com/brave/browser-laptop/pull/13615, https://github.com/EmdaviesSeneca/browser-laptop<br />
|http://openthoughtsopensource.blogspot.ca/2018/03/brave-popup-predicament.html<br />
|-<br />
| 22<br />
| Vimal Raghubir<br />
| GitHubCity (Python library), CyberChef (Node.js web app)<br />
| https://medium.com/@vraghubir/diving-into-open-source-contributions-b2e98796d21c<br />
| https://github.com/iblancasa/GitHubCity/pull/173, https://github.com/gchq/CyberChef/pull/282<br />
| https://medium.com/@vraghubir/cyberchef-and-githubcity-contributions-36135e72e2cf<br />
|-<br />
| 23<br />
| Aaron Scott<br />
| Baystation 12<br />
| https://arscott28081253.wordpress.com/2018/03/27/osd600-release-0-2-intro/<br />
| https://github.com/Baystation12/Baystation12/pull/20928<br />
| https://arscott28081253.wordpress.com/2018/03/27/osd600-release-0-2-final-blog-post/<br />
|-<br />
| 24<br />
| Justin Vuu<br />
| Brave<br />
| https://justosd.wordpress.com/2018/03/26/osd600-release-0-2-part-1/<br />
| https://github.com/brave/browser-laptop/pull/13598<br />
| https://justosd.wordpress.com/2018/03/26/osd600-release-0-2-part-2/<br />
|-<br />
| 25<br />
| Bakytzhan Apetov<br />
| Mozilla dev-tools/debugger.html<br />
| https://bapetov.wordpress.com/2018/03/26/release-0-2-introductory-post-for-the-project/<br />
| https://github.com/devtools-html/debugger.html/pull/5802<br />
| https://bapetov.wordpress.com/2018/03/27/release-0-2-final-post-with-the-fixed-issue/<br />
|-<br />
| 26<br />
| Aleksey Glazkov<br />
| VSCode<br />
| https://aglazkovblog.wordpress.com/2018/03/27/release-0-2-visual-studio-code-introduction/<br />
| https://github.com/Microsoft/vscode/pull/46518<br />
| https://aglazkovblog.wordpress.com/2018/04/06/release-0-2-bug-fix-and-pull-request/<br />
|-<br />
| 27<br />
| Michael Fainshtein<br />
| AVA<br />
| https://wordpress.com/post/moderatelyokaydeveloper.wordpress.com/32<br />
| https://github.com/avajs/ava/pull/1751<br />
| https://wordpress.com/post/moderatelyokaydeveloper.wordpress.com/34<br />
|-<br />
| 28<br />
| Zukhruf Khan<br />
| Upstate Data Summit<br />
| https://zedsdps909blog.wordpress.com/2018/03/27/release-0-2-introduction-part-1/<br />
| https://github.com/UpstateData/data-summit/pull/9<br />
| https://zedsdps909blog.wordpress.com/2018/03/27/release-0-2-the-aftermath-part-2/<br />
|-<br />
| 29<br />
| Joseph Pham<br />
| Firefox Screenshots<br />
| https://jpham14.wordpress.com/2018/03/21/project-intro-firefox-screenshots/<br />
| https://github.com/mozilla-services/screenshots/compare/master...jpham14:issuefix?expand=1#diff-d45944c551eead471a128c9a716e2a79<br />
| https://jpham14.wordpress.com/2018/03/27/firefox-screenshot/<br />
|-<br />
| 30<br />
| Liam Newell<br />
| A browser UI for JSNES, a JavaScript NES emulator <br />
| http://liamnewell.me/blog/bugs/release02-intro/ <br />
| https://github.com/bfirsh/jsnes-web/pull/69 (I already had this finished before monday!! forgot to post) <br />
| http://liamnewell.me/blog/bugs/release02-implementation/<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.2&diff=133277OSD & DPS909 Winter 2018 Release 0.22018-04-09T06:26:33Z<p>Aushakou: /* 6. Submission */</p>
<hr />
<div>=0.2 Release=<br />
<br />
In this release, you are asked to contribute to a real open source project. This release is due '''Monday March 26'''.<br />
<br />
Below you will find a suggested set of projects and tools to consider, as well as links to possible ''Good First Bugs''. You are free to work on other products/tools/bugs besides those listed below, as long as you talk to your professor first.<br />
<br />
Completing this release is a multi-step process, with various deliverables. Please read all instructions carefully so you don't miss any steps.<br />
<br />
==1. Pick a Possible Project(s)==<br />
<br />
Your first step is to research and find a suitable open source project on GitHub. Once you've chosen a project, add it to the table at the bottom, along with your name. This will help other students find you, if they are also working on the same code.<br />
<br />
Important things to consider:<br />
<br />
* Make sure the project is still active. Many projects on GitHub are no longer being developed.<br />
* Try to find larger projects with many contributors vs. small projects, or those with only a small number of contributors. It is difficult to get help, feedback, or traction in small projects.<br />
* Try to find a project with a wide variety of bugs to work on. Projects with only a few issues filed are less likely to be good places to find contributions.<br />
* Look for signals in <code>CONTRIBUTING.md</code> and <code>README.md</code> files that a project is open to contributors.<br />
* Pick a project that uses technologies you are interested in learning, or already know well. Don't pick a project that uses things you dislike.<br />
* Consider picking a project you use yourself, something you love, and/or something you would be proud to say you worked on.<br />
<br />
Here are some projects and areas to consider:<br />
<br />
* [https://github.com/trending GitHub's Trending projects] - you can see which projects are trending on GitHub, and maybe find one that would be interesting to you. Try limiting the language to one you want to work in (e.g., JavaScript).<br />
* [https://github.com/explore GitHub Explore] - list of many projects categorized into topics. Maybe you'll find one that you like there.<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction Mozilla] - you could work on Firefox or any number of other Mozilla projects. Mozilla uses C/C++, JS, HTML, Python, etc. There are literally thousands of ways to get involved.<br />
* [https://github.com/Microsoft/vscode Visual Studio Code] (Electron, TypeScrypt, JS, CSS, React)<br />
* [https://github.com/Brave Brave] - you could work on the Brave web browser for [https://github.com/brave/browser-laptop desktop], [https://github.com/brave/browser-android-tabs Android], or [https://github.com/brave/browser-ios iOS]<br />
* [https://datproject.org/ DAT Project] - p2p web technology, including the [https://beakerbrowser.com/ Beaker Browser]<br />
* [https://github.com/tensorflow/tensorflow Tensorflow] or [https://github.com/PAIR-code/deeplearnjs DeepLearn.js] or any number of other [https://github.com/topics/deep-learning Machine Learning/AI frameworks].<br />
* [https://github.com/topics/bitcoin Bitcoin] or [https://github.com/topics/etherium Etherium] or other [https://github.com/topics/cryptocurrency cryptocurrency/blockchain projects].<br />
* [https://github.com/topics/database Databases] - there are hundreds of open source database projects, libraries, and tools<br />
* [https://github.com/topics/docker Docker] and other container technology is hot right now<br />
* [https://github.com/topics/game-engine Game Engines] - many are open source and have ways to get involved<br />
* [https://github.com/topics/nodejs Node.js] is a huge ecosystem, with thousands of sub-projects, modules, and tools that need help.<br />
* [https://github.com/mozilla/activity-stream Firefox Activity Stream] (JS, CSS, React) [https://github.com/mozilla/activity-stream#for-developers dev docs] [https://github.com/mozilla/activity-stream/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+bug%22 "Good first bug"]<br />
* [http://firefox-dev.tools/debugger.html/ Firefox JavaScript Debugger] (React, JS) [https://t.co/4ewG5n9Q8D bugs], [https://t.co/LHCPAxhgVS more bugs].<br />
* [https://pontoon.mozilla.org/ Pontoon localization tool] (Python, JS, HTML5) [https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Pontoon&resolution=---&list_id=10786825 unedited bug list]<br />
* [https://www.rust-lang.org Rust] (programming language, sites, and project) [https://www.rust-lang.org/en-US/contribute.html contribute docs], [https://github.com/rust-lang/rust/labels/E-easy "easy" bugs], [https://github.com/rust-lang/crates.io/issues?q=is%3Aissue+is%3Aopen+label%3AE-easy Crates.io package manager "easy" bugs], [https://www.rustaceans.org/findwork other ideas for contributing to Rust and tooling]<br />
* [https://addons.mozilla.org/ Addons Server] (Python/Django Server and API) [https://github.com/mozilla/addons-server/labels/contrib%3A%20good%20first%20bug "good first bug"]<br />
<br />
Spend some time looking at these projects and find something that fits your skills, interests, and goals. Fixing bugs in a big project is hard, so it's wise to pick something you will enjoy and succeed at doing.<br />
<br />
==2. Subscribe to your chosen Project(s)==<br />
<br />
Once you've chosen a project or two, spend some time "lurking" in it so you can get a sense of how things work. Before you dive into picking and fixing bugs, it's a good idea to observe how the project works, what areas are being worked on, what the priorities are, which tools/workflows are being used, etc. Here are a few ways you can accomplish this:<br />
<br />
* '''Read''' the project's documentation (website, README, Contributing, Code of Conduct, etc)<br />
* '''Watch''' the [https://help.github.com/articles/watching-and-unwatching-repositories/#watching-a-single-repository project's repository on GitHub] to get email when people file/respond to bugs. NOTE: you might want to setup an inbox filter, as you'll likely get a lot of email when you do this.<br />
* '''Join''' the project's discussion channels. This might be Slack, IRC, or some other tool. It's normal to join channels and not say anything, just "listen," so don't feel weird doing it. You'll learn a lot by watching how they work. When you feel comfortable, introduce yourself and let them know you'd like to contribute.<br />
<br />
After you've spent some time doing this, '''write a blog post introducing the project'''. Here are things to cover:<br />
<br />
* What is the project about?<br />
* Where is the code located?<br />
* Where are their docs?<br />
* How can you get involved?<br />
* Where can you go to get help?<br />
* What are some interesting things you've learned while observing the project (e.g., pull requests fixing bugs, adding features, discussions)?<br />
<br />
==3. Find some Bugs to Fix==<br />
<br />
Once you've found a project you like, and are happy to get involved, it's time to find some bugs to work on. Look in their '''Issues''' and perhaps talk to them on Slack/IRC or wherever they work, and find some possible bugs. Consider looking for issues with labels like '''good-first-bug''', '''bug''', '''help wanted''', etc.<br />
<br />
Try to pick a bug (or bugs) you can accomplish in the time you have available. For example, if a bug is really small, consider fixing more than one. If a bug is really huge (adding a new feature), consider whether it's reasonable to do this during this first release, or if you should wait for the next. You can talk to your professor to get help.<br />
<br />
You are encouraged to work on any/all of the following:<br />
<br />
* Fixing code bugs<br />
* Writing documentation<br />
* Automating processes (e.g., build system work)<br />
* Localization, translation<br />
* Writing tests<br />
<br />
When you've decided on bug(s) to work on, please leave a comment in the bug(s) asking if it's OK for you to do this. Someone else might be working on it, the bug might not exist anymore, or there might be a better bug you can work on. Communicate with the project's community before you spend hours working on the wrong thing.<br />
<br />
==4. Submit Pull Request(s) and Fix Review Comments==<br />
<br />
Submit one or more Pull Requests in order to fix your bug(s). Make sure you follow the project's instructions carefully for submitting work--every project does this slightly differently. When in doubt, go look at other closed pull requests to see how they did things.<br />
<br />
When you get feedback, make sure you respond, and push more commits to fix any problems pointed out by your reviewer.<br />
<br />
==5. FAQ==<br />
<br />
* Can I start my own open source project and work on that? No. This project is about contributing to existing, large, open source projects, which involves learning many skills, tools, and processes that will be valuable to you in your career as a developer.<br />
<br />
* Can I work with a partner, or in a group? No. You can collaborate with others in the course on your bug(s), but you need to "own" your own bug, and do the work yourself. Having people give you advice or help, and doing the same for others, is fine. However, "help" doesn't mean one person does it all.<br />
<br />
* Can I work on something I don't know (e.g., Rust, Firefox, ...)? Yes. As long as you're willing to push yourself to learn what you need to know, you can do it. You have 4 weeks to accomplish this, which is lots of time to research, learn, fail, and succeed.<br />
<br />
* What if I write a fix and the project rejects it, will I still get marks? Yes. You will be marked on the process, how you work, and what you create. Mozilla will almost certainly reject your first attempt in code review, and offer comments on what to fix. It might take a few rounds of review/re-submission for you to get your bug(s) finished. That's normal.<br />
<br />
* When should I start working on my bug? Now. Fixing a bug in a large code base you don't know takes lots of time. You have lots of time (1 month), don't waste it. Work on your bug every few days for a short amount of time; don't leave it until a few days before it's due.<br />
<br />
* What do I do if someone else is already working on a bug? What if someone else also wants to work on a bug? You need to communicate your intent to work on something. Leave a comment in a bug, and let people know you are interested in working on it. If someone else is working on it, but hasn't made progress in a long time, you can leave a polite question asking if it's OK for you to take it over. If another student also wants to work on a bug, come see your professor for help finding another suitable issue.<br />
<br />
==6. Submission==<br />
<br />
Please fill out the table below with all relevant links, including:<br />
<br />
* Your name and the name of the open source project you're working on<br />
* An introductory blog post for your chosen project. See section 2. above for details.<br />
* Links to all Pull Requests you make to the project on GitHub.<br />
* A final blog post describing everything you did. Please include links to bugs, pull requests, and discuss what your bug was about, how you fixed it, what you learned, etc. Feel free to include screenshots, screencasts, video, or anything else you need to properly describe your work.<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Open Source Project<br />
! style="font-weight: bold;" | Project Intro Blog (URL)<br />
! style="font-weight: bold;" | Pull Request(s) (GitHub URLs)<br />
! style="font-weight: bold;" | Final Blog Post (URL)<br />
|-<br />
| 1<br />
| Matthew Quan<br />
| VSCode, Brave (browser-laptop), bridge-troll<br />
| https://mattprogrammingblog.wordpress.com/2018/03/09/osd600-release-0-2-part-1-working-with-vscode/<br />
| https://github.com/brave/browser-laptop/pull/13386, https://github.com/Microsoft/vscode/pull/43950, https://github.com/Microsoft/vscode-docs/pull/1487, https://github.com/humphd/bridge-troll/pull/22<br />
| https://mattprogrammingblog.wordpress.com/2018/03/24/release-0-2-part-2-working-with-brave/, https://mattprogrammingblog.wordpress.com/2018/03/27/osd600-release-2-part-3-working-with-bridge-troll/<br />
|-<br />
| 2<br />
| Yuriy Kartuzov<br />
| Tensorflow<br />
| 1. Learning Technology https://wp.me/p9B1Vb-1e<br />
|<br />
|<br />
|-<br />
| 3<br />
| Soutrik Barua<br />
|Debugger.html<br />
|https://soutrikbarua.blogspot.ca/2018/04/first-open-source-contribution.html<br />
|https://github.com/devtools-html/debugger.html/pull/5775 ,https://github.com/devtools-html/debugger.html/pull/5776<br />
|https://soutrikbarua.blogspot.ca/2018/04/fixing-issues-in-debuggerhtml.html<br />
|-<br />
| 4<br />
|Abel Simon Inocencio<br />
|Blockchain<br />
|<br />
|<br />
|<br />
|-<br />
| 5<br />
|Hao Chen<br />
|Angularjs, Mozilla(Devtool/debugger.html)<br />
| https://medium.com/haorc/project-overview-for-open-source-contribution-2ef4e0f10253<br />
| https://github.com/angular/angular/pull/22431, https://github.com/devtools-html/debugger.html/pull/5619<br />
| https://medium.com/haorc/first-bug-in-open-source-cd3251a329cc, https://medium.com/haorc/bug-fix-in-debugger-html-9011499bf205<br />
|-<br />
| 6<br />
|Qiliang Chen<br />
|Brave browser for laptop (osx)<br />
|https://qchen102.blogspot.ca/2018/03/brave-browser-for-laptop.html<br />
|https://github.com/brave/browser-laptop/pull/13608<br />
|https://qchen102.blogspot.ca/2018/03/release-2-contribution-to-open-source.html<br />
|-<br />
| 7<br />
|Oleh Hodovaniuk<br />
|material-dialogs (Android), QKSMS <br />
|https://ohodovaniuk.wordpress.com/2018/03/13/release-2/<br />
|https://github.com/afollestad/material-dialogs/pull/1527, https://github.com/moezbhatti/qksms/pull/938<br />
|https://ohodovaniuk.wordpress.com/2018/03/18/release-2-process-and-results/<br />
|-<br />
| 8<br />
|Kelvin Cho<br />
|Brave/browser-laptop<br />
|https://klvincho.wordpress.com/2018/03/13/osd600-release-0-2-introduction/<br />
|https://github.com/vgstation-coders/vgstation13/pull/17940<br />
|https://klvincho.wordpress.com/2018/03/27/release-2-0-blog/<br />
|-<br />
| 9<br />
|Lucas Verbeke<br />
|Brave/browser-laptop, vgstation13<br />
|https://thelucasexcerpt.wordpress.com/2018/03/14/osd600-release-2-lucas-verbeke<br />
|https://github.com/vgstation-coders/vgstation13/pull/17938<br />
|https://thelucasexcerpt.wordpress.com/2018/03/27/osd600-release-0-2-lucas-verbeke<br />
|-<br />
| 10<br />
|Owen Mak<br />
|VSCode<br />
|https://makowen.wordpress.com/2018/03/25/merry-go-around-quest-for-finding-a-project-to-contribute/<br />
|https://github.com/Microsoft/vscode/pull/46466, https://github.com/humphd/bridge-troll/pull/15<br />
|https://makowen.wordpress.com/2018/03/26/vscode-titlebar-bug/<br />
|-<br />
| 11<br />
|Jafar Frotan <br />
|Mozilla addons-frontend<br />
|https://medium.com/@jaf.frotan/bugs-bugs-bugs-10c27f1530a7<br />
|https://github.com/mozilla/addons-frontend/pull/4702<br />
|https://medium.com/@jaf.frotan/release-0-2-a7d70fafdd7f<br />
|-<br />
| 12<br />
| Woodson Delhia<br />
| Haskell http-api-data<br />
| https://woodsondelhia.wordpress.com/2018/03/24/open-source-release-0-2-project-introduction/<br />
| https://github.com/fizruk/http-api-data/pull/74#pullrequestreview-104701255<br />
| https://woodsondelhia.wordpress.com/2018/03/26/open-source-release-0-2-http-api-data-bug-fix/<br />
|-<br />
| 13<br />
| Yalong Li<br />
| debugger.html<br />
| https://yalongxyz.blogspot.ca/2018/03/osd-release-02-intro-post.html<br />
| https://github.com/devtools-html/debugger.html/pull/5766<br />
| https://yalongxyz.blogspot.ca/2018/03/osd-release-02-final-post.html<br />
|-<br />
| 14<br />
| Aliaksandr Ushakou<br />
| Brave, VSCode<br />
| https://aushakou.wordpress.com/2018/04/09/introduction-to-brave/<br />
| https://github.com/Microsoft/vscode/pull/44006, https://github.com/brave/browser-laptop/pull/13774, https://github.com/brave/browser-laptop/pull/13775<br />
|<br />
|-<br />
| 15<br />
| Abdul Kabia<br />
| Discord.js<br />
| https://akkabia.wordpress.com/2018/03/19/the-bots-are-taking-over/<br />
|<br />
|<br />
|-<br />
| 16<br />
| Alex Wang<br />
| Mozilla - devtools.html/debugger<br />
| https://alexopensource.wordpress.com/2018/03/24/mozilla-debugger-html/<br />
| https://github.com/devtools-html/debugger.html/pull/5750<br />
| https://wp.me/p9ApzU-1D<br />
|-<br />
| 17<br />
|Michael Kavidas<br />
|VSCode<br />
|<br />
|<br />
|<br />
|-<br />
| 18<br />
|Hongcheng Zhang<br />
|Mozilla-thimble,Android-alert-dialog<br />
|https://hongcheng1993.wordpress.com/2018/03/27/introduction-of-thimble-and-android-alert-dialog/<br />
|https://github.com/mozilla/thimble.mozilla.org/pull/2622, https://github.com/pedant/sweet-alert-dialog/pull/175<br />
|https://hongcheng1993.wordpress.com/2018/03/27/release2-final-post/<br />
|-<br />
| 19<br />
|Patrick Godbout<br />
|Brave/browser-laptop<br />
|https://mb30myopensourceblog.blogspot.ca/2018/03/dps909-release-02-my-first-open-source.html<br />
|https://github.com/brave/browser-laptop/pull/13769<br />
|https://mb30myopensourceblog.blogspot.ca/2018/03/dps909-release-02-my-first-open-source_25.html<br />
|-<br />
| 20<br />
| Zhihao Cai<br />
| Brave(browser-laptop), NextCloud(android)<br />
| https://choyzhihao.wordpress.com/2018/03/26/a-bit-intro-of-brave-browser/<br />
| https://www.transifex.com/user/profile/josechoy/, https://github.com/nextcloud/android/pull/2401<br />
| https://choyzhihao.wordpress.com/2018/03/25/contribute-to-open-source-as-a-translator/<br />
|-<br />
| 21<br />
| Evan Davies<br />
| Brave/browser-laptop<br />
|http://openthoughtsopensource.blogspot.ca/2018/03/brave-putting-browsing-power-back-in.html<br />
|https://github.com/brave/browser-laptop/pull/13615, https://github.com/EmdaviesSeneca/browser-laptop<br />
|http://openthoughtsopensource.blogspot.ca/2018/03/brave-popup-predicament.html<br />
|-<br />
| 22<br />
| Vimal Raghubir<br />
| GitHubCity (Python library), CyberChef (Node.js web app)<br />
| https://medium.com/@vraghubir/diving-into-open-source-contributions-b2e98796d21c<br />
| https://github.com/iblancasa/GitHubCity/pull/173, https://github.com/gchq/CyberChef/pull/282<br />
| https://medium.com/@vraghubir/cyberchef-and-githubcity-contributions-36135e72e2cf<br />
|-<br />
| 23<br />
| Aaron Scott<br />
| Baystation 12<br />
| https://arscott28081253.wordpress.com/2018/03/27/osd600-release-0-2-intro/<br />
| https://github.com/Baystation12/Baystation12/pull/20928<br />
| https://arscott28081253.wordpress.com/2018/03/27/osd600-release-0-2-final-blog-post/<br />
|-<br />
| 24<br />
| Justin Vuu<br />
| Brave<br />
| https://justosd.wordpress.com/2018/03/26/osd600-release-0-2-part-1/<br />
| https://github.com/brave/browser-laptop/pull/13598<br />
| https://justosd.wordpress.com/2018/03/26/osd600-release-0-2-part-2/<br />
|-<br />
| 25<br />
| Bakytzhan Apetov<br />
| Mozilla dev-tools/debugger.html<br />
| https://bapetov.wordpress.com/2018/03/26/release-0-2-introductory-post-for-the-project/<br />
| https://github.com/devtools-html/debugger.html/pull/5802<br />
| https://bapetov.wordpress.com/2018/03/27/release-0-2-final-post-with-the-fixed-issue/<br />
|-<br />
| 26<br />
| Aleksey Glazkov<br />
| VSCode<br />
| https://aglazkovblog.wordpress.com/2018/03/27/release-0-2-visual-studio-code-introduction/<br />
| https://github.com/Microsoft/vscode/pull/46518<br />
| https://aglazkovblog.wordpress.com/2018/04/06/release-0-2-bug-fix-and-pull-request/<br />
|-<br />
| 27<br />
| Michael Fainshtein<br />
| AVA<br />
| https://wordpress.com/post/moderatelyokaydeveloper.wordpress.com/32<br />
| https://github.com/avajs/ava/pull/1751<br />
| https://wordpress.com/post/moderatelyokaydeveloper.wordpress.com/34<br />
|-<br />
| 28<br />
| Zukhruf Khan<br />
| Upstate Data Summit<br />
| https://zedsdps909blog.wordpress.com/2018/03/27/release-0-2-introduction-part-1/<br />
| https://github.com/UpstateData/data-summit/pull/9<br />
| https://zedsdps909blog.wordpress.com/2018/03/27/release-0-2-the-aftermath-part-2/<br />
|-<br />
| 29<br />
| Joseph Pham<br />
| Firefox Screenshots<br />
| https://jpham14.wordpress.com/2018/03/21/project-intro-firefox-screenshots/<br />
| https://github.com/mozilla-services/screenshots/compare/master...jpham14:issuefix?expand=1#diff-d45944c551eead471a128c9a716e2a79<br />
| https://jpham14.wordpress.com/2018/03/27/firefox-screenshot/<br />
|-<br />
| 30<br />
| Liam Newell<br />
| A browser UI for JSNES, a JavaScript NES emulator <br />
| http://liamnewell.me/blog/bugs/release02-intro/ <br />
| https://github.com/bfirsh/jsnes-web/pull/69 (I already had this finished before monday!! forgot to post) <br />
| http://liamnewell.me/blog/bugs/release02-implementation/<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.2&diff=133275OSD & DPS909 Winter 2018 Release 0.22018-04-09T03:04:48Z<p>Aushakou: /* 6. Submission */</p>
<hr />
<div>=0.2 Release=<br />
<br />
In this release, you are asked to contribute to a real open source project. This release is due '''Monday March 26'''.<br />
<br />
Below you will find a suggested set of projects and tools to consider, as well as links to possible ''Good First Bugs''. You are free to work on other products/tools/bugs besides those listed below, as long as you talk to your professor first.<br />
<br />
Completing this release is a multi-step process, with various deliverables. Please read all instructions carefully so you don't miss any steps.<br />
<br />
==1. Pick a Possible Project(s)==<br />
<br />
Your first step is to research and find a suitable open source project on GitHub. Once you've chosen a project, add it to the table at the bottom, along with your name. This will help other students find you, if they are also working on the same code.<br />
<br />
Important things to consider:<br />
<br />
* Make sure the project is still active. Many projects on GitHub are no longer being developed.<br />
* Try to find larger projects with many contributors vs. small projects, or those with only a small number of contributors. It is difficult to get help, feedback, or traction in small projects.<br />
* Try to find a project with a wide variety of bugs to work on. Projects with only a few issues filed are less likely to be good places to find contributions.<br />
* Look for signals in <code>CONTRIBUTING.md</code> and <code>README.md</code> files that a project is open to contributors.<br />
* Pick a project that uses technologies you are interested in learning, or already know well. Don't pick a project that uses things you dislike.<br />
* Consider picking a project you use yourself, something you love, and/or something you would be proud to say you worked on.<br />
<br />
Here are some projects and areas to consider:<br />
<br />
* [https://github.com/trending GitHub's Trending projects] - you can see which projects are trending on GitHub, and maybe find one that would be interesting to you. Try limiting the language to one you want to work in (e.g., JavaScript).<br />
* [https://github.com/explore GitHub Explore] - list of many projects categorized into topics. Maybe you'll find one that you like there.<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction Mozilla] - you could work on Firefox or any number of other Mozilla projects. Mozilla uses C/C++, JS, HTML, Python, etc. There are literally thousands of ways to get involved.<br />
* [https://github.com/Microsoft/vscode Visual Studio Code] (Electron, TypeScrypt, JS, CSS, React)<br />
* [https://github.com/Brave Brave] - you could work on the Brave web browser for [https://github.com/brave/browser-laptop desktop], [https://github.com/brave/browser-android-tabs Android], or [https://github.com/brave/browser-ios iOS]<br />
* [https://datproject.org/ DAT Project] - p2p web technology, including the [https://beakerbrowser.com/ Beaker Browser]<br />
* [https://github.com/tensorflow/tensorflow Tensorflow] or [https://github.com/PAIR-code/deeplearnjs DeepLearn.js] or any number of other [https://github.com/topics/deep-learning Machine Learning/AI frameworks].<br />
* [https://github.com/topics/bitcoin Bitcoin] or [https://github.com/topics/etherium Etherium] or other [https://github.com/topics/cryptocurrency cryptocurrency/blockchain projects].<br />
* [https://github.com/topics/database Databases] - there are hundreds of open source database projects, libraries, and tools<br />
* [https://github.com/topics/docker Docker] and other container technology is hot right now<br />
* [https://github.com/topics/game-engine Game Engines] - many are open source and have ways to get involved<br />
* [https://github.com/topics/nodejs Node.js] is a huge ecosystem, with thousands of sub-projects, modules, and tools that need help.<br />
* [https://github.com/mozilla/activity-stream Firefox Activity Stream] (JS, CSS, React) [https://github.com/mozilla/activity-stream#for-developers dev docs] [https://github.com/mozilla/activity-stream/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+bug%22 "Good first bug"]<br />
* [http://firefox-dev.tools/debugger.html/ Firefox JavaScript Debugger] (React, JS) [https://t.co/4ewG5n9Q8D bugs], [https://t.co/LHCPAxhgVS more bugs].<br />
* [https://pontoon.mozilla.org/ Pontoon localization tool] (Python, JS, HTML5) [https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Pontoon&resolution=---&list_id=10786825 unedited bug list]<br />
* [https://www.rust-lang.org Rust] (programming language, sites, and project) [https://www.rust-lang.org/en-US/contribute.html contribute docs], [https://github.com/rust-lang/rust/labels/E-easy "easy" bugs], [https://github.com/rust-lang/crates.io/issues?q=is%3Aissue+is%3Aopen+label%3AE-easy Crates.io package manager "easy" bugs], [https://www.rustaceans.org/findwork other ideas for contributing to Rust and tooling]<br />
* [https://addons.mozilla.org/ Addons Server] (Python/Django Server and API) [https://github.com/mozilla/addons-server/labels/contrib%3A%20good%20first%20bug "good first bug"]<br />
<br />
Spend some time looking at these projects and find something that fits your skills, interests, and goals. Fixing bugs in a big project is hard, so it's wise to pick something you will enjoy and succeed at doing.<br />
<br />
==2. Subscribe to your chosen Project(s)==<br />
<br />
Once you've chosen a project or two, spend some time "lurking" in it so you can get a sense of how things work. Before you dive into picking and fixing bugs, it's a good idea to observe how the project works, what areas are being worked on, what the priorities are, which tools/workflows are being used, etc. Here are a few ways you can accomplish this:<br />
<br />
* '''Read''' the project's documentation (website, README, Contributing, Code of Conduct, etc)<br />
* '''Watch''' the [https://help.github.com/articles/watching-and-unwatching-repositories/#watching-a-single-repository project's repository on GitHub] to get email when people file/respond to bugs. NOTE: you might want to setup an inbox filter, as you'll likely get a lot of email when you do this.<br />
* '''Join''' the project's discussion channels. This might be Slack, IRC, or some other tool. It's normal to join channels and not say anything, just "listen," so don't feel weird doing it. You'll learn a lot by watching how they work. When you feel comfortable, introduce yourself and let them know you'd like to contribute.<br />
<br />
After you've spent some time doing this, '''write a blog post introducing the project'''. Here are things to cover:<br />
<br />
* What is the project about?<br />
* Where is the code located?<br />
* Where are their docs?<br />
* How can you get involved?<br />
* Where can you go to get help?<br />
* What are some interesting things you've learned while observing the project (e.g., pull requests fixing bugs, adding features, discussions)?<br />
<br />
==3. Find some Bugs to Fix==<br />
<br />
Once you've found a project you like, and are happy to get involved, it's time to find some bugs to work on. Look in their '''Issues''' and perhaps talk to them on Slack/IRC or wherever they work, and find some possible bugs. Consider looking for issues with labels like '''good-first-bug''', '''bug''', '''help wanted''', etc.<br />
<br />
Try to pick a bug (or bugs) you can accomplish in the time you have available. For example, if a bug is really small, consider fixing more than one. If a bug is really huge (adding a new feature), consider whether it's reasonable to do this during this first release, or if you should wait for the next. You can talk to your professor to get help.<br />
<br />
You are encouraged to work on any/all of the following:<br />
<br />
* Fixing code bugs<br />
* Writing documentation<br />
* Automating processes (e.g., build system work)<br />
* Localization, translation<br />
* Writing tests<br />
<br />
When you've decided on bug(s) to work on, please leave a comment in the bug(s) asking if it's OK for you to do this. Someone else might be working on it, the bug might not exist anymore, or there might be a better bug you can work on. Communicate with the project's community before you spend hours working on the wrong thing.<br />
<br />
==4. Submit Pull Request(s) and Fix Review Comments==<br />
<br />
Submit one or more Pull Requests in order to fix your bug(s). Make sure you follow the project's instructions carefully for submitting work--every project does this slightly differently. When in doubt, go look at other closed pull requests to see how they did things.<br />
<br />
When you get feedback, make sure you respond, and push more commits to fix any problems pointed out by your reviewer.<br />
<br />
==5. FAQ==<br />
<br />
* Can I start my own open source project and work on that? No. This project is about contributing to existing, large, open source projects, which involves learning many skills, tools, and processes that will be valuable to you in your career as a developer.<br />
<br />
* Can I work with a partner, or in a group? No. You can collaborate with others in the course on your bug(s), but you need to "own" your own bug, and do the work yourself. Having people give you advice or help, and doing the same for others, is fine. However, "help" doesn't mean one person does it all.<br />
<br />
* Can I work on something I don't know (e.g., Rust, Firefox, ...)? Yes. As long as you're willing to push yourself to learn what you need to know, you can do it. You have 4 weeks to accomplish this, which is lots of time to research, learn, fail, and succeed.<br />
<br />
* What if I write a fix and the project rejects it, will I still get marks? Yes. You will be marked on the process, how you work, and what you create. Mozilla will almost certainly reject your first attempt in code review, and offer comments on what to fix. It might take a few rounds of review/re-submission for you to get your bug(s) finished. That's normal.<br />
<br />
* When should I start working on my bug? Now. Fixing a bug in a large code base you don't know takes lots of time. You have lots of time (1 month), don't waste it. Work on your bug every few days for a short amount of time; don't leave it until a few days before it's due.<br />
<br />
* What do I do if someone else is already working on a bug? What if someone else also wants to work on a bug? You need to communicate your intent to work on something. Leave a comment in a bug, and let people know you are interested in working on it. If someone else is working on it, but hasn't made progress in a long time, you can leave a polite question asking if it's OK for you to take it over. If another student also wants to work on a bug, come see your professor for help finding another suitable issue.<br />
<br />
==6. Submission==<br />
<br />
Please fill out the table below with all relevant links, including:<br />
<br />
* Your name and the name of the open source project you're working on<br />
* An introductory blog post for your chosen project. See section 2. above for details.<br />
* Links to all Pull Requests you make to the project on GitHub.<br />
* A final blog post describing everything you did. Please include links to bugs, pull requests, and discuss what your bug was about, how you fixed it, what you learned, etc. Feel free to include screenshots, screencasts, video, or anything else you need to properly describe your work.<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Open Source Project<br />
! style="font-weight: bold;" | Project Intro Blog (URL)<br />
! style="font-weight: bold;" | Pull Request(s) (GitHub URLs)<br />
! style="font-weight: bold;" | Final Blog Post (URL)<br />
|-<br />
| 1<br />
| Matthew Quan<br />
| VSCode, Brave (browser-laptop), bridge-troll<br />
| https://mattprogrammingblog.wordpress.com/2018/03/09/osd600-release-0-2-part-1-working-with-vscode/<br />
| https://github.com/brave/browser-laptop/pull/13386, https://github.com/Microsoft/vscode/pull/43950, https://github.com/Microsoft/vscode-docs/pull/1487, https://github.com/humphd/bridge-troll/pull/22<br />
| https://mattprogrammingblog.wordpress.com/2018/03/24/release-0-2-part-2-working-with-brave/, https://mattprogrammingblog.wordpress.com/2018/03/27/osd600-release-2-part-3-working-with-bridge-troll/<br />
|-<br />
| 2<br />
| Yuriy Kartuzov<br />
| Tensorflow<br />
| 1. Learning Technology https://wp.me/p9B1Vb-1e<br />
|<br />
|<br />
|-<br />
| 3<br />
| Soutrik Barua<br />
|Debugger.html<br />
|https://soutrikbarua.blogspot.ca/2018/04/first-open-source-contribution.html<br />
|https://github.com/devtools-html/debugger.html/pull/5775 ,https://github.com/devtools-html/debugger.html/pull/5776<br />
|https://soutrikbarua.blogspot.ca/2018/04/fixing-issues-in-debuggerhtml.html<br />
|-<br />
| 4<br />
|Abel Simon Inocencio<br />
|Blockchain<br />
|<br />
|<br />
|<br />
|-<br />
| 5<br />
|Hao Chen<br />
|Angularjs, Mozilla(Devtool/debugger.html)<br />
| https://medium.com/haorc/project-overview-for-open-source-contribution-2ef4e0f10253<br />
| https://github.com/angular/angular/pull/22431, https://github.com/devtools-html/debugger.html/pull/5619<br />
| https://medium.com/haorc/first-bug-in-open-source-cd3251a329cc, https://medium.com/haorc/bug-fix-in-debugger-html-9011499bf205<br />
|-<br />
| 6<br />
|Qiliang Chen<br />
|Brave browser for laptop (osx)<br />
|https://qchen102.blogspot.ca/2018/03/brave-browser-for-laptop.html<br />
|https://github.com/brave/browser-laptop/pull/13608<br />
|https://qchen102.blogspot.ca/2018/03/release-2-contribution-to-open-source.html<br />
|-<br />
| 7<br />
|Oleh Hodovaniuk<br />
|material-dialogs (Android), QKSMS <br />
|https://ohodovaniuk.wordpress.com/2018/03/13/release-2/<br />
|https://github.com/afollestad/material-dialogs/pull/1527, https://github.com/moezbhatti/qksms/pull/938<br />
|https://ohodovaniuk.wordpress.com/2018/03/18/release-2-process-and-results/<br />
|-<br />
| 8<br />
|Kelvin Cho<br />
|Brave/browser-laptop<br />
|https://klvincho.wordpress.com/2018/03/13/osd600-release-0-2-introduction/<br />
|https://github.com/vgstation-coders/vgstation13/pull/17940<br />
|https://klvincho.wordpress.com/2018/03/27/release-2-0-blog/<br />
|-<br />
| 9<br />
|Lucas Verbeke<br />
|Brave/browser-laptop, vgstation13<br />
|https://thelucasexcerpt.wordpress.com/2018/03/14/osd600-release-2-lucas-verbeke<br />
|https://github.com/vgstation-coders/vgstation13/pull/17938<br />
|https://thelucasexcerpt.wordpress.com/2018/03/27/osd600-release-0-2-lucas-verbeke<br />
|-<br />
| 10<br />
|Owen Mak<br />
|VSCode<br />
|https://makowen.wordpress.com/2018/03/25/merry-go-around-quest-for-finding-a-project-to-contribute/<br />
|https://github.com/Microsoft/vscode/pull/46466, https://github.com/humphd/bridge-troll/pull/15<br />
|https://makowen.wordpress.com/2018/03/26/vscode-titlebar-bug/<br />
|-<br />
| 11<br />
|Jafar Frotan <br />
|Mozilla addons-frontend<br />
|https://medium.com/@jaf.frotan/bugs-bugs-bugs-10c27f1530a7<br />
|https://github.com/mozilla/addons-frontend/pull/4702<br />
|https://medium.com/@jaf.frotan/release-0-2-a7d70fafdd7f<br />
|-<br />
| 12<br />
| Woodson Delhia<br />
| Haskell http-api-data<br />
| https://woodsondelhia.wordpress.com/2018/03/24/open-source-release-0-2-project-introduction/<br />
| https://github.com/fizruk/http-api-data/pull/74#pullrequestreview-104701255<br />
| https://woodsondelhia.wordpress.com/2018/03/26/open-source-release-0-2-http-api-data-bug-fix/<br />
|-<br />
| 13<br />
| Yalong Li<br />
| debugger.html<br />
| https://yalongxyz.blogspot.ca/2018/03/osd-release-02-intro-post.html<br />
| https://github.com/devtools-html/debugger.html/pull/5766<br />
| https://yalongxyz.blogspot.ca/2018/03/osd-release-02-final-post.html<br />
|-<br />
| 14<br />
| Aliaksandr Ushakou<br />
| Brave<br />
| https://aushakou.wordpress.com/2018/04/09/introduction-to-brave/<br />
| https://github.com/Microsoft/vscode/pull/44006<br />
|<br />
|-<br />
| 15<br />
| Abdul Kabia<br />
| Discord.js<br />
| https://akkabia.wordpress.com/2018/03/19/the-bots-are-taking-over/<br />
|<br />
|<br />
|-<br />
| 16<br />
| Alex Wang<br />
| Mozilla - devtools.html/debugger<br />
| https://alexopensource.wordpress.com/2018/03/24/mozilla-debugger-html/<br />
| https://github.com/devtools-html/debugger.html/pull/5750<br />
| https://wp.me/p9ApzU-1D<br />
|-<br />
| 17<br />
|Michael Kavidas<br />
|VSCode<br />
|<br />
|<br />
|<br />
|-<br />
| 18<br />
|Hongcheng Zhang<br />
|Mozilla-thimble,Android-alert-dialog<br />
|https://hongcheng1993.wordpress.com/2018/03/27/introduction-of-thimble-and-android-alert-dialog/<br />
|https://github.com/mozilla/thimble.mozilla.org/pull/2622, https://github.com/pedant/sweet-alert-dialog/pull/175<br />
|https://hongcheng1993.wordpress.com/2018/03/27/release2-final-post/<br />
|-<br />
| 19<br />
|Patrick Godbout<br />
|Brave/browser-laptop<br />
|https://mb30myopensourceblog.blogspot.ca/2018/03/dps909-release-02-my-first-open-source.html<br />
|https://github.com/brave/browser-laptop/pull/13769<br />
|https://mb30myopensourceblog.blogspot.ca/2018/03/dps909-release-02-my-first-open-source_25.html<br />
|-<br />
| 20<br />
| Zhihao Cai<br />
| Brave(browser-laptop), NextCloud(android)<br />
| https://choyzhihao.wordpress.com/2018/03/26/a-bit-intro-of-brave-browser/<br />
| https://www.transifex.com/user/profile/josechoy/, https://github.com/nextcloud/android/pull/2401<br />
| https://choyzhihao.wordpress.com/2018/03/25/contribute-to-open-source-as-a-translator/<br />
|-<br />
| 21<br />
| Evan Davies<br />
| Brave/browser-laptop<br />
|http://openthoughtsopensource.blogspot.ca/2018/03/brave-putting-browsing-power-back-in.html<br />
|https://github.com/brave/browser-laptop/pull/13615, https://github.com/EmdaviesSeneca/browser-laptop<br />
|http://openthoughtsopensource.blogspot.ca/2018/03/brave-popup-predicament.html<br />
|-<br />
| 22<br />
| Vimal Raghubir<br />
| GitHubCity (Python library), CyberChef (Node.js web app)<br />
| https://medium.com/@vraghubir/diving-into-open-source-contributions-b2e98796d21c<br />
| https://github.com/iblancasa/GitHubCity/pull/173, https://github.com/gchq/CyberChef/pull/282<br />
| https://medium.com/@vraghubir/cyberchef-and-githubcity-contributions-36135e72e2cf<br />
|-<br />
| 23<br />
| Aaron Scott<br />
| Baystation 12<br />
| https://arscott28081253.wordpress.com/2018/03/27/osd600-release-0-2-intro/<br />
| https://github.com/Baystation12/Baystation12/pull/20928<br />
| https://arscott28081253.wordpress.com/2018/03/27/osd600-release-0-2-final-blog-post/<br />
|-<br />
| 24<br />
| Justin Vuu<br />
| Brave<br />
| https://justosd.wordpress.com/2018/03/26/osd600-release-0-2-part-1/<br />
| https://github.com/brave/browser-laptop/pull/13598<br />
| https://justosd.wordpress.com/2018/03/26/osd600-release-0-2-part-2/<br />
|-<br />
| 25<br />
| Bakytzhan Apetov<br />
| Mozilla dev-tools/debugger.html<br />
| https://bapetov.wordpress.com/2018/03/26/release-0-2-introductory-post-for-the-project/<br />
| https://github.com/devtools-html/debugger.html/pull/5802<br />
| https://bapetov.wordpress.com/2018/03/27/release-0-2-final-post-with-the-fixed-issue/<br />
|-<br />
| 26<br />
| Aleksey Glazkov<br />
| VSCode<br />
| https://aglazkovblog.wordpress.com/2018/03/27/release-0-2-visual-studio-code-introduction/<br />
| https://github.com/Microsoft/vscode/pull/46518<br />
| https://aglazkovblog.wordpress.com/2018/04/06/release-0-2-bug-fix-and-pull-request/<br />
|-<br />
| 27<br />
| Michael Fainshtein<br />
| AVA<br />
| https://wordpress.com/post/moderatelyokaydeveloper.wordpress.com/32<br />
| https://github.com/avajs/ava/pull/1751<br />
| https://wordpress.com/post/moderatelyokaydeveloper.wordpress.com/34<br />
|-<br />
| 28<br />
| Zukhruf Khan<br />
| Upstate Data Summit<br />
| https://zedsdps909blog.wordpress.com/2018/03/27/release-0-2-introduction-part-1/<br />
| https://github.com/UpstateData/data-summit/pull/9<br />
| https://zedsdps909blog.wordpress.com/2018/03/27/release-0-2-the-aftermath-part-2/<br />
|-<br />
| 29<br />
| Joseph Pham<br />
| Firefox Screenshots<br />
| https://jpham14.wordpress.com/2018/03/21/project-intro-firefox-screenshots/<br />
| https://github.com/mozilla-services/screenshots/compare/master...jpham14:issuefix?expand=1#diff-d45944c551eead471a128c9a716e2a79<br />
| https://jpham14.wordpress.com/2018/03/27/firefox-screenshot/<br />
|-<br />
| 30<br />
| Liam Newell<br />
| A browser UI for JSNES, a JavaScript NES emulator <br />
| http://liamnewell.me/blog/bugs/release02-intro/ <br />
| https://github.com/bfirsh/jsnes-web/pull/69 (I already had this finished before monday!! forgot to post) <br />
| http://liamnewell.me/blog/bugs/release02-implementation/<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD600_and_DPS909_Winter_2018_Lab_4&diff=132267OSD600 and DPS909 Winter 2018 Lab 42018-03-19T00:26:24Z<p>Aushakou: /* 3. Blog */</p>
<hr />
<div>=Contributing to Open Standards=<br />
<br />
This week we're discussing open standards, and for our lab will try writing some tests for the JavaScript (ecmascript) standard.<br />
<br />
In order for implementors of the standard to know if they've got any bugs, a comprehensive set of tests are necessary. These tests should be something that can be run by any and all JavaScript implementations (i.e., we don't Microsoft to have their tests, Google to have their tests, Mozilla to have their tests, etc. and not share with each other). JavaScript should work the same everywhere, no matter which implementation you us.<br />
<br />
In this Lab you will gain experience doing the following:<br />
<br />
* reading a language standard<br />
* running a test suite<br />
* identifying testable aspects of the standard<br />
* writing tests<br />
* sharing work using gist.github.com<br />
<br />
==1. Running the Test Suite==<br />
<br />
The language is specified in https://tc39.github.io/ecma262/, and its test suite is available at https://github.com/tc39/test262.<br />
<br />
To run the tests on your computer using node.js, follow the steps listed in https://github.com/bterlson/test262-harness#test262-harness.<br />
<br />
When you run the tests, do all the tests pass or do any of them fail for you?<br />
<br />
==2. Become Familiar with Tests==<br />
<br />
Read the docs at https://github.com/tc39/test262/blob/master/CONTRIBUTING.md, which cover things like [https://github.com/tc39/test262/blob/master/CONTRIBUTING.md#test-case-names naming], [https://github.com/tc39/test262/blob/master/CONTRIBUTING.md#test-case-style general layout], [https://github.com/tc39/test262/blob/master/CONTRIBUTING.md#test-environment assertions], [https://github.com/tc39/test262/blob/master/CONTRIBUTING.md#handling-errors-and-negative-test-cases error handling], etc.<br />
<br />
Based on what you've just read, take a look at this test for [https://github.com/tc39/test262/blob/master/test/built-ins/String/prototype/toUpperCase/S15.5.4.18_A2_T1.js String.prototype.toUpperCase()]. See if you can make sense of the code and what it's testing.<br />
<br />
==3. Array.reverse==<br />
<br />
In JavaScript, Arrays can be reversed using the <code>reverse()</code> method. It is defined in the standard at https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.reverse. Begin by reading the definition of steps in the spec.<br />
<br />
What sort of things could you test with <code>Array.reverse</code>? Based on what you read above, what sort of things need to be true about how <code>Array.reverse</code> works? Try to write a few tests for things you just thought about, using what you learned in 2.<br />
<br />
To add a new test, you can create new <code>.js</code> files underneath <code>test/</code>.<br />
<br />
==4. Extending the Existing Tests== <br />
<br />
There are actually tests written now. You can see them in [https://github.com/tc39/test262/tree/a62da2b4997767a78bb2834c4fbf4e598b0fc241/test/built-ins/Array/prototype/reverse the Array.prototype.reverse() tests]<br />
<br />
There is a bug to improve these tests, based on things learned while writing the [https://github.com/tc39/test262/tree/a62da2b4997767a78bb2834c4fbf4e598b0fc241/test/built-ins/TypedArray/prototype/reverse TypedArray.prototype.reverse tests].<br />
<br />
Take a look at the code for the [https://github.com/tc39/test262/tree/a62da2b4997767a78bb2834c4fbf4e598b0fc241/test/built-ins/TypedArray/prototype/reverse TypedArray.prototype.reverse tests] and compare it to what is happening in the [https://github.com/tc39/test262/tree/a62da2b4997767a78bb2834c4fbf4e598b0fc241/test/built-ins/Array/prototype/reverse Array.prototype.reverse() tests].<br />
<br />
Can you figure out some things you could change (i.e., ideas to borrow from the other tests)? Try rewriting some of the tests for <code>Array.reverse</code> to do what you think might be better. <br />
<br />
NOTE: you do '''not''' need to submit your tests. This lab is only about reading the spec and existing tests, and understanding how they work.<br />
<br />
==3. Blog==<br />
<br />
Write a blog post about your experience reading the spec and tests and trying to write new tests. Put any code that you wrote into a [https://gist.github.com/ gist] on GitHub (i.e., you don't need to do a pull request or submit them anywhere).<br />
<br />
Please add a line for your blog in the following table:<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! Gist of test cases (URLs)<br />
! Blog Post (URL)<br />
|-<br />
| 1<br />
| Woodson Delhia<br />
| https://gist.github.com/Woody88/7295790410b01f6473f2e7ee502bc0c8<br />
|<br />
|-<br />
| 2<br />
| Hao Chen<br />
| https://gist.github.com/haoRchen/b3249dd14d7ced8fe11487304da335a8<br />
| https://medium.com/haorc/testing-with-javascript-3c6fe1b22d0d<br />
|-<br />
| 3<br />
| Matthew Quan<br />
| https://gist.github.com/irrationalRock/362826160d1646f69d274a3e729d5bb0#file-s15-4-4-8_a1_t1-js<br />
| https://mattprogrammingblog.wordpress.com/2018/03/13/osd600-lab4-looking-at-web-standards/<br />
|-<br />
| 4<br />
| Yuriy Kartuzov<br />
| https://gist.github.com/YuriyKartuzov/c195ed5cb2e09fdae4dfc2106995a604<br />
| https://yuriykartuzov.wordpress.com/2018/03/12/lab-4/<br />
|-<br />
| 5<br />
| Owen Mak<br />
| https://gist.github.com/Owen-Mak/569dd52440e48192a5edab013f0228e4<br />
| https://makowen.wordpress.com/2018/03/13/side-quest-2-ecma-and-unit-tests/<br />
|-<br />
| 6<br />
| Jafar Frotan<br />
| https://gist.github.com/a-one-d-one/913f5830b5bbfb1c7b6abf37eed79100<br />
| https://medium.com/@jaf.frotan/innovation-adhering-to-standards-and-diving-into-testing-bfcc9d8aa5b7<br />
|-<br />
| 7<br />
| Pranoy Santosh<br />
| https://gist.github.com/pranoy10/10fd4bbf04a7490567d527017c8d52df<br />
|<br />
|-<br />
| 8<br />
| Kevin Pham<br />
| https://gist.github.com/kqpham/65891808231e9bfb1d7182d5800b0002<br />
|<br />
|-<br />
| 9<br />
| Zhihao Cai<br />
| https://gist.github.com/josechoy/0b396ef5609ee2e13c4057f81eb5b9b2<br />
| https://choyzhihao.wordpress.com/2018/03/14/get-familiar-with-javascript-standard/<br />
|-<br />
| 10<br />
| Alex Wang<br />
| https://gist.github.com/AlexWang-16/5991e9e7cf9b526cd7cab0b4a069a36a<br />
| https://alexopensource.wordpress.com/2018/03/15/learning-and-working-with-emcascript-standardization-tests/<br />
|-<br />
| 11<br />
| Oleh Hodovaniuk<br />
| https://gist.github.com/ohodovaniuk1/f5f68bca012f9d3b222bd24f0b4252db<br />
| https://ohodovaniuk.wordpress.com/2018/03/13/osd600-lab-4/<br />
|-<br />
| 12<br />
| Qiliang Chen<br />
| https://gist.github.com/KignorChan/e82a9a597e2a02115238227e911ff1b5<br />
| https://qchen102.blogspot.ca/2018/03/studying-for-open-standard.html<br />
|-<br />
| 13<br />
| Bakytzhan Apetov<br />
| https://gist.github.com/apetov/bc60c73a584c2205cc498fe06f295ec3<br />
| https://bapetov.wordpress.com/2018/03/15/lab-4-running-tests/<br />
|-<br />
| 14<br />
| Hongcheng Zhang<br />
| https://gist.github.com/StevenZhang123/bd6697f51205954323895994927c7fd3<br />
| https://hongcheng1993.wordpress.com/2018/03/15/lab4-osd/<br />
|-<br />
| 15<br />
| Patrick Godbout<br />
| https://gist.github.com/PatMB30/7a483999a2986b8358c4155d74c587e8<br />
| https://mb30myopensourceblog.blogspot.ca/2018/03/running-test-suites-and-playing-with.html<br />
|-<br />
| 16<br />
| Justin Vuu<br />
| https://gist.github.com/jevuu/552694721103f4e39304fbd33e9f1287<br />
| https://justosd.wordpress.com/2018/03/16/osd600-lab-4-contributing-to-open-standards/<br />
|-<br />
| 17<br />
| Joseph Pham<br />
| https://gist.github.com/jpham14/24c5772b69e72dafadd1fb126031a739<br />
| https://jpham14.wordpress.com/2018/03/16/lab-4-contributing-to-open-standards/<br />
|-<br />
| 18<br />
| Yalong Li<br />
| https://gist.github.com/yalooong/16fd3eaa19584fe4ad13e1f241f1e3e0<br />
| https://yalongxyz.blogspot.ca/2018/03/ecmascript-test-suite-create-reverse.html<br />
|-<br />
| 19<br />
| Liam Newell<br />
| https://gist.github.com/hibyguy/836dd91212be43a73334a6d7d51eaca3<br />
|<br />
|-<br />
| 20<br />
| Aliaksandr Ushakou<br />
| https://gist.github.com/aushakou/9e35a93b20a82208c58aa12a3da71dd2<br />
|<br />
|-<br />
| 21<br />
|<br />
|<br />
|<br />
|-<br />
| 22<br />
|<br />
|<br />
|<br />
|-<br />
| 23<br />
|<br />
|<br />
|<br />
|-<br />
| 24<br />
|<br />
|<br />
|<br />
|-<br />
| 25<br />
|<br />
|<br />
|<br />
|-<br />
| 26<br />
|<br />
|<br />
|<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.2&diff=132266OSD & DPS909 Winter 2018 Release 0.22018-03-18T22:36:59Z<p>Aushakou: /* 6. Submission */</p>
<hr />
<div>=0.2 Release=<br />
<br />
In this release, you are asked to contribute to a real open source project. This release is due '''Monday March 26'''.<br />
<br />
Below you will find a suggested set of projects and tools to consider, as well as links to possible ''Good First Bugs''. You are free to work on other products/tools/bugs besides those listed below, as long as you talk to your professor first.<br />
<br />
Completing this release is a multi-step process, with various deliverables. Please read all instructions carefully so you don't miss any steps.<br />
<br />
==1. Pick a Possible Project(s)==<br />
<br />
Your first step is to research and find a suitable open source project on GitHub. Once you've chosen a project, add it to the table at the bottom, along with your name. This will help other students find you, if they are also working on the same code.<br />
<br />
Important things to consider:<br />
<br />
* Make sure the project is still active. Many projects on GitHub are no longer being developed.<br />
* Try to find larger projects with many contributors vs. small projects, or those with only a small number of contributors. It is difficult to get help, feedback, or traction in small projects.<br />
* Try to find a project with a wide variety of bugs to work on. Projects with only a few issues filed are less likely to be good places to find contributions.<br />
* Look for signals in <code>CONTRIBUTING.md</code> and <code>README.md</code> files that a project is open to contributors.<br />
* Pick a project that uses technologies you are interested in learning, or already know well. Don't pick a project that uses things you dislike.<br />
* Consider picking a project you use yourself, something you love, and/or something you would be proud to say you worked on.<br />
<br />
Here are some projects and areas to consider:<br />
<br />
* [https://github.com/trending GitHub's Trending projects] - you can see which projects are trending on GitHub, and maybe find one that would be interesting to you. Try limiting the language to one you want to work in (e.g., JavaScript).<br />
* [https://github.com/explore GitHub Explore] - list of many projects categorized into topics. Maybe you'll find one that you like there.<br />
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction Mozilla] - you could work on Firefox or any number of other Mozilla projects. Mozilla uses C/C++, JS, HTML, Python, etc. There are literally thousands of ways to get involved.<br />
* [https://github.com/Microsoft/vscode Visual Studio Code] (Electron, TypeScrypt, JS, CSS, React)<br />
* [https://github.com/Brave Brave] - you could work on the Brave web browser for [https://github.com/brave/browser-laptop desktop], [https://github.com/brave/browser-android-tabs Android], or [https://github.com/brave/browser-ios iOS]<br />
* [https://datproject.org/ DAT Project] - p2p web technology, including the [https://beakerbrowser.com/ Beaker Browser]<br />
* [https://github.com/tensorflow/tensorflow Tensorflow] or [https://github.com/PAIR-code/deeplearnjs DeepLearn.js] or any number of other [https://github.com/topics/deep-learning Machine Learning/AI frameworks].<br />
* [https://github.com/topics/bitcoin Bitcoin] or [https://github.com/topics/etherium Etherium] or other [https://github.com/topics/cryptocurrency cryptocurrency/blockchain projects].<br />
* [https://github.com/topics/database Databases] - there are hundreds of open source database projects, libraries, and tools<br />
* [https://github.com/topics/docker Docker] and other container technology is hot right now<br />
* [https://github.com/topics/game-engine Game Engines] - many are open source and have ways to get involved<br />
* [https://github.com/topics/nodejs Node.js] is a huge ecosystem, with thousands of sub-projects, modules, and tools that need help.<br />
* [https://github.com/mozilla/activity-stream Firefox Activity Stream] (JS, CSS, React) [https://github.com/mozilla/activity-stream#for-developers dev docs] [https://github.com/mozilla/activity-stream/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+bug%22 "Good first bug"]<br />
* [http://firefox-dev.tools/debugger.html/ Firefox JavaScript Debugger] (React, JS) [https://t.co/4ewG5n9Q8D bugs], [https://t.co/LHCPAxhgVS more bugs].<br />
* [https://pontoon.mozilla.org/ Pontoon localization tool] (Python, JS, HTML5) [https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Pontoon&resolution=---&list_id=10786825 unedited bug list]<br />
* [https://www.rust-lang.org Rust] (programming language, sites, and project) [https://www.rust-lang.org/en-US/contribute.html contribute docs], [https://github.com/rust-lang/rust/labels/E-easy "easy" bugs], [https://github.com/rust-lang/crates.io/issues?q=is%3Aissue+is%3Aopen+label%3AE-easy Crates.io package manager "easy" bugs], [https://www.rustaceans.org/findwork other ideas for contributing to Rust and tooling]<br />
* [https://addons.mozilla.org/ Addons Server] (Python/Django Server and API) [https://github.com/mozilla/addons-server/labels/contrib%3A%20good%20first%20bug "good first bug"]<br />
<br />
Spend some time looking at these projects and find something that fits your skills, interests, and goals. Fixing bugs in a big project is hard, so it's wise to pick something you will enjoy and succeed at doing.<br />
<br />
==2. Subscribe to your chosen Project(s)==<br />
<br />
Once you've chosen a project or two, spend some time "lurking" in it so you can get a sense of how things work. Before you dive into picking and fixing bugs, it's a good idea to observe how the project works, what areas are being worked on, what the priorities are, which tools/workflows are being used, etc. Here are a few ways you can accomplish this:<br />
<br />
* '''Read''' the project's documentation (website, README, Contributing, Code of Conduct, etc)<br />
* '''Watch''' the [https://help.github.com/articles/watching-and-unwatching-repositories/#watching-a-single-repository project's repository on GitHub] to get email when people file/respond to bugs. NOTE: you might want to setup an inbox filter, as you'll likely get a lot of email when you do this.<br />
* '''Join''' the project's discussion channels. This might be Slack, IRC, or some other tool. It's normal to join channels and not say anything, just "listen," so don't feel weird doing it. You'll learn a lot by watching how they work. When you feel comfortable, introduce yourself and let them know you'd like to contribute.<br />
<br />
After you've spent some time doing this, '''write a blog post introducing the project'''. Here are things to cover:<br />
<br />
* What is the project about?<br />
* Where is the code located?<br />
* Where are their docs?<br />
* How can you get involved?<br />
* Where can you go to get help?<br />
* What are some interesting things you've learned while observing the project (e.g., pull requests fixing bugs, adding features, discussions)?<br />
<br />
==3. Find some Bugs to Fix==<br />
<br />
Once you've found a project you like, and are happy to get involved, it's time to find some bugs to work on. Look in their '''Issues''' and perhaps talk to them on Slack/IRC or wherever they work, and find some possible bugs. Consider looking for issues with labels like '''good-first-bug''', '''bug''', '''help wanted''', etc.<br />
<br />
Try to pick a bug (or bugs) you can accomplish in the time you have available. For example, if a bug is really small, consider fixing more than one. If a bug is really huge (adding a new feature), consider whether it's reasonable to do this during this first release, or if you should wait for the next. You can talk to your professor to get help.<br />
<br />
You are encouraged to work on any/all of the following:<br />
<br />
* Fixing code bugs<br />
* Writing documentation<br />
* Automating processes (e.g., build system work)<br />
* Localization, translation<br />
* Writing tests<br />
<br />
When you've decided on bug(s) to work on, please leave a comment in the bug(s) asking if it's OK for you to do this. Someone else might be working on it, the bug might not exist anymore, or there might be a better bug you can work on. Communicate with the project's community before you spend hours working on the wrong thing.<br />
<br />
==4. Submit Pull Request(s) and Fix Review Comments==<br />
<br />
Submit one or more Pull Requests in order to fix your bug(s). Make sure you follow the project's instructions carefully for submitting work--every project does this slightly differently. When in doubt, go look at other closed pull requests to see how they did things.<br />
<br />
When you get feedback, make sure you respond, and push more commits to fix any problems pointed out by your reviewer.<br />
<br />
==5. FAQ==<br />
<br />
* Can I start my own open source project and work on that? No. This project is about contributing to existing, large, open source projects, which involves learning many skills, tools, and processes that will be valuable to you in your career as a developer.<br />
<br />
* Can I work with a partner, or in a group? No. You can collaborate with others in the course on your bug(s), but you need to "own" your own bug, and do the work yourself. Having people give you advice or help, and doing the same for others, is fine. However, "help" doesn't mean one person does it all.<br />
<br />
* Can I work on something I don't know (e.g., Rust, Firefox, ...)? Yes. As long as you're willing to push yourself to learn what you need to know, you can do it. You have 4 weeks to accomplish this, which is lots of time to research, learn, fail, and succeed.<br />
<br />
* What if I write a fix and the project rejects it, will I still get marks? Yes. You will be marked on the process, how you work, and what you create. Mozilla will almost certainly reject your first attempt in code review, and offer comments on what to fix. It might take a few rounds of review/re-submission for you to get your bug(s) finished. That's normal.<br />
<br />
* When should I start working on my bug? Now. Fixing a bug in a large code base you don't know takes lots of time. You have lots of time (1 month), don't waste it. Work on your bug every few days for a short amount of time; don't leave it until a few days before it's due.<br />
<br />
* What do I do if someone else is already working on a bug? What if someone else also wants to work on a bug? You need to communicate your intent to work on something. Leave a comment in a bug, and let people know you are interested in working on it. If someone else is working on it, but hasn't made progress in a long time, you can leave a polite question asking if it's OK for you to take it over. If another student also wants to work on a bug, come see your professor for help finding another suitable issue.<br />
<br />
==6. Submission==<br />
<br />
Please fill out the table below with all relevant links, including:<br />
<br />
* Your name and the name of the open source project you're working on<br />
* An introductory blog post for your chosen project. See section 2. above for details.<br />
* Links to all Pull Requests you make to the project on GitHub.<br />
* A final blog post describing everything you did. Please include links to bugs, pull requests, and discuss what your bug was about, how you fixed it, what you learned, etc. Feel free to include screenshots, screencasts, video, or anything else you need to properly describe your work.<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Open Source Project<br />
! style="font-weight: bold;" | Project Intro Blog (URL)<br />
! style="font-weight: bold;" | Pull Request(s) (GitHub URLs)<br />
! style="font-weight: bold;" | Final Blog Post (URL)<br />
|-<br />
| 1<br />
| Matthew Quan<br />
| VSCode, Brave (browser-laptop), bridge-troll<br />
| https://mattprogrammingblog.wordpress.com/2018/03/09/osd600-release-0-2-part-1-working-with-vscode/<br />
| https://github.com/brave/browser-laptop/pull/13386, https://github.com/Microsoft/vscode/pull/43950, https://github.com/Microsoft/vscode-docs/pull/1487, https://github.com/humphd/bridge-troll/pull/22<br />
| <br />
|-<br />
| 2<br />
| Yuriy Kartuzov<br />
| Tensorflow<br />
|<br />
|<br />
|<br />
|-<br />
| 3<br />
| Soutrik Barua<br />
| Mozilla<br />
|<br />
|<br />
|<br />
|-<br />
| 4<br />
|Abel Simon Inocencio<br />
|Blockchain<br />
|<br />
|<br />
|<br />
|-<br />
| 5<br />
|Hao Chen<br />
|Angularjs, Mozilla(Devtool/debugger.html)<br />
|<br />
|<br />
|<br />
|-<br />
| 6<br />
|Qiliang Chen<br />
|Node.js(webtorrent),Node.js(keystone)<br />
|<br />
|<br />
|<br />
|-<br />
| 7<br />
|Oleh Hodovaniuk<br />
|material-dialogs (Android), QKSMS <br />
|https://ohodovaniuk.wordpress.com/2018/03/13/release-2/<br />
|https://github.com/afollestad/material-dialogs/pull/1527, https://github.com/moezbhatti/qksms/pull/938<br />
|https://ohodovaniuk.wordpress.com/2018/03/18/release-2-process-and-results/<br />
|-<br />
| 8<br />
|Kelvin Cho<br />
|Brave/browser-laptop<br />
|https://klvincho.wordpress.com/2018/03/13/osd600-release-0-2-introduction/<br />
|<br />
|<br />
|-<br />
| 9<br />
|Lucas Verbeke<br />
|Brave/browser-laptop<br />
|https://thelucasexcerpt.wordpress.com/2018/03/14/osd600-release-2-lucas-verbeke<br />
|<br />
|<br />
|-<br />
| 10<br />
|Owen Mak<br />
|Elasticsearch<br />
|<br />
|<br />
|<br />
|-<br />
| 11<br />
|Jafar Frotan <br />
|Mozilla addons-frontend<br />
|https://medium.com/@jaf.frotan/bugs-bugs-bugs-10c27f1530a7<br />
|<br />
|<br />
|-<br />
| 12<br />
| Woodson Delhia<br />
| Haskell http-api-data<br />
|<br />
| https://github.com/fizruk/http-api-data/pull/74#pullrequestreview-104701255<br />
|<br />
|-<br />
| 13<br />
| Yalong Li<br />
| debugger.html<br />
|<br />
|<br />
|<br />
|-<br />
| 14<br />
| Aliaksandr Ushakou<br />
| Brave<br />
|<br />
|<br />
|<br />
|-<br />
| 15<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 16<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 17<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 18<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 19<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 20<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 21<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 22<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 23<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 24<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 25<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 26<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.1&diff=131859OSD & DPS909 Winter 2018 Release 0.12018-02-22T09:11:03Z<p>Aushakou: /* 4. Submission */</p>
<hr />
<div>=0.1 Release=<br />
<br />
==Introduction==<br />
<br />
You are asked to create an open source [https://stackoverflow.com/questions/671118/what-exactly-is-restful-programming RESTful API] web service that can find and extract phone numbers from submitted resources, and be used in a [https://en.wikipedia.org/wiki/Microservices microservice architecture]. See below for details about how the API should function.<br />
<br />
Your first release will be due in multiple stages:<br />
<br />
* Part A: Create an initial, partial implementation, due '''Feb 1 by midnight'''<br />
* Part B: Contribute to another student's implementation, due '''Feb 19 by midnight'''<br />
<br />
The goal of this first release is to practice, and make sure you are comfortable with common open source workflows, including:<br />
<br />
* using git and GitHub<br />
* managing GitHub repositories<br />
* creating common project and build artifacts in an open source repo (e.g., LICENSE, Readme.md, automation, etc)<br />
* working with third-party dependencies<br />
* creating and responding to Issues<br />
* creating Pull Requests<br />
* reviewing and merging Pull Requests<br />
* the differences between being a maintainer and a contributor in an open source project<br />
<br />
==API Description==<br />
<br />
Phone numbers seem like a simple thing to work with at first, but it gets [https://github.com/googlei18n/libphonenumber/blob/master/FALSEHOODS.md complicated quickly]. Thankfully, the problem of working with phone numbers anywhere on Earth has already been solved by Google, and the code made open source:<br />
<br />
https://github.com/googlei18n/libphonenumber<br />
<br />
You are asked to use libphonenumber to create a web service, using whatever programming language you want. Your web server must support the following API endpoints, which all return [https://en.wikipedia.org/wiki/JSON JSON formatted] responses:<br />
<br />
1. <code>GET /api/phonenumbers/parse/text/{...string...}</code> to allow sending small snippets of text to be parsed.<br />
<br />
For example, requesting <code>/api/phonenumbers/parse/text/nothing</code> should return an empty list <code>[]</code>. Whereas requesting requesting <code>/api/phonenumbers/parse/text/Seneca%20Phone%20Number%3A%20416-491-5050</code> should return a list with a single, formatted phone number <code>["(416) 491-5050"]</code>.<br />
<br />
2. <code>POST /api/phonenumbers/parse/file</code> with the request's <code>Content-Type</code> being <code>text/plain</code> and the <code>body</code> containing a base64 encoded text file. This allows larger files to be processed, in addition to small bits of text.<br />
<br />
All responses from the API should be given in JSON format, with the exception of errors, which can use HTTP status codes (e.g., [https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors 4xx codes]).<br />
<br />
Phone numbers returned from any of the endpoints above should not be duplicated. That is, if a given input includes a phone number more than once, you should only return one copy of it. <br />
<br />
==Part A Requirements==<br />
<br />
Create a new GitHub repo for your web service. Pick an open source license for your code, making sure it is compatible with <code>libphonenumber</code> and any other dependencies you use. Make sure your repo has both a LICENSE and README.md file, and that your README.md has clear instructions on how to use your code.<br />
<br />
Using any programming language you like, write a server that implements the API described above. You must also include '''tests''' to prove that your server implements the API correctly. These tests need to be runnable from the command-line. You may use any testing framework, and test runner you like.<br />
<br />
File some '''Issues''' in your repo for enhancements that you'd like to see done to your server. Here are some suggestions, but feel free to file anything you like for fixes/enhancements you need:<br />
<br />
# Write more tests to deal with various edge cases<br />
# Add support for parsing a resource at a given URL: <code>GET /api/phonenumbers/url/http%3A%2F%2Fexample.com%2F</code> would cause the server to load the content at http://example.com and parse it for phone numbers.<br />
# Add support for parsing MS Word docs. There are lots of existing open source projects that can help parse a Word doc into Text, which can then be parsed by your earlier code<br />
# Add support for parsing PDF files. There are lots of existing open source projects that can help parse a PDF into Text, which can then be parsed by your earlier code<br />
# Add support for parsing images. Use an OCR (e.g., https://github.com/tesseract-ocr/tesseract or http://tesseract.projectnaptha.com/) tool to first extract text from the image, then parse it as you did earlier<br />
# Add automatic linting to the code, using something like [https://eslint.org/ eslint]. Linters find bugs and style issues.<br />
# Add an example client (e.g., web page) that can be used to manually test the API with various types of inputs<br />
# Add support for running the server on a [https://devcenter.heroku.com/start cloud service like Heroku]<br />
# Add automatic continuous integration (CI) via [https://travis-ci.org/ TravisCI], [https://circleci.com/ CircleCI], etc.<br />
<br />
Make sure your repo has all your code and tests completed before moving to Part B.<br />
<br />
==Part B Requirements==<br />
<br />
Find another student's repo and pick '''two Issues''' you'd like to work on, or file your own to fix things you notice are broken. Leave a comment in the issues to let others know that you're working on this (NOTE: only 1 student can work on an issue at a time).<br />
<br />
Fork this other student's repo, and create a clone of it. Make a branch for each of the issues you want to fix. For example, if you are fixing Issue 12, create a new branch named '''issue12''': <code>git checkout -b issue12 master</code>. Now fix the code and create a Pull Request to get your changes added.<br />
<br />
==4. Submission==<br />
<br />
All submissions are done electronically via GitHub and your blog. Please add info to the table below when you are done one of the sections.<br />
<br />
Part A: after you have created your repo, added your code and tests, and filed some issues, add your repo URL.<br />
<br />
Part B: include URLs to two PRs you made to other student's repos.<br />
<br />
Blog Post: after Part A and B are done, do your blog post. Your final blog post should discuss the following:<br />
<br />
* What did you build? Discuss your web service (e.g., what is its name, how does it work, etc.) and include links so people can find it.<br />
* What was your process for doing this assignment?<br />
* Which language, dependencies, and tools did you use? Why did you choose them?<br />
* What did you find challenging about your work?<br />
* Compare the experience of being a maintainer to that of contributing to someone else's project. Which did you enjoy more? Why?<br />
* What did you learn as you did this work?<br />
* What do you still want to learn more about in subsequent releases?<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Part A (GitHub Repo URL)<br />
! style="font-weight: bold;" | Part B (GitHub PR URLs)<br />
! style="font-weight: bold;" | Blog Post (URL)<br />
|-<br />
| 1<br />
| Bakytzhan (Jean) Apetov<br />
| https://github.com/apetov/phoneparser-js<br />
| https://github.com/alexglazkov9/phonenumberparser-js/pull/7, https://github.com/alexglazkov9/phonenumberparser-js/pull/8<br />
| https://bapetov.wordpress.com/2018/02/14/open-source-project-0-1-release/<br />
|-<br />
| 2<br />
| Yalong Li<br />
| https://github.com/yalooong/phonenumber-parser<br />
| https://github.com/haoRchen/Phone-Number-Parser/pull/10, https://github.com/zeddkay/node-libphonenumber-server/pull/5<br />
| https://yalongxyz.blogspot.ca/2018/02/contributing-for-open-souce-projects-to.html<br />
|-<br />
| 3<br />
| Woodson Delhia<br />
| https://github.com/Woody88/haskell-phonenumbers<br />
|<br />
|<br />
|-<br />
| 4<br />
| Matthew Quan<br />
| https://github.com/irrationalRock/Release1<br />
| https://github.com/simon-inoc/Open-Source/pull/2, https://github.com/apetov/phoneparser-js/pull/10, https://github.com/yalooong/phonenumber-parser/pull/8<br />
| https://mattprogrammingblog.wordpress.com/2018/02/13/osd600-release-1/<br />
|-<br />
| 5<br />
| Aleksey Glazkov<br />
| https://github.com/alexglazkov9/phonenumberparser-js<br />
| https://github.com/aushakou/phoneparser-restful-service/pull/8, https://github.com/aushakou/phoneparser-restful-service/pull/10<br />
| <br />
|-<br />
| 6<br />
| Aliaksandr Ushakou<br />
| https://github.com/aushakou/phoneparser-restful-service<br />
| https://github.com/alexglazkov9/phonenumberparser-js/pull/9, https://github.com/alexglazkov9/phonenumberparser-js/pull/10<br />
| https://aushakou.wordpress.com/2018/02/22/release-0-1/<br />
|-<br />
| 7<br />
| Kelvin Cho<br />
| https://github.com/TheKinshu/phonenumber-Parser<br />
| https://github.com/Micluc/phoneParser/pull/4, https://github.com/Micluc/phoneParser/pull/6<br />
| https://klvincho.wordpress.com/2018/02/21/release-1-0/<br />
|-<br />
| 8<br />
| Zhihao Cai<br />
| https://github.com/josechoy/phonenumber-api<br />
|<br />
|<br />
|-<br />
| 9<br />
|Owen Mak<br />
|https://github.com/Owen-Mak/ParsePNum<br />
|https://github.com/PatMB30/DPS909Release01/pull/5, https://github.com/PatMB30/DPS909Release01/pull/6<br />
|https://makowen.wordpress.com/2018/02/19/mid-boss-servlet-deployment/<br />
| <br />
|-<br />
| 10<br />
|Oleh Hodovaniuk<br />
|https://github.com/ohodovaniuk1/parsephonenumbers<br />
|https://github.com/apetov/phoneparser-js/pull/11, https://github.com/apetov/phoneparser-js/pull/15<br />
|https://ohodovaniuk.wordpress.com/2018/02/12/release-1/<br />
|-<br />
| 11<br />
|Yuriy Kartuzov<br />
|https://github.com/YuriyKartuzov/Project<br />
|https://github.com/AbdulKabia/libphonenumber-osd600/pull/5, https://github.com/AbdulKabia/libphonenumber-osd600/pull/7<br />
|<br />
|-<br />
| 12<br />
|Abdul Kabia<br />
|https://github.com/AbdulKabia/libphonenumber-osd600<br />
|https://github.com/kqpham/phoneparser.js/pull/7,<br />
https://github.com/YuriyKartuzov/Project/pull/6<br />
|https://akkabia.wordpress.com/2018/02/02/play-time-with-google-googles-libphonenumber-library/<br />
|-<br />
| 13<br />
|Patrick Godbout<br />
|https://github.com/PatMB30/DPS909Release01<br />
|https://github.com/Owen-Mak/ParsePNum/pull/6, <br />
https://github.com/Owen-Mak/ParsePNum/pull/8<br />
|https://mb30myopensourceblog.blogspot.ca/2018/02/dps909-release-01-first-open-source.html<br />
|-<br />
| 14<br />
|Evan Davies<br />
|https://github.com/EmdaviesSeneca/PhoneNumberParse<br />
|https://github.com/kqpham/phoneparser.js/pull/9, https://github.com/Vimal-Raghubir/PhoneNumberAPI/pull/13<br />
|http://openthoughtsopensource.blogspot.ca/2018/02/osd600-01-release.html<br />
|-<br />
| 15<br />
|Lucas Verbeke<br />
|https://github.com/Micluc/phoneParser<br />
|https://github.com/TheKinshu/phonenumber-Parser/pull/7, https://github.com/TheKinshu/phonenumber-Parser/pull/8<br />
|https://thelucasexcerpt.wordpress.com/2018/02/20/osd600-release-1-lucas-verbeke<br />
|-<br />
| 16<br />
|Hongcheng Zhang<br />
|https://github.com/StevenZhang123/phonenumberparser-js<br />
|https://github.com/josechoy/phonenumber-api/pull/11, https://github.com/ohodovaniuk1/parsephonenumbers/pull/10<br />
|https://wordpress.com/post/hongcheng1993.wordpress.com/18<br />
|-<br />
| 17<br />
|Leandro Navarro<br />
|https://github.com/jlnavarro42/jsphoneparser<br />
|https://github.com/DanielHWYChang/DPS909_winter2018release1.0/pull/7,<br />
|<br />
|-<br />
| 19<br />
|Hao Chen<br />
|https://github.com/haoRchen/Phone-Number-Parser<br />
|https://github.com/Vimal-Raghubir/PhoneNumberAPI/pull/11, https://github.com/Vimal-Raghubir/PhoneNumberAPI/pull/12<br />
|https://medium.com/haorc/baby-steps-into-the-world-of-open-source-bad2f67e5<br />
|-<br />
| 20<br />
|Abel Simon Inocencio<br />
|https://github.com/simon-inoc/Open-Source<br />
|<br />
|<br />
|-<br />
| 21<br />
|Pranoy Santosh<br />
|https://github.com/pranoy10/dps909-assign1<br />
|https://github.com/kqpham/phoneparser.js/pull/6, <br />
https://github.com/buttersnipps/libphonenumberAPI/pull/5<br />
|http://pranoydps909.blogspot.ca/2018/02/assignment-1-dps909.html<br />
|-<br />
| 22<br />
|Daniel Chang<br />
|https://github.com/DanielHWYChang/DPS909_winter2018release1.0<br />
|<br />
|<br />
|-<br />
| 23<br />
|Vimal Raghubir<br />
|https://github.com/Vimal-Raghubir/PhoneNumberAPI<br />
|https://github.com/haoRchen/Phone-Number-Parser/pull/11, https://github.com/haoRchen/Phone-Number-Parser/pull/11<br />
|https://medium.com/@vraghubir/my-first-open-source-project-5667cbb69d8f<br />
|-<br />
| 24<br />
|Zukhruf Khan<br />
|https://github.com/zeddkay/node-libphonenumber-server<br />
|https://github.com/TheKinshu/phonenumber-Parser/pull/5, https://github.com/jlnavarro42/jsphoneparser/pull/3<br />
|https://zedsdps909blog.wordpress.com/2018/02/10/my-first-open-source-project/<br />
|<br />
|<br />
|-<br />
| 25<br />
|Liam Newell<br />
|https://github.com/hibyguy/Throwable-RESTful-API<br />
|https://github.com/YuriyKartuzov/Project/issues/2, https://github.com/mfainshtein2/phoneparser-js/issues/2<br />
|<br />
|-<br />
| 26<br />
|Joseph Pham<br />
|https://github.com/jpham14/phonenumberParser<br />
|https://github.com/Owen-Mak/ParsePNum/pull/7, https://github.com/jevuu/phoneNum/pull/2<br />
|https://jpham14.wordpress.com/2018/02/07/release-0-1/<br />
|-<br />
| 27<br />
|Aaron Scott<br />
|https://github.com/ARDScott/PhoneParser-NodeJs<br />
|<br />
|<br />
|-<br />
| 28<br />
|Jafar Frotan<br />
|https://github.com/a-one-d-one/libphonenumber-api-js<br />
|https://github.com/haoRchen/Phone-Number-Parser/issues/3<br />
|https://medium.com/@jaf.frotan/into-the-light-with-code-40d38bae54d5<br />
|-<br />
| 29<br />
|Michael Fainshtein<br />
|https://github.com/mfainshtein2/phoneparser-js<br />
|https://github.com/TheKinshu/phonenumber-Parser/pull/11<br />
https://github.com/apetov/phoneparser-js/pull/14<br />
|<br />
|-<br />
| 30<br />
|Alex Wang<br />
|https://github.com/AlexWang-16/webservice-phonelibrary<br />
|https://github.com/hibyguy/Throwable-RESTful-API/pull/8, https://github.com/hibyguy/Throwable-RESTful-API/pull/9<br />
|https://alexopensource.wordpress.com/2018/02/10/first-pull-request-to-an-open-source-project/<br />
|-<br />
| 31<br />
|Qiliang Chen<br />
|https://github.com/KignorChan/libnumberWebServer<br />
|https://github.com/josechoy/phonenumber-api/pull/5<br />
https://github.com/josechoy/phonenumber-api/pull/10<br />
|https://qchen102.blogspot.ca/2018/02/tutorial-create-restful-web-server.html<br />
https://qchen102.blogspot.ca/2018/02/debugging-open-source-api-review.html<br />
|-<br />
| 32<br />
|Michael Kavidas<br />
|https://github.com/mkavidas/libphonenumber-ASP-.Net<br />
|<br />
|<br />
|-<br />
| 33<br />
|Evan Marinzel<br />
|https://github.com/ermarinz/pNumAPI<br />
|https://github.com/ohodovaniuk1/parsephonenumbers/pull/9, https://github.com/DanielHWYChang/DPS909_winter2018release1.0/pull/8<br />
|<br />
|-<br />
| 34<br />
|Justin Vuu<br />
|https://github.com/jevuu/phoneNum<br />
|<br />
|<br />
|-<br />
| 35<br />
| Soutrik Barua<br />
| https://github.com/buttersnipps/libphonenumberAPI<br />
| <br />
| https://soutrikbarua.blogspot.ca/<br />
|-<br />
| 36<br />
| Kevin Pham<br />
| https://github.com/kqpham/phoneparser.js<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD600_and_DPS909_Winter_2018_Lab_3&diff=131701OSD600 and DPS909 Winter 2018 Lab 32018-02-20T04:42:41Z<p>Aushakou: /* 3. Blog */</p>
<hr />
<div>=Fixing a Bug In VSCode=<br />
<br />
This week we've been looking at how one approaches fixing a bug in a project like VSCode, see https://github.com/humphd/vscode/tree/good-first-experience-issue-42726#walkthrough-fixing-a-bug-in-visual-studio-code.<br />
<br />
In this Lab, you are asked to continue your practice of these techniques, and try researching a fix to an existing bug.<br />
<br />
A few instructions before you begin:<br />
<br />
* You must have already completed [[DPS909/OSD600 Winter 2018 Lab 2|Lab 2]]<br />
* You '''may''' work in pairs/groups for this lab, but you '''must each''' do your own write up<br />
* You are '''not''' required to fully fix your bug and submit a pull request. This lab is about research, and learning the techniques and tooling only.<br />
* If you '''do''' fix your bug, and want to submit a pull request, please speak with me so we can co-ordinate your work with other students (i.e., so people don't take opportunities from one another).<br />
<br />
==1. Pick your Bug(s)==<br />
<br />
From the list of available VSCode Issues on GitHub, you can work on any [https://github.com/Microsoft/vscode/labels/bug bug] you like (i.e., has the 'bug' label). Here are some suggestions of bugs that might be worth considering:<br />
<br />
* https://github.com/Microsoft/vscode/issues/16834 Search in folder with special characters `{}` yields no results.<br />
* https://github.com/Microsoft/vscode/issues/26956 Can't find files starting with `./` on MacOS<br />
* https://github.com/Microsoft/vscode/issues/43302 Opening .bat file in VSCode via context menu in windows explorer tries to execute it<br />
* https://github.com/Microsoft/vscode/issues/42720 Color picker: no longer appears in settings editor<br />
* https://github.com/Microsoft/vscode/issues/35245 Markdown references links don't handle escapes<br />
* https://github.com/Microsoft/vscode/issues/39406<br />
I opened some big number of files (), tried to search in them with Ctrl-Shift-F, but I got a message: spawn ENAMETOOLONG<br />
* https://github.com/Microsoft/vscode/issues/34367 Markdown formatting of notifications<br />
* https://github.com/Microsoft/vscode/issues/31600 File Watcher missing external changes<br />
<br />
Pick one or more bugs to work on during this lab. It's OK if other people are working on the same bug, since you're not required to submit a pull request, only do the research.<br />
<br />
==2. Research, Debug, and Try to Understand the Bug==<br />
<br />
After choosing your bug(s), try to recreate them in your dev build of vscode. What is your bug all about? Can you confirm that the bug exists? Can you reproduce it? You might have to do some work to alter your environment in order to get the bug to occur.<br />
<br />
Try to figure out where the code is that relates to this bug. Use the Debugger, search through files in GitHub and git, look at other Issues and Pull Requests (especially closed ones) which may have code or other clues.<br />
<br />
See if you can narrow down what is likely causing this bug.<br />
<br />
It's OK if you can't. Keep track of all your research, guesses, what you tried, what worked, what didn't, questions you have, ideas you're exploring, etc. We'll need all that info for your blog post.<br />
<br />
If you get really stuck, consider switching to a different bug from the list above. Don't waste a lot of time lost on a bug you can't solve. Make sure you're making progress, or switching tracks if you're stuck.<br />
<br />
==3. Can you Fix it? ==<br />
<br />
After you do your research and start to locate the code related to the problem, see if you can make a fix. Your fix can be a simple one, it doesn't have to be perfect at this point: we're doing research.<br />
<br />
What did you fix? What happened when you did? Did your fix correct the bug? Did it break anything else (other parts of the app, the tests, etc)?<br />
<br />
Keep track of what you do. <br />
<br />
==3. Blog==<br />
<br />
Write a blog post about your experience researching and fixing a bug in VSCode. Some things you could discuss in your post:<br />
<br />
* Which bug(s) did you work on?<br />
* What was this bug about? How do you make it happen (steps to reproduce)?<br />
* What did you do to try and track down the cause? How close did you get?<br />
* What tools, techniques, approaches did you take when researching? What worked well, what didn't?<br />
* Were you able to do a fix? What did you change? Did it work for all cases, or was it just a start?<br />
* What did you learn while doing this? What kinds of things did you notice in the code that were surprising or new to you?<br />
<br />
Please add a line for your blog in the following table:<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! VSCode Bug(s) (URLs)<br />
! Blog Post (URL)<br />
|-<br />
| 1<br />
|Liam Newell<br />
|https://github.com/Microsoft/vscode/issues/42720<br />
|http://liamnewell.me/blog/bugs/Lab-3-First-bug-analysis/<br />
|-<br />
| 2<br />
| Matthew Quan<br />
| https://github.com/Microsoft/vscode/issues/38232<br />
|<br />
|-<br />
| 3<br />
|Aliaksandr Ushakou<br />
|https://github.com/Microsoft/vscode/issues/43465<br />
|https://aushakou.wordpress.com/2018/02/20/researching-and-trying-to-fix-a-bug-in-vs-code/<br />
|-<br />
| 4<br />
|<br />
|<br />
|<br />
|-<br />
| 5<br />
|<br />
|<br />
|<br />
|-<br />
| 6<br />
|<br />
|<br />
|<br />
|-<br />
| 7<br />
|<br />
|<br />
|<br />
|-<br />
| 8<br />
|<br />
|<br />
|<br />
|-<br />
| 9<br />
|<br />
|<br />
|<br />
|-<br />
| 10<br />
|<br />
|<br />
|<br />
|-<br />
| 11<br />
|<br />
|<br />
|<br />
|-<br />
| 12<br />
|<br />
|<br />
|<br />
|-<br />
| 13<br />
|<br />
|<br />
|<br />
|-<br />
| 14<br />
|<br />
|<br />
|<br />
|-<br />
| 15<br />
|<br />
|<br />
|<br />
|-<br />
| 16<br />
|<br />
|<br />
|<br />
|-<br />
| 17<br />
|<br />
|<br />
|<br />
|-<br />
| 18<br />
|<br />
|<br />
|<br />
|-<br />
| 19<br />
|<br />
|<br />
|<br />
|-<br />
| 20<br />
|<br />
|<br />
|<br />
|-<br />
| 21<br />
|<br />
|<br />
|<br />
|-<br />
| 22<br />
|<br />
|<br />
|<br />
|-<br />
| 23<br />
|<br />
|<br />
|<br />
|-<br />
| 24<br />
|<br />
|<br />
|<br />
|-<br />
| 25<br />
|<br />
|<br />
|<br />
|-<br />
| 26<br />
|<br />
|<br />
|<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.1&diff=131670OSD & DPS909 Winter 2018 Release 0.12018-02-19T18:25:43Z<p>Aushakou: /* 4. Submission */</p>
<hr />
<div>=0.1 Release=<br />
<br />
==Introduction==<br />
<br />
You are asked to create an open source [https://stackoverflow.com/questions/671118/what-exactly-is-restful-programming RESTful API] web service that can find and extract phone numbers from submitted resources, and be used in a [https://en.wikipedia.org/wiki/Microservices microservice architecture]. See below for details about how the API should function.<br />
<br />
Your first release will be due in multiple stages:<br />
<br />
* Part A: Create an initial, partial implementation, due '''Feb 1 by midnight'''<br />
* Part B: Contribute to another student's implementation, due '''Feb 19 by midnight'''<br />
<br />
The goal of this first release is to practice, and make sure you are comfortable with common open source workflows, including:<br />
<br />
* using git and GitHub<br />
* managing GitHub repositories<br />
* creating common project and build artifacts in an open source repo (e.g., LICENSE, Readme.md, automation, etc)<br />
* working with third-party dependencies<br />
* creating and responding to Issues<br />
* creating Pull Requests<br />
* reviewing and merging Pull Requests<br />
* the differences between being a maintainer and a contributor in an open source project<br />
<br />
==API Description==<br />
<br />
Phone numbers seem like a simple thing to work with at first, but it gets [https://github.com/googlei18n/libphonenumber/blob/master/FALSEHOODS.md complicated quickly]. Thankfully, the problem of working with phone numbers anywhere on Earth has already been solved by Google, and the code made open source:<br />
<br />
https://github.com/googlei18n/libphonenumber<br />
<br />
You are asked to use libphonenumber to create a web service, using whatever programming language you want. Your web server must support the following API endpoints, which all return [https://en.wikipedia.org/wiki/JSON JSON formatted] responses:<br />
<br />
1. <code>GET /api/phonenumbers/parse/text/{...string...}</code> to allow sending small snippets of text to be parsed.<br />
<br />
For example, requesting <code>/api/phonenumbers/parse/text/nothing</code> should return an empty list <code>[]</code>. Whereas requesting requesting <code>/api/phonenumbers/parse/text/Seneca%20Phone%20Number%3A%20416-491-5050</code> should return a list with a single, formatted phone number <code>["(416) 491-5050"]</code>.<br />
<br />
2. <code>POST /api/phonenumbers/parse/file</code> with the request's <code>Content-Type</code> being <code>text/plain</code> and the <code>body</code> containing a base64 encoded text file. This allows larger files to be processed, in addition to small bits of text.<br />
<br />
All responses from the API should be given in JSON format, with the exception of errors, which can use HTTP status codes (e.g., [https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors 4xx codes]).<br />
<br />
Phone numbers returned from any of the endpoints above should not be duplicated. That is, if a given input includes a phone number more than once, you should only return one copy of it. <br />
<br />
==Part A Requirements==<br />
<br />
Create a new GitHub repo for your web service. Pick an open source license for your code, making sure it is compatible with <code>libphonenumber</code> and any other dependencies you use. Make sure your repo has both a LICENSE and README.md file, and that your README.md has clear instructions on how to use your code.<br />
<br />
Using any programming language you like, write a server that implements the API described above. You must also include '''tests''' to prove that your server implements the API correctly. These tests need to be runnable from the command-line. You may use any testing framework, and test runner you like.<br />
<br />
File some '''Issues''' in your repo for enhancements that you'd like to see done to your server. Here are some suggestions, but feel free to file anything you like for fixes/enhancements you need:<br />
<br />
# Write more tests to deal with various edge cases<br />
# Add support for parsing a resource at a given URL: <code>GET /api/phonenumbers/url/http%3A%2F%2Fexample.com%2F</code> would cause the server to load the content at http://example.com and parse it for phone numbers.<br />
# Add support for parsing MS Word docs. There are lots of existing open source projects that can help parse a Word doc into Text, which can then be parsed by your earlier code<br />
# Add support for parsing PDF files. There are lots of existing open source projects that can help parse a PDF into Text, which can then be parsed by your earlier code<br />
# Add support for parsing images. Use an OCR (e.g., https://github.com/tesseract-ocr/tesseract or http://tesseract.projectnaptha.com/) tool to first extract text from the image, then parse it as you did earlier<br />
# Add automatic linting to the code, using something like [https://eslint.org/ eslint]. Linters find bugs and style issues.<br />
# Add an example client (e.g., web page) that can be used to manually test the API with various types of inputs<br />
# Add support for running the server on a [https://devcenter.heroku.com/start cloud service like Heroku]<br />
# Add automatic continuous integration (CI) via [https://travis-ci.org/ TravisCI], [https://circleci.com/ CircleCI], etc.<br />
<br />
Make sure your repo has all your code and tests completed before moving to Part B.<br />
<br />
==Part B Requirements==<br />
<br />
Find another student's repo and pick '''two Issues''' you'd like to work on, or file your own to fix things you notice are broken. Leave a comment in the issues to let others know that you're working on this (NOTE: only 1 student can work on an issue at a time).<br />
<br />
Fork this other student's repo, and create a clone of it. Make a branch for each of the issues you want to fix. For example, if you are fixing Issue 12, create a new branch named '''issue12''': <code>git checkout -b issue12 master</code>. Now fix the code and create a Pull Request to get your changes added.<br />
<br />
==4. Submission==<br />
<br />
All submissions are done electronically via GitHub and your blog. Please add info to the table below when you are done one of the sections.<br />
<br />
Part A: after you have created your repo, added your code and tests, and filed some issues, add your repo URL.<br />
<br />
Part B: include URLs to two PRs you made to other student's repos.<br />
<br />
Blog Post: after Part A and B are done, do your blog post. Your final blog post should discuss the following:<br />
<br />
* What did you build? Discuss your web service (e.g., what is its name, how does it work, etc.) and include links so people can find it.<br />
* What was your process for doing this assignment?<br />
* Which language, dependencies, and tools did you use? Why did you choose them?<br />
* What did you find challenging about your work?<br />
* Compare the experience of being a maintainer to that of contributing to someone else's project. Which did you enjoy more? Why?<br />
* What did you learn as you did this work?<br />
* What do you still want to learn more about in subsequent releases?<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Part A (GitHub Repo URL)<br />
! style="font-weight: bold;" | Part B (GitHub PR URLs)<br />
! style="font-weight: bold;" | Blog Post (URL)<br />
|-<br />
| 1<br />
| Bakytzhan (Jean) Apetov<br />
| https://github.com/apetov/phoneparser-js<br />
| https://github.com/alexglazkov9/phonenumberparser-js/pull/7, https://github.com/alexglazkov9/phonenumberparser-js/pull/8<br />
| https://bapetov.wordpress.com/2018/02/14/open-source-project-0-1-release/<br />
|-<br />
| 2<br />
| Yalong Li<br />
| https://github.com/yalooong/phonenumber-parser<br />
| https://github.com/haoRchen/Phone-Number-Parser/pull/10, https://github.com/zeddkay/node-libphonenumber-server/pull/5<br />
| https://yalongxyz.blogspot.ca/2018/02/contributing-for-open-souce-projects-to.html<br />
|-<br />
| 3<br />
| Woodson Delhia<br />
| https://github.com/Woody88/haskell-phonenumbers<br />
|<br />
|<br />
|-<br />
| 4<br />
| Matthew Quan<br />
| https://github.com/irrationalRock/Release1<br />
| https://github.com/simon-inoc/Open-Source/pull/2, https://github.com/apetov/phoneparser-js/pull/10, https://github.com/yalooong/phonenumber-parser/pull/8<br />
| https://mattprogrammingblog.wordpress.com/2018/02/13/osd600-release-1/<br />
|-<br />
| 5<br />
| Aleksey Glazkov<br />
| https://github.com/alexglazkov9/phonenumberparser-js<br />
|<br />
|<br />
|-<br />
| 6<br />
| Aliaksandr Ushakou<br />
| https://github.com/aushakou/phoneparser-restful-service<br />
| https://github.com/alexglazkov9/phonenumberparser-js/pull/9, https://github.com/alexglazkov9/phonenumberparser-js/pull/10<br />
|<br />
|-<br />
| 7<br />
| Kelvin Cho<br />
| https://github.com/TheKinshu/phonenumber-Parser<br />
|<br />
|<br />
|-<br />
| 8<br />
| Zhihao Cai<br />
| https://github.com/josechoy/phonenumber-api<br />
|<br />
|<br />
|-<br />
| 9<br />
|Owen Mak<br />
|https://github.com/Owen-Mak/ParsePNum<br />
|https://github.com/PatMB30/DPS909Release01/pull/5, https://github.com/PatMB30/DPS909Release01/pull/6<br />
|https://makowen.wordpress.com/2018/02/19/mid-boss-servlet-deployment/<br />
| <br />
|-<br />
| 10<br />
|Oleh Hodovaniuk<br />
|https://github.com/ohodovaniuk1/parsephonenumbers<br />
|https://github.com/apetov/phoneparser-js/pull/11, https://github.com/apetov/phoneparser-js/pull/15<br />
|<br />
|-<br />
| 11<br />
|Yuriy Kartuzov<br />
|https://github.com/YuriyKartuzov/Project<br />
|https://github.com/AbdulKabia/libphonenumber-osd600/pull/5, https://github.com/AbdulKabia/libphonenumber-osd600/pull/7<br />
|<br />
|-<br />
| 12<br />
|Abdul Kabia<br />
|https://github.com/AbdulKabia/libphonenumber-osd600<br />
|https://github.com/kqpham/phoneparser.js/pull/7,<br />
https://github.com/YuriyKartuzov/Project/pull/6<br />
|https://akkabia.wordpress.com/2018/02/02/play-time-with-google-googles-libphonenumber-library/<br />
|-<br />
| 13<br />
|Patrick Godbout<br />
|https://github.com/PatMB30/DPS909Release01<br />
|https://github.com/Owen-Mak/ParsePNum/pull/6, <br />
https://github.com/Owen-Mak/ParsePNum/pull/8<br />
|https://mb30myopensourceblog.blogspot.ca/2018/02/dps909-release-01-first-open-source.html<br />
|-<br />
| 14<br />
|Evan Davies<br />
|https://github.com/EmdaviesSeneca/PhoneNumberParse<br />
|<br />
|<br />
|-<br />
| 15<br />
|Lucas Verbeke<br />
|https://github.com/Micluc/phoneParser<br />
|https://github.com/TheKinshu/phonenumber-Parser/pull/7, https://github.com/TheKinshu/phonenumber-Parser/pull/8<br />
|<br />
|-<br />
| 16<br />
|Hongcheng Zhang<br />
|https://github.com/StevenZhang123/phonenumberparser-js<br />
|<br />
|<br />
|-<br />
| 17<br />
|Leandro Navarro<br />
|https://github.com/jlnavarro42/jsphoneparser<br />
|https://github.com/DanielHWYChang/DPS909_winter2018release1.0/pull/7,<br />
|<br />
|-<br />
| 19<br />
|Hao Chen<br />
|https://github.com/haoRchen/Phone-Number-Parser<br />
|https://github.com/Vimal-Raghubir/PhoneNumberAPI/pull/11, https://github.com/Vimal-Raghubir/PhoneNumberAPI/pull/12<br />
|https://medium.com/haorc/baby-steps-into-the-world-of-open-source-bad2f67e5<br />
|-<br />
| 20<br />
|Abel Simon Inocencio<br />
|https://github.com/simon-inoc/Open-Source<br />
|<br />
|<br />
|-<br />
| 21<br />
|Pranoy Santosh<br />
|https://github.com/pranoy10/dps909-assign1<br />
|https://github.com/kqpham/phoneparser.js/pull/6, https://github.com/buttersnipps/libphonenumberAPI/pull/5<br />
|<br />
|-<br />
| 22<br />
|Daniel Chang<br />
|https://github.com/DanielHWYChang/DPS909_winter2018release1.0<br />
|<br />
|<br />
|-<br />
| 23<br />
|Vimal Raghubir<br />
|https://github.com/Vimal-Raghubir/PhoneNumberAPI<br />
|<br />
|<br />
|-<br />
| 24<br />
|Zukhruf Khan<br />
|https://github.com/zeddkay/node-libphonenumber-server<br />
|https://github.com/TheKinshu/phonenumber-Parser/pull/5, https://github.com/jlnavarro42/jsphoneparser/pull/3<br />
|https://zedsdps909blog.wordpress.com/2018/02/10/my-first-open-source-project/<br />
|<br />
|<br />
|-<br />
| 25<br />
|Liam Newell<br />
|https://github.com/hibyguy/Throwable-RESTful-API<br />
|https://github.com/YuriyKartuzov/Project/issues/2, https://github.com/mfainshtein2/phoneparser-js/issues/2<br />
|<br />
|-<br />
| 26<br />
|Joseph Pham<br />
|https://github.com/jpham14/phonenumberParser<br />
|https://github.com/Owen-Mak/ParsePNum/pull/7<br />
|<br />
|-<br />
| 27<br />
|Aaron Scott<br />
|https://github.com/ARDScott/PhoneParser-NodeJs<br />
|<br />
|<br />
|-<br />
| 28<br />
|Jafar Frotan<br />
|https://github.com/a-one-d-one/libphonenumber-api-js<br />
|<br />
|<br />
|-<br />
| 29<br />
|Michael Fainshtein<br />
|https://github.com/mfainshtein2/phoneparser-js<br />
|<br />
|<br />
|-<br />
| 30<br />
|Alex Wang<br />
|https://github.com/AlexWang-16/webservice-phonelibrary<br />
|https://github.com/hibyguy/Throwable-RESTful-API/pull/8, https://github.com/hibyguy/Throwable-RESTful-API/pull/9<br />
|https://alexopensource.wordpress.com/2018/02/10/first-pull-request-to-an-open-source-project/<br />
|-<br />
| 31<br />
|Qiliang Chen<br />
|https://github.com/KignorChan/libnumberWebServer<br />
|https://github.com/josechoy/phonenumber-api/pull/5<br />
https://github.com/josechoy/phonenumber-api/pull/10<br />
|<br />
|-<br />
| 32<br />
|Michael Kavidas<br />
|https://github.com/mkavidas/libphonenumber-ASP-.Net<br />
|<br />
|<br />
|-<br />
| 33<br />
|Evan Marinzel<br />
|https://github.com/ermarinz/pNumAPI<br />
|<br />
|<br />
|-<br />
| 34<br />
|Justin Vuu<br />
|https://github.com/jevuu/phoneNum<br />
|<br />
|<br />
|-<br />
| 35<br />
| Soutrik Barua<br />
| https://github.com/buttersnipps/libphonenumberAPI<br />
| <br />
| https://soutrikbarua.blogspot.ca/<br />
|-<br />
| 36<br />
| Kevin Pham<br />
| https://github.com/kqpham/phoneparser.js<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.1&diff=131514OSD & DPS909 Winter 2018 Release 0.12018-02-15T06:05:38Z<p>Aushakou: /* 4. Submission */</p>
<hr />
<div>=0.1 Release=<br />
<br />
==Introduction==<br />
<br />
You are asked to create an open source [https://stackoverflow.com/questions/671118/what-exactly-is-restful-programming RESTful API] web service that can find and extract phone numbers from submitted resources, and be used in a [https://en.wikipedia.org/wiki/Microservices microservice architecture]. See below for details about how the API should function.<br />
<br />
Your first release will be due in multiple stages:<br />
<br />
* Part A: Create an initial, partial implementation, due '''Feb 1 by midnight'''<br />
* Part B: Contribute to another student's implementation, due '''Feb 19 by midnight'''<br />
<br />
The goal of this first release is to practice, and make sure you are comfortable with common open source workflows, including:<br />
<br />
* using git and GitHub<br />
* managing GitHub repositories<br />
* creating common project and build artifacts in an open source repo (e.g., LICENSE, Readme.md, automation, etc)<br />
* working with third-party dependencies<br />
* creating and responding to Issues<br />
* creating Pull Requests<br />
* reviewing and merging Pull Requests<br />
* the differences between being a maintainer and a contributor in an open source project<br />
<br />
==API Description==<br />
<br />
Phone numbers seem like a simple thing to work with at first, but it gets [https://github.com/googlei18n/libphonenumber/blob/master/FALSEHOODS.md complicated quickly]. Thankfully, the problem of working with phone numbers anywhere on Earth has already been solved by Google, and the code made open source:<br />
<br />
https://github.com/googlei18n/libphonenumber<br />
<br />
You are asked to use libphonenumber to create a web service, using whatever programming language you want. Your web server must support the following API endpoints, which all return [https://en.wikipedia.org/wiki/JSON JSON formatted] responses:<br />
<br />
1. <code>GET /api/phonenumbers/parse/text/{...string...}</code> to allow sending small snippets of text to be parsed.<br />
<br />
For example, requesting <code>/api/phonenumbers/parse/text/nothing</code> should return an empty list <code>[]</code>. Whereas requesting requesting <code>/api/phonenumbers/parse/text/Seneca%20Phone%20Number%3A%20416-491-5050</code> should return a list with a single, formatted phone number <code>["(416) 491-5050"]</code>.<br />
<br />
2. <code>POST /api/phonenumbers/parse/file</code> with the request's <code>Content-Type</code> being <code>text/plain</code> and the <code>body</code> containing a base64 encoded text file. This allows larger files to be processed, in addition to small bits of text.<br />
<br />
All responses from the API should be given in JSON format, with the exception of errors, which can use HTTP status codes (e.g., [https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors 4xx codes]).<br />
<br />
Phone numbers returned from any of the endpoints above should not be duplicated. That is, if a given input includes a phone number more than once, you should only return one copy of it. <br />
<br />
==Part A Requirements==<br />
<br />
Create a new GitHub repo for your web service. Pick an open source license for your code, making sure it is compatible with <code>libphonenumber</code> and any other dependencies you use. Make sure your repo has both a LICENSE and README.md file, and that your README.md has clear instructions on how to use your code.<br />
<br />
Using any programming language you like, write a server that implements the API described above. You must also include '''tests''' to prove that your server implements the API correctly. These tests need to be runnable from the command-line. You may use any testing framework, and test runner you like.<br />
<br />
File some '''Issues''' in your repo for enhancements that you'd like to see done to your server. Here are some suggestions, but feel free to file anything you like for fixes/enhancements you need:<br />
<br />
# Write more tests to deal with various edge cases<br />
# Add support for parsing a resource at a given URL: <code>GET /api/phonenumbers/url/http%3A%2F%2Fexample.com%2F</code> would cause the server to load the content at http://example.com and parse it for phone numbers.<br />
# Add support for parsing MS Word docs. There are lots of existing open source projects that can help parse a Word doc into Text, which can then be parsed by your earlier code<br />
# Add support for parsing PDF files. There are lots of existing open source projects that can help parse a PDF into Text, which can then be parsed by your earlier code<br />
# Add support for parsing images. Use an OCR (e.g., https://github.com/tesseract-ocr/tesseract or http://tesseract.projectnaptha.com/) tool to first extract text from the image, then parse it as you did earlier<br />
# Add automatic linting to the code, using something like [https://eslint.org/ eslint]. Linters find bugs and style issues.<br />
# Add an example client (e.g., web page) that can be used to manually test the API with various types of inputs<br />
# Add support for running the server on a [https://devcenter.heroku.com/start cloud service like Heroku]<br />
# Add automatic continuous integration (CI) via [https://travis-ci.org/ TravisCI], [https://circleci.com/ CircleCI], etc.<br />
<br />
Make sure your repo has all your code and tests completed before moving to Part B.<br />
<br />
==Part B Requirements==<br />
<br />
Find another student's repo and pick '''two Issues''' you'd like to work on, or file your own to fix things you notice are broken. Leave a comment in the issues to let others know that you're working on this (NOTE: only 1 student can work on an issue at a time).<br />
<br />
Fork this other student's repo, and create a clone of it. Make a branch for each of the issues you want to fix. For example, if you are fixing Issue 12, create a new branch named '''issue12''': <code>git checkout -b issue12 master</code>. Now fix the code and create a Pull Request to get your changes added.<br />
<br />
==4. Submission==<br />
<br />
All submissions are done electronically via GitHub and your blog. Please add info to the table below when you are done one of the sections.<br />
<br />
Part A: after you have created your repo, added your code and tests, and filed some issues, add your repo URL.<br />
<br />
Part B: include URLs to two PRs you made to other student's repos.<br />
<br />
Blog Post: after Part A and B are done, do your blog post. Your final blog post should discuss the following:<br />
<br />
* What did you build? Discuss your web service (e.g., what is its name, how does it work, etc.) and include links so people can find it.<br />
* What was your process for doing this assignment?<br />
* Which language, dependencies, and tools did you use? Why did you choose them?<br />
* What did you find challenging about your work?<br />
* Compare the experience of being a maintainer to that of contributing to someone else's project. Which did you enjoy more? Why?<br />
* What did you learn as you did this work?<br />
* What do you still want to learn more about in subsequent releases?<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Part A (GitHub Repo URL)<br />
! style="font-weight: bold;" | Part B (GitHub PR URLs)<br />
! style="font-weight: bold;" | Blog Post (URL)<br />
|-<br />
| 1<br />
| Bakytzhan (Jean) Apetov<br />
| https://github.com/apetov/phoneparser-js<br />
| https://github.com/alexglazkov9/phonenumberparser-js/pull/7, https://github.com/alexglazkov9/phonenumberparser-js/pull/8<br />
| https://bapetov.wordpress.com/2018/02/14/open-source-project-0-1-release/<br />
|-<br />
| 2<br />
| Yalong Li<br />
| https://github.com/yalooong/phonenumber-parser<br />
| https://github.com/haoRchen/Phone-Number-Parser/pull/10, https://github.com/zeddkay/node-libphonenumber-server/pull/5<br />
| https://yalongxyz.blogspot.ca/2018/02/contributing-for-open-souce-projects-to.html<br />
|-<br />
| 3<br />
| Woodson Delhia<br />
| https://github.com/Woody88/haskell-phonenumbers<br />
|<br />
|<br />
|-<br />
| 4<br />
| Matthew Quan<br />
| https://github.com/irrationalRock/Release1<br />
| https://github.com/simon-inoc/Open-Source/pull/2, https://github.com/apetov/phoneparser-js/pull/10, https://github.com/yalooong/phonenumber-parser/pull/8<br />
| https://mattprogrammingblog.wordpress.com/2018/02/13/osd600-release-1/<br />
|-<br />
| 5<br />
| Aleksey Glazkov<br />
| https://github.com/alexglazkov9/phonenumberparser-js<br />
|<br />
|<br />
|-<br />
| 6<br />
| Aliaksandr Ushakou<br />
| https://github.com/aushakou/phoneparser-restful-service<br />
| https://github.com/alexglazkov9/phonenumberparser-js/pull/9<br />
|<br />
|-<br />
| 7<br />
| Kelvin Cho<br />
| https://github.com/TheKinshu/phonenumber-Parser<br />
|<br />
|<br />
|-<br />
| 8<br />
| Zhihao Cai<br />
| https://github.com/josechoy/phonenumber-api<br />
|<br />
|<br />
|-<br />
| 9<br />
| Owen Mak<br />
| https://github.com/Owen-Mak/ParsePNum<br />
| https://github.com/PatMB30/DPS909Release01/pull/5<br />
|<br />
|-<br />
| 10<br />
|Oleh Hodovaniuk<br />
|https://github.com/ohodovaniuk1/parsephonenumbers<br />
|https://github.com/apetov/phoneparser-js/pull/11<br />
|<br />
|-<br />
| 11<br />
|Yuriy Kartuzov<br />
|https://github.com/YuriyKartuzov/Project<br />
|<br />
|<br />
|-<br />
| 12<br />
|Abdul Kabia<br />
|https://github.com/AbdulKabia/libphonenumber-osd600<br />
|<br />
|<br />
|-<br />
| 13<br />
|Patrick Godbout<br />
|https://github.com/PatMB30/DPS909Release01<br />
|https://github.com/Owen-Mak/ParsePNum/pull/6<br />
|<br />
|-<br />
| 14<br />
|Evan Davies<br />
|https://github.com/EmdaviesSeneca/PhoneNumberParse<br />
|<br />
|<br />
|-<br />
| 15<br />
|Lucas Verbeke<br />
|https://github.com/Micluc/phoneParser<br />
|<br />
|<br />
|-<br />
| 16<br />
|Hongcheng Zhang<br />
|https://github.com/StevenZhang123/phonenumberparser-js<br />
|<br />
|<br />
|-<br />
| 17<br />
|Leandro Navarro<br />
|https://github.com/jlnavarro42/jsphoneparser<br />
|<br />
|<br />
|-<br />
| 19<br />
|Hao Chen<br />
|https://github.com/haoRchen/Phone-Number-Parser<br />
|https://github.com/Vimal-Raghubir/PhoneNumberAPI/pull/11, https://github.com/Vimal-Raghubir/PhoneNumberAPI/pull/12<br />
|https://medium.com/haorc/baby-steps-into-the-world-of-open-source-bad2f67e5<br />
|-<br />
| 20<br />
|Abel Simon Inocencio<br />
|https://github.com/simon-inoc/Open-Source<br />
|<br />
|<br />
|-<br />
| 21<br />
|Pranoy Santosh<br />
|https://github.com/pranoy10/dps909-assign1<br />
|https://github.com/kqpham/phoneparser.js/pull/6<br />
|<br />
|-<br />
| 22<br />
|Daniel Chang<br />
|https://github.com/DanielHWYChang/DPS909_winter2018release1.0<br />
|<br />
|<br />
|-<br />
| 23<br />
|Vimal Raghubir<br />
|https://github.com/Vimal-Raghubir/PhoneNumberAPI<br />
|<br />
|<br />
|-<br />
| 24<br />
|Zukhruf Khan<br />
|https://github.com/zeddkay/node-libphonenumber-server<br />
|https://github.com/TheKinshu/phonenumber-Parser/pull/5, https://github.com/jlnavarro42/jsphoneparser/pull/3<br />
|https://zedsdps909blog.wordpress.com/2018/02/10/my-first-open-source-project/<br />
|<br />
|<br />
|-<br />
| 25<br />
|Liam Newell<br />
|https://github.com/hibyguy/Throwable-RESTful-API<br />
|<br />
|<br />
|-<br />
| 26<br />
|Joseph Pham<br />
|https://github.com/jpham14/phonenumberParser<br />
|https://github.com/Owen-Mak/ParsePNum/pull/7<br />
|<br />
|-<br />
| 27<br />
|Aaron Scott<br />
|https://github.com/ARDScott/PhoneParser-NodeJs<br />
|<br />
|<br />
|-<br />
| 28<br />
|Jafar Frotan<br />
|https://github.com/a-one-d-one/libphonenumber-api-js<br />
|<br />
|<br />
|-<br />
| 29<br />
|Michael Fainshtein<br />
|https://github.com/mfainshtein2/phoneparser-js<br />
|<br />
|<br />
|-<br />
| 30<br />
|Alex Wang<br />
|https://github.com/AlexWang-16/webservice-phonelibrary<br />
|https://github.com/hibyguy/Throwable-RESTful-API/pull/8, https://github.com/hibyguy/Throwable-RESTful-API/pull/9<br />
|https://alexopensource.wordpress.com/2018/02/10/first-pull-request-to-an-open-source-project/<br />
|-<br />
| 31<br />
|Qiliang Chen<br />
|https://github.com/KignorChan/libnumberWebServer<br />
|https://github.com/josechoy/phonenumber-api/pull/5<br />
|<br />
|-<br />
| 32<br />
|Michael Kavidas<br />
|https://github.com/mkavidas/libphonenumber-ASP-.Net<br />
|<br />
|<br />
|-<br />
| 33<br />
|Evan Marinzel<br />
|https://github.com/ermarinz/pNumAPI<br />
|<br />
|<br />
|-<br />
| 34<br />
|Justin Vuu<br />
|https://github.com/jevuu/phoneNum<br />
|<br />
|<br />
|-<br />
| 35<br />
| Soutrik Barua<br />
| https://github.com/buttersnipps/libphonenumberAPI<br />
| <br />
| https://soutrikbarua.blogspot.ca/<br />
|-<br />
| 36<br />
| Kevin Pham<br />
| https://github.com/kqpham/phoneparser.js<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909/OSD600_Winter_2018_Lab_2&diff=131513DPS909/OSD600 Winter 2018 Lab 22018-02-15T06:03:06Z<p>Aushakou: /* 3. Blog */</p>
<hr />
<div>=Working on Large Open Source Projects=<br />
<br />
Working on open source projects means working with large and often complex code-bases, custom build systems and test harnesses, using new technologies and tools, and using new workflows. The more you do this, the better you'll get at it.<br />
<br />
We'll work with a variety of large open source projects in order to practice. Today we will begin with Microsoft's open source editor, [https://code.visualstudio.com/ Visual Studio Code]<br />
<br />
==1. Install Visual Studio Code (as a user)==<br />
<br />
VSCode is one of the most popular editors in use today. It works on all platforms, and has an excellent set of extensions for solving common development problems. It's also free and open source.<br />
<br />
Begin by installing VSCode and set it up as a user. Take a look at the [https://code.visualstudio.com/docs docs] and find some extensions to install, and get your settings configured.<br />
<br />
Throughout this course, it is recommended that you use VSCode for your work.<br />
<br />
==2. Install Visual Studio Code (as a dev)==<br />
<br />
If you want to contribute to VSCode (fix bugs, add features), you have to build the code from source instead of only downloading it. Follow these steps to accomplish this:<br />
<br />
# Read the contributing instructions at https://github.com/Microsoft/vscode/wiki/How-to-Contribute<br />
# '''Fork''' https://github.com/Microsoft/vscode on GitHub, so you have a copy<br />
# '''Clone''' your fork locally<br />
# Add a '''remote''' for Microsoft's repo: <code>git remote add upstream git@github.com:Microsoft/vscode.git</code><br />
# Make sure you can '''build, run, test, debug''' VSCode on your local machine<br />
<br />
As you follow these steps, keep track of any problems you encounter, steps you follow, and things you learn. We'll use those to blog about our experience later on.<br />
<br />
==3. Related Technologies ==<br />
<br />
VSCode is a desktop application written using web technologies. It uses a number of popular open source projects, including:<br />
<br />
* TypeScript<br />
* Electron<br />
* node.js<br />
* eslint<br />
* tslint<br />
* gulp<br />
* mocha<br />
* sinon<br />
* yarn<br />
<br />
Research each of the above, and make sure you are familiar with them. Make sure you have a general knowledge of what each one is about, where to find more information (docs), etc. We will be fixing bugs in this code starting next week, and it's important that you have a working build and general understanding of the technologies involved.<br />
<br />
==3. Blog==<br />
<br />
Write a blog post about your experience getting started with VSCode. Some things you could discuss in your post:<br />
<br />
* Which extensions did you install? Why did you choose them? What do they do?<br />
* Which settings did you change? Why?<br />
* Did you have an issues trying to get VSCode built from source?<br />
* What about running the tests?<br />
* How about live debugging?<br />
* What did you find out about the related technologies used by VSCode? For example: what are TypeScript and Electron?<br />
<br />
Please add a line for your blog in the following table:<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! GitHub Fork of VSCode (repo URL)<br />
! Blog Post (URL)<br />
|-<br />
| 1<br />
| Example Name<br />
| https://github.com/humphd/vscode<br />
| https://examplestudent.wordpress.com/2018/02/05/working-with-vscode/<br />
|-<br />
| 2<br />
| Yalong Li<br />
| https://github.com/yalooong/vscode<br />
| https://yalongxyz.blogspot.ca/2018/02/building-vscode.html<br />
|-<br />
| 3<br />
| Matthew Quan<br />
| https://github.com/irrationalRock/vscode<br />
| https://mattprogrammingblog.wordpress.com/2018/02/10/osd600-lab-2-building-vscode/<br />
|-<br />
| 4<br />
| Bakytzhan Apetov<br />
| https://github.com/apetov/vscode<br />
| https://bapetov.wordpress.com/2018/02/12/installing-vs-code-from-source/<br />
|-<br />
| 5<br />
| Alex Wang<br />
| https://github.com/AlexWang-16/vscode<br />
|<br />
|-<br />
| 6<br />
| Woodson Delhia<br />
| https://github.com/Woody88/vscode<br />
| https://woodsondelhia.wordpress.com/2018/02/12/forking-installing-vscode-project/<br />
|-<br />
| 7<br />
| Joseph Pham<br />
| https://github.com/jpham14/vscode<br />
|<br />
|-<br />
| 8<br />
| Yuriy Kartuzov<br />
| https://github.com/YuriyKartuzov/vscode<br />
|<br />
|-<br />
| 9<br />
| Patrick Godbout<br />
| https://github.com/PatMB30/vscode<br />
| https://mb30myopensourceblog.blogspot.ca/2018/02/introduction-with-vscode-extensions.html<br />
|-<br />
| 10<br />
| Owen Mak<br />
| https://github.com/Owen-Mak/vscode<br />
| https://makowen.wordpress.com/2018/02/12/first-encounter-building-vscode/<br />
|-<br />
| 11<br />
|Oleh Hodovaniuk<br />
|https://github.com/ohodovaniuk1/vscode<br />
|https://ohodovaniuk.wordpress.com/2018/02/12/osd600-lab-2-visual-studio-code/<br />
|-<br />
| 12<br />
|Evan Marinzel<br />
|https://github.com/ermarinz/vscode<br />
|https://marinsdevspace.wordpress.com/2018/02/14/a-closer-look-at-microsoft-vscode/<br />
|-<br />
| 13<br />
|Pranoy Santosh<br />
|https://github.com/pranoy10/vscode<br />
|http://pranoydps909.blogspot.ca/2018/02/working-is-vs-code-source.html<br />
|-<br />
| 14<br />
|Soutrik Barua<br />
|https://github.com/buttersnipps/vscode<br />
|http://soutrikbarua.blogspot.ca/2018/02/my-journey-with-visual-studio-code.html<br />
|-<br />
| 15<br />
|Qiliang Chen<br />
|https://github.com/KignorChan/vscode<br />
|https://qchen102.blogspot.ca/2018/02/visual-studio-code-developer-edition.html<br />
|-<br />
| 16<br />
|Zukhruf Khan<br />
|https://github.com/zeddkay/vscode<br />
|https://zedsdps909blog.wordpress.com/2018/02/13/installing-visual-studio-code-again/<br />
|-<br />
| 17<br />
|Hao Chen<br />
|https://github.com/haoRchen/vscode<br />
|https://medium.com/haorc/setting-up-vscode-for-future-contributions-cf579afd83f8<br />
|-<br />
| 18<br />
|Aliaksandr Ushakou<br />
|https://github.com/aushakou/vscode<br />
|https://aushakou.wordpress.com/2018/02/15/getting-started-with-vs-code-as-a-developer/<br />
|-<br />
| 19<br />
|<br />
|<br />
|<br />
|-<br />
| 20<br />
|<br />
|<br />
|<br />
|-<br />
| 21<br />
|<br />
|<br />
|<br />
|-<br />
| 22<br />
|<br />
|<br />
|<br />
|-<br />
| 23<br />
|<br />
|<br />
|<br />
|-<br />
| 24<br />
|<br />
|<br />
|<br />
|-<br />
| 25<br />
|<br />
|<br />
|<br />
|-<br />
| 26<br />
|<br />
|<br />
|<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909/OSD600_Winter_2018_Lab_1&diff=131313DPS909/OSD600 Winter 2018 Lab 12018-02-06T04:28:15Z<p>Aushakou: /* Submission */</p>
<hr />
<div>=Start blogging=<br />
<br />
The "open" in "Open Source" means more than just that the code is available. Real open source is open in terms of its process, too: open source is about working in the open. A big part of working in the open is writing about that work, teaching one another things we discover as we go, and helping to draw attention to important ideas. Blogging is a major part of open source, and we'll use our blogs to write, discuss, debate, announce, plan, and learn.<br />
<br />
Open source also values writing like this for the historical perspective it gives. Long after project or code decisions are made, we often need and want to go back and understand why things happened as they did. Blogging contributes to the historical record.<br />
<br />
Finally, blogging provides a way to capture our hard word and contributions. When students are applying for jobs, it's helpful to have something they can point to, in order to showcase their previous work. By keeping a blog now, you help build a record of your abilities, experience, and contributions. <br />
<br />
Having your own blog will enable you to more easily join the global open source community. A blog gives you a voice, which you can use when and how you want. <br />
<br />
You will be required to keep a weekly blog for the duration of the course. We'll use this blog to share what we're learning, discuss open source, submit our labs and releases, etc.<br />
<br />
In this lab you will create, configure, and use your blog for the first time.<br />
<br />
==1. Pick a Blogging Platform==<br />
<br />
If you already have a blog, you're free to use it (skip to the next section). If you don't, there are a number of free, popular blogging platforms you can use:<br />
<br />
* [https://www.blogger.com/about/?r=1-null_user Blogger]<br />
* [https://wordpress.com/ Wordpress]<br />
* [https://medium.com/ Medium]<br />
<br />
Take a look at the different options and choose one you like. Create an account for yourself.<br />
<br />
==2. Create a tag for "Open Source" posts==<br />
<br />
Blogging platforms allow you to tag your posts (sometimes called a "category," or a "feed"). This allows you to syndicate posts you've written on a given topic without also including others (e.g., you might want to write about "Open Source" and "Baseball" in the same blog).<br />
<br />
Create a blog post that introduces yourself (it can be short), and add an "Open Source" tag/category/feed. Each platform is slightly different in terms of how you do this.<br />
<br />
==3. Create a CDOT Wiki account==<br />
<br />
For various aspects of the course, including this lab, you will need to be able to edit this wiki. Make sure you have an account, or [https://wiki.cdot.senecacollege.ca/wiki/Special:RequestAccount request one].<br />
<br />
==4. Add your "Open Source" RSS feed to the CDOT Planet==<br />
<br />
We automatically aggregate all the blogs of our students and faculty who are working on open source at Seneca, and publish it to http://zenit.senecac.on.ca/~chris.tyler/planet/ (aka, Planet CDOT). Add your own blog's "open source" feed by following the instructions at the [[Planet CDOT Feed List]].<br />
<br />
==5. Write a post about an Open Source Project==<br />
<br />
Pick an open source project that you find interesting and write an introductory post. You can find thousands of projects on Github:<br />
<br />
* [https://github.com/explore Explore project showcases]<br />
* [https://github.com/trending Trending projects]<br />
<br />
Here are some ideas you can use to research and write about the project you choose:<br />
<br />
* What is it called?<br />
* What is the project about? What problem does it solve?<br />
* How old is it? When did it start?<br />
* Which websites are associated with it (e.g., does it have a separate site beyond Github?)<br />
* What language(s) is it written in?<br />
* How many open Issues does it have?<br />
* How many people have contributed to the code?<br />
* Who is using the project? What are they doing with it?<br />
<br />
Your post doesn't have to be long--a few paragraphs is enough. It should serve as a gentle introduction to the project, and include links to get someone started who wants to learn more.<br />
<br />
==Submission==<br />
<br />
You will have completed your lab when your blog post from Step 5 appears on the [http://zenit.senecac.on.ca/~chris.tyler/planet/ CDOT Planet site]. I will mark them as they appear there.<br />
<br />
Please add a line for your blog in the following table:<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! Blog (URL)<br />
! First Blog Post (URL)<br />
|-<br />
| 1<br />
| Example Name<br />
| https://examplestudent.wordpress.com<br />
| https://examplestudent.wordpress.com/2017/09/05/first-open-source-post/<br />
|-<br />
| 2<br />
| Patrick Godbout<br />
| http://mb30myopensourceblog.blogspot.ca/<br />
| http://mb30myopensourceblog.blogspot.ca/2018/01/introduction-post.html<br />
|-<br />
| 3<br />
| Zukhruf Khan<br />
| https://zedsdps909blog.wordpress.com/<br />
| https://zedsdps909blog.wordpress.com/2018/01/23/my-first-blog-post/<br />
|-<br />
| 4<br />
| Aliaksandr Ushakou<br />
| https://aushakou.wordpress.com/<br />
| https://aushakou.wordpress.com/2018/02/06/open-source-project-animate-css/<br />
|-<br />
| 5<br />
| Joseph Pham<br />
| https://jpham14.wordpress.com/<br />
| https://jpham14.wordpress.com/2018/01/25/lab-1-peertube/<br />
|-<br />
| 6<br />
| Alex Wang<br />
| https://alexopensource.wordpress.com/<br />
| https://alexopensource.wordpress.com/2018/01/23/first-blog-post/<br />
|-<br />
| 7<br />
| Matthew Quan<br />
| https://mattprogrammingblog.wordpress.com/<br />
| https://mattprogrammingblog.wordpress.com/2018/01/26/osd-lab-1-highlighting-an-open-source-project/<br />
|-<br />
| 8<br />
| Hao Chen<br />
| https://medium.com/feed/haorc/tagged/opensource<br />
| https://medium.com/haorc/entitas-for-unity-93d9b83d29c9<br />
|-<br />
| 9<br />
| Evan Davies<br />
| https://openthoughtsopensource.blogspot.ca/<br />
| https://openthoughtsopensource.blogspot.ca/2018/01/introduction.html<br />
|-<br />
| 10<br />
| Liam Newell<br />
| http://liamnewell.me/blog<br />
| http://liamnewell.me/blog/coding/First-opensource-blog-post/<br />
|-<br />
| 11<br />
| Bakytzhan (Jean) Apetov<br />
| https://bapetov.wordpress.com<br />
| https://bapetov.wordpress.com/2018/01/25/first-post-open-source-asp-net-core/<br />
|-<br />
| 12<br />
|Oleh Hodovaniuk<br />
|https://ohodovaniuk.wordpress.com/<br />
|https://ohodovaniuk.wordpress.com/2018/01/27/osd600-exploring-the-open-source-project-swift/<br />
|-<br />
| 13<br />
|Vimal Raghubir<br />
|https://medium.com/@vraghubir<br />
|https://medium.com/@vraghubir/kubernetes-c4337591515f<br />
|-<br />
| 14<br />
|Yalong Li<br />
|https://yalongxyz.blogspot.ca/<br />
|https://yalongxyz.blogspot.ca/2018/01/my-first-post.html<br />
|-<br />
| 15<br />
|Abdul Kabia<br />
|https://akkabia.wordpress.com/<br />
|https://akkabia.wordpress.com/2018/01/25/first-blog-post/<br />
|-<br />
| 16<br />
|Qiliang Chen<br />
|https://qchen102.blogspot.ca/<br />
|https://qchen102.blogspot.ca/2018/01/first-post.html<br />
|-<br />
| 17<br />
|Owen Mak<br />
|https://makowen.wordpress.com/<br />
|https://makowen.wordpress.com/2018/01/30/first-official-blog/<br />
|-<br />
| 18<br />
|Simon Inocencio<br />
|https://haxbyte.wordpress.com/<br />
|https://haxbyte.wordpress.com/2018/02/04/oh-crud-its-my-0th-post-what-open-source-frameworks-have-i-used-in-the-past-and-what-are-my-experiences-with-them-part-1/<br />
|<br />
|-<br />
| 19<br />
|Leandro Navarro<br />
|https://leandroosdblog.wordpress.com/<br />
|https://leandroosdblog.wordpress.com/2018/01/25/introduction/<br />
|-<br />
| 20<br />
|Zhihao Cai<br />
|https://choyzhihao.wordpress.com/<br />
|https://choyzhihao.wordpress.com/2018/01/30/soundnode-app-open-source-project/<br />
|-<br />
| 21<br />
|Justin Vuu<br />
|https://justosd.wordpress.com/<br />
|justosd.wordpress.com/2018/01/31/parable-of-the-polygons/<br />
|-<br />
| 22<br />
|Woodson Delhia<br />
|https://woodsondelhia.wordpress.com/<br />
|https://woodsondelhia.wordpress.com/2018/01/31/functional-programming-for-web<br />
|-<br />
| 23<br />
|Kelvin Cho<br />
|https://klvincho.wordpress.com/<br />
|https://klvincho.wordpress.com/2018/01/31/osd600-lab-1/<br />
|-<br />
| 24<br />
|Daniel Chang<br />
|http://danielchangopen.blogspot.ca/<br />
|http://danielchangopen.blogspot.ca/2018/01/lab-1-look-around-open-source-projects.html<br />
|-<br />
| 25<br />
|Yuriy Kartuzov<br />
|https://yuriykartuzov.wordpress.com/<br />
|https://yuriykartuzov.wordpress.com/2018/02/01/first/<br />
|-<br />
| 26<br />
|Hongcheng Zhang<br />
|https://hongcheng1993.wordpress.com<br />
|https://hongcheng1993.wordpress.com/2018/02/01/first-post-for-open-source/<br />
|-<br />
| 27<br />
|Kevin Pham<br />
|http://kqpham2.blogspot.ca<br />
|http://kqpham2.blogspot.ca/2018/02/introduction.html<br />
|-<br />
| 28<br />
|Pranoy Santosh<br />
|https://pranoydps909.blogspot.ca/<br />
|https://pranoydps909.blogspot.ca/2018/02/introduction-dps909.html<br />
|-<br />
| 29<br />
|Michael Fainshtein<br />
|https://moderatelyokaydeveloper.wordpress.com<br />
|https://moderatelyokaydeveloper.wordpress.com/2018/02/05/lab-1-opencv/<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=OSD_%26_DPS909_Winter_2018_Release_0.1&diff=131098OSD & DPS909 Winter 2018 Release 0.12018-01-30T06:29:12Z<p>Aushakou: /* 4. Submission */</p>
<hr />
<div>=0.1 Release=<br />
<br />
==Introduction==<br />
<br />
You are asked to create an open source [https://stackoverflow.com/questions/671118/what-exactly-is-restful-programming RESTful API] web service that can find and extract phone numbers from submitted resources, and be used in a [https://en.wikipedia.org/wiki/Microservices microservice architecture]. See below for details about how the API should function.<br />
<br />
Your first release will be due in multiple stages:<br />
<br />
* Part A: Create an initial, partial implementation, due '''Feb 1 by midnight'''<br />
* Part B: Contribute to another student's implementation, due '''Feb 19 by midnight'''<br />
<br />
The goal of this first release is to practice, and make sure you are comfortable with common open source workflows, including:<br />
<br />
* using git and GitHub<br />
* managing GitHub repositories<br />
* creating common project and build artifacts in an open source repo (e.g., LICENSE, Readme.md, automation, etc)<br />
* working with third-party dependencies<br />
* creating and responding to Issues<br />
* creating Pull Requests<br />
* reviewing and merging Pull Requests<br />
* the differences between being a maintainer and a contributor in an open source project<br />
<br />
==API Description==<br />
<br />
Phone numbers seem like a simple thing to work with at first, but it gets [https://github.com/googlei18n/libphonenumber/blob/master/FALSEHOODS.md complicated quickly]. Thankfully, the problem of working with phone numbers anywhere on Earth has already been solved by Google, and the code made open source:<br />
<br />
https://github.com/googlei18n/libphonenumber<br />
<br />
You are asked to use libphonenumber to create a web service, using whatever programming language you want. Your web server must support the following API endpoints, which all return [https://en.wikipedia.org/wiki/JSON JSON formatted] responses:<br />
<br />
1. <code>GET /api/phonenumbers/parse/text/{...string...}</code> to allow sending small snippets of text to be parsed.<br />
<br />
For example, requesting <code>/api/phonenumbers/parse/text/nothing</code> should return an empty list <code>[]</code>. Whereas requesting requesting <code>/api/phonenumbers/parse/text/Seneca%20Phone%20Number%3A%20416-491-5050</code> should return a list with a single, formatted phone number <code>["(416) 491-5050"]</code>.<br />
<br />
2. <code>POST /api/phonenumbers/parse/file</code> with the request's <code>Content-Type</code> being <code>text/plain</code> and the <code>body</code> containing a base64 encoded text file. This allows larger files to be processed, in addition to small bits of text.<br />
<br />
All responses from the API should be given in JSON format, with the exception of errors, which can use HTTP status codes (e.g., [https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors 4xx codes]).<br />
<br />
Phone numbers returned from any of the endpoints above should not be duplicated. That is, if a given input includes a phone number more than once, you should only return one copy of it. <br />
<br />
==Part A Requirements==<br />
<br />
Create a new GitHub repo for your web service. Pick an open source license for your code, making sure it is compatible with <code>libphonenumber</code> and any other dependencies you use. Make sure your repo has both a LICENSE and README.md file, and that your README.md has clear instructions on how to use your code.<br />
<br />
Using any programming language you like, write a server that implements the API described above. You must also include '''tests''' to prove that your server implements the API correctly. These tests need to be runnable from the command-line. You may use any testing framework, and test runner you like.<br />
<br />
File some '''Issues''' in your repo for enhancements that you'd like to see done to your server. Here are some suggestions, but feel free to file anything you like for fixes/enhancements you need:<br />
<br />
# Write more tests to deal with various edge cases<br />
# Add support for parsing a resource at a given URL: <code>GET /api/phonenumbers/url/http%3A%2F%2Fexample.com%2F</code> would cause the server to load the content at http://example.com and parse it for phone numbers.<br />
# Add support for parsing MS Word docs. There are lots of existing open source projects that can help parse a Word doc into Text, which can then be parsed by your earlier code<br />
# Add support for parsing PDF files. There are lots of existing open source projects that can help parse a PDF into Text, which can then be parsed by your earlier code<br />
# Add support for parsing images. Use an OCR (e.g., https://github.com/tesseract-ocr/tesseract or http://tesseract.projectnaptha.com/) tool to first extract text from the image, then parse it as you did earlier<br />
# Add automatic linting to the code, using something like [https://eslint.org/ eslint]. Linters find bugs and style issues.<br />
# Add an example client (e.g., web page) that can be used to manually test the API with various types of inputs<br />
# Add support for running the server on a [https://devcenter.heroku.com/start cloud service like Heroku]<br />
# Add automatic continuous integration (CI) via [https://travis-ci.org/ TravisCI], [https://circleci.com/ CircleCI], etc.<br />
<br />
Make sure your repo has all your code and tests completed before moving to Part B.<br />
<br />
==Part B Requirements==<br />
<br />
Find another student's repo and pick '''two Issues''' you'd like to work on, or file your own to fix things you notice are broken. Leave a comment in the issues to let others know that you're working on this (NOTE: only 1 student can work on an issue at a time).<br />
<br />
Fork this other student's repo, and create a clone of it. Make a branch for each of the issues you want to fix. For example, if you are fixing Issue 12, create a new branch named '''issue12''': <code>git checkout -b issue12 master</code>. Now fix the code and create a Pull Request to get your changes added.<br />
<br />
==4. Submission==<br />
<br />
All submissions are done electronically via GitHub and your blog. Please add info to the table below when you are done one of the sections.<br />
<br />
Part A: after you have created your repo, added your code and tests, and filed some issues, add your repo URL.<br />
<br />
Part B: include URLs to two PRs you made to other student's repos.<br />
<br />
Blog Post: after Part A and B are done, do your blog post. Your final blog post should discuss the following:<br />
<br />
* What did you build? Discuss your web service (e.g., what is its name, how does it work, etc.) and include links so people can find it.<br />
* What was your process for doing this assignment?<br />
* Which language, dependencies, and tools did you use? Why did you choose them?<br />
* What did you find challenging about your work?<br />
* Compare the experience of being a maintainer to that of contributing to someone else's project. Which did you enjoy more? Why?<br />
* What did you learn as you did this work?<br />
* What do you still want to learn more about in subsequent releases?<br />
<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | #<br />
! style="font-weight: bold;" | Name<br />
! style="font-weight: bold;" | Part A (GitHub Repo URL)<br />
! style="font-weight: bold;" | Part B (GitHub PR URLs)<br />
! style="font-weight: bold;" | Blog Post (URL)<br />
|-<br />
| 1<br />
| Bakytzhan (Jean) Apetov<br />
| https://github.com/apetov/phoneparser-js<br />
|<br />
|<br />
|-<br />
| 2<br />
| Yalong Li<br />
| https://github.com/yalooong/phonenumber-parser<br />
|<br />
|<br />
|-<br />
| 3<br />
| Woodson Delhia<br />
| https://github.com/Woody88/haskell-phonenumbers<br />
|<br />
|<br />
|-<br />
| 4<br />
| Matthew Quan<br />
| https://github.com/irrationalRock/Release1<br />
|<br />
|<br />
|-<br />
| 5<br />
| Aleksey Glazkov<br />
| https://github.com/alexglazkov9/phonenumberparser-js<br />
|<br />
|<br />
|-<br />
| 6<br />
| Aliaksandr Ushakou<br />
| https://github.com/aushakou/phoneparser-restful-service<br />
|<br />
|<br />
|-<br />
| 7<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 8<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 9<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 10<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 11<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 12<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 13<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 14<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 15<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 16<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 17<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 19<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 20<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 21<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 22<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 23<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 24<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 25<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 26<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909/OSD600_Winter_2018_Lab_1&diff=130937DPS909/OSD600 Winter 2018 Lab 12018-01-25T18:54:05Z<p>Aushakou: /* Submission */</p>
<hr />
<div>=Start blogging=<br />
<br />
The "open" in "Open Source" means more than just that the code is available. Real open source is open in terms of its process, too: open source is about working in the open. A big part of working in the open is writing about that work, teaching one another things we discover as we go, and helping to draw attention to important ideas. Blogging is a major part of open source, and we'll use our blogs to write, discuss, debate, announce, plan, and learn.<br />
<br />
Open source also values writing like this for the historical perspective it gives. Long after project or code decisions are made, we often need and want to go back and understand why things happened as they did. Blogging contributes to the historical record.<br />
<br />
Finally, blogging provides a way to capture our hard word and contributions. When students are applying for jobs, it's helpful to have something they can point to, in order to showcase their previous work. By keeping a blog now, you help build a record of your abilities, experience, and contributions. <br />
<br />
Having your own blog will enable you to more easily join the global open source community. A blog gives you a voice, which you can use when and how you want. <br />
<br />
You will be required to keep a weekly blog for the duration of the course. We'll use this blog to share what we're learning, discuss open source, submit our labs and releases, etc.<br />
<br />
In this lab you will create, configure, and use your blog for the first time.<br />
<br />
==1. Pick a Blogging Platform==<br />
<br />
If you already have a blog, you're free to use it (skip to the next section). If you don't, there are a number of free, popular blogging platforms you can use:<br />
<br />
* [https://www.blogger.com/about/?r=1-null_user Blogger]<br />
* [https://wordpress.com/ Wordpress]<br />
* [https://medium.com/ Medium]<br />
<br />
Take a look at the different options and choose one you like. Create an account for yourself.<br />
<br />
==2. Create a tag for "Open Source" posts==<br />
<br />
Blogging platforms allow you to tag your posts (sometimes called a "category," or a "feed"). This allows you to syndicate posts you've written on a given topic without also including others (e.g., you might want to write about "Open Source" and "Baseball" in the same blog).<br />
<br />
Create a blog post that introduces yourself (it can be short), and add an "Open Source" tag/category/feed. Each platform is slightly different in terms of how you do this.<br />
<br />
==3. Create a CDOT Wiki account==<br />
<br />
For various aspects of the course, including this lab, you will need to be able to edit this wiki. Make sure you have an account, or [https://wiki.cdot.senecacollege.ca/wiki/Special:RequestAccount request one].<br />
<br />
==4. Add your "Open Source" RSS feed to the CDOT Planet==<br />
<br />
We automatically aggregate all the blogs of our students and faculty who are working on open source at Seneca, and publish it to http://zenit.senecac.on.ca/~chris.tyler/planet/ (aka, Planet CDOT). Add your own blog's "open source" feed by following the instructions at the [[Planet CDOT Feed List]].<br />
<br />
==5. Write a post about an Open Source Project==<br />
<br />
Pick an open source project that you find interesting and write an introductory post. You can find thousands of projects on Github:<br />
<br />
* [https://github.com/explore Explore project showcases]<br />
* [https://github.com/trending Trending projects]<br />
<br />
Here are some ideas you can use to research and write about the project you choose:<br />
<br />
* What is it called?<br />
* What is the project about? What problem does it solve?<br />
* How old is it? When did it start?<br />
* Which websites are associated with it (e.g., does it have a separate site beyond Github?)<br />
* What language(s) is it written in?<br />
* How many open Issues does it have?<br />
* How many people have contributed to the code?<br />
* Who is using the project? What are they doing with it?<br />
<br />
Your post doesn't have to be long--a few paragraphs is enough. It should serve as a gentle introduction to the project, and include links to get someone started who wants to learn more.<br />
<br />
==Submission==<br />
<br />
You will have completed your lab when your blog post from Step 5 appears on the [http://zenit.senecac.on.ca/~chris.tyler/planet/ CDOT Planet site]. I will mark them as they appear there.<br />
<br />
Please add a line for your blog in the following table:<br />
<br />
{| class="wikitable"<br />
! #<br />
! Name<br />
! Blog (URL)<br />
! First Blog Post (URL)<br />
|-<br />
| 1<br />
| Example Name<br />
| https://examplestudent.wordpress.com<br />
| https://examplestudent.wordpress.com/2017/09/05/first-open-source-post/<br />
|-<br />
| 2<br />
| Patrick Godbout<br />
| http://mb30myopensourceblog.blogspot.ca/<br />
| http://mb30myopensourceblog.blogspot.ca/2018/01/introduction-post.html<br />
|-<br />
| 3<br />
| Zukhruf Khan<br />
| https://zedsdps909blog.wordpress.com/<br />
| https://zedsdps909blog.wordpress.com/2018/01/23/my-first-blog-post/<br />
|-<br />
| 4<br />
| Aliaksandr Ushakou<br />
| https://aushakou.wordpress.com/<br />
| https://aushakou.wordpress.com/2018/01/25/introduction/<br />
|-<br />
| 5<br />
|<br />
|<br />
|<br />
|-<br />
| 6<br />
|<br />
|<br />
|<br />
|-<br />
| 7<br />
|<br />
|<br />
|<br />
|-<br />
| 8<br />
|<br />
|<br />
|<br />
|-<br />
| 9<br />
|<br />
|<br />
|<br />
|-<br />
| 10<br />
|<br />
|<br />
|<br />
|-<br />
| 11<br />
|<br />
|<br />
|<br />
|-<br />
| 12<br />
|<br />
|<br />
|<br />
|-<br />
| 13<br />
|<br />
|<br />
|<br />
|-<br />
| 14<br />
|<br />
|<br />
|<br />
|-<br />
| 15<br />
|<br />
|<br />
|<br />
|-<br />
| 16<br />
|<br />
|<br />
|<br />
|-<br />
| 17<br />
|<br />
|<br />
|<br />
|-<br />
| 18<br />
|<br />
|<br />
|<br />
|-<br />
| 19<br />
|<br />
|<br />
|<br />
|-<br />
| 20<br />
|<br />
|<br />
|<br />
|-<br />
| 21<br />
|<br />
|<br />
|<br />
|-<br />
| 22<br />
|<br />
|<br />
|<br />
|-<br />
| 23<br />
|<br />
|<br />
|<br />
|-<br />
| 24<br />
|<br />
|<br />
|<br />
|-<br />
| 25<br />
|<br />
|<br />
|<br />
|-<br />
| 26<br />
|<br />
|<br />
|<br />
|-<br />
| 27<br />
|<br />
|<br />
|<br />
|-<br />
| 28<br />
|<br />
|<br />
|<br />
|-<br />
| 29<br />
|<br />
|<br />
|<br />
|-<br />
| 30<br />
|<br />
|<br />
|<br />
|-<br />
| 31<br />
|<br />
|<br />
|<br />
|-<br />
| 32<br />
|<br />
|<br />
|<br />
|-<br />
| 33<br />
|<br />
|<br />
|<br />
|-<br />
| 34<br />
|<br />
|<br />
|<br />
|-<br />
| 35<br />
|<br />
|<br />
|<br />
|-<br />
| 36<br />
|<br />
|<br />
|<br />
|-<br />
| 37<br />
|<br />
|<br />
|<br />
|-<br />
| 38<br />
|<br />
|<br />
|<br />
|-<br />
| 39<br />
|<br />
|<br />
|<br />
|-<br />
| 40<br />
|<br />
|<br />
|<br />
|-</div>Aushakouhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Planet_CDOT_Feed_List&diff=130936Planet CDOT Feed List2018-01-25T18:49:02Z<p>Aushakou: /* Feeds */</p>
<hr />
<div>= Introduction =<br />
<br />
Seneca students and faculty working on open source related projects and research, as well as some faculty, students, and researchers from other institutions, use [http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT] to aggregate their blogs. This page contains the information about who is blogging in [http://www.planetplanet.org/ Planet Feed Reader format] and serves as the feed configuration for the planet.<br />
<br />
If you do not have an existing blog, you can open a free account at [http://wordpress.com/ Wordpress.com] or [https://www.blogger.com/ Blogger.com] or you can set up your own blog software such as [http://www.s9y.org Serendipity].<br />
<br />
'''Note:''' Additions to the feed list will not take effect until they are merged into the Planet configuration, which is an automatic process scheduled at regular intervals. If you add a feed and do not see it picked up in the Planet within three hours, please check your feed entry carefully and then contact [[User:Chris Tyler|Chris Tyler]] .<br />
<br />
= IMPORTANT NOTICE =<br />
<br />
{{Admon/caution|The Internet has a Long Memory / Posts may be Permanent!|Blogs which are included in the Planet CDOT Feed List will have their content aggregated into Planet CDOT. They will also be mentioned (automatically) on the Planet CDOT Twitter account, and may also be picked up by other RSS feed aggregators, seach engines, and caches. It will be difficult or impossible to delete all mentions of a post at a later date. Be aware of the long memory of the Internet when posting!}}<br />
<br />
= Requirements =<br />
<br />
* Blog postings fed to the planet must conform to the [[Blog Guidelines]].<br />
* Feeds that are inactive for a significant period of time may get deleted from this list.<br />
<br />
= Using a Tagged/Category Feed =<br />
<br />
A tagged or category feed includes only articles that are tagged with particular keywords or placed in a particular topic category. This can be useful for sending only selected posts to the planet.<br />
<br />
These are the URL formats for tagged or category feeds on popular blogging services/software:<br />
<br />
* [http://www.wordpress.com Wordpress]: <code><nowiki>[http://</nowiki>''blog-user-name''.wordpress.com/category/''category-name''/feed/]</code><br />
* [http://blogger.com Blogger]: <code><nowiki>[http://</nowiki>''blog-user-name''.blogspot.com/feeds/posts/default/-/''category-name'']</code><br />
* [http://s9y.org Serendipity]: <code><nowiki>[http://</nowiki>''blog-main-url''/index.php?/feeds/categories/''cateogrynumber''-''categoryname'']</code><br />
<br />
= Feed Info Format =<br />
<br />
You can add your blog's [http://en.wikipedia.org/wiki/RSS_(file_format) RSS feed] at the end of the list below by specifying the following:<br />
<br />
# The URL to your blog's open source Atom or [http://en.wikipedia.org/wiki/RSS_(file_format) RSS Feed] (i.e., a category or tag). NOTE: Please do not put the URL to your blog -- use the URL for your feed. Please do not use the feed for your entire blog (unless your blog contains only open source-related postings). We only want open source related content.<br />
# Your name as you want it to appear in the list of names for the planet<br />
# Optionally, a URL to a [http://en.wikipedia.org/wiki/Hackergotchi hackergotchi] ([http://wouterverhelst.livejournal.com/21322.html how to]). Your picture should be an 65x85 PNG with a transparent background.<br />
<br />
= Feeds =<br />
<br />
<pre><br />
[http://sp0009.blogspot.ca/feeds/posts/default/-/spo600]<br />
name = ShlokKumar Purani<br />
<br />
[https://giorgiosadze.wordpress.com/category/spo600-osd600/feed]<br />
name = Giorgi Osadze<br />
<br />
[https://mattirrationalprogramming.wordpress.com/category/spo600-osd600/feed]<br />
name = Matthew Quan<br />
<br />
[https://opensourcetoronto.wordpress.com/category/open-source/feed/]<br />
name = Hans van den Pol<br />
<br />
[https://ppatel221.wordpress.com/category/open-source/feed/]<br />
name = Parthkumar Patel<br />
<br />
[https://anthonylomagno.wordpress.com/category/open-source-development/feed/]<br />
name = Anthony LoMagno<br />
<br />
[https://achimienti.wordpress.com/category/spo600/feed]<br />
name = Adam Chimienti<br />
<br />
[https://mrrajevski.wordpress.com/category/spo600/feed]<br />
name = Matt Rajevski<br />
<br />
[https://svitlanagalianova.blogspot.ca/feeds/posts/default/]<br />
name = Svitlana Galianova<br />
<br />
[https://firefoxmacblog.wordpress.com/category/open-source/feed/]<br />
name = Fateh Sandhu<br />
<br />
[https://gblogs2017.wordpress.com/category/open-source/feed/]<br />
name = Gaurav Verma<br />
<br />
[https://ohodovaniuk.wordpress.com/feed/]<br />
name = Oleh Hodovaniuk<br />
<br />
[https://www.jielselmani.me/blog?category=Open+Source&format=rss]<br />
name = Jiel Selmani<br />
<br />
[http://www.danepstein.ca/category/open-source/feed]<br />
name = Dan Epstein<br />
<br />
[https://edyedyschool.tumblr.com/rss]<br />
name = Eduardo Sorozabal<br />
<br />
[http://mkavidas.wordpress.com/category/OSD/feed/]<br />
name = Michael Kavidas<br />
<br />
[https://sgupta44blog.wordpress.com/tag/open-source/feed/]<br />
name = Shivam Gupta<br />
<br />
[https://dsych.wordpress.com/category/DPS909/feed/]<br />
name=Dmytro Sych<br />
<br />
[https://mordax.github.com/atom.xml]<br />
name = Maya Filipp<br />
<br />
[https://medium.com/feed/haorc/tagged/opensource]<br />
name = Hao Chen<br />
<br />
[https://medium.com/feed/seanprashad/tagged/opensource]<br />
name = Sean Prashad<br />
<br />
[https://dps909blog.wordpress.com/category/Open-Source/feed/]<br />
name=Xiao Lei Huang<br />
<br />
[https://cgsingh.wordpress.com/category/osd600/feed/]<br />
name=Christopher Singh<br />
<br />
[https://shivgajiwala.blogspot.ca/]<br />
name=Shiv Gajiwala<br />
<br />
[http://jgoguette.wordpress.com/category/open-source/feed]<br />
name=Jerry Goguette<br />
<br />
[https://theoduleblog.wordpress.com/category/school/dps909/feed/]<br />
name = Theo D <br />
<br />
[https://rahul3guptablog.wordpress.com/category/dps909/feed/]<br />
name = Rahul Gupta<br />
<br />
[https://ebraublog.wordpress.com/category/CDOT/feed/]<br />
name = Eric Brauer<br />
<br />
[http://hcoelho.com/blog/feed]<br />
name = Henrique Coelho<br />
<br />
[https://npolugari.wordpress.com/feed/]<br />
name = Nagashashank<br />
<br />
[https://vishnuhacks.wordpress.com/category/spo600/feed/]<br />
name = Vishnu Santhosh Kumar<br />
<br />
[https://jamesshin37.wordpress.com/feed/]<br />
name = James Shin<br />
<br />
[http://donaldtn.blogspot.com/feeds/posts/default/-/spo600]<br />
name=Donald Nguyen<br />
<br />
[https://senecaram.wordpress.com/feed/]<br />
name=Ramanan Manokaran<br />
<br />
[https://jlasob.wordpress.com/tag/SPO600/feed]<br />
name=Jayme Laso-Barros<br />
<br />
[https://brunodigiuseppe.wordpress.com/category/CDOT/feed/]<br />
name= Bruno Di Giuseppe<br />
<br />
[http://actsangblog.wordpress.com/feed/]<br />
name=Alfred Tsang<br />
<br />
[http://stronglytyped.ca/category/spo600/feed/]<br />
name=Bradly Hoover<br />
<br />
[http://yakmarpro.wordpress.com/category/open-source/feed]<br />
name=Nicolas Ramkay<br />
<br />
[http://mavillaflor.wordpress.com/category/open-source/feed]<br />
name=Mark Anthony Villaflor<br />
<br />
[http://sylask.wordpress.com/category/SPO600/feed/]<br />
name=Emmanuel Ho Fidelino<br />
<br />
[http://blog.jordantheriault.com/category/open-source/feed/]<br />
name=Jordan Theriault<br />
<br />
[http://droxxes.wordpress.com/category/seneca/feed/]<br />
name=Tai Nguyen<br />
<br />
[http://acadosdev.blogspot.com/feeds/posts/default/]<br />
name=Yoav Gurevich<br />
<br />
[http://pphanopensource.blogspot.ca/feeds/posts/default/]<br />
name=Phuoc Phan<br />
<br />
[http://amkonopko.wordpress.com/feed/]<br />
name=Amadeus Konopko<br />
<br />
[http://fahmadi6.wordpress.com/feed/]<br />
name=Faranak Ahmadi<br />
<br />
[http://rsbr600.blogspot.ca/feeds/posts/default]<br />
name=Ronald Hernandez<br />
<br />
[http://ygcdw.blogspot.com/feeds/posts/default]<br />
name=Yoav Gurevich<br />
<br />
[http://sdealmeida.com/category/open-source/feed/]<br />
name=Simon de Almeida<br />
<br />
[http://jamaljalali.wordpress.com/feed/]<br />
name=Jamal Jalali-Dolatshahi<br />
<br />
[http://aadavis1.blogspot.ca/feeds/posts/default]<br />
name=Alexander Davis<br />
<br />
[http://thevakaran.wordpress.com/category/open-source/feed/]<br />
name=Thevakaran Virutthasalam<br />
<br />
[http://kyu6.wordpress.com/feed/]<br />
name=Keren Yu <br />
<br />
[http://chestersbr600.wordpress.com/]<br />
name=VicChester Ngo<br />
<br />
[http://cty6sbr600.wordpress.com/feed/]<br />
name=Kalpaniya Parmar<br />
<br />
[http://cty6.wordpress.com/feed/]<br />
name=Luis Fuentes<br />
<br />
[http://sbr600.wordpress.com/2012/01/26/build-from-source/]<br />
name=Rachit Chaudhary (DJ)<br />
<br />
[http://sbr600.wordpress.com/2012/01/26/introduction/]<br />
name=Rachit Chaudhary (DJ)<br />
<br />
[http://craigcain.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Craig Cain<br />
<br />
[http://i0x777.wordpress.com/feed/]<br />
name=Nikhil Sharma<br />
<br />
[http://wolfleaderslair.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Dennis Villasenor<br />
<br />
[http://rubensmaximus.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Rubens Maximus (GameArtist)<br />
<br />
[http://fedoraisfun.wordpress.com/category/open_source/feed/]<br />
name=Alan Lau<br />
<br />
[http://ruihui.me/SPO600/feed/]<br />
name=Ruihui Yan<br />
<br />
# Disabled - 404<br />
#[http://www.spectakular.com/category/open-source/feed/]<br />
#name=Simon Jung<br />
<br />
[http://james.boelen.ca/category/open_source/feed/]<br />
name=James Boelen<br />
<br />
# Disabled - 410<br />
#[http://mbrzuzy.wordpress.com/category/open-source/feed/]<br />
#name=Marcin Brzuzy<br />
<br />
[http://ben1amin.wordpress.com/category/seneca/feed/]<br />
name=Benjamin Chalovich<br />
<br />
# Disabled - 410<br />
#[http://edghardest1.wordpress.com/category/open-source-topics/feed/]<br />
#name=Ed Arvelaez<br />
<br />
[http://dboddie46.wordpress.com/category/SBR600A/feed/]<br />
name=Derrick Boddie<br />
<br />
# Disabled - 404<br />
#[http://aali83.blogspot.com/feeds/posts/default/-/oop344]<br />
#name=Ahmad Ali<br />
<br />
[http://gr8can8dian.wordpress.com/category/sbr600/feed/]<br />
name=Lorin Soura<br />
<br />
[http://kirtonmike.wordpress.com/category/SBR600/feed/]<br />
name=Mike Kirton<br />
<br />
[http://fuzzux.wordpress.com/category/SBR600/feed/]<br />
name=Tim Furzer<br />
<br />
[http://nageyi.wordpress.com/feed/]<br />
name=Faisal Nageyi<br />
<br />
[http://KrazyDre.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Andrei Artamonov<br />
<br />
[http://mjcorsame.wordpress.com/feed/]<br />
name=Michael John Corsame<br />
<br />
[http://msbreezy12.wordpress.com/category/SBR/feed/]<br />
name=Chantell Mcintosh<br />
<br />
[http://sbr600cabbott.blogspot.com/feeds/posts/default]<br />
name=Chris Abbott<br />
<br />
[http://kopay.wordpress.com/category/sbr600-win2011/feed]<br />
name=Pirathapan Sivalingam<br />
<br />
# Disabled - 404<br />
#[http://mysnogorodsky.blogspot.com/feeds/posts/default?alt=rss]<br />
#name=Marina Ysnogorodsky<br />
<br />
[http://wsong18.blogspot.com/feeds/posts/default/-/open-source]<br />
name=Wei Song<br />
<br />
[http://davidsosd60020102blog.blogspot.com/feeds/posts/default]<br />
name=David Takasaki<br />
<br />
[http://zwang98.blogspot.com/feeds/posts/default]<br />
name=Joe Wang<br />
<br />
[http://sbr700.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Jonathan Deni<br />
#face=https://techontherun.sslpowered.com/techontherun.ca/jonthumb.png<br />
<br />
[http://dgilloch.blogspot.com/feeds/posts/default]<br />
name=Daniel Gilloch<br />
<br />
[http://jmchen11.wordpress.com/feed/]<br />
name=Jianming Chen<br />
<br />
[http://paulfedora.wordpress.com/tag/cdot/feed/]<br />
name=Paul Whalen<br />
<br />
# Disabled - 404<br />
#[http://maxamaxim.wordpress.com/tag/cdot/feed/]<br />
#name=M A <br />
<br />
[http://dmchisho.wordpress.com/feed/]<br />
name=David Chisholm<br />
<br />
[http://pokerface3.blogspot.com/feeds/posts/default/-/SBR?alt=rss]<br />
name=David Cabral<br />
<br />
[http://zbhuang1.blogspot.com/feeds/posts/default/-/open%20source]<br />
name=Zhibin Huang<br />
<br />
[http://sidsbr.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Sadiki Latty<br />
<br />
[http://aryafarzan.wordpress.com/category/OOP344/feed/]<br />
name=Arya Farzan<br />
<br />
[http://dsventura.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Dan Ventura<br />
<br />
[http://acfunktron.blogspot.com/feeds/posts/default]<br />
name=Anton Chan<br />
<br />
[http://adaniel3.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Arlene Daniel<br />
<br />
[http://tyrant911-processingdotjs.blogspot.com/feeds/posts/default/-/processing.js]<br />
name=Alex Londono<br />
<br />
[http://ausleyj.blogspot.com/feeds/posts/default]<br />
name=Ausley Johnson<br />
<br />
[http://arminoop344.blogspot.com/feeds/posts/default]<br />
name=Armin Kumarshellah<br />
<br />
[http://cloudscorpion.blogspot.com/feeds/posts/default/-/open-source]<br />
name=Joseph Hughes<br />
<br />
[http://travisrawn.blogspot.com/feeds/posts/default]<br />
name=Travis Rawn<br />
<br />
[http://jmpiltz.blogspot.com/feeds/posts/default]<br />
name=Jonathan Piltz<br />
<br />
[http://andrewgrimo.wordpress.com/category/open-source/feed/]<br />
name=Andrew Grimo<br />
<br />
[http://mschranz.wordpress.com/category/open_source/feed/]<br />
name=Matthew Schranz<br />
<br />
[http://apvsbr700.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Alex Vlahopoulos<br />
#face=https://techontherun.sslpowered.com/techontherun.ca/alexthumb.png<br />
<br />
[http://asalga.wordpress.com/category/open-source/feed/]<br />
name=Andor Salga (asalga)<br />
<br />
[http://jabhad.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Mohamed Aden<br />
<br />
[http://jonathandeni.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Jonathan Deni<br />
#face=https://techontherun.sslpowered.com/techontherun.ca/jonthumb.png<br />
<br />
[http://manoutoftime.wordpress.com/category/open-source/feed/]<br />
name=Konstantin Novichikhin<br />
<br />
[http://scorchedicee.wordpress.com/category/Seneca/feed/]<br />
name=Adam Sone<br />
<br />
# Temporarily disabled due to non-Seneca posts 2014-01-06 CTyler<br />
#[http://murraysaul.wordpress.com/feed/]<br />
#name=Murray Saul<br />
<br />
[http://xwn740arcadeproject.blogspot.com/feeds/posts/default]<br />
name=Arcade Project - LUX Group@<br />
#face=http://matrix.senecac.on.ca/~mpaivaneto/ourbaby.png<br />
<br />
[http://feeds.feedburner.com/lsblakk_open-source]<br />
name=Lukas Blakk (lsblakk)<br />
#face=http://avnerd.tv/sharedFiles/lukas_hackergotchi.png<br />
<br />
[http://nashutzu.blogspot.com/feeds/posts/default]<br />
name=George Popescu (GeorgeP)<br />
<br />
[http://blog.chris.tylers.info/index.php?/feeds/categories/20-Seneca-Planet.rss]<br />
name=Chris Tyler (ctyler)<br />
face=http://zenit.senecac.on.ca/~chris.tyler/chris_tyler_hackergotchi_4a.png<br />
<br />
[http://blog.humphd.org/tag/seneca/rss/]<br />
name=David Humphrey<br />
<br />
[http://gratnam1.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Gajendran Ratnam (gratnam1)<br />
<br />
[http://senecajon.blogspot.com/feeds/posts/default]<br />
name=Jonathan Cheung (jcheung23)<br />
<br />
[http://lsdaly.blogspot.com/feeds/posts/default]<br />
name=Louis Daly (lsdaly)<br />
<br />
[http://bhearsum.blogspot.com/feeds/posts/default/-/seneca]<br />
name=Ben Hearsum<br />
<br />
# Re-enabled 2011-04-29 - new blog URL<br />
# Disabled 2009-09-15 due to 404's (site rearranged?)<br />
[http://tea.cesaroliveira.net/archives/tag/seneca/feed]<br />
name=Cesar Oliveira<br />
<br />
[http://r3ap3r.wordpress.com/category/seneca/feed]<br />
name=Brandon Collins<br />
<br />
[http://armenzg.blogspot.com/feeds/posts/default/-/open%20source]<br />
name=Armen Zambrano G. (armenzg)<br />
<br />
[http://vlam6.wordpress.com/category/open-source/feed/]<br />
name=Vincent Lam<br />
<br />
[http://dejant.blogspot.com/feeds/posts/default]<br />
name=Dejan Tolj<br />
<br />
[http://shivaris.blogspot.com/feeds/posts/default/-/OSD600]<br />
name=Hien Huynh<br />
<br />
[http://raynrant.blogspot.com/feeds/posts/default]<br />
name=Andrew Raynier (JM)<br />
face=http://zenit.senecac.on.ca/wiki/imgs/Hackergotchi.png<br />
<br />
[http://vijeysdps909.blogspot.com/feeds/posts/default]<br />
name=Vijey Bala<br />
<br />
[http://sedejong.blogspot.com/feeds/posts/default]<br />
name=Shomar Dejonge<br />
<br />
[http://dbaranski.wordpress.com/category/open-source/feed/]<br />
name=Dominic Baranski<br />
<br />
[http://kmsingh.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Kerry M. Singh<br />
<br />
[http://tjduavis.wordpress.com/category/open-source/feed/]<br />
name=Timothy Duavis<br />
<br />
[http://opensourcekennethlee.blogspot.com/feeds/posts/default]<br />
name=Kenneth Lee<br />
<br />
[http://cleung.wordpress.com/category/Seneca/feed/]<br />
name=Catherine Leung<br />
<br />
[http://dtheosab.wordpress.com/category/open-source/feed/]<br />
name=Daino Theosabrata<br />
<br />
# This is my old blog<br />
[http://simon-jung.blogspot.com/feeds/posts/default]<br />
name=Simon Jung (old)<br />
<br />
[http://aeraj.blogspot.com/feeds/posts/default/-/open%20source]<br />
name=AJ Rehman<br />
<br />
[http://xrayon.blogspot.com/feeds/posts/default]<br />
name=Fima Kachinski<br />
<br />
[http://littlesvr.ca/grumble/category/safeforseneca/feed/]<br />
name=Andrew Smith<br />
<br />
[http://jbopensrc.wordpress.com/category/open-source/feed]<br />
name=Jesse Buchanan<br />
<br />
[http://ayhfung.blogspot.com/feeds/posts/default]<br />
name=Andrew Fung<br />
<br />
[http://mozcoz.blogspot.com/feeds/posts/default/-/Open%20Source]<br />
name=Amit Gundu<br />
<br />
# Changed CTyler 2009-02-12 from [http://www.blogger.com/feeds/15922666655846514311/blogs]<br />
[http://dsmukherji.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Devashish<br />
<br />
[http://yhan11.wordpress.com/category/open-source/feed]<br />
name=Yongsheng Han<br />
<br />
[http://peter.sykokillers.com/category/open-source/feed/]<br />
name=Peter Chan<br />
<br />
<br />
# Updated 2011-04-28 - corrected feed URL<br />
[http://peterevanoff.wordpress.com/category/open-source/feed/]<br />
name=Peter Evanoff<br />
<br />
[http://blog.cresencia.ca/category/open-source/osd600/feed/]<br />
name=Joseph Cresencia<br />
<br />
[http://bertenshaw.blogspot.com/feeds/posts/default]<br />
name=David Bertenshaw<br />
<br />
[http://ljubomirgorscak.blogspot.com/feeds/posts/default]<br />
name=Ljubomir Gorscak<br />
<br />
# Disabled - 404<br />
#[http://sameropensource.blogspot.com/feeds/posts/default]<br />
#name=Samer Ziadeh (samer)<br />
<br />
[http://dailypackage.fedorabook.com/index.php?/feeds/index.rss2]<br />
name=Fedora Daily Package<br />
<br />
[http://blog.fardad.com/feeds/posts/default/-/Seneca]<br />
name=Fardad Soleimanloo<br />
<br />
[http://selmys.wordpress.com/category/opensource/feed]<br />
name=John Selmys<br />
face=http://cs.senecac.on.ca/~selmys/john_selmys_hackergotchi.png<br />
<br />
[http://pconstantino.wordpress.com/feed]<br />
name=Patricia Constantino<br />
<br />
[http://bombshelter13.blogspot.com/feeds/posts/default]<br />
name=Katherine Masseau<br />
<br />
[http://zadkielm.blogspot.com/feeds/posts/default/-/open%20source]<br />
name=Ezadkiel Marbella<br />
<br />
[http://blog.sidkalra.com/category/opensource/feed]<br />
name=Sid Kalra<br />
<br />
[http://pplam3.blogspot.com/feeds/posts/default]<br />
name=Patrick Lam<br />
<br />
[http://dee132.blogspot.com/feeds/posts/default/-/seneca]<br />
name=Chris Bishop<br />
<br />
[http://spo600osp.blogspot.com/feeds/posts/default]<br />
name=Wayne Williams<br />
<br />
# Updated 2011-04-28 - updated feed URL<br />
[http://zghansar.wordpress.com/category/open-source/feed/]<br />
name=Zaid Ghansar<br />
face=http://www.alhudainstitute.ca/zaid/z.png<br />
<br />
[http://aaronmt.github.com/atom.xml]<br />
name=Aaron Train<br />
face=http://matrix.senecac.on.ca/~amtrain/other/mypic.png<br />
<br />
[http://scottosd.blogspot.com/feeds/posts/default/-/Open%20Source/]<br />
name=Scott Lunel<br />
<br />
[http://belligero.org/index.php?option=com_content&view=section&id=1&format=feed&type=rss]<br />
name=Jason Tarka<br />
<br />
# Updated 2011-04-28 - no more tag, but still Seneca related<br />
[http://petermcintyre.wordpress.com/feed/]<br />
name=Peter McIntyre<br />
<br />
[http://vesperrin.blogspot.com/feeds/posts/default/-/open%20source]<br />
name=Leonard Lee (vesper)<br />
<br />
[http://jsdoodnauth.wordpress.com/category/open-source/feed/]<br />
name=Joshua Doodnauth<br />
<br />
[http://mohaksblog.blogspot.com/feeds/posts/default]<br />
name=Mohak Vyas<br />
#face=http://matrix.senecac.on.ca/~mdvyas/MohakVyas.png<br />
<br />
[http://pdirezze.blogspot.com/feeds/posts/default]<br />
name=Paul DiRezze<br />
<br />
[http://miltonpaiva.wordpress.com/feed/]<br />
name=Milton Paiva<br />
#face=http://matrix.senecac.on.ca/~mpaivaneto/orkut.png<br />
<br />
[http://de-luxer.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Nestor Chan<br />
#face=http://matrix.senecac.on.ca/~tnchan/n516840997_9173.PNG<br />
<br />
[http://varinderjhand.wordpress.com/feed/]<br />
name=Varinder Singh <br />
<br />
[http://ajhooper.blogspot.com/feeds/posts/default]<br />
name=Aaron Hooper<br />
<br />
[http://nadavid.blogspot.com/feeds/posts/default]<br />
name=Neil David<br />
<br />
[http://cdpatel1.blogspot.com/feeds/posts/default]<br />
name=Chinmay Patel<br />
#face=http://www.geocities.com/chinmay_patel@ymail.com/chinmay.jpg<br />
<br />
[http://jvalianes.blogspot.com/feeds/posts/default]<br />
name=Jesse Valianes<br />
<br />
[http://bbarcick.blogspot.com/feeds/posts/default/-/Open%20Source]<br />
name=Bartosz Barcicki<br />
<br />
[http://heidenreich.wordpress.com/tag/seneca-college/feed/]<br />
name=Michal Heidenreich<br />
<br />
[http://kezhong.wordpress.com/feed/atom/]<br />
name=Kezhong Liang <br />
<br />
[http://wfred.wordpress.com/category/open-source/feed/]<br />
name=Fred Wang<br />
<br />
[http://jsinghfoss.wordpress.com/category/spring-framework/feed/]<br />
name=Jatinder Singh<br />
<br />
[http://rparsi.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Rahi Parsi<br />
<br />
<br />
# Changed 2011-04-28 - missing a capital "S" from Seneca to display feed<br />
[http://aaronrey15.blogspot.com/feeds/posts/default/-/Seneca]<br />
name=Aaron Chan<br />
<br />
# Disabled 2011-04-28 - posts were deleted, empty feed<br />
#[http://flashalive.wordpress.com/category/Open%20Source/feed/]<br />
#name=Ryan Wang<br />
<br />
[http://kvuhome.blogspot.com/feeds/posts/default/-/Open%20Source]<br />
name=Khanh Vu<br />
<br />
[http://daeseonmoon.wordpress.com/category/open-source/feed/]<br />
name=Daeseon Moon<br />
<br />
[http://abraini.wordpress.com/category/seneca/feed/]<br />
name=Andrew Braini<br />
<br />
[http://minicheong.blogspot.com/feeds/posts/default]<br />
name=Frankie Law<br />
<br />
[http://farhadnorouzi.blogspot.com/feeds/posts/default]<br />
name=Farhad Norouzi<br />
<br />
[http://jdeport.wordpress.com/category/software-development/open-source/feed/]<br />
name=John Dang<br />
<br />
[http://pliu.wordpress.com/category/open-source/feed/]<br />
name=Peter Liu<br />
<br />
[http://blog.wikiscraps.com/feeds/posts/default/-/oss]<br />
name=M. Mead Armsby (mead)<br />
<br />
[http://paritosha.blogspot.com/feeds/posts/default]<br />
name=Paritosh Aggarwal(paritosh1010)<br />
<br />
[http://wb-os.blogspot.com/feeds/posts/default]<br />
name=Le Yang<br />
<br />
[http://garykwong.wordpress.com/category/education/feed/]<br />
name=Gary Kwong (nth10sd)<br />
<br />
[http://opensourceproject.wordpress.com/category/open-source/feed/]<br />
name=Nabeel Khan (nkhan26)<br />
<br />
[http://xiajunshi.wordpress.com/category/open-source/feed/]<br />
name=Shelley Shi<br />
<br />
[http://hendrikinmozilla.wordpress.com/feed/]<br />
name=Hendrik<br />
<br />
[http://t3rrychan.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Terry Chen (jchen124)<br />
<br />
[http://ahiltssbr700.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Adam Hilts<br />
<br />
[http://ysasaki600.wordpress.com/feed/]<br />
name=Yu Sasaki<br />
<br />
[http://enderstruth.wordpress.com/category/open-source/feed/]<br />
name=Roger Dicke<br />
<br />
[http://wobblyretroaction.blogspot.com/feeds/posts/default/-/Open%20source]<br />
name=Matthew Lam<br />
<br />
[http://asydik.wordpress.com/category/professional/open-source/feed/]<br />
name=Mickael Medel (aSydiK)<br />
<br />
[http://cwdesautels.blogspot.com/feeds/posts/default]<br />
name=Carl Desautels<br />
<br />
[http://rselby-oop344.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Remington Selby<br />
<br />
[http://mikey-osd600a.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Michael Dennis<br />
<br />
[http://horndavid.blogspot.com/feeds/posts/default?alt=rss]<br />
name=David Horn<br />
<br />
[http://annasob.wordpress.com/feed/]<br />
name=Anna Sobiepanek<br />
<br />
[http://drozhkov.blogspot.com/feeds/posts/default/-/seneca]<br />
name=Dmitriy Rozhkov<br />
<br />
[http://www.hodgin.ca/?feed=rss2&cat=4]<br />
name=Daniel Hodgin<br />
<br />
[http://xderick.blogspot.com/feeds/posts/default/-/OSD]<br />
name=Yong Hong<br />
<br />
[http://s2000c.blogspot.com/feeds/posts/default/-/OOP344]<br />
name=Sunny Chau<br />
<br />
[http://kxu9.blogspot.com/feeds/posts/default]<br />
name=Kai Xu<br />
<br />
[http://oop-era.blogspot.com/feeds/posts/default]<br />
name=Eric Austerberry<br />
<br />
[http://docsage.blogspot.com/feeds/posts/default/-/OOP344]<br />
name=Eric Dell<br />
<br />
[http://ehren.wordpress.com/category/Seneca/feed/]<br />
name=Ehren Metcalfe<br />
<br />
[http://bsmith19.wordpress.com/category/Seneca/feed/]<br />
name=Brandon Smith<br />
<br />
[http://dcucereavii.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Diana Cucereavii<br />
<br />
[http://paul-oop344.blogspot.com/feeds/posts/default/]<br />
name=Paul Repasi<br />
<br />
[http://istessema.wordpress.com/category/oop344/feed/]<br />
name=Iyosias Tessema<br />
<br />
[http://nedape.blogspot.com/feeds/posts/default]<br />
name=Neda Pezeshki<br />
<br />
[http://justletmepassoop344.blogspot.com/feeds/posts/default]<br />
name=Brian Parreno<br />
<br />
[http://dliu53.wordpress.com/category/open-source/feed/]<br />
name=Donghui Liu<br />
<br />
[http://oop344ylseow.blogspot.com/feeds/posts/default]<br />
name=Yip Lim, Seow<br />
<br />
[http://mercedes-oop344.blogspot.com/feeds/posts/default]<br />
name=Suwon An<br />
<br />
[http://dtychshenko.blogspot.com/feeds/posts/default/-/OOP344]<br />
name=Dmitriy Tychshenko<br />
<br />
[http://victran.blogspot.com/feeds/posts/default/-/OOP344]<br />
name=Victor Tran<br />
<br />
# Changed 2011-04-27 - updated feed URL to proper<br />
[http://krazyazn.blogspot.com/feeds/posts/default]<br />
name=Michael Lin<br />
<br />
[http://xshi18.blogspot.com/feeds/posts/default]<br />
name=Xiaozhe Shi<br />
<br />
[http://feihong-xiong.blogspot.com/feeds/posts/default]<br />
name=Feihong Xiong<br />
<br />
# Changed 2011-11-01 - created category just for PlanetCDOT<br />
[http://orbitalstation.wordpress.com/category/planetcdot/feed/]<br />
name=Hasan (northWind) Kamal-Al-Deen<br />
face=http://matrix.senecac.on.ca/~hkamal-al-deen/images/Exclaim65x85.png<br />
<br />
[http://hduan2.wordpress.com/feed/]<br />
name= Haoliang Duan<br />
<br />
[http://anastasias-myblog.blogspot.com/feeds/posts/default/-/OOP344]<br />
name= Anastasia Semionova<br />
<br />
[http://franksun123.blogspot.com/feeds/posts/default/]<br />
name= Dong Sun<br />
<br />
[http://rkyoop344.blogspot.com/feeds/posts/default/]<br />
name=Keyan Ren<br />
<br />
[http://szymonsoop.blogspot.com/feeds/posts/default/]<br />
name= Szymon Ahmed<br />
<br />
[http://ywang268.blogspot.com/feeds/posts/default/]<br />
name=Yu Wang<br />
<br />
[http://wangcong422.blogspot.com/feeds/posts/default/]<br />
name=Cong Wang<br />
<br />
[http://dennyp.wordpress.com/category/Seneca/feed/]<br />
name=Denny Papagiannidis<br />
<br />
[http://saecob.blogspot.com/feeds/posts/default/-/OpenSource]<br />
name= Sergiu Ecob<br />
<br />
[http://gkrilov.blogspot.com/feeds/posts/default]<br />
name=Greg Krilov<br />
<br />
[http://qinzhi2001.blogspot.com/feeds/posts/default]<br />
name=David Chen<br />
<br />
[http://tchen-oop344.blogspot.com/feeds/posts/default]<br />
name=Terence Chen<br />
<br />
[http://opp344-yxue.blogspot.com/feeds/posts/default]<br />
name=Yong Xue<br />
<br />
[http://ttsuji1.blogspot.com/feeds/posts/default]<br />
name=Trevor Tsuji<br />
<br />
[http://oyoung4.blogspot.com/feeds/posts/default]<br />
name=Oliver Young<br />
<br />
[http://minyxo.blogspot.com/feeds/posts/default/-/Open%20Source]<br />
name=Edward Sin<br />
<br />
[http://jdbcdps.blogspot.com/feeds/posts/default]<br />
name=Julia Vasserman<br />
<br />
[http://shunyao-cpa.blogspot.com/feeds/posts/default]<br />
name=Shun Yao Zhang<br />
<br />
[http://oop344ylseow.blogspot.com/feeds/posts/default]<br />
name=Yip Lim Seow<br />
<br />
[http://capereir.wordpress.com/feed/]<br />
name=Chris Pereira<br />
<br />
[http://dev-blog.zerogin.com/category/opensource/feed/]<br />
name=Tom Wisniewski (t0mmyw)<br />
<br />
[http://cdnpadawan.wordpress.com/feed/]<br />
name=Matthew Daniels<br />
<br />
[http://processingjs.org/blog/?feed=rss2]<br />
name=Processing.js Blog<br />
<br />
[http://dseifried.wordpress.com/category/school/feed/]<br />
name=David Seifried<br />
<br />
[http://s-aleinikov.blog.ca/feed/atom/posts/]<br />
name=Sergey Aleinikov<br />
<br />
[http://wfchen2010.blogspot.com/feeds/posts/default]<br />
name=Wen Fang Chen<br />
<br />
[http://donna-oberes.blogspot.com/feeds/posts/default?alt=rss]<br />
name=Donna Oberes<br />
<br />
[http://carolynwoodley.blogspot.com/feeds/posts/default]<br />
name=Carolyn Woodley<br />
<br />
[http://shengwei-seneca.blogspot.com/feeds/posts/default]<br />
name=Shengwei Wang<br />
<br />
[http://zakoop344.blogspot.com/feeds/posts/default]<br />
name=Wei Tong<br />
<br />
[http://gtawaf.blogspot.com/feeds/posts/default/-/Seneca]<br />
name=Gamal Tawaf <br />
<br />
[http://rift-tlosam.blogspot.com/feeds/posts/default/-/seneca]<br />
name=Brendan McDorman<br />
<br />
[http://hdc23.wordpress.com/category/OOP344/feed]<br />
name=Dachuan Huang<br />
<br />
[http://feliploko.wordpress.com/category/seneca/feed]<br />
name=Felipe de Oliveira<br />
<br />
[http://shunyao-cpa.blogspot.com/feeds/posts/default]<br />
name=shun yao zhang<br />
<br />
[http://galewis.blogspot.com/feeds/posts/default]<br />
name=Gustone Lewis<br />
<br />
[http://hmo6.blogspot.com/feeds/posts/default]<br />
name=Mo Hsiu Mei<br />
<br />
[http://derekambrose.blogspot.com/feeds/posts/default/-/open%20source]<br />
name=Derek Ambrose<br />
<br />
[http://scottdowne.wordpress.com/category/open-source/feed/]<br />
name=Scott Downe<br />
<br />
[http://jjleeos.blogspot.com/feeds/posts/default]<br />
name = Jeffrey Lee<br />
<br />
[http://harjinderv.tumblr.com/tagged/Open_Source/rss]<br />
name = Harjinder Virdi<br />
<br />
[http://cldenobrega.wordpress.com/category/open-source/feed/]<br />
name = Crystal de Nobrega (cldenobrega)<br />
<br />
[http://lchen97.blogspot.com/feeds/posts/default]<br />
name=Chris Chen<br />
<br />
[http://oleg-oop.blogspot.com/feeds/posts/default]<br />
name=Aleh Pliats<br />
<br />
[http://88mishok.blogspot.com/feeds/posts/default]<br />
name=Francois Des Jarlais<br />
<br />
[http://bikarin.blogspot.com/feeds/posts/default]<br />
name=Irina Balzamova<br />
<br />
[http://mashhaque.blogspot.com/feeds/posts/default]<br />
name=Mashfique Haque<br />
<br />
[http://yxue11.blogspot.com/feeds/posts/default]<br />
name=Yong Xue<br />
<br />
[http://tdao75.blogspot.com/feeds/posts/default]<br />
name=Thanh Dao<br />
<br />
[http://minooz.wordpress.com/category/CDOT/feed/]<br />
name=Minoo Ziaei<br />
<br />
[http://gbatumbya.wordpress.com/category/seneca/cdot/feed/]<br />
name=Grace Simon Batumbya<br />
<br />
[http://sonnilion.wordpress.com/feed/]<br />
name=Matt Postill<br />
<br />
[http://acchung1.blogspot.com/feeds/posts/default/-/oop344]<br />
name=Alex Chun Yang Chung<br />
<br />
[http://hckim.wordpress.com/category/open-source/feed/]<br />
name=Han Chul Kim<br />
<br />
[http://xizhangblog.blogspot.com/feeds/posts/default/-/oop344]<br />
name=Xi Zhang<br />
<br />
[http://lwu11.blogspot.com/feeds/posts/default]<br />
name=Ling Wu<br />
<br />
[http://jasonquan.wordpress.com/category/OOP344/feed/]<br />
name=Jason Quan<br />
<br />
[http://jessefulton.wordpress.com/category/SBR600/feed/]<br />
name=Jesse Fulton<br />
<br />
[http://ligangbory.wordpress.com/feed/]<br />
name=Gang Li<br />
<br />
[http://kliu39.wordpress.com/feed/]<br />
name=Kun Liu<br />
<br />
[http://mariabustoss.wordpress.com/feed/]<br />
name=Maria Bustos-Roman<br />
<br />
[http://kavisbr.blogspot.com/feeds/posts/default]<br />
name=Kavishankar Srivamathevan<br />
<br />
[http://dsegree.wordpress.com/feed/]<br />
name=Daniel Segree<br />
<br />
[http://sajed481.wordpress.com/opensource/feed/]<br />
name=Mohammad Abdullah Sajed Shadani<br />
<br />
[http://asalwi123.wordpress.com/feed/]<br />
name=Aries Alwi<br />
<br />
[http://jmulwani.wordpress.com/feed/]<br />
name=Jayaditya Mulwani<br />
<br />
[http://sbr600blog.blogspot.com/feeds/posts/default]<br />
name=Andrew Greene<br />
<br />
[http://chadpilkey.wordpress.com/category/opensource/feed/]<br />
name=Chad Pilkey<br />
<br />
[http://ejtorre.blog.ca/feed/rss2/posts/]<br />
name=Eugene Torre<br />
<br />
[http://lynart.wordpress.com/category/CDOT/feed/]<br />
name=Vince Lee<br />
<br />
[http://stani.ca/?feed=rss2&cat=3]<br />
name=Robert Stanica<br />
<br />
[http://cdot-callaghan.posterous.com/rss.xml?tag=CDOT]<br />
name=Peter Callaghan<br />
<br />
[http://shayanzafar.wordpress.com/category/open-source/feed/]<br />
name=Shayan Zafar Ahmad<br />
<br />
[http://zyu26.wordpress.com/feed/]<br />
name=Zhiping Yu<br />
<br />
[http://maximumou.blogspot.com/feeds/posts/default]<br />
name=Zhi Chang Ou<br />
<br />
[http://www.kypertrast.net/seneca/category/open-source/feed/]<br />
name=Michael Afidchao<br />
<br />
[http://rickeyre.ca/open-source-feed.xml]<br />
name=Rick Eyre<br />
<br />
[http://ayufidin.blogspot.ca/feeds/posts/default]<br />
name=Alon Yufidin<br />
<br />
[http://sudodamha.blogspot.com/feeds/posts/default]<br />
name=Ahmad Taychouri<br />
<br />
[http://amartinencosbr600.blogspot.com/feeds/posts/default]<br />
name=Andrei Martinenco<br />
<br />
[http://sbr600.tumblr.com/rss]<br />
name=Daniel Delidjakov<br />
<br />
[http://ashtramwasser.blogspot.ca/feeds/posts/default]<br />
name=Alina Shtramwasser<br />
<br />
[http://limed3.wordpress.com/category/open-source/feed/]<br />
name=Edwin Lim<br />
<br />
[http://rlawrence5.wordpress.com/feed/]<br />
name=Ryan Lawrence<br />
<br />
[http://okhattab.wordpress.com/feed/]<br />
name=Omarr Khattab<br />
<br />
[http://aadavis1.blogspot.ca//feeds/posts/default]<br />
name=Alexander Davis<br />
<br />
[http://kdayalingam.wordpress.com/category/dpi908/feed]<br />
name=Kowrinanthan Dayalingam<br />
<br />
[http://jcqiu.wordpress.com/feed/]<br />
name=Jiecheng Qiu<br />
<br />
[http://mikeshutov.blogspot.com/feeds/posts/default/-/open-source]<br />
name=Mike Shutov<br />
<br />
[http://avru.wordpress.com/category/open-source/feed/]<br />
name=Anh Tran<br />
<br />
[http://kyle.barnhart.ca/feeds/posts/default/-/Open%20Source]<br />
name=Kyle Barnhart<br />
<br />
[http://gloriaip.wordpress.com/feed/]<br />
name=Gloria Ip<br />
<br />
[http://www.mandeepgarg.wordpress.com/feed/]<br />
name=Mandeep Garg<br />
<br />
[http://bharmidy.blogspot.ca/feeds/posts/default/-/open%20source]<br />
name=Bryce Harmidy<br />
<br />
[http://ddinisalves.wordpress.com/category/open-source/feed/]<br />
name=Diana Dinis-Alves<br />
<br />
[http://andrewow.wordpress.com/category/sbr600/feed/]<br />
name=Andrew Oatley-Willis<br />
<br />
[http://dima1086.blogspot.com/feeds/posts/default/-/Open%20Source]<br />
name=Dmytro Kostenyuk<br />
<br />
# Disabled - 404<br />
#[http://hapombo.blogspot.ca/feeds/posts/default]<br />
#name=Hugo Pombo<br />
<br />
[http://petepabs.wordpress.com/feed/]<br />
name=Peter Valerio<br />
<br />
[http://sabanane.wordpress.com/feed/]<br />
name=Japheth N.<br />
<br />
[http://rtang12.blogspot.ca/feeds/posts/default]<br />
name=Ruowen Tang<br />
<br />
[http://softwarebuildrun.wordpress.com/feed/]<br />
name=Rudolf R Janns<br />
<br />
[http://wkhan10.wordpress.com/feed]<br />
name=Waqas Khan<br />
<br />
[http://blog.marcussaad.com/?feed=rss2&lang=en]<br />
name=Marcus Saad<br />
<br />
[http://sedgestuff.wordpress.com/category/open-source-cdot/feed/]<br />
name=Kieran Sedgwick<br />
<br />
[http://alicoding.com/rss/]<br />
name=Ali Al Dallal<br />
<br />
[http://garydengblog.wordpress.com/category/open-source/feed/]<br />
name=Gary Deng<br />
<br />
[http://dylansegna.wordpress.com/feed/]<br />
name=Dylan Segna<br />
<br />
[http://andreikopytov.wordpress.com/category/CDOT/feed/]<br />
name=Andrei Kopytov<br />
<br />
[http://igoryen.wordpress.com/category/CDOT/feed/]<br />
name=Igor Entaltsev<br />
<br />
[http://jasdeep.ca/ruby/feed/]<br />
name=Jasdeep Singh<br />
<br />
[http://echanna.blogspot.ca/feeds/posts/default/-/open-source]<br />
name=Edward Hanna<br />
<br />
[http://eliocharles.wordpress.com/category/open-edx/feed/]<br />
name=Edward Hanna<br />
<br />
[http://nexjmdi.blogspot.com/feeds/posts/default]<br />
name=Yoav Gurevich<br />
<br />
[http://senecahealth.wordpress.com/feed/]<br />
name=Seneca Health Projects Blog<br />
<br />
[http://tqyu.wordpress.com/]<br />
name=Tony Yu<br />
<br />
[http://kwkofler.wordpress.com/category/open-source/feed/]<br />
name=Kevin Kofler<br />
<br />
[http://revenlight.wordpress.com/category/open-source/feed/]<br />
name=Dzmitry Kavalchyk<br />
<br />
[http://mlveis.wordpress.com/category/open-source/feed/]<br />
name=Michael Veis<br />
<br />
[http://maronin.wordpress.com/category/open-source/feed/]<br />
name=Mark Aronin<br />
<br />
[http://elnushaj.wordpress.com/feed/]<br />
name=Elsi Nushaj<br />
<br />
[http://chaoboxie.wordpress.com/category/open-source/feed/]<br />
name=Chaobo Xie<br />
<br />
[http://mbbaig.wordpress.com/category/open-source/feed/]<br />
name=Mohamed Baig<br />
<br />
[http://cholantesh.wordpress.com/category/opensource/feed]<br />
name=Natesh Mayuranathan<br />
<br />
[http://shavyg2.wordpress.com/category/open-source/feed/]<br />
name=Shavauhn Gabay<br />
<br />
[http://pbouianov.wordpress.com/category/open-source/feed/]<br />
name=Petr Bouianov<br />
<br />
[http://tecknologikk.blogspot.ca/feeds/posts/default/-/sbr600]<br />
name=Taylor Barras<br />
<br />
[http://andeic1.wordpress.com/category/open-source/feed/]<br />
name=Alex Craig<br />
<br />
[http://basyager.wordpress.com/feed/]<br />
name=Slava Basatski<br />
<br />
[http://adow2.wordpress.com/category/opensource/feed/]<br />
name=Ai Dow<br />
<br />
[http://hfazal.wordpress.com/category/open-source/feed/]<br />
name=Husain Fazal<br />
<br />
[http://btulchinsky.wordpress.com/category/open-source/feed/]<br />
name=Barry Tulchinsky<br />
<br />
[http://ttran57.blogspot.com/feeds/posts/default]<br />
name=Thanh Tran <br />
<br />
[http://jasoncarman.wordpress.com/category/sbr600/feed/]<br />
name=Jason Carman<br />
<br />
[http://ywen10.blogspot.com/feeds/posts/default]<br />
name=Yue Wen<br />
<br />
[http://nitinprakash.wordpress.com/category/open-source/feed/]<br />
name=Nitin Prakash Panicker<br />
<br />
[http://msousa3.blogspot.com/feeds/posts/default]<br />
name=Michael Sousa<br />
<br />
[http://professorplumpi.wordpress.com/feed/]<br />
name=Richard Kim<br />
<br />
[http://cjiang13.wordpress.com/category/SBR600/feed/]<br />
name=Charley Jiang<br />
<br />
# Disabled - 404<br />
#[http://yshin8.blogspot.com/feeds/posts/default]<br />
#name=Yonghoon Shin<br />
<br />
[http://sspaleta.wordpress.com/feed/]<br />
name=Shiela Spaleta<br />
<br />
[http://darthjawa.wordpress.com/category/sbr600/cdot-planet/feed/]<br />
name=Dmitry Kozunov<br />
<br />
[http://matthewtorrance.com/category/osd/feed/]<br />
name=Matthew Torrance<br />
<br />
[http://bzcareermongodb.blogspot.ca/feeds/posts/default]<br />
name=Zakeria Hassan<br />
face=https://0.gravatar.com/avatar/66e5e21053f70a3c30325b392337d54d?d=https%3A%2F%2Fidenticons.github.com%2F01cbc34a00bb2b4209eca3ca9eceb565.png&s=420<br />
<br />
[http://singhrajdeepblog.wordpress.com/feed/]<br />
name=Rajdeep Singh<br />
<br />
# Disabled - 404<br />
#[http://www.peymangg.com/feed/]<br />
#name=Peyman Mahdi<br />
<br />
[http://kkmusinguzi.wordpress.com/feed/]<br />
name=Keith Musinguzi<br />
<br />
[http://atpenrose.wordpress.com/feed/]<br />
name=Adam Penrose<br />
<br />
[http://jdlatorre.blogspot.ca/feeds/posts/default]<br />
name= Juan Latorre<br />
<br />
[http://mbustossbr.wordpress.com/feed/]<br />
name=Maria Bustos-Roman<br />
<br />
[http://msmahmood1.blogspot.com/feeds/posts/default/-/opensource]<br />
name=Mohammad Shaheer Mahmood<br />
<br />
[http://alexkotliar.wordpress.com/category/open-source/feed/]<br />
name=Alex Kotliar<br />
<br />
[http://codescriptplay.blogspot.ca/feeds/posts/default/-/opensource]<br />
name=Kajanthan Tharmabalan<br />
<br />
[http://dchenxd.wordpress.com/category/open-source/feed/]<br />
name=Xiaodong Chen<br />
<br />
[http://jespiritucpp.wordpress.com/category/open-source/feed]<br />
name=Jeffrey Espiritu<br />
<br />
[http://thedib.blogspot.ca/feeds/posts/default]<br />
name=Jose Giagonia<br />
<br />
[http://mkmatthewblog.wordpress.com/feed]<br />
name=Matthew K Wong<br />
<br />
[http://jrromasanta1.wordpress.com/feed/]<br />
name=Jose Romasanta<br />
<br />
[http://shaj02.wordpress.com/feed/]<br />
name=Shajinth Pathmakulaseelan<br />
<br />
[http://jeremyedgell.wordpress.com/category/Programming/feed/]<br />
name=Jeremy Edgell<br />
<br />
[http://spo600yg.blogspot.com/feeds/posts/default]<br />
name=Yoav Gurevich<br />
<br />
[http://vprasanth.com/blog/archives/category/spo600-2/feed]<br />
name=Prasanth Vaaheeswaran<br />
<br />
[http://hzhong10.blogspot.ca/feeds/posts/default]<br />
name=Hua Zhong<br />
<br />
[http://nrkemp4.tumblr.com/tagged/spo600/rss]<br />
name=Nick Kemp<br />
<br />
[http://www.shlee.ca/category/open-source/feed/]<br />
name=Sanghyun Lee<br />
<br />
[http://mctenenbaum.wordpress.com/category/open-source/feed]<br />
name=Moshe Tenenbaum<br />
<br />
[http://estereh.blogspot.com/feeds/posts/default/-/SPO600]<br />
name=Eugen (Jevenijs) Sterehov<br />
<br />
[http://compiledsprawl.blogspot.com/feeds/posts/default/-/open-source]<br />
name=Matthew Grosvenor<br />
<br />
[http://sinomai.wordpress.com/category/planet-cdot/feed/]<br />
name=Matt Jang<br />
<br />
[http://admixdev.com/category/programming-2/feed/]<br />
name=Alexander Snurnikov<br />
<br />
# Disabled - 404<br />
#[http://mstiver-balla.com/rss?tag=SPO600]<br />
#name=Michael Stiver-Balla<br />
<br />
[http://donmcarthur.wordpress.com/category/spo600/feed]<br />
name=Donald McArthur<br />
<br />
[http://hamabama.wordpress.com/feed]<br />
name=Dmitry Yastremskiy<br />
<br />
[http://hesam-chobanlou.com/feed/atom.php]<br />
name=Hesam Chobanlou<br />
<br />
[http://rgideonthomas.wordpress.com/feed/]<br />
name=Gideon Thomas<br />
<br />
[http://hzahoori.wordpress.com/category/open-source/feed]<br />
name=Habib Zahoori<br />
<br />
[http://linpei.blogspot.ca/feeds/posts/default]<br />
name=Linpei Fan<br />
<br />
[http://brockmoote.wordpress.com/feed/]<br />
name=Stanley Moote<br />
<br />
[http://rawkamatic.github.io/opensourcefeed]<br />
name=Hunter Jansen<br />
<br />
[http://avadac.wordpress.com/category/open-source/feed/]<br />
name=Ava Dacayo<br />
<br />
[http://gklo.github.io/feed.xml]<br />
name=Glaser Lo<br />
<br />
[http://openmillar.wordpress.com/feed-2/]<br />
name=Jeremy Millar<br />
<br />
[http://frankpanico.wordpress.com/category/open-source/feed/]<br />
name=Frank Panico<br />
<br />
[http://elliottheguy.wordpress.com/tag/open-source/feed/]<br />
name=Elliot Kwan<br />
<br />
[http://jlaverty.blogspot.com/feeds/posts/default]<br />
name=James Laverty<br />
<br />
[http://okevin0.wordpress.com/category/open-source/feed/]<br />
name=Shuming Lin<br />
<br />
[http://hopensources.blogspot.ca/feeds/posts/default/-/open%20source]<br />
name=Haiyu Qiao<br />
<br />
[http://fadiprogramming.wordpress.com/feed/]<br />
name=Fadi Tawfig<br />
<br />
[https://ryandangdeveloper.wordpress.com/feed/]<br />
name=Ryan Dang<br />
<br />
# Disabled - connection reset<br />
#[https:/http://rdaoud1.wordpress.com/category/open-source/feed/]<br />
#name=Rafid Daoud<br />
<br />
[http://paracr4ckbeginnings.wordpress.com/feed/]<br />
name=Brendan Donald Henderson<br />
<br />
[http://odjahanpour.wordpress.com/category/spo600/feed]<br />
name=Omid Djahanpour<br />
<br />
[http://liandrew.ca/feed.opensource.xml]<br />
name=Andrew Li<br />
<br />
[http://adamsharpe8.blogspot.ca/feeds/posts/default/-/Open%20Source]<br />
name=Adam Nicholas Sharpe<br />
<br />
[http://blog.gabrielcastro.ca/feeds/posts/default/-/open%20source]<br />
name=Gabriel Castro<br />
<br />
[http://edwinlum.wordpress.com/category/open-source/feed/]<br />
name=Edwin Lum<br />
<br />
[http://hosunghwang.wordpress.com/feed/]<br />
name=Hosung Hwang<br />
<br />
[https://ahkol.wordpress.com/blog/feed/]<br />
name=Adam Kolodko<br />
<br />
[https://andrewbennerlearn.wordpress.com/feed/]<br />
name=Andrew Benner<br />
<br />
[http://adsantokhi.wordpress.com/category/open-source/feed]<br />
name=Anil Santokhi<br />
<br />
[http://www.bpcoding.com/blog/category/spo/]<br />
name=Bruno Pereira<br />
<br />
[http://spo600.wordpress.com/feed/]<br />
name=Thana Annis<br />
<br />
[http://markieta.blogspot.ca/feeds/posts/default/]<br />
name=Christopher Markieta<br />
<br />
[http://blog.neilguzman.com/feed/category/cdot/atom]<br />
name=Neil Guzman<br />
<br />
[https://ysong55spd600.wordpress.com/category/SPO600/feed/]<br />
name=Yan Song<br />
<br />
[https://kleverlogs.wordpress.com/feed/]<br />
name=Klever Loza Vega<br />
<br />
[https://lisyonok85.wordpress.com/feed/]<br />
name=Artem Luzyanin<br />
<br />
[https://jangabrielona.wordpress.com/category/open-source/feed]<br />
name=Jan Ona<br />
<br />
[https://maxwelllefevre.wordpress.com/feed/]<br />
name=Maxwell LeFevre<br />
<br />
[http://spo-asm.blogspot.com/feeds/posts/default/-/SPO600/]<br />
name=James Boyer<br />
<br />
[http://gchau2.wordpress.com/feed/]<br />
name=Gary Chau<br />
<br />
[http://dokidoki.duckdns.org/tag/polished/rss/]<br />
name=Kenny Nguyen<br />
<br />
[https://ddmedinski.wordpress.com/feed/]<br />
name=Danylo Medinski<br />
<br />
[https://klvincho.wordpress.com/category/SPO600/feed/]<br />
name=Kelvin Cho<br />
<br />
[https://thelucasexcerpt.wordpress.com/category/SPO600/feed/]<br />
name=Lucas Verbeke<br />
<br />
[https://joulecpa.wordpress.com/feed]<br />
name=Hong Zhan Huang<br />
<br />
[https://jgricespo.wordpress.com/feed]<br />
name=Justin Grice<br />
<br />
[http://http://stephenruthland.wordpress.com/feed/]<br />
name=Stephen Ruthland<br />
<br />
[https://andersoncdot.wordpress.com/feed/]<br />
name=Anderson Malagutti<br />
<br />
[http://chalispo600.wordpress.com/feed/]<br />
name=Cha Li<br />
<br />
[https://kojimiyauchi.wordpress.com/feed/]<br />
name=Koji Miyauchi<br />
<br />
[http://alam61spo600.blogspot.ca/feeds/posts/default/]<br />
name=Alan Lam<br />
<br />
[https://martinliam.wordpress.com/feed/]<br />
name=Liam Christopher Martin<br />
<br />
[http://annafatsevych.com/blog/category/CDOT/feed/]<br />
name=Anna Fatsevych<br />
<br />
[http://main.justinflowers.ca/web/wordpress/?cat=2&feed=rss2]<br />
name=Justin Flowers<br />
<br />
[http://joelaro.wordpress.com/category/open-source/feed/]<br />
name=Joel Aro<br />
<br />
[https://barbaradegraafsoftware.wordpress.com/category/open-source/feed/]<br />
name=Barbara deGraaf<br />
<br />
[http://blog.leapproject.ca/feed/]<br />
name=LEAP Project<br />
<br />
[https://dyegorov.wordpress.com/category/spo600/feed/]<br />
name=Dmytro Yegorov<br />
<br />
[http://klepetinskiy.blogspot.ca/feeds/posts/default/-/spo600]<br />
name=Kirill Lepetinskiy<br />
face=http://i.imgur.com/vPVBSTB.png<br />
<br />
[http://migueldcode.wordpress.com/feed/]<br />
name=Miguel Dizon<br />
<br />
[http://jjakuseneca.blogspot.ca/feeds/posts/default/]<br />
name=Joseph Jaku<br />
<br />
[http://gkpatel2.blogspot.ca/feeds/posts/default/]<br />
name=Gaurav Patel<br />
<br />
[http://sjhan5.blogspot.ca/feeds/posts/default/]<br />
name=Suk-Joong Han<br />
<br />
[http://spo600.blogspot.com/feeds/posts/default]<br />
name=Claire Debika Sullivan<br />
face=http://lh4.googleusercontent.com/-5YBwDhK8MqY/AAAAAAAAAAI/AAAAAAAAAEw/ATvCW93etzY/s80-c/photo.jpg<br />
<br />
[http://krevprogramming.blogspot.ca/feeds/posts/default/]<br />
name=Yehoshua Ghitis<br />
<br />
[http://kevinpaiva.com/category/spo600/feed/]<br />
name=Kevin Manuel Paiva<br />
<br />
[http://jaejoblog.wordpress.com/feed/]<br />
name = Jae Jo<br />
<br />
[http://joeysoddthoughts.blogspot.ca/feeds/posts/default/]<br />
name=Giuseppe Ranieri<br />
<br />
[http://spo6002015.blogspot.ca/feeds/posts/default/]<br />
name=Nitish Bajaj<br />
<br />
[https://tng23spo600.wordpress.com/feed/]<br />
name=Tom Ng<br />
<br />
[https://wordpresscom98745.wordpress.com/]<br />
name=Ricardo Bocanegra Meza<br />
<br />
[http://andrei600.wordpress.com/category/open-source/feed]<br />
name=Andrei Topala<br />
<br />
[http://spo600ninawip.blogspot.com/feeds/posts/default/]<br />
name=Nina Wip<br />
<br />
[http://berwoutcanada.blogspot.ca/feeds/posts/default/]<br />
name=Berwout de Vries Robles<br />
<br />
[https://yunhaowang.wordpress.com/feed/]<br />
name=Yunhao Wang<br />
<br />
[http://dwauspo600.blogspot.ca/feeds/posts/default/]<br />
name=David Wesley Au<br />
<br />
[http://techspotnewsx.blogspot.ca/feeds/posts/default/-/SPO600]<br />
name=Laily Ajellu<br />
<br />
[http://kyleklerks.wordpress.com/category/CDOT/feed/]<br />
name=Kyle Klerks<br />
<br />
[http://marangonim.blogspot.ca/feeds/posts/default/-/BigBlueButton]<br />
name=Matthew Marangoni<br />
<br />
[http://marangonim.blogspot.ca/feeds/posts/default/-/SPO600]<br />
name=Matthew Marangoni<br />
<br />
[http://pgincanada.blogspot.ca/feeds/posts/default/-/BigBlueButton]<br />
name=Jaeeun Cho<br />
<br />
[http://ozhurbenko.blogspot.ca/feeds/posts/default/-/BigBlueButton]<br />
name=Oleksandr Zhurbenko<br />
<br />
[https://johnjamesa70.wordpress.com/category/open-source/feed]<br />
name = John James<br />
<br />
[https://andreybykin.wordpress.com/category/open-source/feed]<br />
name = Andrey Bykin<br />
<br />
[http://raygervais.ca/category/open-source/feed]<br />
name = Ray Gervais<br />
<br />
[https://jlonghiblog.wordpress.com/feed]<br />
name = Joshua Longhi<br />
<br />
[https://timothymoy.wordpress.com/tag/open-source/feed/]<br />
name = Timothy Moy<br />
<br />
[https://naperkovskiy.wordpress.com/feed/]<br />
name = Igor Naperkovskiy<br />
<br />
[https://lenisac.wordpress.com/category/seneca/feed/]<br />
name = Len Isac<br />
<br />
[https://gapizzacalla.wordpress.com/]<br />
name = Garrett Pizzacalla<br />
<br />
[http://brookspatola.blogspot.ca/feeds/posts/default]<br />
name = Brooks Patola<br />
<br />
[https://badrmodoukh.wordpress.com/tag/open-source/feed/]<br />
name = Badr Modoukh<br />
<br />
[https://trandangkhue27.wordpress.com/tag/open_source/feed/]<br />
name = Dang Khue Tran<br />
<br />
[https://kramsamujh.wordpress.com/category/OSD600/feed/]<br />
name = Kevin Ramsamujh<br />
<br />
[https://tonypark0403.wordpress.com/category/Open-Source/feed/]<br />
name = Tony Park<br />
<br />
[https://pyang16.wordpress.com/category/open-source/feed/]<br />
name = Peiying Yang<br />
<br />
[https://cartryblog.wordpress.com/category/open-source/feed/]<br />
name = Eugueni Antsyferov<br />
<br />
[http://mikedohertyblog.wordpress.com]<br />
name = Mike Doherty<br />
<br />
[http://mdbellprog.blogspot.com/feeds/posts/default]<br />
name = Matthew Bell<br />
<br />
[https://johnjamesa70.wordpress.com/category/spo600/feed]<br />
name = John James<br />
<br />
[http://mfainshtein4.wordpress.com/category/CDOT/feed/] <br />
name=Max Fainshtein<br />
<br />
[http://http://hhashimi3.wordpress.com/feed/]<br />
name = Hamid Hashimi<br />
<br />
[https://derrickwhleung.wordpress.com/feed/]<br />
name = Derrick Leung<br />
<br />
[https://osd600mytryniuk.wordpress.com/category/Open-Source/feed/]<br />
name = Oleg Mytryniuk<br />
<br />
[https://jdseneca.wordpress.com/feed/]<br />
name = Jonathan Desmond<br />
<br />
[https://mchepigablog.wordpress.com/category/opensource/feed/]<br />
name= Margaryta Chepiga<br />
<br />
[http://zhazhazenan.blogspot.com/feeds/posts/default/-/Open%20Source]<br />
name = Zenan Zha<br />
<br />
[https://quangdattran.wordpress.com/category/spo600/]<br />
name = Quang Dat Tran<br />
<br />
[https://lawrencereyesoo.wordpress.com/feed/]<br />
name = Lawrence Reyes<br />
<br />
[https://leblogedeblotte.blogspot.com/feeds/posts/default/-/spo600]<br />
name = Lucas Blotta<br />
<br />
[http://pokim8989.blogspot.com/feeds/posts/default/-/Open%20source]<br />
name = John Kim<br />
<br />
[https://kdsbrowne.wordpress.com/feed/]<br />
name = Kert Browne<br />
<br />
[https://bbhawgandeen.wordpress.com/feed/]<br />
name = Brandon Bhagwandeen<br />
<br />
[https://medium.com/feed/@arsalanskhalid]<br />
name = Arsalan Khalid<br />
<br />
[https://jmrodriguesgoncalves.blogspot.ca/feeds/posts/default?alt=rss]<br />
name = Joao Rodrigues<br />
<br />
[https://ytian38.wordpress.com/category/OSD600/feed/]<br />
name = Yankai Tian<br />
<br />
[https://ewhite7blog.wordpress.com/tag/open-source/feed/]<br />
name = earle white<br />
<br />
[https://michaelpierreblog.wordpress.com/category/Open-Source/feed/]<br />
name = Michael Pierre<br />
<br />
[http://amehic.wordpress.com/category/open-source/feed]<br />
name=Ajla Mehic<br />
<br />
[https://lejara.wordpress.com/open-source/feed/]<br />
name=Leonel Jara<br />
<br />
[http://mmbabol.blogspot.com/feeds/posts/default/-/open-source]<br />
name = Mat Babol<br />
<br />
[https://sofiangotrong.wordpress.com/category/SPO600/feed/]<br />
name = Sofia Ngo-Trong<br />
<br />
[https://chunsinglam.wordpress.com/category/spo600/feed/]<br />
name = Chun Sing Lam<br />
<br />
[https://nicholas95com.wordpress.com/category/spo600/feed/]<br />
name = Nicholas Krause<br />
<br />
[https://jybaeblog.wordpress.com/category/SPO600/feed/]<br />
name = Jiyoung Bae<br />
<br />
[https://www.marcobeltempo.com/feed/]<br />
name = Marco Beltempo<br />
<br />
[http://ericschvartzman.blogspot.com/feeds/posts/default]<br />
name = Eric Schvartzman<br />
<br />
[http://belavina.me/feed.xml]<br />
name = Olga Belavina<br />
<br />
[http://eric-spo600.blogspot.com/feeds/posts/default]<br />
name = Eric Ferguson<br />
<br />
[https://bpatola.wordpress.com/feed/]<br />
name = Aaron Brooks Patola<br />
<br />
[https://jose-spo600.blogspot.ca/feeds/posts/default]<br />
name = José Aderbal Aragão Filho<br />
<br />
[https://jnguyen36blog.wordpress.com/category/spo600/feed/]<br />
name = John Nguyen<br />
<br />
[https://assmith2017.blogspot.ca/feeds/posts/default]<br />
name = Azusa Shimazaki<br />
<br />
[https://mithilanblog.wordpress.com/category/open-source/feed/]<br />
name = Mithilan Sivanesan<br />
<br />
[https://ron-spo.blogspot.com/feeds/posts/default]<br />
name = Ronen Agarunov<br />
<br />
[https://dps909.defilippis.ca/index.php/feed/]<br />
name = Steven De Filippis<br />
<br />
[https://srichardson6blog.wordpress.com/feed/]<br />
name = Shaun Richardson<br />
<br />
[https://pabinski.wordpress.com/feed/]<br />
name = Pablo Calderon<br />
<br />
[https://mswelke.wordpress.com/feed/]<br />
name = Matthew Welke<br />
<br />
[https://marvinrsanchez.wordpress.com/feed/]<br />
name = Marvin Sanchez<br />
<br />
[https://ghkuo.wordpress.com/feed/]<br />
name = Guan Huei Kuo<br />
<br />
[https://bluesockphil.wordpress.com/category/open-source/feed/]<br />
name = Phil Henning<br />
<br />
[https://smohiti.wordpress.com/feed/]<br />
name = Saeed Mohiti<br />
<br />
[https://techbreaksblog.wordpress.com/category/open-source/]<br />
name = Hadi Saeed<br />
<br />
[https://derrickwhleung.wordpress.com/feed/]<br />
name = Derrick Leung<br />
<br />
[https://jalemansite.wordpress.com/category/feed/]<br />
name = Johann Aleman<br />
<br />
[https://jespiritutech.wordpress.com/feed/]<br />
name = Jeffrey Espiritu<br />
<br />
[https://sanjitps.wordpress.com/feed/]<br />
name = Sanjit Pushpaseelan<br />
<br />
[http://blog.auios.com/feed.php]<br />
name = Connor Ngo<br />
<br />
[https://mb30myopensourceblog.blogspot.ca/feeds/posts/default]<br />
name = Patrick Godbout<br />
<br />
[https://franklinchenw.blogspot.ca/feeds/posts/default/]<br />
name = Qichang Chen<br />
<br />
[https://spo600geoff.blogspot.ca/feeds/posts/default/]<br />
name = Geoffrey Wu<br />
<br />
[https://alexopensource.wordpress.com/category/open-source/feed/]<br />
name = Alex Wang<br />
<br />
[https://zedsdps909blog.wordpress.com/category/Open-Source/feed/]<br />
name = Zukhruf Khan<br />
<br />
[http://qchen102.blogspot.com/feeds/posts/default/]<br />
name=Qiliang Chen<br />
<br />
[http://arscott28081253.wordpress.com/category/open-source/feed/]<br />
name = Aaron Scott<br />
<br />
[http://danielchangopen.blogspot.com/feeds/posts/default/-/opensource]<br />
name = Daniel Chang<br />
<br />
[https://aushakou.wordpress.com/category/open-source/feed/]<br />
name = Aliaksandr Ushakou<br />
<br />
</pre></div>Aushakou