On Wed, Mar 11, 2015 at 1:10 PM, Rich Bowen wrote:
> The paragraph that begins with "Despite all those advantages ..." doesn't
> seem to contribute anything to the proposal, and might benefit from either
> being cut, or by calling out an action - that is, does this mean that you
> expect to engage
On Wed, Mar 11, 2015 at 3:23 PM, Shane Curcuru wrote:
> On 3/11/15 4:20 PM, Martijn Dashorst wrote:
>> Great initiative!
>>
>> Just one question: I don't see anything related to the groovy name and
>> possible trademark in the proposal. Does Pivotal have any claims to
>> the name groovy, and if so
On Wed, Mar 11, 2015 at 12:18 PM, Stephen Connolly
wrote:
> If there have been over 200 contributors to the project, I would expect to
> see an effort to pull some of them in shortly after entering incubation...
> Assuming they can demonstrate merrit.
If anybody can share 'prior art' in this area
On 3/11/15 4:20 PM, Martijn Dashorst wrote:
> Great initiative!
>
> Just one question: I don't see anything related to the groovy name and
> possible trademark in the proposal. Does Pivotal have any claims to
> the name groovy, and if so are those claims transferred to the ASF?
Good point. Just
The github-asf integration is fairly smooth, if not as cool as the big
Merge button. For the requester there is no difference, only the Apache
committer have to do manual steps.
An example email, which we set up to go to dev@:
http://apache-taverna-dev.markmail.org/thread/gq62b33me5mjjkjw
If you
On Wednesday, March 11, 2015, Cédric Champeau
wrote:
> Don't worry your question is perfectly legitimate. I don't know if it's
> specific to Groovy, but we indeed have a lot of contributors, but not so
> many recurrent one that may become committers.
Thanks, please also be aware that a committe
Don't worry your question is perfectly legitimate. I don't know if it's
specific to Groovy, but we indeed have a lot of contributors, but not so
many recurrent one that may become committers.
2015-03-11 22:11 GMT+01:00 jan i :
> On Wednesday, March 11, 2015, Roman Shaposhnik
> wrote:
>
> > On We
On Wednesday, March 11, 2015, Roman Shaposhnik wrote:
> On Wed, Mar 11, 2015 at 12:08 PM, jan i >
> wrote:
> > Hi.
> >
> > Having just skimmed the proposal, that in general look good, one thing
> > caught my eye.
> >
> > The proposal talks several places about a vibrant community and the
> initia
2015-03-11 21:37 GMT+01:00 Pascal Schumacher :
> Am 11.03.2015 um 21:24 schrieb Benedikt Ritter:
>
> Is the groovy project aware that (to my knowledge) the coding has to
> happen on ASF infrastructure? You won't be able to use the github web UI
> for merging PRs for example, because currently the
Am 11.03.2015 20:08, schrieb jan i:
The proposal talks several places about a vibrant community and the
initial commiters are only 5.
I am not raising it as a problem, just would like a little explanation.
It is only 5 because we did work mostly with github pull requests. Many
people just spe
Hello,
This is a call for a vote for releasing Apache Slider 0.70.0-incubating.
This is a source+binary release with one .tar file (appdef_1.tar), which is a
text file used for -ve testing.
Summary of fixes: http://s.apache.org/AnM
Vote thread: http://s.apache.org/YQx
Results: http://s.apache.o
Am 11.03.2015 um 21:24 schrieb Benedikt Ritter:
Is the groovy project aware that (to my knowledge) the coding has to
happen on ASF infrastructure? You won't be able to use the github web
UI for merging PRs for example, because currently the ASF only mirrors
git repositories from git.apache.org
Yes Benedikt, we're aware of that.
It's actually been one of the (pain) points we raised when discussing with
our (then-soon-to-be) mentors and champion.
Working with the Github infrastructure was very smooth, very handy and
practical.
But we'll have to get used to this new approach!
Guillaume
On
2015-03-11 21:24 GMT+01:00 Benedikt Ritter :
> Is the groovy project aware that (to my knowledge) the coding has to happen
> on ASF infrastructure? You won't be able to use the github web UI for
> merging PRs for example, because currently the ASF only mirrors git
> repositories from git.apache.or
Is the groovy project aware that (to my knowledge) the coding has to happen
on ASF infrastructure? You won't be able to use the github web UI for
merging PRs for example, because currently the ASF only mirrors git
repositories from git.apache.org to github.
I'm very excited about this project, and
Great initiative!
Just one question: I don't see anything related to the groovy name and
possible trademark in the proposal. Does Pivotal have any claims to
the name groovy, and if so are those claims transferred to the ASF?
Martijn
---
A good answer to this is to take a look at who actually contributed for the
past 4 years:
https://github.com/groovy/groovy-core/graphs/contributors?from=2011-01-01&to=2015-03-11&type=c
and you will see that there are not so many regular contributors. GitHub
helped us a lot recently to have more con
The paragraph that begins with "Despite all those advantages ..."
doesn't seem to contribute anything to the proposal, and might benefit
from either being cut, or by calling out an action - that is, does this
mean that you expect to engage more closely with these projects to help
them do better
+1
Regards,
Alan
> On Mar 10, 2015, at 7:33 AM, Thejas Nair wrote:
>
> The Singa Incubator Proposal document has been updated based on
> feedback in the proposal thread.
>
> This vote is proposing the inclusion of Apache Singa as incubator project.
> The vote will run for at least 72 hours.
>
If there have been over 200 contributors to the project, I would expect to
see an effort to pull some of them in shortly after entering incubation...
Assuming they can demonstrate merrit.
An initial committer list of 5 for such a big project with a large and
diverse history of contributions would
Hi!
It is my pleasure and privilege to open up the following
proposal:
https://wiki.apache.org/incubator/GroovyProposal
for wide discussion before conducting and IPMC
vote on it. In order to engage as much potential stakeholders
as possible we will be soliciting input on {dev,users}@groovy.cod
Thanks for the input on the name. Naming is always tricky!
We can look into that as the project goes through incubation and
before it graduates.
Apache guideline on naming - http://www.apache.org/foundation/marks/naming.html
On Tue, Mar 10, 2015 at 3:52 PM, Olemis Lang wrote:
> On 3/10/15, Thejas
On Tue, Mar 10, 2015 at 11:52 PM, Olemis Lang wrote:
> ...I do not know if this matters at all but JFYI , <> is considered
> as an obscene word by native Spanish speakers in quite a few regions
It does matter in terms of "marketing" IMO.
Also, dunno if that's been discussed already and it's
23 matches
Mail list logo
