what are responsibilities for release of revisions to tesseract source?

[Hhh Vvv]

Hello.

I have been contracted to work with Tesseract on OCR related technology.

In developing code in C++ around engine, there are certain (quite simple)

enhancements I have developed to make my life easier within

code, to useful effect, without disturbing base code operation too much.

So now I have these patches to support my version of tesseract. What

are my responsibilities regarding releasing these to core code in order to

adhere in letter and spirit to code license?

It's only two files, with about 3 lines of diff each, but it's useful and maybe

suitable to share, and we want to make sure we adhere to community 

license requirements.

Please advise. Thanks.

H. Vidal, Jr.

[Zdenko Podobný]

The best way is to create a pull request in github.com.

Or sent a patch to this forum.

Zdenko

--
You received this message because you are subscribed to the Google Groups "tesseract-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-dev+unsubscribe@googlegroups.com.
To post to this group, send email to tesser...@googlegroups.com.
Visit this group at https://groups.google.com/group/tesseract-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-dev/53682439-1ec2-49c9-9971-3bdccbd1615e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Hhh Vvv]

Just, literally, post the patches in line with a post here????

They're small, but....

well, I guess, let me know.... :)

hv

On Thursday, January 19, 2017 at 3:32:32 AM UTC-5, Zdenko Podobný wrote:

The best way is to create a pull request in github.com.

Or sent a patch to this forum.

Zdenko

On Wed, Jan 18, 2017 at 11:21 PM, Hhh Vvv <hv1...@gmail.com> wrote:

Hello.

I have been contracted to work with Tesseract on OCR related technology.

In developing code in C++ around engine, there are certain (quite simple)

enhancements I have developed to make my life easier within

code, to useful effect, without disturbing base code operation too much.

So now I have these patches to support my version of tesseract. What

are my responsibilities regarding releasing these to core code in order to

adhere in letter and spirit to code license?

It's only two files, with about 3 lines of diff each, but it's useful and maybe

suitable to share, and we want to make sure we adhere to community 

license requirements.

Please advise. Thanks.

H. Vidal, Jr.

--
You received this message because you are subscribed to the Google Groups "tesseract-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-de...@googlegroups.com.

[Zdenko Podobný]

PR is preferable way, but you can send a patch in attachment or inline of e-amil...

Zdenko

To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-dev+unsubscribe@googlegroups.com.

To post to this group, send email to tesser...@googlegroups.com.
Visit this group at https://groups.google.com/group/tesseract-dev.

To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-dev/242a67a1-be3f-4c7e-b107-db9401fc8818%40googlegroups.com.

[Jeff Breidenbach]

Responsibilities are described in Tesseract's license. Read it.

https://github.com/tesseract-ocr/tesseract/blob/master/LICENSE