[JSR348-122] JSR-348 changes from individual perspective Created: 21/Sep/11  Updated: 21/Sep/11  Resolved: 21/Sep/11

Status: Closed
Project: jsr348
Component/s: General, Process Doc, Standing Rules
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: sean_sheedy Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File jsr-348-comments.txt    

 Description   

In the September EC meeting (and prior to close of the Public Review) I expressed reservation about this JSR ultimately coming from a mindset other than that of a community which was, as I expressed it, "collaborating freely on a free platform, finding value not in the platform itself but in what can be created from it". Participating EG members should understand that I know a lot of work has gone into this, and the push for transparency is apparent. However, I kept finding instances where loopholes existed that could be exploited by someone less interested in collaborating and more interested in competing. That there remains an interest in monetization and control through licensing makes these loopholes difficult if not impossible to fill. Long story short, I was encouraged by other EG members to file my comments rather than abstain and let the JSR conclude without my input.

These comments are provided from the perspective of someone who believes that the Java platform should be an open platform as described to us developers so many times over the years in so many venues.

Had this JSR been limited to election reform and not touched license related issues, it would have met the original criteria of not being "controversial" (we had decided early this year to limit this JSR to low hanging fruit we could all agree on, and save the difficult revisions for the post-348 JSR.)

Comments to the Process and Standing Rules docs are attached.



 Comments   
Comment by pcurran [ 21/Sep/11 ]

This is not one issue, it's at least 10 and maybe 20. Since we are now only one week away from Final Draft it's likely that many of these will need to be deferred.

As a courtesy, and to help you to triage your issues and to group them where appropriate, I will comment on the points raised in your text document by means of an email to the Observer's alias.

However, we won't be able to process these unless you file them separately.

Comment by pcurran [ 21/Sep/11 ]

I'm closing this "monster issue" on assumption that you will log/have logged separate issues for everything you care about.

Generated at Thu Mar 23 12:58:01 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.