dbrosIus wrote:
> >>> +1 and git please
> >>>
> >>> Original message
> >>> From: Phil Steitz
> >>> Date: 10/25/2015 3:15 PM (GMT-05:00)
> >>> To: Commons Developers List
> >>> Subject: Re: Propo
an use to identify the code
>> that we will be accepting, should the VOTE pass?
>>
>> Thanks!
>>
>> Phil
>>
>>> On 10/25/15 12:25 PM, dbrosIus wrote:
>>> +1 and git please
>>>
>>> ---- Original message ----
>&
: Proposed Contribution to Apache Commons,
On 10/2/15 12:08 PM, Gary Gregory wrote:
Well, a champion can volunteer to shepherd this through our incubator I
suppose,
OK, I will volunteer to do this. I propose that we start this as a
Commons Sandbox project. To do that, we need a VOTE to accept
ns Developers List
> Subject: Re: Proposed Contribution to Apache Commons,
>
> On 10/2/15 12:08 PM, Gary Gregory wrote:
>> Well, a champion can volunteer to shepherd this through our incubator I
>> suppose,
> OK, I will volunteer to do this. I propose that we start this as a
>
On 10/26/15 4:04 AM, Siegfried Goeschl wrote:
> Hi folks,
>
> I basically agree here with Bernd
>
> * the project needs clean-up
> * I think the idea is worthwhile
> * having something similar to “grok” as a stand-alone package together with a
> programmatic approach to build regexp could be th
Hi folks,
I basically agree here with Bernd
* the project needs clean-up
* I think the idea is worthwhile
* having something similar to “grok” as a stand-alone package together with a
programmatic approach to build regexp could be the way to go
* there is no community around so I think GitHu
On Sun, Oct 25, 2015 at 4:10 PM, Bernd Eckenfels
wrote:
> Am Sun, 25 Oct 2015 15:58:28 -0700
> schrieb Phil Steitz :
>
> > On 10/25/15 3:53 PM, Gary Gregory wrote:
> > > Let's see, would we run this through the Apache Incubator or could
> > > we simply run it through our Commons Sandbox and then
Am Sun, 25 Oct 2015 15:58:28 -0700
schrieb Phil Steitz :
> On 10/25/15 3:53 PM, Gary Gregory wrote:
> > Let's see, would we run this through the Apache Incubator or could
> > we simply run it through our Commons Sandbox and then up to Commons
> > itself?
> I think we can just start in the sandbox,
On Sun, Oct 25, 2015 at 3:58 PM, Phil Steitz wrote:
> On 10/25/15 3:53 PM, Gary Gregory wrote:
> > Let's see, would we run this through the Apache Incubator or could we
> > simply run it through our Commons Sandbox and then up to Commons itself?
> I think we can just start in the sandbox, followi
+1 and it seems Git is too popular to avoid.
Gary
On Sun, Oct 25, 2015 at 12:15 PM, Phil Steitz wrote:
> On 10/2/15 12:08 PM, Gary Gregory wrote:
> > Well, a champion can volunteer to shepherd this through our incubator I
> > suppose,
>
> OK, I will volunteer to do this. I propose that we star
On 10/25/15 3:53 PM, Gary Gregory wrote:
> Let's see, would we run this through the Apache Incubator or could we
> simply run it through our Commons Sandbox and then up to Commons itself?
I think we can just start in the sandbox, following the Incubator IP
clearance process as we have done before.
Let's see, would we run this through the Apache Incubator or could we
simply run it through our Commons Sandbox and then up to Commons itself?
Gayr
On Sun, Oct 25, 2015 at 12:06 AM, Javin Paul wrote:
> @ Siegfried Goeschl
>
> Having retired computer scientists turn to Open Source is great idea,
+1 and git please
Original message
From: Phil Steitz
Date: 10/25/2015 3:15 PM (GMT-05:00)
To: Commons Developers List
Subject: Re: Proposed Contribution to Apache Commons,
On 10/2/15 12:08 PM, Gary Gregory wrote:
> Well, a champion can volunteer to shepherd this thro
On 10/2/15 12:08 PM, Gary Gregory wrote:
> Well, a champion can volunteer to shepherd this through our incubator I
> suppose,
OK, I will volunteer to do this. I propose that we start this as a
Commons Sandbox project. To do that, we need a VOTE to accept the
code, a software grant and the IP cle
@ Siegfried Goeschl
Having retired computer scientists turn to Open Source is great idea,
nothing can beat experience and having them contributed to Apache or Github
is simply awesome.
On Sun, Oct 25, 2015 at 2:10 AM, Siegfried Goeschl <
siegfried.goes...@it20one.com> wrote:
> Hi Norman & Jeff,
gh-pages is the right place for it. You just have to browse to the
correct place on github.io to see it.
On Sat, Oct 24, 2015 at 5:59 PM, Dave Brosius wrote:
> Correct.
>
> This was the branch that Mr Shapiro used when he introduced the project to
> us, so that's where i did the work. And yes, i
Correct.
This was the branch that Mr Shapiro used when he introduced the project
to us, so that's where i did the work. And yes, it is now merged.
My colleague Jeff Rothenberg and I, retirees, have developed an alternative to
using regular expressions for searching for (and optionally replacin
Hello everybody,
the pull request was merged, but it is in the "gh-pages" branch not in
"master", so it's not visible by default on the github page.
-Pascal
Am 24.10.2015 um 22:27 schrieb Dave Brosius:
Dear My. Shapiro,
Greetings!
Thanks for wanting to share this codebase, and making it av
Dear My. Shapiro,
Greetings!
Thanks for wanting to share this codebase, and making it available at
github.
I have attempted to cleanup the repository to make it more approachable
for others who want to take a look, including reorganizing the src tree
and adding a proper maven build system.
: Proposed Contribution to Apache Commons,
My colleague, Jeff Rothenberg, and I are retired computer scientists and are
no strangers to regular expression theory and practice. Both of us have used
regular expressions for decades and have taught many other programmers how to
use them. Stephen Kleene
Hi Norman & Jeff,
I skimmed through the email conversation ….
* Personally I really like the idea that retired computer scientists turn to
Open Source :-)
* Looking at the GitHub project I indeed see a cultural gap which needs be
closed to do meaningful Open Source work
* I try to ignore the
My colleague, Jeff Rothenberg, and I are retired computer scientists and are
no strangers to regular expression theory and practice. Both of us have used
regular expressions for decades and have taught many other programmers how to
use them. Stephen Kleene (https://en.wikipedia.org/wiki/Stephen_Col
Well, a champion can volunteer to shepherd this through our incubator I
suppose, like CommonsRDF, which seems pretty inactive ATM. There is also
the issue of "donate and forget" vs. staying plugged in the community.
I just do not have the extra FOSS cycles to dig into the code ATM to see
what's un
On 10/2/15 11:46 AM, Gary Gregory wrote:
> I do not have time to dig into this one ATM but I'd like to give my 2c.
>
> Does this project introduce a new RE-like language or is it an API wrapper
> for REs? It sounds like it is both.
It looks to me like what it says it is, which is an alternative to
I do not have time to dig into this one ATM but I'd like to give my 2c.
Does this project introduce a new RE-like language or is it an API wrapper
for REs? It sounds like it is both.
A project like this I could see in Commons if the project was split into an
API module and modules for different p
On Tue, Sep 29, 2015 at 5:42 PM, Phil Steitz wrote:
> On 9/29/15 3:55 PM, Gary Gregory wrote:
> > Norman,
> >
> > Hello and welcome to Apache Commons.
> >
> > It's not clear to me why Naomi is better than regular expressions.
> Pointing
> > to Javadocs is not the best way to get traction.
> >
> >
Hi,
On 09/30/2015 01:44 AM, Jochen Wiedmann wrote:
Hi, Norman,
On Tue, Sep 29, 2015 at 10:06 PM, wrote:
My colleague Jeff Rothenberg and I, retirees, have developed an alternative to
using regular expressions for searching for (and optionally replacing)
patterns in text.
Something that is
Hi, Norman,
On Tue, Sep 29, 2015 at 10:06 PM, wrote:
> My colleague Jeff Rothenberg and I, retirees, have developed an alternative to
> using regular expressions for searching for (and optionally replacing)
> patterns in text.
I admit that I am becoming somewhat cautious by reading about "an
a
Added a pull request with a first pass at moving all of this to a maven
build. builds and generates javadoc fine. Might need some more fine tuning.
On 09/29/2015 08:27 PM, Dave Brosius wrote:
Also the source code is not in the proper package structure. The
class's have packages, but are just
On 9/29/15 3:55 PM, Gary Gregory wrote:
> Norman,
>
> Hello and welcome to Apache Commons.
>
> It's not clear to me why Naomi is better than regular expressions. Pointing
> to Javadocs is not the best way to get traction.
>
> Your project would be better served by having some documentation on your
Also the source code is not in the proper package structure. The class's
have packages, but are just dumped directly in src. There is javadoc,
but just dumped in the main folder. I just dump that, and having support
building the javadoc from build tools. Setting the structure of the
project up
Perhaps i am blind, but i don't see any maven, ant or gradle build
files. You really need to add these for your code base to be accessible
to others wanted to uptake it. (Hopefully maven).
--dave
On 09/29/2015 06:55 PM, Gary Gregory wrote:
Norman,
Hello and welcome to Apache Commons.
It's n
Norman,
Hello and welcome to Apache Commons.
It's not clear to me why Naomi is better than regular expressions. Pointing
to Javadocs is not the best way to get traction.
Your project would be better served by having some documentation on your
front page with an example driven tutorial.
Is Naomi
My colleague Jeff Rothenberg and I, retirees, have developed an alternative to
using regular expressions for searching for (and optionally replacing)
patterns in text. We believe it is generally useful to Java programmers and
would like to contribute it to Apache Commons, where we will continue to
34 matches
Mail list logo
