groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pascal Schumacher <>
Subject Re: groovy.sql Documentation and the doco process
Date Mon, 06 Jul 2015 16:30:16 GMT
Hi Duncan,

Am 05.07.2015 um 23:52 schrieb Duncan Dickinson:
> I noticed that the "Working with a relational database" section of the 
> documentation is empty: 
> . 
> However there does appear to be doco in 

> - is this something just awaiting the next website refresh?
The groovy documentation is bound to the groovy version e.g.

There are just two shortcuts: 
(for the current version) and (for the next 
version/current master). You can that the sql-userguide will be included 
in the next release.
> I was thinking that I could add to the documentation so read up on 
> Peter L's how-to blog post. It all looks straight forward but I'm keen 
> not to start something that's already being worked on - hence this 
> email to check status.
> Lastly, there doesn't appear to be a process around co-ordinating 
> documentation aside from people tagging the document they're working 
> on. I was wondering if the Jira "Documentation" component* couldn't be 
> used to a greater extent. Essentially we'd likely have 2 types of 
> tickets - a bug for errors/typos/etc and a task for new/modifying 
> doco. Perhaps a Lead for the component may also be useful.
> This would mean that people could allocate themsleves a ticket and 
> keep it updated to let people know that it's actively being worked on.
Feel free to send a pull request tagging the section you want to work on 
and/or create a jira ticket.
> Lastly, I assume that the Apache 2 licence covers the documentation...
> * 
Yes the current version of the documentation is Apache 2 licensed (it 
was Creative Commons BY-SA 3.0 licensed before), see:


View raw message