groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jochen Theodorou <blackd...@gmx.org>
Subject Re: Capturing GEPs better
Date Thu, 11 Oct 2018 16:56:35 GMT
+1 or the idea and +1 for groovy.apache.org

On 11.10.2018 16:56, Cédric Champeau wrote:
> This is typically what should live at groovy.apache.org 
> <http://groovy.apache.org> :)
> 
> Le jeu. 11 oct. 2018 à 16:54, Guillaume Laforge <glaforge@gmail.com 
> <mailto:glaforge@gmail.com>> a écrit :
> 
>     +1
>     I like the idea of having GEPs on the wiki side of the site.
> 
>     Le jeu. 11 oct. 2018 à 15:35, Paul King <paulk@asert.com.au
>     <mailto:paulk@asert.com.au>> a écrit :
> 
>         This is an example of what I had in mind:
>         http://groovy-lang.org/wiki/GEP-1.html
> 
>         On Thu, Oct 11, 2018 at 6:21 PM Paul King <paulk@asert.com.au
>         <mailto:paulk@asert.com.au>> wrote:
> 
>             One of the things which I don't believe we ever brought
>             across from the codehaus move was the GEP part of the
>             codehaus wiki:
> 
>             https://web.archive.org/web/20150504145954/http://docs.codehaus.org/display/GroovyJSR/Groovy+Enhancement+Proposal
> 
>             We certainly have merged the outcomes from the GEPs into the
>             language as needed and parts of the doco and some tests
>             capture bits of the GEP design and outcomes as does some of
>             the issues in Jira but not the original GEPs.
> 
>             I was going to try to bring those across and convert to
>             asciidoc on the way - for historical purposes but also to be
>             in a better position to cater for new ones. We have made do
>             with using Jira but I'm not sure that is the best way to
>             capture this kind of information.
> 
>             I was thinking under groovy-website rather than the core
>             repo. Thoughts?
> 
>             Cheers, Paul.
> 


Mime
View raw message