Please be aware that making the jsr-314-observers board visible to the public
is a customization of the code that needs to be implemented.
It would help us if we understood why it is necessary to customize the off-the-shelf software to make the observers boards public. I'm not questioning the need, but rather trying to understand why the observers boards are different than the public boards, which are public facing already. If we understood better what the problem is, I think we would have an easier time remaining patient.
Also, as discussed with Roger, we are waiting on a couple of really critical
fixes to the code that we are using for the boards that prevent us to release the
features you are looking forward to.
Such fixes are being implemented outside Sun, and, as much as we would like
to have them now, they are going to take some time to be developed,
tested and implemented.
Understood.
So, here is a summary of what we will do:
We will import the current subscribers from jsr-314-open into
jsr-314-observers.
Great!
The mailing list jsr-314-open will go away.
Subscribers to jsr-314-observers will be able to both read and write
to the board/alias.
This doesn't add any restrictions to what we currently have with jsr-314-open, so we are willing to migrate immediately based on the information you have provided. (Note that we are still seeking public read access, but that was never possible with jsr-314-open, so by migrating we can pursue this need)
Other users who are NOT subscribed will be able to read the
jsr-314-observers archives in the discussion board
I'm assuming you mean "not subscribed, but signed in
jcp.org members". I just want to clarify the current state.
Users may request to become subscribers by filling out the existing
form to join the jsr-314-observers board; Ed and/or Roger would then be
able to review the nomination and approve/decline the request using the
existing form.
That's fine in the short term. In the long run, I don't see why we need a human task in the subscription process. That will burden Ed and Roger and slow down the subscription. I'd like to request that the process be completely automated.
Note: the list of boards on
jcp.org is browsable by logged-in users, but
there are publicly-readable boards that anyone can read, though they
can't see the navigation if they don't log in. So, a question about read
permissions: do you want the list readable by registered users of
jcp.org, who will have handy navigation to find the jsr-314-observers
board, or do you want anyone with an internet connection to be able to
read it, with the idea that you would send out a direct link to the world?
First of all, one of my major complaints with
jcp.org right now is that the list of boards is not visible at first view. I don't understand why the complete list can't be displayed (obviously, the jsr-xxx-eg boards can be hidden). When I first arrived at the boards page, I thought that there were only a handful of boards. Later I realized there are a lot more, just hidden.
So yes, we want the complete board list to be visible. There is no reason to hide the names of any of the boards (with the exception of the jsr-xxx-eg boards).
We also want a search engine, such as Google, to be able to navigate to the threads in the jsr-314-observers forum so that they can be indexed. That means they should be visible by an anonymous visitor.
Once again, just so that there will be no misunderstanding, I am restating
the current status next to each of your requests marking it with ****:
1) Make jsr-xxx-observers readable by the world and writable by anyone
w/ post access to jsr-314-open
****Waiting of third party developers****
Your saying we can't even migrate without critical fixes? We really want to migrate as soon as possible, so anything that can be done to speed this up would be great.
2) Import the archives of jsr-314-open into jsr-314-observers
****Waiting on third party developers****
Again, I'm wondering which fixes we need to at least do the migration.