apastsya jsr348 issues - Githubissues

apastsya / jsr348

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

JSR348-156: platform comaptibility requirements for new specs unclear

#138 apastsya opened 11 years ago
0
JSR348-153: Licensor Name Space is not formally defined

#137 apastsya closed 7 years ago
4
JSR348-152: Member should not be capitalized in the Standing Rules

#136 apastsya closed 7 years ago
2
JSR348-151: minor changes

#135 apastsya closed 7 years ago
3
JSR348-150: Seats unfilled in elections can remain unfilled for a year

#134 apastsya closed 7 years ago
2
JSR348-148: Elections: grandfather seat holder terms that began prior to EC merge

#133 apastsya closed 7 years ago
3
JSR348-147: Give PMO ability to investigate and act on voting fraud with certain conditions

#132 apastsya closed 7 years ago
8
JSR348-146: EC as level playing field

#131 apastsya closed 7 years ago
2
JSR348-145: RI/TCK licenses permitted that allow Ri/TCK to effectively be withdrawn by spec lead

#130 apastsya closed 7 years ago
3
JSR348-143: appeals process open ended; other sections need to provide appeals procedure for those areas

#129 apastsya closed 7 years ago
3
JSR348-142: Prospective EG members petitions for membership are public; appeal process for rejections

#128 apastsya closed 7 years ago
2
JSR348-141: Change "offered for the lifetime..." to "continuously available"

#127 apastsya closed 7 years ago
2
JSR348-140: License changes during MR require unanimous EG approval except for limited circumstances

#126 apastsya closed 7 years ago
2
JSR348-139: prices of licenses to be disclosed in the license terms

#125 apastsya closed 7 years ago
2
JSR348-136: spec lead chooses what counts as "administrative", can suppress info that should be public

#124 apastsya closed 7 years ago
2
JSR348-134: meta-issue: lack of enforcement creates loopholes, opportunities for misuse

#123 apastsya closed 7 years ago
2
JSR348-133: "Agent" designation unfairly discriminates against individual members already underrepresented

#122 apastsya closed 7 years ago
2
JSR348-132: elected members terms should be grandfathered

#121 apastsya closed 7 years ago
4
JSR348-131: rule that ballot topics must be discussed at EC meetings raises issues

#120 apastsya closed 7 years ago
4
JSR348-130: abstentions are embodiment of agreement to disagree

#119 apastsya closed 7 years ago
8
JSR348-129: EC votes are just advice? problem: advice can be ignored

#118 apastsya closed 7 years ago
3
JSR348-128: any member can call for a vote to clarify "agreement".

#117 apastsya closed 7 years ago
3
JSR348-127: ec must vote to cancel meetings once scheduled

#116 apastsya closed 7 years ago
2
JSR348-126: rules around missing F2F meetings

#115 apastsya closed 7 years ago
4
JSR348-125: need third party not tied up in discussions to take minutes

#114 apastsya closed 7 years ago
3
JSR348-124: private session should be agreed to by EC

#113 apastsya closed 7 years ago
2
JSR348-122: JSR-348 changes from individual perspective

#112 apastsya closed 7 years ago
4
JSR348-120: Should the JSR Review period always be four weeks, or 2-4 weeks at the option of the submitter?

#111 apastsya closed 7 years ago
8
JSR348-119: Should a transfer ballot include the terms on which the new owner of the JSR intends to license it?

#110 apastsya closed 7 years ago
6
JSR348-118: profiles can be based on latest or next platform version

#109 apastsya closed 7 years ago
6
JSR348-117: 1.2.3 vs. 1.2.4

#108 apastsya closed 7 years ago
2
JSR348-116: public access to non-written communication must not be required

#107 apastsya closed 7 years ago
2
JSR348-114: Maintenance Review definition should reference Maintenance Lead, not Spec Lead

#106 apastsya closed 7 years ago
2
JSR348-113: JSR Approval Ballot - definition could be clearer

#105 apastsya closed 7 years ago
4
JSR348-112: Clarification of obligation to offer TCK and RI licenses "for ever"

#104 apastsya closed 7 years ago
3
JSR348-111: Clarify that agenda items marked For Action cannot be modified during the meeting, and new For Action items cannot be added

#103 apastsya closed 7 years ago
3
JSR348-110: List the names of EG members and their organisation affiliation on the JSR page

#102 apastsya closed 7 years ago
3
JSR348-109: The current definition of consensus is too vague

#101 apastsya closed 7 years ago
3
JSR348-108: Harmonize language with RFC 2119

#100 apastsya closed 7 years ago
3
JSR348-107: It should be permissible to vote no in a Maintenance Review Ballot if an issue referenced in an earlier "conditional yes vote" has not been addressed

#99 apastsya closed 7 years ago
3
JSR348-106: The Maintenance Lead may submit a written statement for consideration during a Maintenance Renewal Ballot

#98 apastsya closed 7 years ago
3
JSR348-105: Clean up the Unresponsive Spec Lead section

#97 apastsya closed 7 years ago
5
JSR348-103: Remove the notes from the Standing Rules

#96 apastsya closed 7 years ago
2
JSR348-102: Harmonize Issue List and Issue list

#95 apastsya closed 7 years ago
3
JSR348-101: Bad formatting in section 6.3

#94 apastsya closed 7 years ago
2
JSR348-100: Spurious blank line in Process Document

#93 apastsya closed 7 years ago
2
JSR348-98: Ensure that Spec Lead has flexibility in logging and responding issues

#92 apastsya closed 7 years ago
5
JSR348-97: Minor changes in anticipation of merging the two ECs

#91 apastsya closed 7 years ago
9
JSR348-96: Specifications should be directly available as HTML on the web

#90 apastsya closed 7 years ago
2
JSR348-95: Section 1.1.2 needs a little rewording to alleviate ambiguities

#89 apastsya closed 7 years ago
3