Skip to content
This repository has been archived by the owner on Sep 4, 2018. It is now read-only.

Conference Call Notes, March 29, 2017

Jump to bottom
John Hampton edited this page Mar 31, 2017 · 1 revision

March 29, 2017:

  • The wiki Home page contains a summary of last night's conference call. Team members are free to add/edit content on the Wiki.

  • Please add some info about yourself to the Squad Members wiki page so we can learn a little about you, your time zone, and how to best keep in touch with you.

  • We're hoping to do another conference call next Tuesday at 8pm EST (that time had the most votes on the Slack poll). If team members prefer another time, let @sethbergman or @jhampton know! We are here to help. A tentative Weekly Schedule is on the wiki.

  • The boilerplate for the sample app has been uploaded by Seth to the GitHub repo here - go ahead and clone it locally, and follow the install/start instructions to see if you can get it running on your machine.

  • There are still two last-minute changes for the sample app that Seth and John need to add - they should be ready shortly.

    • Adjust the Angular module registration so the dummy favorite-teams component located in /app/components/demo renders on the main page - John can add this - see PR #4. This just serves as an an example of adding a component to the page, the component will be removed from the index page later.
    • Add a watcher / live-reload task to watch for changes, so the server doesn't need to be restarted / browser doesn't have to be reloaded when changes are made during development - Seth can add this

  • Features to Work on This is the why we're here - to build and learn. We'd like each member of the squad to add at least ONE feature that they would like to add to the sample app. It can be anything, so feel free to be creative. Ideally, you will be able to utilize all four of the CRUD actions (Create / Read / Update / Delete) on a component of your choice, and display / persist data to and from the back-end. Once you know what you would like to build, please add a GitHub issue describing the feature. The goal is to build something in a separate feature branch that won't cause conflicts with what anyone else wants to build, ideally on a separate route /page. Once your issue is up, anyone else on the team can review it, add suggestions, and then you are free to go to work. We can continue using this pattern for adding features to the application, as long as it suits everybody.

Ask questions if you need help or don't know where to start!

Clone this wiki locally