[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[technology-pmc] Re: [ptp-dev] Eclipse Technology projects website standards
|
Ward,
While I don't have any objection to conforming to required standards,
such as reporting project status, I find it a bit annoying when you
send out an email like this one that implies that we have been
negligent in some activity and now must be punished, when instead
this is the first I've heard of such a requirement or indeed that
there was a deadline for meeting it.
I read with interest your PMC minutes:
"The fourth item was the Technology sub-projects (lack of)
conformance to the adopted Eclipse website standards. We decided that
the reasons were two-fold: one is a lack of motivation (no
consequence for not doing so), the other is a lack of understanding
what to do (in spite of the detailed instructions)."
Unfortunately you completely miss the third alternative: "failure of
the PMC to communicate project requirements to the community". It's
great to have detailed instructions on what your requirements are,
but I don't know how you expect us to know what your expectations are
or when new requirements are introduced. Is there some web page that
we should be regularly scanning, or an email list we should be
subscribed to? Rather than "friendly nagging", you might find it more
productive to regularly email out a description of your requirements,
highlighting any new additions or changes.
We are and have been totally committed to meeting your project
requirements, but would prefer to work with you in a spirit of
collaboration and cooperation, rather than coercion. I would be happy
to discuss further how this can be achieved.
Regards,
Greg
On Nov 21, 2006, at 7:21 AM, Anne Jacko wrote:
Dear Technology Project Committers:
Please read this email carefully because it includes instructions
for something that you must do. Your project website does not
properly report project status. As a consequence your project must
attend "website school" wherein you and committers from other
technology projects will work together to rectify this condition.
1. You must enroll at least one committer from your project in one
of the two school sessions to be conducted by conference call.
Choose one of yourselves that understands how your website is
organized and can edit the text files associated with the project-
status infrastructure. If you are not sure who this is, or how they
are to be chosen, discuss this on your dev list now. Attendance is
mandatory and attendance will be taken. The session choices are:
Monday, November 27, 1pm Eastern, 10am Pacific (1 hour)
Thursday, December 7, 4pm Eastern, 1pm Pacific (1 hour)
866-362-7064 or 613-287-8000 particpant passcode 874551#
Enroll this week by sending one email per project to
emo@xxxxxxxxxxx listing attendee(s), contact information, and
selected session. Enroll early as sessions may fill.
2. You, as a website school attendee, must cooperatively read,
understand, and follow the published instructions for project
status reporting. You will be excused from class once all attendees
have successfully tested their work. You may expedite this work by
reading or even completing the instructions before class, but your
attendance is still required to help others. The instructions
appear here:
http://www.eclipse.org/projects/dev_process/project-status-
infrastructure.php
That's it. Two steps. But, remember, even though only one person
from your project must attend the class, you are all responsible
for that person's attendance and success.
Website school has been invented by the Technology PMC as a form of
"friendly nagging" for projects that haven't yet found the time to
conform to Eclipse website standards. Please take this seriously as
it is the kindest reminder we could concoct before commencing
unfriendly nagging. PMC meeting minutes appear here:
http://www.eclipse.org/technology/pmc-minutes.php?key=2006.11.13
I thank you for your attention.
Best regards,
Ward Cunningham
ward.cunningham@xxxxxxxxxxx
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
