Over the next week or two, I'm going to commit
some of the components for a baseline architecture
(a thin fiber that runs from an applicant's
request for a health inspection through to the
backend). Major development probably won't get
underway until (the holidays?) the beginning
of January.
In the meantime, I'm working on setting up a Wiki
for technical documentation for e-Sanitarian. A
high-level overview of it's architecture, use
cases, docs and such. I've seen Wiki used very
effectively for open source development in several
Apache projects, and have great confidence it'll
fit this project well. I'll post a follow-up
as soon as the URL of the Wiki becomes present-
able.
I'm also setting up a -dev mailing list through
SourceForge. The forums aren't as effective as an
archived mailing list for the types of discussions
I foresee us having, so I encourage all developers
to discuss the software design, implementation and
testing issues through the mailing list. A follow
up will ensue shortly when the mailing list is
ready for subscribers.
Since I'm situated in the northeast, I've been
in contact with the health departments in nearby
states and hope to meet with officials to gather
more detailed system requirements. Initially,
we plan to focus on becoming compliant with
food safety and sanitation regulations in the NE
for this reason in the first release.
As Project Manager I'll be heading up the require
ments gathering process. Most of the help I'll
campaign for from the community is for help in
developing and testing e-Sanitarian. However, if
you already have experience in the "business" as
a health or food safety inspector or working for
our target audience, we could also use your
domain-specific expertise.
That's the roadmap ... for the next month or so
anyway <g> ... and while the project gets going
I'd love to hear any feedback that you have out
there.
Thank you,
Derek Harmon,
e-Sanitarian
Project Manager
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The first step completed has been the establishment
of a pair of mailing lists:
e-sanitarian-users is a mailing list intended for
end user and administrator questions (how to use
the solution in the office). Initially, I expect
this list will be low usage since we're still
very early in the development process and don't
have a user base to speak of (yet).
e-sanitarian-developers is for technical develop-
ment discussions (use case analysis, class and
security design, coding patterns and practices,
and test planning/unit test development).
Just to differentiate the "Developers" forum
from the mailing list, I plan to post overarching
announcements in the forum that may be more general
interest. I expect the mailing list to be more
technical (i.e., don't discuss classes or specific
lines of code in the forum, choose the mailing
list intead).
More details on project preparations will be
forthcoming early next week. I hope everyone
has a good weekend.
Regards,
Derek Harmon,
e-Sanitarian
Project Manager
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi All,
Over the next week or two, I'm going to commit
some of the components for a baseline architecture
(a thin fiber that runs from an applicant's
request for a health inspection through to the
backend). Major development probably won't get
underway until (the holidays?) the beginning
of January.
In the meantime, I'm working on setting up a Wiki
for technical documentation for e-Sanitarian. A
high-level overview of it's architecture, use
cases, docs and such. I've seen Wiki used very
effectively for open source development in several
Apache projects, and have great confidence it'll
fit this project well. I'll post a follow-up
as soon as the URL of the Wiki becomes present-
able.
I'm also setting up a -dev mailing list through
SourceForge. The forums aren't as effective as an
archived mailing list for the types of discussions
I foresee us having, so I encourage all developers
to discuss the software design, implementation and
testing issues through the mailing list. A follow
up will ensue shortly when the mailing list is
ready for subscribers.
Since I'm situated in the northeast, I've been
in contact with the health departments in nearby
states and hope to meet with officials to gather
more detailed system requirements. Initially,
we plan to focus on becoming compliant with
food safety and sanitation regulations in the NE
for this reason in the first release.
As Project Manager I'll be heading up the require
ments gathering process. Most of the help I'll
campaign for from the community is for help in
developing and testing e-Sanitarian. However, if
you already have experience in the "business" as
a health or food safety inspector or working for
our target audience, we could also use your
domain-specific expertise.
That's the roadmap ... for the next month or so
anyway <g> ... and while the project gets going
I'd love to hear any feedback that you have out
there.
Thank you,
Derek Harmon,
e-Sanitarian
Project Manager
The first step completed has been the establishment
of a pair of mailing lists:
e-sanitarian-users is a mailing list intended for
end user and administrator questions (how to use
the solution in the office). Initially, I expect
this list will be low usage since we're still
very early in the development process and don't
have a user base to speak of (yet).
e-sanitarian-developers is for technical develop-
ment discussions (use case analysis, class and
security design, coding patterns and practices,
and test planning/unit test development).
Just to differentiate the "Developers" forum
from the mailing list, I plan to post overarching
announcements in the forum that may be more general
interest. I expect the mailing list to be more
technical (i.e., don't discuss classes or specific
lines of code in the forum, choose the mailing
list intead).
More details on project preparations will be
forthcoming early next week. I hope everyone
has a good weekend.
Regards,
Derek Harmon,
e-Sanitarian
Project Manager