[jira] [Commented] (JOSHUA-324) Address Apache Joshua 6.1 RC#2 Issues

2017-01-17 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/JOSHUA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827366#comment-15827366
 ] 

Hudson commented on JOSHUA-324:
---

SUCCESS: Integrated in Jenkins build joshua_master #166 (See 
[https://builds.apache.org/job/joshua_master/166/])
JOSHUA-324 Address Apache Joshua 6.1 RC#2 Issues (lewis.mcgibbney: rev 
ae755a8bc0b1de9475285fcc8d35d8a8b5f00a6f)
* (add) LICENSE.txt
* (edit) CHANGES.md
* (delete) LICENSE
* (edit) src/main/assembly/src.xml
* (edit) doap_joshua.rdf


> Address Apache Joshua 6.1 RC#2 Issues
> -
>
> Key: JOSHUA-324
> URL: https://issues.apache.org/jira/browse/JOSHUA-324
> Project: Joshua
>  Issue Type: Task
>Affects Versions: 6.1
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Blocker
> Fix For: 6.1
>
>
> Feedback from [~jmclean] (thank you Justin) on our RC#2 is as follows
> {code}
> ==
> - Your missing incubating in the release artifacts name. [1]
> - There are a number of binary files in the source release that look to be
> compiled source code.
> I checked:
> - name doesn’t include incubating
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE is missing a few things (see below)
> - a source file is missing an Apache header [7]
> - Several unexpected binary files are contained in the source release
> [8][9][10][11]
> - Can compile from source
> License is missing:
> - MIT licensed normalize.css v3.0.3 bundled in [5]
> - glyph icon fonts [6]
> Not an issue but it's a little odd to have LICENSE and NOTICE.txt - usually
> both are bare or both have .txt extension.
> Also while looking at your site I noticed that the download links of you
> incubating site [2] points to github, please change to point to the offical
> release area.
> Also the 6.1 release has already been tagged and it available for public
> download on github [4]  before this vote is finished. This is IMO against
> Apache release policy [3] please remove.
> I also notice you recently released the language packs (18th Nov) but there
> doesn’t seem to have been a vote for that? Any reason for this?
> ===
> [1] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> [2] 
> https://cwiki.apache.org/confluence/display/JOSHUA/Apache+Joshua+%28Incubating%29+Home
> [3] http://www.apache.org/dev/release.html#what
> [4] https://github.com/apache/incubator-joshua/releases
> [5] ./demo/bootstrap/css/bootstrap.min.css
> [6] apache-joshua-6.1/demo/bootstrap/fonts/*
> [7] ./src/test/java/org/apache/joshua/decoder/ff/tm/OwnerMapTest.java
> [8] ./bin/GIZA++
> [9] ./bin/mkcls
> [10 ]./bin/snt2cooc.out
> [11] ,/src/test/resources/berkeley_lm/lm.berkeleylm.gz
> [12] http://www.mail-archive.com/general%40incubator.apache.org/msg57543.html
> [13] http://www.mail-archive.com/general%40incubator.apache.org/msg57551.html
> {code}
> This is a blocking issue and until addressed we cannot release 6.1-incubating



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JOSHUA-324) Address Apache Joshua 6.1 RC#2 Issues

2017-01-17 Thread Lewis John McGibbney (JIRA) 

[ 
https://issues.apache.org/jira/browse/JOSHUA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827360#comment-15827360
 ] 

Lewis John McGibbney commented on JOSHUA-324:
-

I'll be finishing my QA and producing an RC#3 tomorrow folks. Thanks.
I've just committed 
{code}
commit ae755a8bc0b1de9475285fcc8d35d8a8b5f00a6f
Author: Lewis John McGibbney 
Date:   Tue Jan 17 19:12:10 2017 -0800

JOSHUA-324 Address Apache Joshua 6.1 RC#2 Issues
{code}

> Address Apache Joshua 6.1 RC#2 Issues
> -
>
> Key: JOSHUA-324
> URL: https://issues.apache.org/jira/browse/JOSHUA-324
> Project: Joshua
>  Issue Type: Task
>Affects Versions: 6.1
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Blocker
> Fix For: 6.1
>
>
> Feedback from [~jmclean] (thank you Justin) on our RC#2 is as follows
> {code}
> ==
> - Your missing incubating in the release artifacts name. [1]
> - There are a number of binary files in the source release that look to be
> compiled source code.
> I checked:
> - name doesn’t include incubating
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE is missing a few things (see below)
> - a source file is missing an Apache header [7]
> - Several unexpected binary files are contained in the source release
> [8][9][10][11]
> - Can compile from source
> License is missing:
> - MIT licensed normalize.css v3.0.3 bundled in [5]
> - glyph icon fonts [6]
> Not an issue but it's a little odd to have LICENSE and NOTICE.txt - usually
> both are bare or both have .txt extension.
> Also while looking at your site I noticed that the download links of you
> incubating site [2] points to github, please change to point to the offical
> release area.
> Also the 6.1 release has already been tagged and it available for public
> download on github [4]  before this vote is finished. This is IMO against
> Apache release policy [3] please remove.
> I also notice you recently released the language packs (18th Nov) but there
> doesn’t seem to have been a vote for that? Any reason for this?
> ===
> [1] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> [2] 
> https://cwiki.apache.org/confluence/display/JOSHUA/Apache+Joshua+%28Incubating%29+Home
> [3] http://www.apache.org/dev/release.html#what
> [4] https://github.com/apache/incubator-joshua/releases
> [5] ./demo/bootstrap/css/bootstrap.min.css
> [6] apache-joshua-6.1/demo/bootstrap/fonts/*
> [7] ./src/test/java/org/apache/joshua/decoder/ff/tm/OwnerMapTest.java
> [8] ./bin/GIZA++
> [9] ./bin/mkcls
> [10 ]./bin/snt2cooc.out
> [11] ,/src/test/resources/berkeley_lm/lm.berkeleylm.gz
> [12] http://www.mail-archive.com/general%40incubator.apache.org/msg57543.html
> [13] http://www.mail-archive.com/general%40incubator.apache.org/msg57551.html
> {code}
> This is a blocking issue and until addressed we cannot release 6.1-incubating



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Rebase on Relese

2017-01-17 Thread lewis john mcgibbney 
Hi Matt,

On Mon, Jan 16, 2017 at 9:27 AM, <
dev-digest-h...@joshua.incubator.apache.org> wrote:

>
> From: Matt Post 
> To: dev@joshua.incubator.apache.org
> Cc:
> Date: Fri, 13 Jan 2017 12:28:59 -0500
> Subject: Re: Rebase on Relese
> Hi Lewis,
>
> Welcome back!
>
> I think we have checked off all the things on your list, and are ready any
> time for the release. Do you have the time to double-check, and then to
> head up this effort?
>
>
I'll try to get back on to it today.
Thanks for everyone patience.
Lewis

Re: Plugging self-hosted Joshua into mailman?

2017-01-17 Thread Karel Novotný 
Thanks Lewis, will go through the documentation.

best

karel


On 17.1.2017 18:07, lewis john mcgibbney wrote:
> Hi Karel,
> The short answer is yes.
> I would advise you to start at the Tutorial
> https://cwiki.apache.org/confluence/display/JOSHUA/Getting+Started
> If you find anything which causes you problems then please write back here.
> Once you have skipped through the tutorial then you will have a much better
> feel for the workflow required.
> I can see the Apache Tika language identification and translate API's being
> of particular use here when considered in a runtime context. We have a
> Joshua implementation over in Tika which can aid you in this task however
> try the Joshua tutorial first.
> Lewis
>
> On Mon, Jan 16, 2017 at 7:41 AM, Chris Mattmann  wrote:
>
>> Hi Karel,
>>
>> I would recommend moving this thread to dev@joshua.incubator.apache.org
>> instead of the private list. I’ve moved private to BCC.
>>
>> Thank you.
>>
>> Cheers,
>> Chris
>>
>>
>>
>> On 1/16/17, 6:58 AM, wrote:
>>
>> Hello,
>>
>> We would like to build a self-hosted machine translation system that
>> could be plugged into our mailman installs. The objective is that the
>> members of our multicultural network would be able to send email in
>> their mother language and it would be delivered to the list
>> machine-translated (and vise versa).
>>
>> Are we on the right track with Joshua? I suppose that a lot of
>> configuration would be needed, but at this point I want to know if I am
>> not completely mistaken when considering your sw for this.
>>
>> Thanks
>>
>> karel
>>
>>
>> --
>> ~~~
>> Karel Novotny
>> Knowledge Sharing & Network Development Coordinator
>> APC - The Association for Progressive Communications
>> https://www.apc.org
>> GSM: +420 605 243 246 (GMT +1)
>> jabber: ka...@riseup.net
>> Working/online: Monday - Thursday
>> ~~~
>> My public OpenPGP key: https://pgp.mit.edu/pks/lookup?op=get=
>> 0x7FDEF502377E4FCA
>>
>>
>>
>>
>>
>>
>

-- 
~~~
Karel Novotny 
Knowledge Sharing & Network Development Coordinator
APC - The Association for Progressive Communications 
https://www.apc.org
GSM: +420 605 243 246 (GMT +1)
jabber: ka...@riseup.net
Working/online: Monday - Thursday
~~~
My public OpenPGP key: 
https://pgp.mit.edu/pks/lookup?op=get=0x7FDEF502377E4FCA

Re: Plugging self-hosted Joshua into mailman?

2017-01-17 Thread lewis john mcgibbney 
Hi Karel,
The short answer is yes.
I would advise you to start at the Tutorial
https://cwiki.apache.org/confluence/display/JOSHUA/Getting+Started
If you find anything which causes you problems then please write back here.
Once you have skipped through the tutorial then you will have a much better
feel for the workflow required.
I can see the Apache Tika language identification and translate API's being
of particular use here when considered in a runtime context. We have a
Joshua implementation over in Tika which can aid you in this task however
try the Joshua tutorial first.
Lewis

On Mon, Jan 16, 2017 at 7:41 AM, Chris Mattmann  wrote:

> Hi Karel,
>
> I would recommend moving this thread to dev@joshua.incubator.apache.org
> instead of the private list. I’ve moved private to BCC.
>
> Thank you.
>
> Cheers,
> Chris
>
>
>
> On 1/16/17, 6:58 AM, wrote:
>
> Hello,
>
> We would like to build a self-hosted machine translation system that
> could be plugged into our mailman installs. The objective is that the
> members of our multicultural network would be able to send email in
> their mother language and it would be delivered to the list
> machine-translated (and vise versa).
>
> Are we on the right track with Joshua? I suppose that a lot of
> configuration would be needed, but at this point I want to know if I am
> not completely mistaken when considering your sw for this.
>
> Thanks
>
> karel
>
>
> --
> ~~~
> Karel Novotny
> Knowledge Sharing & Network Development Coordinator
> APC - The Association for Progressive Communications
> https://www.apc.org
> GSM: +420 605 243 246 (GMT +1)
> jabber: ka...@riseup.net
> Working/online: Monday - Thursday
> ~~~
> My public OpenPGP key: https://pgp.mit.edu/pks/lookup?op=get=
> 0x7FDEF502377E4FCA
>
>
>
>
>
>


-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Re: Plugging self-hosted Joshua into mailman?

2017-01-17 Thread Matt Post 
Hello,

Joshua would be suitable to this. We have models built for FR→EN and ES→EN. I 
want to improve these because some certain data was left out. I could also 
build ones for the other direction.

One question — What do you mean about 3rd party services being "untrustworthy"?

matt


> On Jan 16, 2017, at 12:27 PM, Karel Novotný  wrote:
> 
> Hello developers,
> 
> I am new to this list, so missing a lot of background. Apologies
> beforehand for eventually dumb questions...
> 
> We would like to build a self-hosted machine translation system that
> could be plugged into our mailman installs. The objective is that the
> members of our multicultural network would be able to send email in
> their mother language and it would be delivered to the list
> machine-translated (and vise versa). The translation pairs we care about
> most are EN<->FR and EN<->ES
> 
> Our dream scenario is:
> 
> 1. A translator machine is installed on our server, so the messages
> don't need to be run through untrustworthy 3rd party services (googletrans)
> 2. Mailman (or similar) is connected to such a translator
> 3. Mailing list users can opt to receive messages sent to the mailing
> list in following format:
> 
> 
> Message body
> --
> Message body translated
> -
> 
> 4. Similarly, the system can be configured so that when receiving
> messages from specific senders the messages get translated from FR or ES
> into EN
> 
> Our default language used on lists is EN
> 
> Is Joshua relevant for this? Any previous experience with similar setup?
> I suppose that a lot of configuration would be needed, but at this point
> I want to know if I am not completely mistaken when considering your
> Joshua for this.
> 
> Thanks
> 
> karel
> 
> ---
> 
> -- 
> ~~~
> Karel Novotny 
> Knowledge Sharing & Network Development Coordinator
> APC - The Association for Progressive Communications 
> https://www.apc.org
> GSM: +420 605 243 246 (GMT +1)
> jabber: ka...@riseup.net
> Working/online: Monday - Thursday
> ~~~
> My public OpenPGP key: 
> https://pgp.mit.edu/pks/lookup?op=get=0x7FDEF502377E4FCA
> 
>