Fall 2007

My milestone report is here. There wasn't a whole lot that happened, but I did implement a way to keep track of the number of times a user has viewed a piece of content.

What I had planned to do this week was work on the production servers, determine how they were holding up to the strain of beta testers, and look for anyplace that we might be able to streamline huge bottlenecks. I couldn't do any of that since we didn't have a beta test. Since others, like Brad, have mentioned what a big deal access control is, maybe you should have redirected your efforts towards that until the issues that you couldn't control were fixed?

As soon as possible we need to get the website public. We've been trying very hard to convince our customers to allow the production servers I set up to actually be used, since we can locally manage them and they're free for them until the end of the semester. I think that we're close to being allowed to run the beta, but it's really out of our hands.

The backend is nearing completion. We need to finish access control, but that's the last major feature. I can see the light at the end of the tunnel. Of course, now that we're almost done, the front end has a ton of stuff to implement, so soon I expect the teams to be shuffled. The relation and search teams are in similar places, I believe; Dave was assimilated into the front end today.

Everyone was busy this past week catching up on other classes. This had to happen eventually, so it's just as well it happened in a week when a lot of us were blocked.

How about the problem mentioned above? How might this week have been smoother with the same amount of work completed but better planning? --Chelsea

Luke and Bethany, we pushed hard and made the deadline. We really need you to come through with your side and unblock us by allowing the beta to go public.