I'm fine with explaining that it's there for voiced opinions, but tell me again, is this something that will be resolved and synced to a mailing list once we get all of that sorted out?

What is the expectation we'd like to set?

The public forums serve two purposes:

1. To allow the public to notify us of a deficiency in the spec, or submit a feature request
2. To allow community members to discuss amongst themselves

A few thoughts:

#1 - I'm not sure. Should we just point them to the issue tracker? That would streamline the process, however limiting public visibility to the initial discussion, and I like discussion.

#2 - Sure.

Any others?

---
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"

On Tue, 2009-12-15 at 22:27 -0500, Dan Allen wrote:

Lincoln (and other editors of .org),

We we come to a consensus, we should probably explain the role of the jsr-314-public forum on www.javaserverfaces.org (just so people understand why it is there and set some expectations).

-Dan

On Tue, Dec 15, 2009 at 10:25 PM, Dan Allen <dan.j.allen@gmail.com> wrote:

We have our first post on jsr-314-public by a community member (okay, so he is an EG member on JSR-299, but it still counts).

http://wiki.jcp.org/boards/index.php?t=3049

Not to give you guys more work, but occasionally we need to monitor this forum and decide if we want to "pick up" and issue and bring it into design. Here's how I think the process will go:

1. Get clarification from community about the issue (if necessary).
2. Post that we have taken this up as an issue for design in the EG (they can follow as an observer, unless of course they have post access)

Naturally with two places to discuss, there is the risk of creating parallel threads. Just remember that the public forums are there for two reasons:

1. To allow the public to notify us of a deficiency in the spec or a feature request
2. To allow community members to discuss amongst themselves

It's a public forum. So they should do most of the talking and we do most of the listening ;)

If you have other ideas about how it should go, please share it. I'm just laying out my perspective here.

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen