3:34 a.m.
On 3 sept. 2011, at 11:17, Gunnar Morling wrote:
Emmanuel,
the general set-up of the infrastructure looks really great. In
particular a big +1 for making the website editable via GitHub.
For the time being, I'd find it great to have some more background on
the EG members, so that we all know with whom we're working (I've been
in touch with you and Gerhard, but not with Richard for instance, and
who is on board from Oracle's side?).
Yes that's a good idea. I'll start an email series on introduction. There are a
few members of Oracle to this expert group or this list.
Maybe everyone just shoots a short note to the list? Or perhaps an "EG
people" section on beanvalidation.org makes sense? If you all think
that's useful I could create such a section on the site.
We can. But I'm a bit reluctant to antagonize this list over the "raw"
expert group. I don't want to limit the work to EG members.
--Gunnar
2011/9/1 Emmanuel Bernard <emmanuel(a)hibernate.org>:
> Hello everyone,
> Welcome to this group and thanks for joining. I have been waiting for the
> summer vacations to end before soliciting you. But now is the time to start.
> I have been working mainly on the infrastructure of the specification with
> to goal to streamline our work as much as possible. The goal for this infra
> is to:
> - work the spec in the open
> - make contributions as easy as possible
> - have me do less work :)
> Infrastructure
> The spec has:
> - a website http://beanvalidation.org
> - source repositories https://github.com/beanvalidation (spec, API, TCK and
> the website itself)
> - a mailing list (this one)
> - a forum for more casual interactions (not sure it is useful)
> - a issue tracker http://beanvalidation.org/issues
> All publicly accessible.
> The portal for everything Bean Validation is
> http://beanvalidation.org. People can find the latest news as well as
> information on how to contribute.
> I encourage you to read the contribute section
> http://beanvalidation.org/contribute. This page (and associated pages)
> explains how to contribute to the specification document, the API, the TCK,
> the RI and even the beanvalidation.org website itself. Let me know if you
> think something needs to be refined and clarified.
> Process
> I have listed the main goals of this specification
> in http://beanvalidation.org/roadmap/ but the true source is the issue
> tracker http://beanvalidation.org/issues.
> Our first objective is going to make sure that what we want to do is in JIRA
> and sort the work in decreasing priority.
> Once this settled, I will call for one or two subjects at a given time on
> which we can brainstorm on this mailing list and or on the issue tracker
> before converging and writing a proposal (see
> http://beanvalidation.org/contribute/specification/). I don't have to be the
> one writing a proposal necessarily.
> All of this is a base proposal for our work, we can change it. So feel free
> to speak up and contribute.
> Let the fun start!
> Emmanuel Bernard
> JBoss by Red Hat
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
>
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev