CSC322.01 2016S, Class 05: Iteration 0: Wrapup ============================================== _Overview_ * Preliminaries. * Admin. * Upcoming Work. * Extra Credit. * Questions. * Presentation format. * Preparation time. * Presentations. * Work time. Preliminaries ------------- ### Admin * Missing: BL * Don't forget to submit weekly electronic reports on Wednesday nights. I only think I got two last night (Grant Board and Resource Portal). * We will be working on bi-weekly in-class presentations, starting this week. (Details in the outline/eboard.) * It's probably time to check in with your clients and mentors, if you haven't done so already. Clients should be in-person meetings; mentors will probably be Skype. I generally suggest the last hour or two of class for such meetings. * Do you have any planned meetings? * Reminder: You have responsibility to your team; if you can't be in class, let them know in advance. ### Questions Presentation Format ------------------- These presentations will be every-other week, so that you have more work time in the alternate weeks. * _Intended Goals_. Remind us of your goals for the time period and the points you associated with those goals. * _Overview of Accomplishments_. Which of those goals did you accomplish? What other (unexpected) things did you deal with along the way? And what points would you assign to them? * _Demo_. Show off the current state of your system, focusing on the parts you were working on. * _Code Walkthrough_. Show us an interesting part of your code from the past two weeks and explain it to us. (Optional today.) * _New Goals_. What do you intend to accomplish over the next two-week iteration? What points have you assigned to each task? How are you dividing the work? * _Questions_. Questions to your peers. Questions from your peers. Please strive for organized and coherent presentations. Time To Prepare Presentations ----------------------------- You will have some time to work on your presentations. Presentation: Notifications --------------------------- ### Goals * Send a message to the classroom [3] NO * See all the texts that have been sent [8] NO * Get Cucumber running and write cucumber tests [8] Yes * Learn enough CSS to contribute/pair [0] Yes * Restructure the CSS folder [4] Yes * Make the repo installable [2] Yes * Configure Heroku [2] No, but not necessary Sam says: * You are supposed to work in pairs (or, better yet, as a whole team) * You are not supposed to insult your group mates * Share! * Include points * Include goals that were not accomplished ### Accomplishments * Get Cucumber running and write cucumber tests [8] Yes * Learn enough CSS to contribute/pair [0] Yes * Restructure the CSS folder [4] Yes * Make the repo installable [2] Yes * Get money to pay for text messaging [1] Yes Velocity of 14. * 86% code coverage * Last week 6/337 passed. Now 307/337 pass. Yay! ### Demo * Look! Tests! Unfortunately, we are sending texts as part of our tests and we have no idea where they are going. * Look! Pretty buttons! No documentation! We'll work on it. ### Code * Look! Undocumented code. ### Plans * Stomp all of the bugs. [9] (LG and AM) * Message history. [8] (LG and AM) * More Cucumber tests for privacy stuff [5] (EE and RHB) * Get RSpec running [2] (EE and RHB) * Document general design of CSS [4] (CMV and KC) * Finalize mockup for send a message [1] (CMV and KC) * Finalize mockup for history [1] (CMV and KC) * Finalize mockup for settings [1] (CMV and KC) * Finalize mockup for login [1] (CMV and KC) * Finalize mockup for admin path [1] (CMV and KC) * Finalize mockup for classrooms [1] (CMV and KC) * Finalize mockup for edit users [1] (CMV and KC) ### Questions _How will you do a better job of working together?_ > We will try harder. And it seems like we are moving on to things that are better done in pairs. _What kinds of cukes are you writing?_ > Mostly Web stuff. Get it working. _Can Leah leave now?_ > Yes. Presentation: Board Bank ------------------------ ### Goals * Getting to ground level! * Get Travis to run the tests. [ ] * Restructure HTML and CSS and other files. DRY it out. [ ] * Update all the Gems. Yay version mismatches! [ ] * Implement elastic search, which wasn't working properly [ ] * Learned not to install external libraries into source code. [ ] * Updated README [ ] ### Accomplishments * Get Travis to run the tests. [ ] Somewhat. * Restructure HTML and CSS and other files. DRY it out. [ ] Somewhat. * Update all the Gems. Yay version mismatches! Learned pipeline issues. Broke things. [ ] * Met with previous semester's people. They can't help. [ ] * Implement elastic search, which wasn't working properly. Seems to be working. [ ] * Learned not to install external libraries into source code. [ ] * Updated README [ ] ### Demo * Search! Yay! * Broken UI! Boo! ### Code * Not today. ### Plans ### Questions Presentation: Grant Application Management ------------------------------------------ ### Goals ### Accomplishments * Install Travis [6] * Assign roles [.5] * Implement "as a user I don't want stupid messages when I log in because I hate being irritated. [-1] ### Demo ### Code ### Plans * Talk to previous team and/or Alex about AWS issues. [2] * Finalize reviewer functionality. (Meet with Nicole.) [7] * Write tests for reviewer functionality. [8] * Clean up Cucumber tests - write step definitions. [8] * Need email sending gem. [6] * DRY out the code / refactor / clean up. [5] * Walk through user paths manually, and then with cucumber [8] ### Questions ### Goals ### Accomplishments ### Demo ### Code ### Plans ### Questions Work Time ---------