Skip to content

GSoC 2018 Baani

Jump to bottom
Baani Leen Kaur edited this page Aug 10, 2018 · 25 revisions

Baani

Work Hours

Days Hours (IST) Meeting Tool
Monday 06:00 - 09:00 & 18:00 - 00:00 N/A Slack
Tuesday 07:00 - 17:00 1:1 Meeting Ancy Baani (10:00 - 10:30) Google Hangouts, Slack
Wednesday 06:00 - 08:00 & 18:00 - 00:00 GH Pages - All Team Meeting (08:00 - 09:00) Slack, Zoom
Thursday 06:00 - 18:00 & 17:00-23:00 N/A Slack
Friday 07:00 - 17:00 GSoC Happy Hour (21:30-22:30) Slack
Saturday 06:00 - 12:00 & 22:00-00:30 N/A Slack
Sunday 00:00 - 01:30 & 06:00-10:00 N/A Slack

Short Bio

I am a sophomore at IIIT Delhi, India pursuing a B.Tech in Computer Science & Engineering. I love to play around with code & build stuff that impacts lives.

I am one of the 6 Google Venkat Scholars, and also one of the 100 Women Techmakers Udacity scholars, worldwide. I am also a recipient of the Facebook F8 scholarship, Google Developers Day Conference scholarship, Grace Hoppers Celebrations, India conference scholarship by Google.

I have always been creative and full of new ideas and themes, and programming just gives me the tools to implement them.

Profile Links

Gmail | My Blog | GitHub | LinkedIn | My Proposal

Weekly Status Report for Week 1

What have you accomplished this week (list specific items accomplished)?

  1. Setting up an Angular app for current codebase, while ensuring code does not break. (Issue #175)
  2. Attended Github Pages Weekly meeting, Community session, 1:1 with Janice, 1:1 with Divyanshu.
  3. Submitted the PR for the nav-bar(as discussed in all-teams meeting).
  4. Actively participate in slack discussion.

What issues or roadblocks have you encountered this week? Was awaiting confirmation from mentors & May, is I could make the app from scratch without worrying about the existing codebase or not.

Have they been resolved, and if so, how? Yes. After getting mentor's approval. I got May's approval yesterday.

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Data Collection.
  2. Creating a database JSON file (use ER diagram), using data from GSoC 2015-2017.
  3. Attend all the Team Building Sessions, weekly GH-Pages sessions & 1:1 meetings.

How does your progress compare to your project schedule? It is in sync with it.

Weekly Status Report for Week 2

What have you accomplished this week (list specific items accomplished)?

  1. Sent updated PR for Navigation Bar incorporating changes suggested in Wednesday's All Teams Meeting. (Issue #175)
  2. Attended Github Pages Weekly meeting & 1:1 meetings.
  3. Sent the PR for Contact Us page.
  4. Sent the PR for the JSON Data Files.
  5. Actively participate in slack discussion.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Write a blog for Week 2.
  2. Create the Projects Page.
  3. Create the JSON file for the entire database ( Members - using Github API, Projects, Programs)

How does your progress compare to your project schedule? On time

Weekly Status Report for Week 3

What have you accomplished this week (list specific items accomplished)?

  1. Submitted Week 2 PRs - Ensured high modularity in code.
  2. Had a 1:1 with Ancy, Janice; discussed about the contents on the About us page.
  3. Wrote a blog about Angular Lifecycle Hooks.
  4. Submitted PR to shift to icon stack symbols.
  5. Submitted a PR to make the home page slider, using carousel and ngFor.
  6. Attended all teams meeting, presented my work and incorporated the suggestions.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Submit Week 4 PRs.
  2. Write a blog summing up what I learnt in Coding Phase 1.
  3. Check for mobile responsiveness for the app.

How does your progress compare to your project schedule? On time.

Weekly Status Report for Week 4

What have you accomplished this week (list specific items accomplished)?

  1. Submitted week 4 PRs.
  2. Had a 1:1 with Ancy, 2:1 with Janice & Divyanshu.
  3. Attended all teams meeting.
  4. Worked on mobile responsiveness of the app.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Make Contact Us page mobile responsive.
  2. Read about using Bootstrap instead of media queries as suggested by Divyanshu.
  3. Submit PR for Week 5.

How does your progress compare to your project schedule? On time.

Weekly Status Report for Week 5

What have you accomplished this week (list specific items accomplished)?

  1. Submitted week 5 PRs.
  2. Incorporated feedback to Week 3 and 4 PRs.
  3. Had a 1:1 with Ancy.
  4. Attended all teams meeting.
  5. Worked on the mobile responsiveness of the App.
  6. Published a blog on Week 4.
  7. Created first timers issues and guided newcomers on getting started.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Setup a DB on MLab.
  2. Store the data in the DB.
  3. Create an API for using the MongoDB database.

How doesyour progress compare to your project schedule? On time.

Weekly Status Report for Week 6

What have you accomplished this week (list specific items accomplished)?

  1. Submitted week 6 PRs.
  2. Incorporated feedback from mentors.
  3. Had a 1:1 with Ancy.
  4. Attended all teams meeting.
  5. Setup MongoDB on MLab.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Publish Blog.
  2. Submit Week 7 PRs.
  3. Incorporate feedback of mentors.

How doesyour progress compare to your project schedule? On time.

Weekly Status Report for Week 7

What have you accomplished this week (list specific items accomplished)?

  1. Submitted week 7 PRs.
  2. Incorporated feedback from mentors on past PRs.
  3. Had a 1:1 with Ancy and Janice.
  4. Attended all teams meeting.
  5. Created newcomers issues.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Publish Blog.
  2. Incorporated feedback of mentors.
  3. Work on Documentation

How does your progress compare to your project schedule? On time.

Weekly Status Report for Week 8

What have you accomplished this week (list specific items accomplished)?

  1. Attended all meetings
  2. Incorporated feedback from mentors on past PRs.
  3. Had a 1:1 with Ancy and Janice.
  4. Attended all teams meeting.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Publish Blog.
  2. Close past PRs.
  3. Work on Documentation

How does your progress compare to your project schedule? On time.

Weekly Status Report for Week 9

What have you accomplished this week (list specific items accomplished)?

  1. Ported the existing Program Page to the new codebase, integrated it with mLab, and set up the MEAN stack to get data from the mLab DB into the program page, which having minimal code redundancy.
  2. Resolved Merge conflicts (manually), Incorporated feedback from mentors on past PRs.
  3. Create newcomer issues, available to be assigned to others.
  4. Had a 1:1 with May.
  5. Attended all teams meeting.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Set Up the MEAN stack for the slack-systers-opensource inviter.
  2. Ensure validation through reCaptcha.
  3. Add the signing of the Code of conduct. (Compulsory scrolling through it).
  4. Integrate Github Authentication.
  5. Send the data entered by the user to the database.
  6. Send an email to the user, having the link to sign up on slack.

How does your progress compare to your project schedule? On time.

Weekly Status Report for Week 10

What have you accomplished this week (list specific items accomplished)?

  1. Set up the Slack Open Source MEAN stack App. Sent a PR for the same.
  2. Wrote an in-depth blog on how to connect an existing Angular 5 App to a MongoDB database - something for which I could not find good resources online during the time I researched about the same problem. https://medium.com/@BaaniLeen/connecting-angular-5-app-to-mongodb-database-mean-stack-9b4b4232e219
  3. Studied about how to host the MEAN apps on Heroku, tried deploying a demo MEAN app to Heroku, faced verification issue for integration with mLab (credit card verification needed), found a workaround for that by integrating Heroku from Mlab side, as well as compared between the different methods of Hosting MEAN apps, including AWS. Also discussed with the community why the MEAN app cannot be deployed on GH-Pages.(need a node server running instance) https://systers-opensource.slack.com/archives/C99N86T43/p1531657786000017 https://systers-opensource.slack.com/archives/C99N86T43/p1531720776000090
  4. Discussed about various ways of Documentation and why I feel Sphinx and RTFM should be used for the same, consistently across different languages. https://systers-opensource.slack.com/archives/C99N86T43/p1531599628000041
  5. Attended all teams meeting, 1:1 with Ancy, Janice, Bethany as well as work sessions with May and all my mentors to discuss about code and get feedback about my work. Discussed with Bethany about various aspects of our project. Discussed with May about setting up an instance on AWS instead of Heroku since we do not have an account on the later. Discussed the Pros and cons with Monal. Discussed with May regarding refactoring the code and maintaining consistency of design in the entire website. Also, as discussed with May for the slackopensource inviter, we can do away with the Recaptcha since we already are using GitHub to authenticate the user. https://systers-opensource.slack.com/archives/C99N86T43/p1531801913000110 https://systers-opensource.slack.com/archives/C99N86T43/p1531886711000008
  6. Read about Npm install and the package.json file in depths and wrote a blog about the same : https://medium.com/@BaaniLeen/npm-install-the-magic-command-dc786693e740 Refer to the review left by Bethany, which motivated me to read more and understand how it works : https://github.com/systers/systers.github.io/pull/240.
  7. Submitted PRs #15,#18, #19 for the slack inviter and working on fixing the minor details while porting the current Home Page to Angular before turning in my work for the same.
  8. Submitted PRs #244, #249 and #250 for Systers.io repo. Refactored the navbar. Aligned the card footers for the project and newcomers page.
  9. Ported the current website UI to Angular.
  10. Added Github Authentication. Switched to a NodeJS, ExpressJS app since Angular was not needed since the app does not involve alot of different pages and components and adding Github Authentication for a MEAN app was throwing up alot of unnecessary errors, which could easily be done away with. Also, adding Github Authentication to a MEAN app (latest versions) did not have any good resources online. Tried to run the az-webdev repo, since it was our inspiration for the slack inviter, but according to the instructions mentioned in its contributing guidelines, it was not working. Discussed the error with the community but could not get any breakthrough about how to resolve it. Finally implemented a NodeJS-ExpressJS app, using Jade as the templating engine. Discussed with Bethany about other Templating engines- pros and cons, and decided to stick with Jade. The reason I used Jade instead of HTML was that since I needed to access the server side variables on the client side, Jade inserted the value of the variables at the server side and then converted into HTML to be run at the client side.
  11. Sent a PR for sending an email to the email ID of the user mentioned on his/her Github profile.
  12. Added a basic checkbox for the 'I agree to the TnC'.
  13. Read in-depth about Jade and how to create good UI interfaces in it. Read about Jade-Bootstrap http://rajasegar.github.io/JADE-Bootstrap/getting-started.html. Faced issues with the spacing since unlike the usual Bootstrap spacing, we do not have mt-x or pt-x working for Jade. Looked up how to introduce a new line in Jade in depth and finally came up with the solution : br |
    (A br followed by a pipe which is followed by a few spaces) I did try to look up for convertors from Jade to HTML but realised we would not need them as Jade lets us access the Express variables with ease.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Fix issues #29, #20, #31 for the slack inviter.
  2. Resolve all codacy errors and incorporate mentor feedback.
  3. Submit another blog about what I learnt about node and Express Apps, how to use Github Authentication, How to Do access express(server side) variables using Jade, why I chose to use Jade instead of HTML, why do we not need a MEAN stack App for the slack inviter, etc.
  4. Add the Newcomers Issues to the systers.io repo. Send a PR for the same.
  5. Finalise upon the Template of the email to be sent with the slack invitation.
  6. Read up on how to use environment variables and add it to gitignore to ensure privacy and security is not compromised.
  7. Shift the Slack App from Local DB to MLab.
  8. Host the apps.

How does your progress compare to your project schedule? On time.

Weekly Status Report for Week 11

What have you accomplished this week (list specific items accomplished)?

  1. Wrote a blog about Pug : https://medium.com/@BaaniLeen/pug-framework-for-node-applications-fbc5d3c02ee7
  2. Incorporated mentor feedback and codacy errors for PR #28. Closed all open issues and PRs which have been resolved in the past or have been included in PR#28.
  3. Resolved Merge conflicts from the terminal while resolving PRs - #249, #250.
  4. Read about how to integrate Newcomers issues on a website.
  5. Reviewed PR#248.
  6. Submitted PR#253, #259, #260, #261, #262 for systers.io repo. Fixed UI bugs and changes suggested by mentors.
  7. Reopened PR#28 wrt gsoc2018 branch.
  8. Successfully did a git rebase, and caught on the lost merge conflicts code, after repeated attempts. https://systers-opensource.slack.com/archives/C99N86T43/p1532516259000176 PR#255, #258. #259 on systers.io repo.
  9. Tried out implementing embedding Github issues in the webpage, unsuccessful attempt, finally got some suggestions to use iframes instead. Thanks to @anumeha:) https://systers-opensource.slack.com/archives/C99N86T43/p1532439529000287
  10. Discussed about how the error message should be displayed : https://systers-opensource.slack.com/archives/C99N86T43/p1532482608000068.
  11. Read about Front end performance metrics: https://systers-opensource.slack.com/archives/C99N86T43/p1532534868000100
  12. Attended 1:1 with mentors.
  13. Submitted PR#261 , #257, #263 systers.io repo. Fixed UI bugs and changes suggested by mentors. Resolved merge conflicts.
  14. Gave phase 1 and 2 demos.
  15. Got feedback about the UI implementation for Issue#256 on slack. https://systers-opensource.slack.com/archives/C99N86T43/p1532703809000169
  16. Discussed about the r=all not working for the embedded issues link from Publiclab. Slack LInks: https://systers-opensource.slack.com/archives/C99N86T43/p1532574287000146; https://systers-opensource.slack.com/archives/C99N86T43/p1532574360000105.
  17. Created an upstream issue for the same on the community-toolbox repo on Publiclab : https://github.com/publiclab/community-toolbox/issues/28
  18. As pointed out by Bethany, read and figured out why on clicking onto an issue in the iframe, we get a blank screen (Github Content security policy does not permit the content to be displayed in the iframe, thus giving an error), The same issue can be accessed by opening in a new tab/window. https://github.com/systers/systers.github.io/pull/263
  19. Reported some improvements/bugs for community website: https://systers-opensource.slack.com/archives/C99N86T43/p1532575856000057 , https://systers-opensource.slack.com/archives/C99N86T43/p1532575977000108, https://systers-opensource.slack.com/archives/C99N86T43/p1532576078000011.
  20. Improvised on the Newcomers Issue Page, tried out various approaches to finally display the projects with their respective issues on the websites, sorted acc to their tech stack. Slack link: https://systers-opensource.slack.com/archives/C99N86T43/p1532619465000180
  21. Had a 1:1 with may and discussed about having first-timers-issue as the label for all repos.
  22. Attended Community session ; Had a 1:1 work session with Janice.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Submit PRs for existing open bugs/issues on systers.github.io/slack inviter repo.
  2. Submit a blog.
  3. Report more UI bugs.
  4. Attend all meetings.
  5. Resolve all codacy errors and incorporate mentor feedback.
  6. Finalise upon the Template of the email to be sent with the slack invitation.
  7. Read up on how to use environment variables and add it to gitignore to ensure privacy and security is not compromised.
  8. Shift the Slack App from Local DB to MLab.
  9. Host the apps.

How does your progress compare to your project schedule? On time.

Weekly Status Report for Week 11

What have you accomplished this week (list specific items accomplished)?

  1. Incorporated mentor feedback in PR #263. Resolved merge conflicts.
  2. Submitted PR#264.
  3. Read in depth about how to deploy an existing MEAN app on Heroku. Trying to fix the error by looking at the Heroku logs. Also, since I would need to create a PR for the same, and once the PR is merged, only then can I test the changes, so am trying to replicate the same for a local MEAN repo, learn the crux of what needs to be done and then apply it to our branch and create a PR for the same. https://devcenter.heroku.com/articles/mean-apps-restful-api
  4. Wrote a blog on Embedding Newcomers Issues on webpages. https://medium.com/@BaaniLeen/embedding-newcomers-issues-on-a-webpage-7731dce77dbe
  5. Reviewed PR#265. Requested for it to be closed since it did not follow Systers OSS guidelines.
  6. Attended All teams meetings.
  7. Read and understood the link shared by Anumeha for the deployment of the app and discussed with the community that it is only applicable to Angular Apps being served statically by express(to the best of my understanding) : https://systers-opensource.slack.com/archives/C99N86T43/p1532885542000063
  8. Was able to successfully deploy a NodeJS - MLab demo lab and access the API calls and insert data into MLab and get data from there! https://shrouded-sands-41552.herokuapp.com/api/contacts. Shared about my major takeaways from the same on Slack: https://systers-opensource.slack.com/archives/C99N86T43/p1532974252000390.
  9. Finally deployed the MEAN Stack App on Heroku, with proper connection to MLab: https://shrouded-sands-41552.herokuapp.com/ . Discussed about the same on Slack: https://systers-opensource.slack.com/archives/C99N86T43/p1533009724000102 and my learnings: https://systers-opensource.slack.com/archives/C99N86T43/p1533010156000131.
  10. Deployed the systers.io MEAN Stack App on heroku through my personal account: https://systers-opensource.slack.com/archives/C99N86T43/p1533062330000356. Resolved the Memory Leakage error.
  11. The Mlab database was still not getting accessed, discussed with Bethany in the 1:1 meeting and resolved the same. https://systers-opensource.slack.com/archives/C99N86T43/p1533140072000087
  12. Attended 1:1 meetings with all mentors.
  13. Was able to successfully deploy the Systers Slack Inviter App(nodeJS) on Heroku. Created a procfile to run the same since start script was not working. Created PR #36.
  14. Ported from the local DB to the MLab Database.
  15. Github Authentication was not working on the Heroku App. Firstly the issue was since the callback URL also had to be updated in the Github App which was created for doing Github Authentication and since even after that the error repeated, I figured out after online research that the issue was due to cookies being stored on the browser. https://systers-opensource.slack.com/archives/C99N86T43/p1533222950000167
  16. Fixed the request timeout error for Github Authentication after understanding the reason behind it. https://systers-opensource.slack.com/archives/C99N86T43/p1533222950000167
  17. Incorporated mentor feedback in PR#264 for systers.io repo.
  18. Conducted AMA Office hour for newcomers. (4 hours every week)
  19. Created the template for the slack inviter email.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Submit PRs for existing open bugs/issues on systers.github.io and slack inviter repo.
  2. Submit a blog.
  3. Report more UI bugs.
  4. Attend all meetings.
  5. Send a PR for the Slack Inviter Email to be sent.
  6. Work on getting the feedback from the community and incorporating that.

How does your progress compare to your project schedule? On time.

Weekly Status Report for Week 12

What have you accomplished this week (list specific items accomplished)?

  1. Transferred ownership of the Systers Github Authentication App from BaaniLeen to Systers.
  2. Updated the PR with the new heroku app links.
  3. Conducted AMA Office hour for newcomers. 🙂
  4. Created PR#275.
  5. Created new bug issues - #270, 271, 272, 273, 274 to be worked upon.
  6. Attended the all teams meeting.
  7. Submitted PR for adding TnC for slack inviter. Faced problem with how to test it locally, since the callback URl for the Github Auth app was updated to the heroku link, and the page on which TnC was to be added had to appear after having Github Authentication. Changed the order of pages showing up to test the app locally.
  8. Attended All Teams meetings.
  9. Wrote a blog.
  10. Created UI for Thank You page in Jade, as well as did routing in NodeJS. Submitted a PR for the same.
  11. Resolved the Heroku App Cannot GET /<component-name> error. Submitted a PR for the same.
  12. Fixed the alignment of the Contributors Page on systers.io. Submited a PR for the same.
  13. Discussed about the implementation of the Feedback from the marketing team with May, all the mentors and @anumeha.
  14. Added Mobile Responsiveness for the Contact Us Page. Submitted a PR for the same.
  15. Updated
    tag to ;. Created a PR for the same.
  16. Fixed the Newcomers Page UI change (Issue #271). Submitted a PR for the same.
  17. Attended 1:1 meetings with mentors.
  18. Worked on the documentation: https://docs.google.com/document/d/18X83wQjltI2PyWmYqNx4cHvGdTBTu2NaWnlIizdsLO8/edit https://systers-opensource.slack.com/archives/C99N86T43/p153369200100006110. Deployed the systers.io MEAN Stack App on heroku through my personal account: https://systers-opensource.slack.com/archives/C99N86T43/p1533062330000356. Resolved the Memory Leakage error.
  19. Fixed the error page issue.

What issues or roadblocks have you encountered this week? N/A

Have they been resolved, and if so, how? N/A

Do any of the issues or roadblocks still exist and what steps have been taken to resolve them? N/A

Is further assistance necessary to resolve existing issues? N/A

What do you plan to accomplish next week?

  1. Fix all UI bugs.
  2. Submit the final blog.
  3. Attend all meetings.
  4. Incorporating community feedback.
  5. Give my live demo

How does your progress compare to your project schedule? On time.

Github Pages

Documentation

Projects

GSoC Students

Programs application pages

Clone this wiki locally