You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.
Some of the issues we've raised would be better addressed in a non-normative Guidelines document than in the Process Document or the Standing Rules.
We already have a Spec Lead Guide. We should have equivalent documents targeted at EC members, EG members, and just-plain JCP members.
Rather than creating monolithic documents it might be better to think of these as an FAQ_ or _Knowledge Base where the individual entries might be tagged as most of interest to one or more of those groups.
The simplest way to start this might be to create a mailing-list to which people can mail questions and post answers, and a Wiki to display the results once they have been formalized into "answers" or "topics."
This is not strictly a JSR 348 matter, but I'm logging it here for now so we don't forget it.
The text was updated successfully, but these errors were encountered:
Jira issue originally created by user pcurran:
Some of the issues we've raised would be better addressed in a non-normative Guidelines document than in the Process Document or the Standing Rules.
We already have a Spec Lead Guide. We should have equivalent documents targeted at EC members, EG members, and just-plain JCP members.
Rather than creating monolithic documents it might be better to think of these as an FAQ_ or _Knowledge Base where the individual entries might be tagged as most of interest to one or more of those groups.
The simplest way to start this might be to create a mailing-list to which people can mail questions and post answers, and a Wiki to display the results once they have been formalized into "answers" or "topics."
This is not strictly a JSR 348 matter, but I'm logging it here for now so we don't forget it.
The text was updated successfully, but these errors were encountered: