Create Presentation materials, rehearse

[marckunze]

15 minutes

what happened why it happened further improvements

demo of product

Prove that we do good job on important product

[marckunze]

Need to go over what we are going to say and show at the presentation, maybe prepare materials.

[MarkHammondJr]

This presentation just became even more important. I know Prof. Brick said we were released from taking a final exam, but I wouldn't be surprised if the presentation replaced it.

[JackLindgren]

Please let me know what I can contribute to the presentation (graphics, a slideshow, whatever) - I know I've been totally absent from the coding on this (and will be informing prof Brick of this fact). I was thinking about writing a summary of the history of the project based on the issue tracker and Google group posts. Also, (and I think this is a different issue) do we have the program documented other than the functional spec/wiki? I am reasonably in the groove of writing documentation right now and would like to take this on if it's still open.

[marckunze]

Feel free to self-assign. I haven't started on anything. I was going to do a google docs presentation or ppt online, but I won't be able to start until Saturday afternoon at the earliest. So if you want to start pulling together some materials and then just send us the link to review that's fine.

[JackLindgren]

Here is an overview I created of the project and the steps (it needs more work but I'm posting it here now, I'll be adding more to the later stages ASAP). I was going to put it all into a Prezi presentation (what they use for TED talks!) and then we can all wear black turtlenecks and talk about building the future. https://docs.google.com/document/d/1NBe6ghcZp9bSW7rMQ9oJmh-PlIK9dBuePclXSk6K11w/edit?usp=sharing

[JackLindgren]

Also wrote a user-facing documentation of how to use the site: https://docs.google.com/document/d/1byMh4hFD8Gw2HKUGsx2UxWVAyki0WnT_nwoHbH_GTB0/edit?usp=sharing

[marckunze]

Do you think you could add the user documentation to the wiki as a markdown document.

[marckunze]

Just rostering off all the technologies we used, am I missing anything? Not sure where to put git/github on this.

Front	Back
HTML5	Ruby
CSS3	Sinatra
Bootstrap	Datamapper
js	Postgresql / sqlite
jquery	Heroku
	Pony
	Mandrill
	Warden

[MarkHammondJr]

I hope you don't mind, but I edited in one you forgot.

[marckunze]

no problem. I just realized how many gems and tools we included in all of this.

[MarkHammondJr]

All because learning rails would have been too much work.

[marckunze]

Yup, basically we started simple, you keep adding one more thing, and then boom, you might as well have started with rails because at least the documentation and community is stronger.

[JackLindgren]

Added the user documentation to the wiki. Started working on a slideshow (https://prezi.com/luzjnqju3wf9/rancor/)

[marckunze]

What were you planning to use the empty boxes in the end for?

Since we don't have class tomorrow night, does anyone have time to meet in the afternoon on Thursday and go over what to say and rehearse briefly before class? We probably all can't talk. And who wants to take on performing a live demo?

At this point I'm thinking the order is

• This presentation (needs to cover)
  • what happened
  • why it happened
  • Further improvements
• Live demo
• Open to Questions

[JackLindgren]

the empty boxes are for a recap at the end - I was going to go through the timeline of how features were added and what tools were used to implement them. also, so I'm clear, Pony is a Ruby gem that allows sending email, and Mandrill is the outside service that sends it, right? they connect to each other right?

[marckunze]

Correct on the pony/mandrill, although mandrill does have an API we are not using it.

[JackLindgren]

I'm worried that I'm prioritizing the issues based on what I was thinking about the most, so please let me know if I should elaborate on some of the points on here: http://prezi.com/luzjnqju3wf9/?utm_campaign=share&utm_medium=copy

The stuff that doesn't tie into a direct solution seems harder to explain in here - the broad stroke decisions at the beginning (what framework? how to do the database?) are easier to put in here than the details toward the end (fixing styling, removing bugs, etc.)

[dennisccsf]

i haven't got anything to add but it looks great so far.

[nvh82]

Looks good! So I am back from out of town. The site really came together. Is there anything that I can help work on these last two days?!

[marckunze]

I think the framework elaboration is fine. With the details what happened as we progressed was a lot of short iterations. We wrote the spec, added that into a bunch of issues. Then tried to divy that up into tasks. As we progressed with the project it became 1. add feature/enhancement, 2. think about what the next missing piece is, 3. add that to the tracker, then add that feature(back to 1) and repeat until we roughed it all out. I don't think the details were that easy to identify until you get closer to it all. It was a code, run, review output, repeat.

[marckunze]

With the determine & prioritize functionality I would say it was. Write spec, break spec into issues, slot issues into core product and enhancements, with a lot of consideration on can we do it vs. how hard would it be.

[nvh82]

I just added a last push...the new_user page scales now and it's more uniform with our other page layouts.

So how is our presentation going to flow...are we all going to present a portion/speak? How should we coordinate this?

[marckunze]

Not sure all of us can speak (15 mins split among 7 people is a lot of transitions), I was thinking 3-4 with maybe 2 splitting the presenting, 1 doing demo, and the rest answering questions. I was hoping we could meet before class to rehearse all of this.

[dennisccsf]

i'm free to meet up before class

[nvh82]

I can meet before class at 5PM.

[MarkHammondJr]

I'm free whenever.

[marckunze]

I'm thinking maybe 3 in the afternoon. Just need a few people to do the run through with a couple of working through what we're saying, syncing that up with the presentation and runs through the demo. @allabouttoledo are you free to meet if we have to update the presentation?

Also, @MarkHammondJr , do you remember why we decided to split it up into modular style? I'm just thinking that and the helper functions are what turned us into something that was about as close to rails as sinatra.

[MarkHammondJr]

Warden forced us to move into the modular style.

[marckunze]

ok, just figured it was worth noting as one of the challenges how this thing went from a simple little sinatra app with a few files to this pretty involved structure that is has now.

[JackLindgren]

I will add:

• Warden forced us into a modular style
• Write spec, break spec into issues, slot issues into core product and enhancements, with a lot of consideration on can we do it vs. how hard would it be

I have work until 5:00 - I'll try to get there ASAP after though.

I will post a link to the Prezi here and in the Google group later tonight or during the day tomorrow in case I am running late/get hit by a bus/bit by an ASP/strangled by a Python/murdered for making dad jokes/etc.

[nvh82]

Can you post where you guys will be and I will head straight there after work - I get off at 4:30PM.

[marckunze]

Last time the plan was to meet up outside of the classroom, then just find a space to work. Does 3 work for the early folk? Then post here or shoot an email out or something.

[MarkHammondJr]

I'm fine with 3. I'll probably just be sick of studying by that time anyways.

[fontl]

I can make it.

[JackLindgren]

Here is the link: http://prezi.com/gq_oevyls5me/?utm_campaign=share&utm_medium=copy

Let me know ASAP if we need to change anything.

[marckunze]

Looking at it now, we'll let you know if anything is off. We're in the next room over from the classroom at the moment

[nvh82]

I am almost there...15min. I'll head to the room next to our classroom

[marckunze]

Done.phew

[MarkHammondJr]

Well I think that went well.

[marckunze]

I hope so, we'll see what the final grades say. And of course see what users and whoever looks at the code thinks. Now the weird cool down period from having obsessively worked on this for the past couple months.

[MarkHammondJr]

Grades are in. 75 for the project (highest was 83).

[marckunze]

Our size might have worked against us in that regard because of not self-voting. Had there only been us and DuMaf we would have received 6 and we would have received their 4. But we'll never know how it all broke by vote.