1.0 Milestone

0 views
Skip to first unread message

brendanlevy

unread,
Oct 29, 2009, 1:15:38 AM10/29/09
to Sappira
From the conversations I have had with you individually over the past
week I am glad to hear we are all essentially agreed about the general
structure. Most future overall design conversations I hope we will
have largely on the code site so that everyone can follow the thought
process collectively. Thank you for the excellent edits, comments, and
code commits that have already been added.

The next step is that everyone reads the requirements and begins to
deconstruct our vision into various issues. I have already begun to do
that and to discuss the rest with those of you who have expertise in
specific areas, but now I would like everyone who is willing to claim
an area of work, from describing the action of a specific form, to
implementing a button, to streamlining the CSS architecture to create
an issue. While I don't want any work wasted I believe there exists
enough clarity and foundation to design the basic functionality and as
ambiguity or potential branch points occur we can discuss them.

To guide this work here is a schedule of the next most relevant dates
in the timeline, most notably that we plan to consider the overall
structure of models and modules locked by the end of next week.

* Requirements Meeting Group Chat
Saturday October 31st at 12:00 American CST
If you are able to be online during this time I would like to have as
many of us meet as possible to see if there are any areas of confusion
and if there are any teams that we could logically form.

* Database Models Locked
Friday November 6th
By this date all models will be considered final for 1.0 release, with
the exception of fields necessary to add audit functionality so that
views can be coded without further changes.

* Planned 1.0 Alpha
Wednesday January 13th
By this date we plan to have an essentially feature complete
application.

Thanks for your time!

Yours,
Brendan

Issues I will be working on this week (to be kept track of in the
issue tracker from this point forward):
* Ensuring there are no problems with using the issue tracker
* Planning to be online frequently to be available to chat
* Will ensure that our demo server is kept up to date daily with the
SVN
* Beginning to recruit a user testing group
* Fixing a few single button forms (e.g. Admit and Discharge)
Reply all
Reply to author
Forward
0 new messages