Regarding your
suggestions to move forward, why is it not good enough to have the discussion
on a public mailing list?
I'm confused - isn't this (phoenix-dev) a public
mailing list?
>> Yes it is
public and that is the point I was trying to make. In your
original criteria to remove your veto, you required everything to be done
through bugzilla. My point is that we should also be able to use
the mailing list, since it is public.
Regardless, here is
what I believe Nathan has done and I believe it is available for all to
review.
2. Denis is out of
the office but he did check-in the code for the updates Nathan did to these
pages: http://www.eclipse.org/community/rcp.php,
http://www.eclipse.org/community/rcpos.php,
http://www.eclipse.org/community/rcpcp.php.
I also reviewed these pages before they were checked
in.
But until you said this on this list, nobody except
you and Denis knew this, right? So it wasn't done in
public.
>>>> Ok,
but now that I have said it, does that count as being public and for your
criteria?
3.
Nathan has been working with Susan on the RSS feeds and a community
bulletin. One example is http://www.eclipse.org/org/press-release/20060309cb_elections.php.
But again, the work wasn't done in
public.
>>> But now it is, via this mailing
list, so does that count?
4. Nathan will be
doing a number of pages for the Eclipse Awards. I will review them and
commit them next week. Unfortunately they can not go public until March
21, for obvious reasons.
P.S. You
realize that if you commit them next week they become public, right? Because
the CVS is publically readable.
>>>> Yes
and probably another reason why we are not going to use bugzilla.
I
understand that you are frustrated. The bar is being raised (back to where it
once was) for all the projects.
>>> You are
correct I am frustrated. I agree with raising the bar but this just
sounds like bad process that is adding no
value.
