Skip to content
rubygeek edited this page Sep 14, 2010 · 25 revisions

Skype ids: mrnicksgirl, rebeccag47, bevcnelson

Next Meeting
Aug 12, 9:30p CST

Tasks are stored in Pivotal Tracker

Past Meetings

Aug 5, 9:30CST

Nola got some tweaks on the UI and set up on heroku and its running, not quite setup. Rebecca set up the whitelist table on the site and its ready to go. Still some debugging. This week work on blog post and troubleshooting the site.

7/29, 9.30pm
Graph is working !
White list is working !

7/14/10
Nola found a new graph called highcharts and got it basically working, still needs better query to find task counts for week for a user
Rebecca got a white list of users setup, so only those users can make accounts.

Next:
Nola will finish graph, and do the deleted tasks
Rebecca will take the list of devchix and write a rake task to load those into a table.

6/20/10
Just a quick catch up meeting, everyone has been so busy!
Nola will work on report
Rebecca will look at using devise to make real user accounts

5/23/10
Progress:

  • closed look and feel story, Nola added some things to make it look decent and its good for now
  • closed task report, Rebecca did a basic report of task history, good for now. More work to do but we need to do some mockups and brain storm a bit.
  • closed controller tests story, since our controller right now is mostly REST, no point to test now.. next time lets do TDD
  • remaining story is to add Task Validations, Nola will help Beverly with that when she has time
  • added some new stories: Real Authentication, Report mockups, Easy way to make development data
  • added some future stories to keep in mind

4/3/10

  • Spent a while working out some git branching issues. Rebecca had been evaluating Gruff for charts and working in a local branch. We pushed the branch to the repository ‘git push origin gruff’. Eventually found the way for others to pull it down : ‘git checkout -b origin/gruff’
  • Decided the dependency mess for gruff is too much and decided to try the Google Charts API.
  • Decided our next steps are to create some screens that display task history, from there we will see what we need to graph and can further investigate Google Charts. http://code.google.com/p/google-charts-on-rails/

3/21/10
Agenda

  • Nola got dailytasks.net domain!
  • move delete task button in index page to the detail view of a task (Rebecca)
  • talk about improving ui, who wants to do css? (Beverly / Nola)
  • talk about task report / graph (Rebecca, look at Gruff, CSS library, Googles Graph API, others?)
  • task validation with model tests (Beverly)
  • git branches demo
  • use codesmith.me coding standards? stole their standards, review

For Next week
Complete items with name, start the tasks on pivotal tracker

Branching
#List all branches in your git repo (local)
git branch
#Create a NEW branch and switch to it
git checkout -b mynewbranch
#Switch branches
git checkout mynewbranch
git checkout master
#Merge mynewbranch to master
git checkout master
git merge mynewbranch

3/14/10

Nola

  • attach users to task

Rebeca

  • work on show, edit, update actions

Beverly

  • what do you want to work on next?

This week we got some more knowledge of git and how committing and pushing worked. We saw how to look at the history of the github project and see who comited what and when. There was some misunderstanding of actions for the controller and we got those sorted out. Everybody seems ready to go on the project!

2/28/10

Action items for this week

Nola

Nola & Beverly

  • get github working for Beverly
  • work on user accounts together

Rebecca

  • work on task CRUD

Together we came up with a task list and some future ideas:

User Accounts

  • create a user table that consists of just user id and user name
  • when a user goes to: host/[name] will assign the user variable in session to [name]

Basic Task CRUD

  • create form to add task (new action)
  • create form to edit task (edit action)
  • display task list (index action)
  • display task details (show action)
  • task should have (task id, task name, description, owner_id/user_id, is_deleted)

Task Checkoff

  • add checkboxes to the task
  • save task_id with current date
  • task history (task_id, task_history_id, completion_date)

Task Report

  • Display how many tasks were completed today
  • For a week display how many tasks were completed on each day
  • Display a graph

Task Deletion

  • set flag “is_deleted” to true if deleted
  • change task list to only show tasks that are not deleted,(need to still show deleted tasks in the count)

Future

  • add authentication
  • add user profiles
  • users can add friends
  • create a facebook/twitter post feature where you can announce your total for the day, or announce a specific task completed.
  • add “hard delete” when you really want to delete a task, never to be seen or counted again
  • add recurring by weekday, by date, and/or by category (“happens on Tuesday”)
  • add mass adding of tasks, either with ajax adding new task form or with a big text edit box where each line get created as a task
  • group tasks, could be something to better the world or help people. You can choose to see a list of group tasks, do it and it shows on your profile .. like helping the elderly… recycling..

2/21/10

  • Decided to use github for source code control. We all got setup with git.

Download git and install locally, the steps we used

  • Create a github account http://github.com
  • Using this repository to test our git setup : http://github.com/rubygeek/learning-git
  • This is the command to clone the repo: git clone git@github.com:rubygeek/learning-git.git
  • If you get an error about public key, you need to add an ssh key to your github account. See help pages on github for your OS.
  • If you get permission denied but your ssh key is setup, you may need to ask Nola to add you to the project.
  • We discussed using git add -p, see this post for more: http://www.rubygeek.com/2010/02/17/gitting-better-with-git/

We decided to use Pivotal Tracker to track stories and tasks. For now we are creating a rough draft of stories on the wiki and we will enter them after we’ve had a chance to discuss Stories

This week we will independently:

  • Work through any issues with our git setup
  • Those brand new to ruby/rails checking out this tutorial: http://guides.rubyonrails.org/getting_started.html

Other resources:
*Nola’s shared repository : http://github.com/rubygeek/rubygeek
*http://www.buildingwebapps.com/podcasts