Jesse, here's some more feedback on the docuware from Bjorn:
***
The "Scope" section is not a scope, it's a list of project
objectives. The
scope section should define the area of technical operation of the
project:
what's in, what's out. A better scope section would be:
The scope of the Jetty project is an extensible framework for, and
examplary
implementation of, an embeddable HTTP server and servlet container.
That's it. It's very clear what is in scope and what is out of
scope. The
rest of the current scope section can be turned into an "Objectives"
section.
***
Anne Jacko
emo@xxxxxxxxxxx
On Feb 26, 2009, at 11:17 AM, Jesse McConnell wrote:
no worries, was easy to update
cheers!
jesse
--
Jesse McConnell
jesse@xxxxxxxxxxx
On Thu, Feb 26, 2009 at 12:21 PM, Anne Jacko <emo@xxxxxxxxxxx> wrote:
Jess, you might want to wait to see if Bjorn has any suggestions.
I've asked
him to review your docuware and get back to me about it. Thanks.
Anne Jacko
emo@xxxxxxxxxxx
On Feb 26, 2009, at 10:20 AM, Jesse McConnell wrote:
ok sure thing, I'll see how to do that in google docs and get an
updated copy back to you, thanks so much for the help, very much
appreciated
jesse
--
Jesse McConnell
jesse@xxxxxxxxxxx
On Thu, Feb 26, 2009 at 12:13 PM, Anne Jacko <emo@xxxxxxxxxxx> wrote:
Hi Jesse,
Thanks for the update. It's definitely getting closer. I'll get
Bjorn's
feedback on it and then get back to you.
There are three minor things still to be done:
1. page numbers
2. the Communication Channel needs to be listed
3. the planned review date needs to be listed
Anne Jacko
emo@xxxxxxxxxxx
On Feb 25, 2009, at 9:11 AM, Jesse McConnell wrote:
Anne,
How is this shaping up? I am hoping the formatting is shaping up ok
and content wise I think it is closer to the mark now.
cheers,
Jesse
--
Jesse McConnell
jesse@xxxxxxxxxxx
On Tue, Feb 24, 2009 at 5:25 PM, Anne Jacko <emo@xxxxxxxxxxx> wrote:
Hi Jesse,
Thanks for sending you draft docuware. It's OK to base your review
docuware
on your proposal, but we need the docuware in a different format --
html
or
pdf is fine, but not php. Also, a key element is the committer bios.
The
docuware serves as a "mass election" for the committers, and the
community
needs to know why these people have the honor of being committers on
the
project. The bios don't have to be long, but they should contain
specific
information about each committer. The examples I sent you might help
with
this.
Here's an example of a project that used an edited version of their
proposal
for the review docuware:
http://www.eclipse.org/proposals/fproj/fprof_Creation_Review.html
Anne Jacko
emo@xxxxxxxxxxx
On Feb 24, 2009, at 2:37 PM, Jesse McConnell wrote:
I am hoping to get this into the March 11th project creation review,
please let me know what I need to adjust for this!
It is similar to the proposal document, primary changes are additions
of the Code Contribution, sections and the addition of our second
mentor Bjorn.
cheers!
jesse
--
Jesse McConnell
jesse@xxxxxxxxxxx
<creation-review-v1.zip>
<Eclipse_Creation_Review.pdf>
<Eclipse_Creation_Review.pdf>
