groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <brit...@apache.org>
Subject Re: Build/CI infrastructure etc
Date Fri, 27 Mar 2015 14:45:45 GMT
2015-03-27 15:24 GMT+01:00 Andrew Bayer <abayer@apache.org>:

> I'd say this is appropriate for dev@. Basically, private@ is only for
> matters that cannot be public - voting/proposing new committers or PMC
> members most notably, and dealing with issues that can't or shouldn't be
> discussed publicly. The default assumption should be for any discussion to
> happen on the public lists.
>

CVEs are an example of such issues that shouldn't be discussed publicly.

Benedikt


>
> A.
>
> On Friday, March 27, 2015, Cédric Champeau <cedric.champeau@gmail.com>
> wrote:
>
> > BTW technically speaking should this discussion be on dev@ or private@ ?
> >
> > My assumption was that dev@ was more for discussing technical issues
> with
> > Groovy itself; and private@ more for issues like this, but I may be
> wrong.
> >
> > 2015-03-27 14:56 GMT+01:00 Andrew Bayer <andrew.bayer@gmail.com
> > <javascript:;>>:
> >
> > > That'll definitely work for now - I'll start a separate thread on wiki
> > > options going forward.
> > >
> > > A.
> > >
> > > On Friday, March 27, 2015, Cédric Champeau <cedric.champeau@gmail.com
> > <javascript:;>>
> > > wrote:
> > >
> > > > Ok since I prefer Asciidoctor over Confluence and that the Apache
> Wiki
> > > > is... well; what is is, I implemented a simple wiki for Groovy [1].
> TBH
> > > > this is by far my favorite option, because you can use Asciidoctor
> > > locally
> > > > to render, and it will integrate well with the website design.
> > > >
> > > > So the document about the release process is now rendered directly on
> > the
> > > > website [2]. If you want to update it, all you have to do is to edit
> > the
> > > > source [3] and submit a pull request. Once a PR is merged, it will
> take
> > > > around 5 minutes for the site to be updated. Each "adoc" file in the
> > > "wiki"
> > > > directory will automatically create a new file.
> > > >
> > > > Questions about the process welcome of course!
> > > >
> > > > NB: While nested directories in the wiki are supported, the rendered
> > page
> > > > have a problem with stylesheets, I will work later on this.
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://github.com/groovy/groovy-website/commit/f1678ab71734647b402c5374b5ae7ee051076bd1
> > > > [2] http://groovy-lang.org/wiki/groovy-release.html
> > > > [3]
> > > >
> > > >
> > >
> >
> https://github.com/groovy/groovy-website/blob/master/site/src/site/wiki/groovy-release.adoc
> > > >
> > > >
> > > > 2015-03-27 8:11 GMT+01:00 Guillaume Laforge <glaforge@gmail.com
> > <javascript:;>
> > > > <javascript:;>>:
> > > >
> > > > > Confluence preferred then
> > > > >
> > > > > 2015-03-27 2:51 GMT+01:00 Andrew Bayer <andrew.bayer@gmail.com
> > <javascript:;>
> > > > <javascript:;>>:
> > > > >
> > > > > > Not that I'm aware of...
> > > > > > On Mar 26, 2015 17:11, "Emmanuel Lécharny" <elecharny@gmail.com
> > <javascript:;>
> > > > <javascript:;>> wrote:
> > > > > >
> > > > > > > Le 26/03/15 21:20, Andrew Bayer a écrit :
> > > > > > > > Ok - would Confluence be ok with everyone? I detest
MoinMoin.
> > =)
> > > > > > >
> > > > > > > Yuk :/
> > > > > > >
> > > > > > > Any other option ?
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Guillaume Laforge
> > > > > Groovy Project Manager
> > > > >
> > > > > Blog: http://glaforge.appspot.com/
> > > > > Social: @glaforge <http://twitter.com/glaforge> / Google+
> > > > > <https://plus.google.com/u/0/114130972232398734985/posts>
> > > > >
> > > >
> > >
> >
>



-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message