Difference between revisions of "SE2006:group bar:minutes"
Jump to navigation
Jump to search
| Line 51: | Line 51: | ||
| − | == | + | ==Mar 1== |
* We worked on breaking this project into smaller pieces. | * We worked on breaking this project into smaller pieces. | ||
* For database we are going to use SQL and for the rest of the project, we will probably use Java. | * For database we are going to use SQL and for the rest of the project, we will probably use Java. | ||
| + | |||
| + | * We will use Javadoc for documentation of the API | ||
| + | |||
| + | * Next meeting we are going to talk about: | ||
| + | ** Time budgeting | ||
| + | ** Eclipse review | ||
| + | ** Java prep | ||
| + | ** Kevin will bug Skylar about getting Java API installed on Quark. | ||
| + | ** We have two solutions so far on the table | ||
| + | ** We will talk more about documentation | ||
Revision as of 22:46, 1 March 2006
Feb 15
Possible meeting time: Working M/W/F in the evening for 1 or 2 hours starting the 27th. Toby, Kevin, and I are going to be working this weekend on clustcomp projects and then going to a conference on Feb 22-26.
- Languages:
- php - most of us are familiar. big libraries. web stuff.
- java with tomcat - web stuff. good development environment.
- python - learn a new language.
- perl - most of us are familiar. less good, but good web stuff.
- ruby - learn a new language. there may be other reasons but we don't know what they are because we don't know ruby.
- Caching Location data:
- with memcache (http://www.danga.com/memcached/)
- postgres
- mysql
- Communication
- using a mailing list for now.
- developing new methods as they seem fit (wiki,cvs,bulletin board).
- Group name:
- kartgoolers.
- cartooglers.
- pwners
- colin's team.
- group-b
- group bar
- Assignment:
- send us your group name choice to list. we accept write ins. if anyone feels super strong about a name then tell us why.
- submit your leader (self?)nominations.
Feb 28
- We have decided on some of the roles:
- Aybars: Libarian
- Alex & ColinC: Developers
- Tobias: Leader
- Kevin: Architect
- We have roughly agreed on meeting Monday, Tuesday and Wednesdays.
- We have discussed which language to use, and decided that we'll decide on that later after we break the project up a little bit more (possibly tomorrow).
- Tomorrow we will discuss the documentation.
- We will look at the lab 2 solutions soon.
- Error checking?
Mar 1
- We worked on breaking this project into smaller pieces.
- For database we are going to use SQL and for the rest of the project, we will probably use Java.
- We will use Javadoc for documentation of the API
- Next meeting we are going to talk about:
- Time budgeting
- Eclipse review
- Java prep
- Kevin will bug Skylar about getting Java API installed on Quark.
- We have two solutions so far on the table
- We will talk more about documentation
