7:39 a.m.
Hi all
Please take a look at http://www.cdi-spec.org/ and give it a good review before we tweet
it etc. :-)
Pete
2:33 a.m.
Hi Pete,
Looks good so far.
There are a few typos/minor issues in the FAQ section. What's the best way
to report them?
Jens
Am 24.04.13 14:39 schrieb "Pete Muir" unter <pmuir(a)redhat.com>:
Hi all
Please take a look at http://www.cdi-spec.org/ and give it a good review
before we tweet it etc. :-)
Pete
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
2:48 a.m.
That would have been good info to include!
The sources for the site are in git - https://github.com/cdi-spec/cdi-spec.org. In
particular, FAQs are in https://github.com/cdi-spec/cdi-spec.org/tree/master/faq.
I guess we can use the github issue tracker for the site, unless anyone violently objects
:-)
Pete
On 25 Apr 2013, at 08:33, Jens Schumann <jens.schumann(a)openknowledge.de> wrote:
Hi Pete,
Looks good so far.
There are a few typos/minor issues in the FAQ section. What's the best way
to report them?
Jens
Am 24.04.13 14:39 schrieb "Pete Muir" unter <pmuir(a)redhat.com>:
> Hi all
>
> Please take a look at http://www.cdi-spec.org/ and give it a good review
> before we tweet it etc. :-)
>
> Pete
> _______________________________________________
> cdi-dev mailing list
> cdi-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
3:14 a.m.
Wow, this is *awesome*! By far the best site I've ever seen for a standard.
For a spec that hasn't had a physical web presence yet, this is one heck of
a way to come out. Putting this information out there and making it
approachable is going to send this spec soaring.
Great job.
On Thu, Apr 25, 2013 at 1:48 AM, Pete Muir <pmuir(a)redhat.com> wrote:
That would have been good info to include!
The sources for the site are in git -
https://github.com/cdi-spec/cdi-spec.org. In particular, FAQs are in
https://github.com/cdi-spec/cdi-spec.org/tree/master/faq.
I guess we can use the github issue tracker for the site, unless anyone
violently objects :-)
I've been using the issue tracker for several projects, including
Asciidoctor. My impression is that it works splendidly It puts the issues
right inline with the code, making them easy to find, easy to reference and
encourages people to fix them. What else can you ask for in an issue
tracker? (well, there's always room for improvement, but I can't complain).
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://google.com/profiles/dan.j.allen
http://mojavelinux.com
http://mojavelinux.com/seaminaction
3:55 a.m.
Looks ok, good start.
LieGrue,
strub
----- Original Message -----
From: Pete Muir <pmuir(a)redhat.com>
To: cdi-dev <cdi-dev(a)lists.jboss.org>
Cc:
Sent: Wednesday, 24 April 2013, 14:39
Subject: [cdi-dev] Preview of cdi-spec.org available
Hi all
Please take a look at http://www.cdi-spec.org/ and give it a good review before
we tweet it etc. :-)
Pete
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
4257
days inactive
4259
days old
4 comments
4 participants
participants (4)
-
Dan Allen -
Jens Schumann -
Mark Struberg -
Pete Muir