Re: [Graph] the future of commons-graph and modularization

2017-07-07 Thread Bruno P. Kinoshita
Hi Oliver, >I know, I am very late to rejoin the party. :) Happy to see some activity on [graph] again. I used the snapshot in a project once, but after that only had to use libraries in Python and PHP, so never had time or the need to use the project again. >May I ask whether there is still s

Re: [daemon] @author tags

2017-07-07 Thread Bruno P. Kinoshita
No objections, +1, and thanks for taking care of that :) Bruno On Saturday, 8 July 2017, 2:43:24 PM NZST, Gary Gregory wrote: Hi All, I would like to remove @author tags from [daemon] per our guidelines. Any objections? Gary

[daemon] @author tags

2017-07-07 Thread Gary Gregory
Hi All, I would like to remove @author tags from [daemon] per our guidelines. Any objections? Gary

Re: [VOTE][LAZY] Move commons-collections to git.

2017-07-07 Thread Gary Gregory
+1 Gary On Jul 7, 2017 05:25, "Rob Tompkins" wrote: > Hello all, > > I would like to call a vote by lazy consensus for migrating the codebase > of Apache Commons Collections to git. > > This vote will be successful if nobody raises objections within the next > 72 hours, e.g. by July 10, 2017 13

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

2017-07-07 Thread rubin55
Github user rubin55 commented on the issue: https://github.com/apache/commons-cli/pull/15 Yes, I did see that PosixParser was also a part of the patch, but I thought not to touch it since it's marked as Deprecated (I would not expect changes to deprecated classes as a user at least).

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

2017-07-07 Thread rubin55
Github user rubin55 commented on the issue: https://github.com/apache/commons-cli/pull/15 Yes, I did see that PosixParser was also a part of the patch, but I thought not to touch it since it's marked as Deprecated (I would not expect changes to deprecated classes as a user at least).

[GitHub] commons-text issue #55: TEXT-97: RandomStringGenerator able to pass multiple...

2017-07-07 Thread ameyjadiye
Github user ameyjadiye commented on the issue: https://github.com/apache/commons-text/pull/55 Yeah, will see if we can simplify API in 2.x . I need opinion on the method I have given in this PR, According to me it's good addition to existing API but go through JIRA discussion once.

[GitHub] commons-text issue #55: TEXT-97: RandomStringGenerator able to pass multiple...

2017-07-07 Thread jbduncan
Github user jbduncan commented on the issue: https://github.com/apache/commons-text/pull/55 Revisiting this in 2.x sounds good to me! The only other thought I have is that I think this should go up as a new issue on Apache JIRA if it hasn't already. Other than that, e

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

2017-07-07 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-cli/pull/15 Looking at [CLI-217.patch](https://issues.apache.org/jira/secure/attachment/12568952/CLI-217.patch), I was wondering if we shouldn't also include changes to `PosixParser`? The changes would be

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

2017-07-07 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-cli/pull/15 Looking at [CLI-217.patch](https://issues.apache.org/jira/secure/attachment/12568952/CLI-217.patch), I was wondering if we shouldn't also include changes to `PosixParser`? The changes would be

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

2017-07-07 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-cli/pull/15 Yes aside from the `.gitignore` changes, this all looks quite reasonable. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

2017-07-07 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-cli/pull/15 Yes aside from the `.gitignore` changes, this all looks quite reasonable. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

Re: [VOTE][LAZY] Move commons-collections to git.

2017-07-07 Thread Mark Dacek
+1 On Jul 7, 2017 8:26 AM, "Rob Tompkins" wrote: > Hello all, > > I would like to call a vote by lazy consensus for migrating the codebase > of Apache Commons Collections to git. > > This vote will be successful if nobody raises objections within the next > 72 hours, e.g. by July 10, 2017 1300 (

[VOTE][LAZY] Move commons-collections to git.

2017-07-07 Thread Amey Jadiye
+1 On Jul 7, 2017 5:55 PM, "Rob Tompkins" wrote: > Hello all, > > I would like to call a vote by lazy consensus for migrating the codebase > of Apache Commons Collections to git. > > This vote will be successful if nobody raises objections within the next > 72 hours, e.g. by July 10, 2017 1300 (

[VOTE][LAZY] Move commons-collections to git.

2017-07-07 Thread Rob Tompkins
Hello all, I would like to call a vote by lazy consensus for migrating the codebase of Apache Commons Collections to git. This vote will be successful if nobody raises objections within the next 72 hours, e.g. by July 10, 2017 1300 (UTC). Cheers, -Rob --

[GitHub] commons-text issue #55: TEXT-97: RandomStringGenerator able to pass multiple...

2017-07-07 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-text/pull/55 @jbduncan has a point here, but the code here does conform to the style of the existing code. So, I'd lean more towards the changes @ameyjadiye is proposing mainly because to re-work the code i