Re: [Graph] the future of commons-graph and modularization
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 some activity on Apache Commons Graph? I have not seen any activity in a while (couple of years maybe?). >Is there a GitHub mirror of Sandbox as a whole or Graph? I don't think so. I think only proper components are currently mirror/hosted at GitHub. But I think it would make sense to check with infra if that's possible. Let's wait to see if someone will comment on this thread, if not we can start a new topic and ask this to others. >What would be the required steps to make an initial release of Apache >Commons Graph and how could I support these steps? I think creating a multi-module project is a good idea, with a simple API and implementations and algorithms. Then try to keep up with requests from users, bug fixes, and also work with other projects to see if there's any interest in using, and if there are any requirements coming from these projects. I commented on SANDBOX-458 with some examples of use cases of graphs in ASF projects. Might be easier to get a few ASF projects as users first. Cheers Bruno On Friday, 7 July 2017, 4:22:39 AM NZST, Oliver Kopp wrote: Hi, 2013-05-26 17:35 GMT+02:00 Simone Tripodi : > What I would like to propose to work _in a separated branch_, is > trying to split the big monolith in smaller modules and separate APIs > from related implementation as much as possible. I know, I am very late to rejoin the party. :) Here some pointers, I could reconstruct from the mails: - current code: http://svn.apache.org/viewvc/commons/sandbox/graph/trunk/src/main/java/ - the current modularization is going on at http://svn.apache.org/viewvc/commons/sandbox/graph/branches/modularization/ - overview on alternatives to Apache Commons Graph: https://issues.apache.org/jira/browse/SANDBOX-458 According to the homepage, there is no current release: https://commons.apache.org/sandbox/commons-graph/ May I ask whether there is still some activity on Apache Commons Graph? Is there a GitHub mirror of Sandbox as a whole or Graph? What would be the required steps to make an initial release of Apache Commons Graph and how could I support these steps? Cheers, Oliver -- https://github.com/koppor/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [daemon] @author tags
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
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.
+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 1300 (UTC). > > Cheers, > -Rob > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
[GitHub] commons-cli issue #15: CLI-217: Optional partial matching
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). --- 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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-cli issue #15: CLI-217: Optional partial matching
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). --- 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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-text issue #55: TEXT-97: RandomStringGenerator able to pass multiple...
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. --- 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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-text issue #55: TEXT-97: RandomStringGenerator able to pass multiple...
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, everything LGTM. --- 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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-cli issue #15: CLI-217: Optional partial matching
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 at https://github.com/apache/commons-cli/blob/master/src/main/java/org/apache/commons/cli/PosixParser.java#L127 and https://github.com/apache/commons-cli/blob/master/src/main/java/org/apache/commons/cli/PosixParser.java#L134 based on the bottom of that patch file. No worries if there is a distinct reason for not including those, just curious if you saw that in the patch. --- 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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-cli issue #15: CLI-217: Optional partial matching
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 at https://github.com/apache/commons-cli/blob/master/src/main/java/org/apache/commons/cli/PosixParser.java#L127 and https://github.com/apache/commons-cli/blob/master/src/main/java/org/apache/commons/cli/PosixParser.java#L134 based on the bottom of that patch file. No worries if there is a distinct reason for not including those, just curious if you saw that in the patch. --- 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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-cli issue #15: CLI-217: Optional partial matching
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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-cli issue #15: CLI-217: Optional partial matching
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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE][LAZY] Move commons-collections to git.
+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 (UTC). > > Cheers, > -Rob > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
[VOTE][LAZY] Move commons-collections to git.
+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 (UTC). > > Cheers, > -Rob > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
[VOTE][LAZY] Move commons-collections to git.
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 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-text issue #55: TEXT-97: RandomStringGenerator able to pass multiple...
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 into a static `builder()` method pattern would require changes that would necessitate a major version change. We could, though, revisit this in the 2.X version if you with @jbduncan. Thoughts? --- 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 project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
