Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » General (non-technical) » Eclipse Foundation » [PROJECT] [BUGZILLA] - Critical Issues Need Independent Supervision
[PROJECT] [BUGZILLA] - Critical Issues Need Independent Supervision [message #9804] Sat, 08 January 2005 13:01
Eclipse UserFriend
Originally posted by:

[writing through htmp-nntp gateway, as i've no r/w-access to the nntp


You've maybe noticed the bugzilla-battle:

[GOVERNANCE] - Mr. Kent Johnson (IBM) Obfuscates Status and Relations of


What [beside J2SE 5.0 status] causes me to evaluate the "eclipse
foundations" in the bugzilla 'discipline' was this one:

compiler compiles import for non-existing interface

You have most possibly detected the same name: Mr. Kent Johnson.


This is not the way to process critical issues.

The issue was closed, although the user has taken all efforts to proove
the problem.

Mr. Kent Johnson, the critical IBM team (JDT.Core) and every other team
should be supervised, thus they cannot close issues like they want.

Independent, Ruled Based, Clear and Transparent.


The Issue-Tracking-System is the medium which ensures that the status of
a code-base is made transparently visible, without exclusive control of
the teams.

It should reflect reality.


The user base needs a clear picture of the codebase they rely on.

Ignoring this is rude, arrogant and inefficient.

Ignoring this has nothing to do with an open-source project.

Possibly with an IBM & Co [members(silent acceptors)] project.


Previous Topic:[GOVERNANCE] - Mr. Kent Johnson (IBM) Obfuscates Status and Relations of Issues
Next Topic:Eclipse-oriented competition, CUSEC 2005, Ottawa
Goto Forum:

Current Time: Wed May 23 04:53:09 GMT 2018

Powered by FUDForum. Page generated in 0.01990 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top