apastsya jsr358 issues - Githubissues

apastsya / jsr358

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

JSR358-100: The Process Document contains a reference to "one or both Executive Committees"

#71 apastsya opened 8 years ago
0
JSR358-99: Maintenance Lead to specify at Maintenance Release whether future changes are expected

#70 apastsya opened 8 years ago
0
JSR358-98: Require a renewal ballot when Dormant JSRs are revived?

#69 apastsya opened 8 years ago
0
JSR358-97: Further changes to the Maintenance Review process

#68 apastsya opened 8 years ago
0
JSR358-96: Create errata process, separate from the MR process

#67 apastsya opened 9 years ago
0
JSR358-95: Patrick: initiate Doodle polls on patent policy

#66 apastsya closed 7 years ago
2
JSR358-94: Patrick: Assign specific issues for review

#65 apastsya opened 9 years ago
0
JSR358-93: Create a standard Spec license

#64 apastsya opened 9 years ago
0
JSR358-92: Create a standard Community TCK License

#63 apastsya opened 9 years ago
0
JSR358-91: Remove from licenses any barriers to full compliance with JCP 2.8's transparency requirements

#62 apastsya opened 9 years ago
0
JSR358-90: Steve Wolfe: write up Flat-IP use-case re defensive termination

#61 apastsya closed 7 years ago
3
JSR358-89: Mike Milinkovich: review JSPA for language preventing release of interim implementations prior to Final Release

#60 apastsya opened 9 years ago
1
JSR358-88: Provide non-normative guidelines on RI license selection

#59 apastsya opened 9 years ago
2
JSR358-87: Define a standard list of open-source RI licenses

#58 apastsya opened 9 years ago
2
JSR358-85: IP should vest as soon as granted rather than when the JSR goes final

#57 apastsya opened 9 years ago
2
JSR358-84: Need a complete answer on the ASLv2 incompatibility issue

#56 apastsya opened 10 years ago
0
JSR358-82: Suggested language to help track changes in employment status

#55 apastsya opened 10 years ago
1
JSR358-80: Additional transarency requirements

#54 apastsya closed 7 years ago
3
JSR358-77: Update the EC Standing Rules

#53 apastsya closed 7 years ago
4
JSR358-75: Although there is no TCK for process-change JSRs we ought to "test" whether we successfully implement the changes we specify

#52 apastsya closed 7 years ago
3
JSR358-73: Clarify the meaning of the term "conditional yes vote" in the Process Document

#51 apastsya closed 7 years ago
3
JSR358-72: Clarify what is appropriate for a MR and what should go into a new JSR

#50 apastsya closed 7 years ago
3
JSR358-70: Require Spec/Maintenance Lead to make statement for Release Ballots on expectations for follow-on work

#49 apastsya closed 7 years ago
3
JSR358-68: Should the review period be extended when an Expert Group publishes an update to a milestone draft?

#48 apastsya closed 7 years ago
3
JSR358-66: Modify Process Document to simplify the transition of a JSR from one Spec Lead (or Maintenance Lead) to another

#47 apastsya opened 10 years ago
1
JSR358-65: Should we shorten the time-periods between JSR deadlines in the interests of more rapid posting of milestones?

#46 apastsya closed 7 years ago
3
JSR358-64: Mandate collaborative development process for RIs

#45 apastsya opened 10 years ago
0
JSR358-63: Add Incubator stage in Process Document.

#44 apastsya closed 7 years ago
3
JSR358-62: Add named anchors for all defined terms in the Process Document

#43 apastsya closed 7 years ago
4
JSR358-49: Ambiguity of Specification, Content and License causes Spec Leads to ignore it or use other licenses

#42 apastsya opened 11 years ago
4
JSR358-48: A goal of RI/TCK IP working group should be access to the RI/TCK by community

#41 apastsya opened 11 years ago
3
JSR358-47: Can/Should we strengthen reciprocity to apply across JSRs?

#40 apastsya opened 11 years ago
0
JSR358-45: Reciprocity should be mandated

#39 apastsya opened 11 years ago
0
JSR358-44: Ensure that implementers are granted the right to incorporate IP into future as well as current implementations of a JSR

#38 apastsya opened 11 years ago
0
JSR358-42: Language in the JSR 336 TCK license appears to prohibit implementations of the Spec

#37 apastsya opened 12 years ago
2
JSR358-41: Flatten the current "hub and spoke" IP model

#36 apastsya opened 12 years ago
0
JSR358-40: JSPA 5.F.IV, drop or modify scope of exemption for Oracle RI/TCK licensing

#35 apastsya opened 12 years ago
1
JSR358-39: Remove confidentiality language from the JSPA

#34 apastsya opened 12 years ago
2
JSR358-38: Define standard Terms of Use for participation in JSR collaboration projects

#33 apastsya opened 12 years ago
3
JSR358-37: Collaboration with other Standards-Setting Organizations

#32 apastsya opened 12 years ago
1
JSR358-36: Refactor the JSPA

#31 apastsya closed 7 years ago
3
JSR358-35: Escrow process

#30 apastsya opened 12 years ago
0
JSR358-34: End of Life for JSRs

#29 apastsya opened 12 years ago
2
JSR358-33: Withdrawal of IP grants

#28 apastsya opened 12 years ago
0
JSR358-32: Expert Group dissolution at Final Release

#27 apastsya opened 12 years ago
1
JSR358-31: Strengthen TCK quality requirements

#26 apastsya opened 12 years ago
3
JSR358-30: Create an Architecture Council?

#25 apastsya opened 12 years ago
2
JSR358-29: The role of the Reference Implementation

#24 apastsya opened 12 years ago
4
JSR358-28: Fee structure changes

#23 apastsya opened 12 years ago
2
JSR358-26: Keep or eliminate the obligation to license Essential Patents on FRAND terms for JSRs in which you do not participate

#22 apastsya opened 12 years ago
11