Just so you know, there is a JIRA component for documentation too. We could
probably use that to list things which are bad. Again, if things can be
fixed, no need to file a JIRA, otherwise, it might not be a bad idea to use
it for our website fixes. What do you think?
Here is the link to our Documentation component in JIRA
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+OPENEJB+AND+resolution+%3D+Unresolved+AND+component+%3D+documentation+ORDER+BY+priority+DESC&mode=hide

On Tue, May 24, 2011 at 7:09 PM, David Blevins <[email protected]>wrote:

>
> On May 24, 2011, at 3:48 PM, Karan Malhi wrote:
>
> > Hi ,
> >
> > Would like to clean up our website a bit and identify links/pages with
> > stale/incorrect content. If you have ideas for content which would make
> our
> > site more useful, please do come forward and share them on this thread.
> Not
> > sure how we should approach this collaboratively, but the easiest is that
> if
> > you find something which is wrong, stale or poorly organised, either fix
> it,
> > or simply identify it and share it on this thread if you do not have time
> to
> > fix it. Somebody can probably pick it up and fix it.
> >
> > You could share the page in the following format:
> > [url] :- Issue
> >
> > For example,
> > [https://cwiki.apache.org/confluence/display/OPENEJB/News ] :- News is
> > stale, I am not sure how to update it, can somebody look into it
> >
> > Looking forward to some interesting ideas :)
>
> Such an excellent initiative.
>
> Don't have time to list all the example pages individually, but they need
> some love.  They took a hit when I was feverishly updating all our examples
> to show the most current APIs right before speaking at JAX London -- like
> literally the night before speaking.. was up till like 3am.
>
> All the snippet links are bad.  Updating them raises a question....
>
>
>    Do we need an OPENEJBx4 documentation base?
>
>
> The short answer is likely "yes and it will be a pain in the butt" :)
>
>
> -David
>
>


-- 
Karan Singh Malhi

Reply via email to