2/27

Spending some time figuring out if the alert should be project specific and how much harder that would be.

At the moment it would seem that a map dataset would need to be kept somewhere. Where the projectNames would represent the keys, and the values would be represented by boolean enabled/disabled values. Not sure if they would want this functionality but we'll try implementing it before thursday.

Maybe getting somewhat off track here, should probably go back to trying to collect the daily project details tommorrow and figuring out why that's not working first before implementing any new functionality.

2/25

Currently working on completing 3 things before the next Referentia meeting this coming week.

1) Must retrieve the dailyProjectDetails data from the stdCmd alert class. Might not be able to use this method to retrieve the data.

2) Need to write the ProjectSelector class to select which project the data will represent.

3) Need to recreate the drop down list on the jsp page and populate it with projects.

2/23 Version 1.0 release class

Sitting in class right now.

Issues:
1) Annotate the hackyStat statistics screenshots.

2) Add screenshots to the guides and use cases.

Demo's went well, need to do 2 things for the next week. Populate the body of the emails with data from dailyProjectDetails, and implement a timeframe selector for the jsp page.

Larger goals for the next week include html generation of data via xslt scripts to populate the body of the emails.

2/22

Worked all night on overhauling the project from its old model to the newer integrated design which actually plugs into the hackystat system instead of standing on its own. Still stuck on the Apache bug documented on the news page however.

Be sure to ask Austen and Aaron about the concerns brought up at the CSDL meeting, as well as the idea that this email functionality already exists in another form within the hackyStat system.

Be sure to ask Phillip about the bug.

2/21

Some future things of note to ask during next Referentia meeting.

What are the goals they wish to achieve with the new email functionality? Will they want to extend the alert system to other aspects of either the developer process or events within the projects they are working on.

2/19-2/20

Make extensive revisions to the system, added a new package to the system which will house the Alert section of the program. Running into some workspace issues when trying to see data, or possibly some sensor issues when trying to send data, not sure which it is. Currently working on powerpoint presentation to give to CSDL tommorrow. Really not too sure what i'm going to say. I'll try reading Cedric's paper for some ideas.

2/15

Got my first sense of agile programming today. Had a meeting with the Referentia staff today at 12:30. Upon review of the previous requirements by Aaron, Ryan and Austen they decided to take the project in a different direction for the time being.

Instead they now want me to concentrate on developing a branch of the current application module which can autogenerate emails on a to-be-determined frequency. The content of the emails is an alteration of the DailyProjectDetails and the recipient of the email will be the developer to whom the data pertains.

Basically they want to be able to report back statistics to individual developers on all the normal data collected. This is combining statistics reporting with a reformatting of the DailyProjectDetails.

For the past week I had been working on the MVC design for the managment reporting but Aaron says to put a hold on that for the time being.

I told them that's fine and that i'll start working on this new aspect of the project instead.

2/10-2/13

For the past 4 days i've been working on updating the content of the google projects webpage so that it covers what i am doing as well as what i hope to accomplish extensively.

My primary goal at this point is to go back over the hackyStat documentation to gain further understanding of the hackystat system, and to find whether the implementations which i hope to incorporate into my application exist already. I'm just hoping at this point not to have to build the data collection and analysis portion extensively from scratch.

2/9

Entered in the first use case and the issues hoping to accomplish by the 1.0 release.

2/8

2/8 – Meeting with Referentia

Aaron wants reporting for: code issues, file metrics, coverage, commits.

Said to look at http://tsubaki/hackystat/controller?Key=S5ASQkXWuzPK&Page=analyses as a reference.

Create a confluence page.

Find a suitable App to model the ProjectStatus app after.

Ask Philip if I should be using telemetry for the trend lines or not.

First Post

HAH!!