>
Hi Sam,
Just one minor clarification. Any issues for an apache project need to go through the apache representative for the TCK in question not through the licensees main contact.
Regards, Lance
There is a mismatch between the Sun/JCP/TCK model and Apache here that we simply will have to work through over time.
Sun's model is to assign a single representative per company. This generally makes sense, as this person can get to know the unique issues with respect to WebSphere, JRun, etc. that may cut accross JSR boundaries.
Open source flips that model. There is one code base shared by multiple companies. For the overwhelming majority of issues, it does not make sense to treat the issue as Macromedia or IBM specific, so for these issues, it makes sense to go through the Apache representative. However there always is the possibility that there will be some Macromedia or IBM specific issues to be dealt with. These clearly will have to go through the licensee main contact.
In some cases, the differences may simply be over priority. If there is an issue that is if critical importance to Macromedia then they understandably may want to pursue the issue through their main contact.
Overall, I don't expect that this will cause major problems. As I said, I expect the overwhelming majority of issues to be common. As for the rest, the way to effectively deal with it is to have effective cross channel communications. IBM, Macromedia, and Apache already have high bandwidth channels set up; if the Sun contacts for these companies talk amoungst themselves regularly, then I doubt there will be any problem.
- Sam Ruby
