Re: [VOTE] - Graduate Apache Joshua (incubating) as a TLP

[Tom Barber]

+1 ship it

On Fri, 21 Sep 2018, 16:34 Chris Mattmann,  wrote:

> +1 binding.
>
>
>
> Go Joshua Go!
>
>
>
> Cheers,
> Chris
>
>
>
>
>
>
>
>
>
> From: Tommaso Teofili 
> Reply-To: "dev@joshua.incubator.apache.org" <
> dev@joshua.incubator.apache.org>
> Date: Friday, September 21, 2018 at 5:54 AM
> To: "gene...@incubator.apache.org" 
> Cc: "dev@joshua.incubator.apache.org" 
> Subject: [VOTE] - Graduate Apache Joshua (incubating) as a TLP
>
>
>
> Hi all,
>
>
>
>
>
> The Apache Joshua podling PMC would like the project to graduate to a TLP.
>
> Joshua entered Incubation on February 13th, 2016.
>
> The 6.1 release was the first one done within ASF as an Incubator
>
> project, the PPMC has grown since incubation start.
>
>
>
> Vote:
>
> [ ] +1 - Recommend Graduation of Apache Joshua as a TLP
>
> [ ] -1 - Do not recommend graduation of Apache Joshua because ….
>
>
>
>
>
> The Graduation Proposal was written, discussed and voted on the
>
> project dev@ list [1,2] and here on general@ [3]. As per
>
> recommendations made in [3], the By-Laws Clause was removed [4].
>
> The final resolution can be found at [5].
>
>
>
>
>
> Regards,
>
> Tommaso
>
>
>
>
>
> [1] :
> https://lists.apache.org/thread.html/2687c75696b61344dadf085c1f48443f71baaf88a9b012f86c35d2e6@%3Cdev.joshua.apache.org%3E
>
> [2] :
> https://lists.apache.org/thread.html/8ef1f4a9919f56979507fae749af691acb011e9ca7da9bc64bbfc8aa@%3Cdev.joshua.apache.org%3E
>
> [3] :
> https://lists.apache.org/thread.html/6c274f2ec6261828c636e950447a2c7d926bcc91f95cc10f183690a7@%3Cdev.joshua.apache.org%3E
>
> [4] :
> https://lists.apache.org/thread.html/7bd8bb062c96cde65c4d7fd4dd1310aed0169d5922b40ec78216d161@%3Cdev.joshua.apache.org%3E
>
> [5] :
>
> WHEREAS, the Board of Directors deems it to be in the best
>
>
>
> interests of the Foundation and consistent with the
>
>
>
> Foundation's purpose to establish a Project Management
>
>
>
> Committee charged with the creation and maintenance of
>
>
>
> open-source software, for distribution at no charge to
>
>
>
> the public, related to statistical and other forms of machine
>
>
>
> translation.
>
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>
>
>
> Committee (PMC), to be known as the "Apache Joshua Project",
>
>
>
> be and hereby is established pursuant to Bylaws of the
>
>
>
> Foundation; and be it further
>
>
>
> RESOLVED, that the Apache Joshua Project be and hereby is
>
>
>
> responsible for the creation and maintenance of software
>
>
>
> related to statistical and other forms of machine translation;
>
>
>
> and be it further
>
>
>
> RESOLVED, that the office of "Vice President, Apache Joshua" be
>
>
>
> and hereby is created, the person holding such office to
>
>
>
> serve at the direction of the Board of Directors as the chair
>
>
>
> of the Apache Joshua Project, and to have primary responsibility
>
>
>
> for management of the projects within the scope of
>
>
>
> responsibility of the Apache Joshua Project; and be it further
>
>
>
> RESOLVED, that the persons listed immediately below be and
>
>
>
> hereby are appointed to serve as the initial members of the
>
>
>
>
>
> Apache Joshua Project:
>
>
>
>
>
> * Tom Barber  
>
>
>
>
>
> * Thamme Gowda
>
>
>
>
>
> * Felix Hieber
>
>
>
>
>
> * Lewis John McGibbney
>
>
>
>
>
> * Chris Mattmann  
>
>
>
>
>
> * Matt Post   
>
>
>
>
>
> * Paul Ramirez
>
>
>
>
>
> * Henry Saputra   
>
>
>
>
>
> * Kellen Sunderland   
>
>
>
>
>
> * Tommaso Teofili 
>
>
>
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tommaso Teofili
>
>
>
> be appointed to the office of Vice President, Apache Joshua to
>
>
>
> serve in accordance with and subject to the direction of the
>
>
>
> Board of Directors and the Bylaws of the Foundation until
>
>
>
> death, resignation, retirement, removal or disqualification,
>
>
>
> or until a successor is appoi

Re: [VOTE] Graduate the Apache Joshua (Incubating) Project

[Tom Barber]

+1

On Fri, 27 Apr 2018, 00:58 Thamme Gowda,  wrote:

> +1 (binding)
>
>
> Cheers,
> TG
>
> --
> *Thamme Gowda *
> @thammegowda  | https://isi.edu/~tg
> ~Sent via somebody's Webmail server
>
> 2018-04-24 22:02 GMT-07:00 lewis john mcgibbney :
>
> > Hi Folks,
> > I would like to open a VOTE for graduating the Apache Joshua (Incubating)
> > project.
> > For those that are interested, the Incubator guidelines on graduation can
> > be found at [0].
> > Joshua has been reporting to the IPMC since 16th March 2016 and made one
> > Incubating release.
> >
> > Joshua Basics
> >
> >- Podling Proposal 
> >- Status: current
> >- Established: 2016-02-13
> >- Incubating for 802 days
> >- Prior Board Reports  >
> >
> > There are a few issues to resolve before drafting the graduation
> resolution
> > however this community VOTE is timely. The VOTE will be open at least 72
> > hours and will pass if 3 +1's are received from the Joshua PPMC.
> >
> > [ ] +1 Graduate the Apache Joshua (Incubating) Project
> > [ ] -1 NO NOT Graduate the Apache Joshua (Incubating) Project... please
> > provide reasoning
> >
> > P.S. Here is my binding +1
> >
> > [0]
> >
> https://incubator.apache.org/guides/graduation.html#the_graduation_process
> >
> >
> > --
> > http://home.apache.org/~lewismc/
> > http://people.apache.org/keys/committer/lewismc
> >
>

-- 


Spicule Limited is registered in England & Wales. Company Number: 
09954122. Registered office: First Floor, Telecom House, 125-135 Preston 
Road, Brighton, England, BN1 6AF. VAT No. 251478891.




All engagements 
are subject to Spicule Terms and Conditions of Business. This email and its 
contents are intended solely for the individual to whom it is addressed and 
may contain information that is confidential, privileged or otherwise 
protected from disclosure, distributing or copying. Any views or opinions 
presented in this email are solely those of the author and do not 
necessarily represent those of Spicule Limited. The company accepts no 
liability for any damage caused by any virus transmitted by this email. If 
you have received this message in error, please notify us immediately by 
reply email before deleting it from your system. Service of legal notice 
cannot be effected on Spicule Limited by email.

Re: [DISCUSS] Graduation (was Re: Path to TLP)

[Tom Barber]

ant to pursue, I don't have time for it outside of work.
I am happy to still linger on the project, but am unlikely to be much of an
active participant unless I'm explicitly asked for something.

As I've written before here, I think there may still some role for
statistical systems, and therefore, for Joshua. In low-resource situations,
StatMT may still be the right approach overall, or even simply the best way
to quickly build up a working system. There is some promise I think in
deploying models easily on older hardware that people have, and perhaps
getting people to hep contribute translations and translation memories that
could be used to build and improve systems. There are surely more good
ideas in this space in the vein of providing a good tool to users.

It's been a great experience for me working with the Apache community
on Joshua. I am grateful to Chris for convincing us to make Joshua an
Apache incubator project, which put a lot of new life into the project.
Lewis has been a lot of help throughout helping smooth over the transition;
Tommaso has repeatedly helped with tasks large and small; and that is just
three of you. It's too bad therefore that the timing just didn't work out,
but neural MT ascended very rapidly. I know there are other members here
who are also thinking along these lines. At the same time, I hope my
departure from active development doesn’t mean the end of the project for
those of you who wish to keep working on it.

Sincerely,
matt



Le 25 sept. 2017 à 23:10, Tommaso Teofili 

a écrit :

I would also think we're ready for graduation.
My only concern relates to how many of the current committers are

willing

to keep contributing to the project, basically if we have a PMC

which is

big enough for the graduation.

Regards,
Tommaso


Il giorno sab 23 set 2017 alle ore 01:21 Chris Mattmann <

mattm...@apache.org>

ha scritto:


Tom, glad you raised this issue, IMO, Joshua is ready for TLP.

We’ve:

1. Added new PPMC/committers
2. Made a release
3. Been friendly and cordial and welcoming on the lists
4. Vetted the software
5. Have some decent, emerging docs

Graduation time…Thoughts?

Cheers,
Chris

P.S. Subject line change to officially turn this into a [DISCUSS]

and

hopefully
a [VOTE]



On 9/22/17, 4:19 PM, "Tom Barber"  wrote:

   So I've not checked against the checklist on the podling page

yet, but

what
   do people feel is missing from Joshua prior to graduation?

   I'd like to see some non mentors ship a release so we know we've

got

the
   docs right, but of course it doesn't have to be a major release.
Similarly
   was all the licensing stuff resolved etc?

   I'm curious as its not a very fast paced project and it feels

like ones

   like Joshua could sit in the incubator for years without causing

much

   trouble but also not graduating. I'm not in any great rush, but

what do

   people feel about it?

   Tom












--


Spicule Limited is registered in England & Wales. Company Number: 09954122. 
Registered office: First Floor, Telecom House, 125-135 Preston Road, 
Brighton, England, BN1 6AF. VAT No. 251478891.



All engagements are subject to Spicule Terms and Conditions of Business. 
This email and its contents are intended solely for the individual to whom 
it is addressed and may contain information that is confidential, 
privileged or otherwise protected from disclosure, distributing or copying. 
Any views or opinions presented in this email are solely those of the 
author and do not necessarily represent those of Spicule Limited. The 
company accepts no liability for any damage caused by any virus transmitted 
by this email. If you have received this message in error, please notify us 
immediately by reply email before deleting it from your system. Service of 
legal notice cannot be effected on Spicule Limited by email.

[jira] [Resolved] (JOSHUA-333) The English-English Language Pack download links are broken.

[Tom Barber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JOSHUA-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom Barber resolved JOSHUA-333.
---
Resolution: Fixed
  Assignee: Tom Barber

> The English-English Language Pack download links are broken.
> 
>
> Key: JOSHUA-333
> URL: https://issues.apache.org/jira/browse/JOSHUA-333
> Project: Joshua
>  Issue Type: Bug
>Reporter: David Gonzalez
>    Assignee: Tom Barber
>
> On the Apache Joshua English-English wiki page the ruleset (PPDB v2) 
> downloads are all broken (404).
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65142863



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JOSHUA-333) The English-English Language Pack download links are broken.

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-333:
---

Yup, they were copied, the links have now been updated.

> The English-English Language Pack download links are broken.
> 
>
> Key: JOSHUA-333
> URL: https://issues.apache.org/jira/browse/JOSHUA-333
> Project: Joshua
>  Issue Type: Bug
>Reporter: David Gonzalez
>
> On the Apache Joshua English-English wiki page the ruleset (PPDB v2) 
> downloads are all broken (404).
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65142863



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [jira] [Commented] (JOSHUA-333) The English-English Language Pack download links are broken.

[Tom Barber]

Yeah they were copied, I've updated the links.

On 08/01/18 18:55, Matt Post wrote:

Hi folks,

Hope we can dig these up because they’ve been deleted from JHU’s servers.

matt (from my phone)


Le 5 janv. 2018 à 17:51, Lewis John McGibbney (JIRA)  a écrit :


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

Lewis John McGibbney commented on JOSHUA-333:
-

[~bugg_tb] were these files copied when we migrated from [~post]'s server to 
Dropbox?


The English-English Language Pack download links are broken.


Key: JOSHUA-333
URL: https://issues.apache.org/jira/browse/JOSHUA-333
Project: Joshua
 Issue Type: Bug
   Reporter: David Gonzalez

On the Apache Joshua English-English wiki page the ruleset (PPDB v2) downloads 
are all broken (404).
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65142863



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)




--


Spicule Limited is registered in England & Wales. Company Number: 09954122. 
Registered office: First Floor, Telecom House, 125-135 Preston Road, 
Brighton, England, BN1 6AF. VAT No. 251478891.



All engagements are subject to Spicule Terms and Conditions of Business. 
This email and its contents are intended solely for the individual to whom 
it is addressed and may contain information that is confidential, 
privileged or otherwise protected from disclosure, distributing or copying. 
Any views or opinions presented in this email are solely those of the 
author and do not necessarily represent those of Spicule Limited. The 
company accepts no liability for any damage caused by any virus transmitted 
by this email. If you have received this message in error, please notify us 
immediately by reply email before deleting it from your system. Service of 
legal notice cannot be effected on Spicule Limited by email.

Re: [DISCUSS] Graduation (was Re: Path to TLP)

[Tom Barber]

Good words Lewis.

On Fri, Oct 6, 2017 at 9:26 AM, lewis john mcgibbney 
wrote:

> Hi Folks,
> In my limited experience at Apache ;)
> I've come to notice that communities and therefore projects far exceed
> their usefulness outside of what current industry or academia is doing.
> Examples are all over the place, but my own experience stems from my
> involvement with the Apache Nutch project. Key inventors of that software
> moved on to Hadoop and goodness knows whatever else, but the current Nutch
> community remains at around ~1K subscribers on out user@ mailing list.
> I've
> personally seen and pushed >15 releases used by countless (1000's) of
> people around the world. The software exists are THE best maintained,
> highest quality, production ready Web search software current available to
> this day.
> Chris' points are well founded, Tomasso's match very appropriately to the
> fact that Joshua is nowhere near a dead project. I acknowledge that no-one
> said it was. The resources available for Joshua are FAR more comprehensive
> than anywhere else I've seen. FAR FAR more comprehensive. Joshua is the
> FIRST toolkit to be made available as a packaged, consumable,
> community-backed software artifact for anyone attempting to get involved
> with machine translation.
> NONE of the NMT software communities even come close to providing new
> software developers with translation packs as Joshua does. They don't even
> come close. AFAIK, all of the people so far working on NMT have kept
> everything proprietary... which is utterly useless for the next person or
> the next academic, etc.
> This highlights the essence and hits at the heart of why a group of us
> shepharded Joshua into the ASF in the first place.
> Believe me, if people are actively discussing a new release on an Apache
> mailing list (or any mailing list for that matter), there is always purpose
> in continuing.
> To bring this back a bit, I will openly state that Matt you have been an
> excellent champion for JHU as well as representing yourself with regards to
> the way you have adopted and displayed a forward thinking, collaborative
> mentality for Joshua.
> If you feel your job is 'done', then I congratulate you.
> Joshua will live on... at Apache.
> Writing software at Apache is not about a competition. It is about writing
> high quality software in a collaborative environment for the public good.
> We achieve this through peer review from people we have probably never met.
> That is called community.
> If you would be gracious enough to stay with the community as a PMC Chair
> then it would be highly appreciated. If you feel at any time that this is
> too much, then let us know. We will be here and we will act when we cross
> that bridge.
> Over and out folks.
> Lewis
>
>
> On Thu, Oct 5, 2017 at 10:04 PM, <
> dev-digest-h...@joshua.incubator.apache.org> wrote:
>
> >
> >
> > From: Matt Post 
> > To: dev@joshua.incubator.apache.org
> > Cc:
> > Bcc:
> > Date: Fri, 6 Oct 2017 07:03:58 +0200
> > Subject: Re: [DISCUSS] Graduation (was Re: Path to TLP)
> > Thanks Tommaso. Though, I should say, initial thanks goes to Zhifei Li. I
> > just took it over.
> >
> > I think I can stick around in the capacity Chris suggests. Thanks, all.
> >
> > matt
> >
> >
>



-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim <http://twitter.com/spiculeim>

Schedule a meeting with me <http://meetme.so/spicule>

GB: +44(0)5603641316
US: +18448141689

<https://leanpub.com/juju-cookbook>

Path to TLP

[Tom Barber]

So I've not checked against the checklist on the podling page yet, but what
do people feel is missing from Joshua prior to graduation?

I'd like to see some non mentors ship a release so we know we've got the
docs right, but of course it doesn't have to be a major release. Similarly
was all the licensing stuff resolved etc?

I'm curious as its not a very fast paced project and it feels like ones
like Joshua could sit in the incubator for years without causing much
trouble but also not graduating. I'm not in any great rush, but what do
people feel about it?

Tom

Re: Podling Report Reminder - August 2017

[Tom Barber]

Thanks for that Lewis, I've signed it off.

Tom

On Tue, Aug 1, 2017 at 8:29 PM, lewis john mcgibbney 
wrote:

> Hi Folks,
> I've contributed our report.
> Please scope it out and see what you think.
> Lewis
>
> On Sat, Jul 29, 2017 at 6:02 AM, <
> dev-digest-h...@joshua.incubator.apache.org> wrote:
>
> >
> > dev Digest 29 Jul 2017 13:02:50 - Issue 225
> >
> > Topics (messages 2237 through 2237)
> >
> > Podling Report Reminder - August 2017
> > 2237 by: johndament.apache.org
> >
> > Administrivia:
> >
> > -
> > To post to the list, e-mail: dev@joshua.incubator.apache.org
> > To unsubscribe, e-mail: dev-digest-unsubscribe@joshua.
> incubator.apache.org
> > For additional commands, e-mail: dev-digest-help@joshua.
> > incubator.apache.org
> >
> > --
> >
> >
> >
> > -- Forwarded message --
> > From: johndam...@apache.org
> > To: dev@joshua.incubator.apache.org
> > Cc:
> > Bcc:
> > Date: Sat, 29 Jul 2017 13:02:37 -
> > Subject: Podling Report Reminder - August 2017
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 16 August 2017, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, August 02).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/August2017
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
> >
> >
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>



-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim <http://twitter.com/spiculeim>

Schedule a meeting with me <http://meetme.so/spicule>

GB: +44(0)5603641316
US: +18448141689

<https://leanpub.com/juju-cookbook>

Re: [RESULT] [VOTE] Release Apache Joshua 6.1 (Incubating) RC4

[Tom Barber]

Good work Tommaso!

On Wed, May 3, 2017 at 9:27 AM, Tommaso Teofili 
wrote:

> Hi Everyone,
>  As the 72 hours period has come and gone I would like to bring this thread
> to a close.
> The VOTE's have been counted and RESULT's are as follows:
>
> - [4] +1, let's get it released!!!
> Tommaso Teofili *
> Lewis John McGibbney *
> Matt Post *
> John Hewitt *
>
> - [0] +/-0, fine, but consider to fix few issues before...
> - [0] -1, nope, because... (and please explain why)
>
>  *Joshua PMC Binding VOTE
>  I'll progress with the remainder of the release procedure.
>
>  Regards,
>  Tommaso
>



-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim <http://twitter.com/spiculeim>

Schedule a meeting with me <http://meetme.so/spicule>

GB: +44(0)5603641316
US: +18448141689

<https://leanpub.com/juju-cookbook>

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

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-324:
---

Okay [~lewismc] I don't know what it does so I'm not going to tell you to 
remove it, but if you remove apache-release from 
https://github.com/apache/incubator-joshua/blob/master/pom.xml#L257

You'll find it probably starts working. I don't know what the apache-release 
profile is but its stopping maven copying properties from other modules into 
their configs when they run through it.

> 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

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-324:
---

Infact why is it running twice?

[INFO] Replacing 
/tmp/incubator-joshua/target/joshua-incubating-6.1-SNAPSHOT-jar-with-dependencies.jar
 with /tmp/incubator-joshua/target/joshua-incubating-6.1-SNAPSHOT-shaded.jar
[INFO] 
[INFO] --- maven-assembly-plugin:3.0.0:single (assembly) @ joshua-incubating ---
[INFO] Reading assembly descriptor: 
/tmp/incubator-joshua/src/main/assembly/src.xml
[INFO] Building tar: 
/tmp/incubator-joshua/target/joshua-incubating-6.1-SNAPSHOT-src.tar.gz
[INFO] Building zip: 
/tmp/incubator-joshua/target/joshua-incubating-6.1-SNAPSHOT-src.zip
[INFO] 
[INFO] --- maven-assembly-plugin:3.0.0:single (source-release-assembly) @ 
joshua-incubating ---
[INFO] Reading assembly descriptor: 
/tmp/incubator-joshua/src/main/assembly/src.xml


> 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

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-324:
---

Okay so its a bug in the maven archive plugin. Basically on the first run it 
picks up the POSIX flag, on the second run for the source code it doesn't seem 
to pick up any of the configs because stuff liker dryRun is false as well. I 
will suss that out and send a PR upstream, in the mean time you'll have to use 
a local user account or a container to build it I suspect.

> 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

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-324:
---

I have replicated it though, give me a while I'll see what I can do.

> 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

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-324:
---

Just don't run it on your NASA issued laptop! :P Or run it in a docker 
container or something :)

> 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: I want to join the project

[Tom Barber]

Hi Samir

To subscribe please send an email to
dev-subscr...@joshua.incubator.apache.org

Thanks

Tom

On Fri, Jan 27, 2017 at 12:04 PM, Samir Vasani 
wrote:

> Hi,
> Hope you are dong well.
> Myself a Java developer with 6 years of experience in IT industry.
> I would like to contribute my experience to Joshua Project.
> Therefor i request you to subscribe to the forum.
>
> Thanks & Regards,
> Samir Vasani
>



-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim <http://twitter.com/spiculeim>

Schedule a meeting with me <http://meetme.so/spicule>

GB: +44(0)5603641316
US: +18448141689

<https://leanpub.com/juju-cookbook>

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

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-324:
---

My bad, found them: https://dist.apache.org/repos/dist/dev/incubator/joshua/

They aren't whats  in the staging maven repo though, so I'm not sure what 
[~lewi...@apache.org] did there.

> 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

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-324:
---

For what its worth, I can't find the binaries either so i'm not sure where 
[~jmclean] was looking... but yeah, whats in the git repo doesn't count, its 
whats in the tarballs that count.

> 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

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-324:
---

what is in git doesn't count though it's what's in the tarball post build that 
counts

> 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)

Signing off a Joshua Release

[Tom Barber]

Hello folks,

I see plenty of +1's going through the release vote,  which is great to see
people taking an active role in getting the release shipped.

For those of you who are new to the ASF there are a bunch of requirements
to sign off for a release which you can find here:

http://incubator.apache.org/guides/releasemanagement.html#check-list

My current concern is that people who are new to the incubator are +1'ing
software for release without check all or part of the release cycle. Whilst
not mandatory, when you +1 a release please can you try to indicate what
you've checked. The reason for this is,  the tag Lewis has built off isn't
the tip of master, so if you're basing  your +1 on your day to day
development and knowledge of the code base, that's not always whats
shipped. Also in the branching process,  its possible merges or alterations
were accidentally made that Lewis has missed (this is very unlikely I know
but you know, code changes). Also people build software on different OS's,
versions of OS's etc so just because it builds on  Lewis's laptop doesn't
mean it builds on mine, for example.

Also regarding licenses, disclaimers etc, people notice different things or
interpret stuff differently. its always possible that someone might miss a
library etc so its important multiple eyes run over the same stuff.

Cheers,

Tom

-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

GB: +44(0)5603641316
US: +18448141689

Downloading of non ASF licensed code

[Tom Barber]

This may have come up before in the whole licensing chat so apologies if
I'm just going over old ground.

The download-deps.sh file obviously downloads and builds stuff with non ASF
licenses, I realise this is for model training purposes only, and 99.9%
wont care, but should we consider putting a prompt into that script warning
people. I ask because a company might add in the training modules blindly
assuming because the script is distributed by the ASF the modules are also
ASL2.0.

Just a thought.

Tom

-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

GB: +44(0)5603641316
US: +18448141689

Re: [VOTE] Release Apache Joshua 6.1 RC#2

[Tom Barber]

Tests pass, artifacts look good. So I'm gonna say +1

For future releases I'd recommend we rejig the LICENSE file to be a bit
more like this example:

https://github.com/apache/incubator-ponymail/blob/master/LICENSE

Because Bootstrap and JQuery are MIT licensed but its not obvious in that
file where the ASF license end and the MIT block starts.

Tom

On Fri, Nov 25, 2016 at 3:04 PM, John Hewitt  wrote:

> +1
>
> On Nov 24, 2016 02:04, "Tommaso Teofili" 
> wrote:
>
> > +1
> >
> > Tommaso
> >
> > Il giorno mer 23 nov 2016 alle ore 15:25 kellen sunderland <
> > kellen.sunderl...@gmail.com> ha scritto:
> >
> >> +1, many thanks Lewis.
> >>
> >> On Wed, Nov 23, 2016 at 2:34 PM, Matt Post  wrote:
> >>
> >> > +1 Thanks, Lewis!
> >> >
> >> >
> >> > > On Nov 23, 2016, at 12:15 AM, lewis john mcgibbney <
> >> lewi...@apache.org>
> >> > wrote:
> >> > >
> >> > > Hello user@ and dev,
> >> > > Please VOTE on the Apache Joshua 6.1 Release Candidate #2.
> >> > >
> >> > > We solved 50 issues: https://s.apache.org/joshua6.1
> >> > >
> >> > > Git source tag (29c8be650d53216f779a340d33f8f61af4d45629):
> >> > > https://s.apache.org/pk2t <https://s.apache.org/joshua6.1tag>
> >> > >
> >> > > Staging repo:
> >> > > https://repository.apache.org/content/repositories/
> >> orgapachejoshua-1001/
> >> > > <https://repository.apache.org/content/repositories/
> >> > orgapachejoshua-1000/>
> >> > >
> >> > > Source Release Artifacts: https://dist.apache.org/repos/
> >> > > dist/dev/incubator/joshua/
> >> > >
> >> > > PGP release keys (signed using 48BAEBF6):
> >> https://dist.apache.org/repos/
> >> > > dist/release/incubator/joshua/KEYS
> >> > >
> >> > > Vote will be open for 72 hours.
> >> > > Thank you to everyone that is able to VOTE as well as everyone that
> >> > > contributed to Apache Joshua 6.1.
> >> > >
> >> > > [ ] +1, let's get it released!!!
> >> > > [ ] +/-0, fine, but consider to fix few issues before...
> >> > > [ ] -1, nope, because... (and please explain why)
> >> > >
> >> > > P.S. here is my +1
> >> > >
> >> > > --
> >> > > http://home.apache.org/~lewismc/
> >> > > @hectorMcSpector
> >> > > http://www.linkedin.com/in/lmcgibbney
> >> >
> >> >
> >>
> >
>



-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

GB: +44(0)5603641316
US: +18448141689

Re: Russian Language Model for Joshua

[Tom Barber]

HTTP resume exists for a reason. If you ask me nicely I'll post it to a US
S3 bucket next week! :P




--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)

On 17 July 2016 at 23:06, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Thanks Tom and Matt. I’m downloading now, but plane WiFi sucks so
> I may need to restart at some point
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++++++++++
>
>
>
>
>
>
>
>
>
>
> On 7/16/16, 3:16 PM, "Tom Barber"  wrote:
>
> >I  can host it: http://meteorite.bi/downloads/ru.kenlm
> >
> >Tom
> >
> >--
> >
> >Director Meteorite.bi - Saiku Analytics Founder
> >Tel: +44(0)5603641316
> >
> >(Thanks to the Saiku community we reached our Kickstart
> ><
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> >goal, but you can always help by sponsoring the project
> ><http://www.meteorite.bi/products/saiku/sponsorship>)
> >
> >On 16 July 2016 at 22:45, Mcgibbney, Lewis J (398M) <
> >lewis.j.mcgibb...@jpl.nasa.gov> wrote:
> >
> >> Can you make this public for good? Or is it the size which is the issue?
> >> Is this build using master branch Matt? I am having issues building
> models
> >> with masterŠ I¹ll post my issues on another thread.
> >>
> >> Dr. Lewis John McGibbney Ph.D., B.Sc.
> >> Data Scientist II
> >> Computer Science for Data Intensive Applications Group 398M
> >> Jet Propulsion Laboratory
> >> California Institute of Technology
> >> 4800 Oak Grove Drive
> >> Pasadena, California 91109-8099
> >> Mail Stop : 158-256C
> >> Tel:  (+1) (818)-393-7402
> >> Cell: (+1) (626)-487-3476
> >> Fax:  (+1) (818)-393-1190
> >> Email: lewis.j.mcgibb...@jpl.nasa.gov
> >>
> >>
> >>
> >>  Dare Mighty Things
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On 7/16/16, 1:09 PM, "Matt Post"  wrote:
> >>
> >> >Done:
> >> >
> >> >   http://cs.jhu.edu/~post/tmp/ru.kenlm
> >> >   4106251755 bytes, sha1sum:
> 5c894e24dafa42bc44a5bb6822812d6234eda791
> >> >
> >> >Let me know when you have it so I can delete it.
> >> >
> >> >matt
> >> >
> >> >
> >> >> On Jul 15, 2016, at 4:42 PM, Matt Post  wrote:
> >> >>
> >> >> All right, started trying to recompile. If you have a machine with >
> >> >>256 GB of memory, it might be more efficient for me to give you the
> raw
> >> >>ARPA file and for you to compile it. We'll see how it goes. Ping me
> in a
> >> >>day if you don't hear from me.
> >> >>
> >> >> matt
> >> >>
> >> >>
> >> >>> On Jul 15, 2016, at 4:40 PM, Mattmann, Chris A (3980)
> >> >>> wrote:
> >> >>>
> >> >>> Yes please! :)
> >> >>>
> >> >>> Sent from my iPhone
> >> >>>
> >> >>>> On Jul 15, 2016, at 1:39 PM, Matt Post  wrote:
> >> >>>>
> >> >>>> I have one built on Common Crawl. It's 25 GB uncompressed. My KenLM
> >> >>>>compiles of it failed in the past, but I'll try again. I expect it
> to
> >> >>>>be about 8 GB when that's done. Do you want it?
> >> >>>>
> >> >>>> matt
> >> >>>>
> >> >>>>
> >> >>>>> On Jul 15, 2016, at 3:50 PM, Mattmann, Chris A (3980)
> >> >>>>> wrote:
> >> >>>>>
> >> >>>>> Hey Folks,
> >> >>>>>
> >> >>>>> Anyone have a Russian Language Model for Joshua? Lewis was
> working on
> >> >>>>> one, not sure if he has it but just broadening the question.
> >> >>>>>
> >> >>>>> Cheers,
> >> >>>>> Chris
> >> >>>>>
> >> >>>>> ++
> >> >>>>> Chris Mattmann, Ph.D.
> >> >>>>> Chief Architect
> >> >>>>> Instrument Software and Science Data Systems Section (398)
> >> >>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> >>>>> Office: 168-519, Mailstop: 168-527
> >> >>>>> Email: chris.a.mattm...@nasa.gov
> >> >>>>> WWW:  http://sunset.usc.edu/~mattmann/
> >> >>>>> ++
> >> >>>>> Director, Information Retrieval and Data Science Group (IRDS)
> >> >>>>> Adjunct Associate Professor, Computer Science Department
> >> >>>>> University of Southern California, Los Angeles, CA 90089 USA
> >> >>>>> WWW: http://irds.usc.edu/
> >> >>>>> ++
> >> >>>>
> >> >>
> >> >
> >>
> >>
>

Re: Russian Language Model for Joshua

[Tom Barber]

I  can host it: http://meteorite.bi/downloads/ru.kenlm

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 16 July 2016 at 22:45, Mcgibbney, Lewis J (398M) <
lewis.j.mcgibb...@jpl.nasa.gov> wrote:

> Can you make this public for good? Or is it the size which is the issue?
> Is this build using master branch Matt? I am having issues building models
> with masterŠ I¹ll post my issues on another thread.
>
> Dr. Lewis John McGibbney Ph.D., B.Sc.
> Data Scientist II
> Computer Science for Data Intensive Applications Group 398M
> Jet Propulsion Laboratory
> California Institute of Technology
> 4800 Oak Grove Drive
> Pasadena, California 91109-8099
> Mail Stop : 158-256C
> Tel:  (+1) (818)-393-7402
> Cell: (+1) (626)-487-3476
> Fax:  (+1) (818)-393-1190
> Email: lewis.j.mcgibb...@jpl.nasa.gov
>
>
>
>  Dare Mighty Things
>
>
>
>
>
>
>
>
>
>
>
> On 7/16/16, 1:09 PM, "Matt Post"  wrote:
>
> >Done:
> >
> >   http://cs.jhu.edu/~post/tmp/ru.kenlm
> >   4106251755 bytes, sha1sum: 5c894e24dafa42bc44a5bb6822812d6234eda791
> >
> >Let me know when you have it so I can delete it.
> >
> >matt
> >
> >
> >> On Jul 15, 2016, at 4:42 PM, Matt Post  wrote:
> >>
> >> All right, started trying to recompile. If you have a machine with >
> >>256 GB of memory, it might be more efficient for me to give you the raw
> >>ARPA file and for you to compile it. We'll see how it goes. Ping me in a
> >>day if you don't hear from me.
> >>
> >> matt
> >>
> >>
> >>> On Jul 15, 2016, at 4:40 PM, Mattmann, Chris A (3980)
> >>> wrote:
> >>>
> >>> Yes please! :)
> >>>
> >>> Sent from my iPhone
> >>>
>  On Jul 15, 2016, at 1:39 PM, Matt Post  wrote:
> 
>  I have one built on Common Crawl. It's 25 GB uncompressed. My KenLM
> compiles of it failed in the past, but I'll try again. I expect it to
> be about 8 GB when that's done. Do you want it?
> 
>  matt
> 
> 
> > On Jul 15, 2016, at 3:50 PM, Mattmann, Chris A (3980)
> > wrote:
> >
> > Hey Folks,
> >
> > Anyone have a Russian Language Model for Joshua? Lewis was working on
> > one, not sure if he has it but just broadening the question.
> >
> > Cheers,
> > Chris
> >
> > ++
> > Chris Mattmann, Ph.D.
> > Chief Architect
> > Instrument Software and Science Data Systems Section (398)
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 168-519, Mailstop: 168-527
> > Email: chris.a.mattm...@nasa.gov
> > WWW:  http://sunset.usc.edu/~mattmann/
> > ++
> > Director, Information Retrieval and Data Science Group (IRDS)
> > Adjunct Associate Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > WWW: http://irds.usc.edu/
> > ++
> 
> >>
> >
>
>

Re: Russian Language Model for Joshua

[Tom Barber]

Street price is:

r3.8xlarge 32 104 244 2 x 320 SSD $2.66 per Hour



--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 15 July 2016 at 23:32, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Will do.
>
> Adding Paul Zimdars - do we have an Amazon machine that has > 256GB
> of memory? How much would that cost?
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++
>
>
>
>
>
>
>
>
>
>
> On 7/15/16, 1:42 PM, "Matt Post"  wrote:
>
> >All right, started trying to recompile. If you have a machine with > 256
> GB of memory, it might be more efficient for me to give you the raw ARPA
> file and for you to compile it. We'll see how it goes. Ping me in a day if
> you don't hear from me.
> >
> >matt
> >
> >
> >> On Jul 15, 2016, at 4:40 PM, Mattmann, Chris A (3980) <
> chris.a.mattm...@jpl.nasa.gov> wrote:
> >>
> >> Yes please! :)
> >>
> >> Sent from my iPhone
> >>
> >>> On Jul 15, 2016, at 1:39 PM, Matt Post  wrote:
> >>>
> >>> I have one built on Common Crawl. It's 25 GB uncompressed. My KenLM
> compiles of it failed in the past, but I'll try again. I expect it to be
> about 8 GB when that's done. Do you want it?
> >>>
> >>> matt
> >>>
> >>>
>  On Jul 15, 2016, at 3:50 PM, Mattmann, Chris A (3980) <
> chris.a.mattm...@jpl.nasa.gov> wrote:
> 
>  Hey Folks,
> 
>  Anyone have a Russian Language Model for Joshua? Lewis was working on
>  one, not sure if he has it but just broadening the question.
> 
>  Cheers,
>  Chris
> 
>  ++
>  Chris Mattmann, Ph.D.
>  Chief Architect
>  Instrument Software and Science Data Systems Section (398)
>  NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>  Office: 168-519, Mailstop: 168-527
>  Email: chris.a.mattm...@nasa.gov
>  WWW:  http://sunset.usc.edu/~mattmann/
>  ++
>  Director, Information Retrieval and Data Science Group (IRDS)
>  Adjunct Associate Professor, Computer Science Department
>  University of Southern California, Los Angeles, CA 90089 USA
>  WWW: http://irds.usc.edu/
>  ++
> >>>
> >
>

Re: Avoiding master failures with CI

[Tom Barber]

Don't ask about github pushing its like the antichrist! ;)

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 15 July 2016 at 23:31, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Hey Matt,
>
> Apache infra supports Travis CI - just file a ticket and they will
> set it up :)
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++
>
>
>
>
>
>
>
>
>
>
> On 7/15/16, 2:05 PM, "Matt Post"  wrote:
>
> >Question for Chris and/or Lewis:
> >
> >So, Kellen and I took a look at this today, and it looks like a good
> solution. The problem is that it integrates with projects hosted on Github
> that you have write access to. In order to make use of this, we'd need to
> rearrange the setup we have.
> >
> >Currently, we push to a repo at git.apache.org, and that is then pushed
> down to github.com/apache/incubator-joshua. This lets us use the Github
> repo for receiving things like pull requests and so on, but we do not have
> write access to it, so merges and so on have to be handled manually.
> >
> >To use Travis-ci, we'd need to re-enginneer this. Apache would need to
> give us write access to github.com/apache/incubator-joshua, or we'd need
> to use another official host for Joshua. We'd then use git.apache.org as
> the mirror, instead of the other way around.
> >
> >Is there any way that this could be done? I understand Apache's arguments
> about keeping discussions at home, since github may not last forever.
> However, it seems like we could do this if we use git.apache.org as the
> backup mirror, and continue to use JIRA for discussions and so on. In
> general, Github has a lot of tools that could help with development. It
> would be nice if we could make use of them while still checking off
> Apache's logging requirements.
> >
> >matt
> >
> >
> >
> >> On Jul 11, 2016, at 6:50 PM, kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
> >>
> >> Sorry should have provided the link to this page:
> https://travis-ci.org/ .
> >> If you scroll down a bit on that page there's a Pull Request flow
> section,
> >> it's the flow I'd be most in favour of.  There's also a decent (but
> rushed)
> >> demo here: https://www.youtube.com/watch?v=Uft5KBimzyk .  We actually
> don't
> >> need to do a lot of the work that he demos, i.e. no node or gulp
> >> configuration.  Our setup is close enough to default a default java
> project
> >> that we just have to tell it to build java 8 and then it runs maven
> >> properly.
> >>
> >> Using a CI server would have some aspects that are similar to the
> branching
> >> document you mention, and some benefits that are a bit orthogonal.
> Most of
> >> these benefits have to do with unit testing, which isn't covered in the
> doc.
> >>
> >> First the orthogonal benefits:  The main benefit we would get from
> using CI
> >> is that we guarantee code in our repo is never broken.  That is to say
> >> tests always pass and it always builds correctly.  CI servers are really
> >> useful to prevent problems where one developer may have everything
> working
> >> properly on his/her machine, but when they later realize it's not
> working
> >> on another devs machine.  A good example of this is the
> class-based-lm-test
> >> we pushed recently.  It works fine for me locally but it would fail for
> >> anyone without kenlm.so.  There are many other examples (javadoc errors,
> >> code style, etc) but what will happen in these cases is we'll see a big
> >> obvious 'The build has problems' message in the PR page on Github.  If
> the
> >> CI server runs of all of our code quality checks and finds that
> everything
> >> is good we'll get a big 'This PR is ready to merge' message.
> >>
> >> Now to the part that overlaps a bit with branching.  There are various
> >> branching strategies that we could adopt for the project.  The master /
> dev
> >> branch one is a possibility.  I'd suggest we try commit code strictly in
> >> PRs rather than pushing to git.  This would be the equivalent of feature
> >> branching from your link.  The reason I'd suggest th

Re: joshua - Build # 49 - Still Failing!

[Tom Barber]

That one did you are correct, but a few builds later it reverted back to
fine, so whatever it was was transient I guess.

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)

On 13 July 2016 at 13:41, kellen sunderland 
wrote:

> To me it reads as if it failed when trying to upload.
>
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'feabc96bb65f9ea4da42af561362d0f429ea7ded'; remote =
> '1252f3767e96442e19af8fb760ed07156f4a70cc' - RETRYING[WARNING] ***
> CHECKSUM FAILED - Checksum failed on download: local =
> 'feabc96bb65f9ea4da42af561362d0f429ea7ded'; remote =
> '1252f3767e96442e19af8fb760ed07156f4a70cc' - IGNORINGUploading:
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/joshua/joshua/6.0.6-SNAPSHOT/joshua-6.0.6-20160713.055028-28.jar
> 4/1118K
> 8/1118K
> 12/1118K
> 16/1118K
>
>
> 
>
>
> 1116/1118K
> 1118/1118K
> [INFO]
> [ERROR]
> BUILD ERROR[INFO]
> 
> [INFO] Error deploying artifact: Failed to transfer file:
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/joshua/joshua/6.0.6-SNAPSHOT/joshua-6.0.6-20160713.055028-28.jar
> .
> Return code is: 401
>
>
>
> -Kellen
>
>
> On Wed, Jul 13, 2016 at 2:24 PM, Tom Barber 
> wrote:
>
> >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/joshua/joshua/6.0.6-SNAPSHOT/
> >
> > Snapshots are uploading, its just missing the version you're looking for.
> >
> > On Wed, Jul 13, 2016 at 1:20 PM, kellen sunderland <
> > kellen.sunderl...@gmail.com> wrote:
> >
> > > Strange, https://builds.apache.org/job/joshua_master/78/ is passing.
> > > Looks
> > > like the analysis CI is getting an 401 when trying to upload a build
> > > artifact to here:
> > >
> > >
> > >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/joshua/joshua/6.0.6-SNAPSHOT/joshua-6.0.6-20160713.055028-28.jar
> > >
> > >
> > > Anyone know who has admin access on this CI server?  I think we might
> > need
> > > to double check the auth settings for this step.
> > >
> > > -Kellen
> > >
> > >
> > > --
> > >
> > > joshua - Build # 49 - Still Failing:
> > >
> > >
> > > Check console output at
> > https://analysis.apache.org/jenkins/job/joshua/49/
> > > to view the results.
> > >
> >
>

Re: joshua - Build # 49 - Still Failing!

[Tom Barber]

https://repository.apache.org/content/repositories/snapshots/org/apache/joshua/joshua/6.0.6-SNAPSHOT/

Snapshots are uploading, its just missing the version you're looking for.

On Wed, Jul 13, 2016 at 1:20 PM, kellen sunderland <
kellen.sunderl...@gmail.com> wrote:

> Strange, https://builds.apache.org/job/joshua_master/78/ is passing.
> Looks
> like the analysis CI is getting an 401 when trying to upload a build
> artifact to here:
>
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/joshua/joshua/6.0.6-SNAPSHOT/joshua-6.0.6-20160713.055028-28.jar
>
>
> Anyone know who has admin access on this CI server?  I think we might need
> to double check the auth settings for this step.
>
> -Kellen
>
>
> --
>
> joshua - Build # 49 - Still Failing:
>
>
> Check console output at https://analysis.apache.org/jenkins/job/joshua/49/
> to view the results.
>

Re: [DISCUSS] Joshua main Website redirect to wiki?

[Tom Barber]

we could just compile the website elsewhere and push the result to the asf
servers as I plan to do with a new oodt website. jekyll just compiles
static html after all.

Tom
On 9 Jul 2016 22:42, "Matt Post"  wrote:

> I mentioned it a while back and no one objected, so I did it.
>
> The issue is that the GitHub approach no longer worked because Apache does
> not employ Jekyll server side, so there was a major impediment to editing
> files.
>
> I'm open to other options but this is very convenient!
>
> matt (from my phone)
>
> > On Jul 9, 2016, at 5:31 PM, Henry Saputra 
> wrote:
> >
> > HI All,
> >
> > I just noticed that the main Joshua website [1] is now redirect to Wiki
> [2].
> >
> > Was there a discussion why we are doing it this way? I remember there
> used
> > to be HTML website for the main page.
> >
> > Thanks,
> >
> > Henry
> >
> > [1] https://joshua.incubator.apache.org
> > [2]
> >
> https://cwiki.apache.org/confluence/display/JOSHUA/Apache+Joshua+%28Incubating%29+Home
>
>

Re: [IMPORTANT] Roadmap for 6.1 Release

[Tom Barber]

Hey Matt

Over on  OODT our releases are few and far between, although that said,
I've been trying to increase the frequency even if they are very minor. The
main reason being, if someone commits some code, they don't want to wait 12
months for it to hit a stable release! So you might say yearly major
releases and patch releases at sporadic points inbetween to include patches
people have submitted, this also keeps drive by committers interested
because if they get some stuff into the codebase they then may commit more,
rather than say "well I submitted a fix for issue x ages ago and its got
notwhere".  Releases don't need to be set in stone, but I would try and
keep them ticking over.

Just my own 2 cents.

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)

On 23 June 2016 at 21:56, Matt Post  wrote:

> Hi Lewis,
>
> Sorry for taking some time to get back to you. I think the roadmap looks
> great. One thing, though, is that the Amazon folks and I have discussed
> making a number of backwards-incompatible changes in an effort to modernize
> some pieces of the code. This would have to do with things like the config
> file format, a totally new pipeline based on duct tape, and some other
> ideas. We think those changes would be suitable for a 7.0 release (major
> version number change signals backwards incompatibility).
>
> I think we've been doing some good work on improving Joshua, but at the
> same time, I think the release cycle is still little too accelerated for
> me. I would like to push back to semi- yearly or even yearly releases, with
> bug fixes in between. However, I'm also curious how this might affect our
> ability to move out of incubation. Do you have any thoughts on this?
>
> The major downsides to releases are documentation. It's just hard to find
> the time to do.
>
> My own thoughts for what I'd like to do:
>
> - Maybe a 6.1 release (soon, to get it out of the way? or otherwise this
> fall?), where we formalize the Apache move and maybe formalize the release
> of a handful of language packs, without a lot of other changes
>
> - Write a linux.com article advertising this, hopefully attracting some
> attention
>
> - Shoot for a 7.0 release with many of the changes we've discussed (some
> offline). If we get a good showing at MT Marathon in Prague this year, that
> could be a good time to get all of that in order.
>
> - Start getting to work on a version of Joshua that swaps out the core
> decoder for a neural approach
>
> matt
>
>
>
>
> > On Jun 23, 2016, at 4:13 PM, Tom Barber  wrote:
> >
> > I would volunteer some cycles for multi model support in the server and
> an
> > improved rest interface and basic UI for end user interaction if you
> fancy
> > it.
> >
> > --
> >
> > Director Meteorite.bi - Saiku Analytics Founder
> > Tel: +44(0)5603641316
> >
> > (Thanks to the Saiku community we reached our Kickstart
> > <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > goal, but you can always help by sponsoring the project
> > <http://www.meteorite.bi/products/saiku/sponsorship>)
> >
> > On 23 June 2016 at 21:10, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com>
> > wrote:
> >
> >> Hi Folks,
> >> Anyone have any comments on this?
> >> Seeing that the Maven multimodule project seems to be taking flight, it
> >> would be nice to see where the roadmap is going?
> >> Any comments would be great. Also, I'm kinda lost as to what is
> happening
> >> with Jira but it looks like it is not really being used for much.
> >> Thanks
> >>
> >> On Mon, Jun 20, 2016 at 11:34 AM, Lewis John Mcgibbney <
> >> lewis.mcgibb...@gmail.com> wrote:
> >>
> >>> Hi Folks,
> >>> I've just smartened up Jira a bit with our Roadmap being defined as
> >> follows
> >>>
> >>>
> >>>
> >>
> https://issues.apache.org/jira/browse/joshua/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> >>>
> >>> Right now there are only 14/14 issues as RESOLVED for 6.1. This is
> false
> >>> as I know that many more issues have been addressed however I don't
> think
> >>> that Jira tickets

Re: [IMPORTANT] Roadmap for 6.1 Release

[Tom Barber]

I would volunteer some cycles for multi model support in the server and an
improved rest interface and basic UI for end user interaction if you fancy
it.

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 23 June 2016 at 21:10, Lewis John Mcgibbney 
wrote:

> Hi Folks,
> Anyone have any comments on this?
> Seeing that the Maven multimodule project seems to be taking flight, it
> would be nice to see where the roadmap is going?
> Any comments would be great. Also, I'm kinda lost as to what is happening
> with Jira but it looks like it is not really being used for much.
> Thanks
>
> On Mon, Jun 20, 2016 at 11:34 AM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
> > Hi Folks,
> > I've just smartened up Jira a bit with our Roadmap being defined as
> follows
> >
> >
> >
> https://issues.apache.org/jira/browse/joshua/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> >
> > Right now there are only 14/14 issues as RESOLVED for 6.1. This is false
> > as I know that many more issues have been addressed however I don't think
> > that Jira tickets have been created for all changes to the source code.
> > Maybe moving forward we could open Jira issues and link them to the
> Github
> > tickets via commit messages?
> >
> > Additionally, everything that was currently UNRESOLVED has merely been
> > pushed to 6.2. If this is not what is required then please reassign the
> fix
> > version for any ticket(s) to 6.1 and we can fix.
> >
> > Finally, are there any mitigating factor which would prevent a 6.1
> release
> > candidate being prepared right now?
> > Thanks
> > Lewis
> >
> > --
> > *Lewis*
> >
>
>
>
> --
> *Lewis*
>

Re: Wiki access

[Tom Barber]

Yeah that was the question thanks Matt. Lewis hooked me up last night, so I
started documenting the docker and juju deployment stuff:
https://cwiki.apache.org/confluence/display/JOSHUA/Deployment

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)

On 26 May 2016 at 20:34, Matt Post  wrote:

> Hi Tom — This is a dumb question, but where is the Joshua wiki? You're not
> talking about the confluence page, are you? I see you have access there.
>
>
> https://cwiki.apache.org/confluence/display/JOSHUA/Joshua+%28Incubating%29+Home
>
> matt
>
>
>
>
> > On May 25, 2016, at 5:20 PM, Tom Barber  wrote:
> >
> > Hello
> >
> > Can someone give me(bugg_tb) access to the Joshua wiki please.
> >
> > Ta
> >
> > Tom
> > --
> >
> > Director Meteorite.bi - Saiku Analytics Founder
> > Tel: +44(0)5603641316
> >
> > (Thanks to the Saiku community we reached our Kickstart
> > <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > goal, but you can always help by sponsoring the project
> > <http://www.meteorite.bi/products/saiku/sponsorship>)
>
>

Re: too many emails

[Tom Barber]

FWIW I just have a Gmail filter setup to archive them
On 26 May 2016 05:45, "Lewis John Mcgibbney" 
wrote:

> Hi Matt,
>
> As Henry said. Either we get them going to a different list or else you
> subscribe to dev-dig...@joshua.incubator.apache.org (subscribe through
> dev-digest-subscr...@joshua.incubator.apache.org)?
> Which do you prefer?
> Quick reasoning as to why Github convo is shadowed on the Apache lists. If
> Github ever goes away, then we loose all of the conversation. We archive it
> @Apache so we cover our communities.
> Thanks
>
>
> On Wed, May 25, 2016 at 2:11 PM, <
> dev-digest-h...@joshua.incubator.apache.org> wrote:
>
> >
> > From: Matt Post 
> > To: dev@joshua.incubator.apache.org
> > Cc:
> > Date: Wed, 25 May 2016 15:48:24 -0400
> > Subject: too many emails
> > Does someone know how to turn off the mailing of all github comments to
> > dev?
> >
> > The way I see it, we all have to be on dev, so it should be for people,
> > not robots. I am getting every comment about three times.
> >
> > I would just do it but I don't know how.
> >
> >
>

Wiki access

[Tom Barber]

Hello

Can someone give me(bugg_tb) access to the Joshua wiki please.

Ta

Tom
--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

Re: Joshua Deployment with Juju

[Tom Barber]

Thanks Lewis

I got it done today, I'll tidy up the code and commit it somewhere later.

I can now do

juju bootstrap
juju deploy cs:openjdk
juju deploy --repository=/home/bugg/charms local:trusty/joshua-full
joshua-full
juju deploy  cs:bundle/apache-processing-mapreduce-0
juju add-relation openjdk joshua-full
juju add-relation plugin joshua-full
juju ssh joshua-full/0

and then step through the basic pipeline tutorial without it
breaking/failing as far as I can tell.

So its pretty cool!

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)

On 20 May 2016 at 17:44, Lewis John Mcgibbney 
wrote:

> Hi Tom,
> Dynamite. Really cool to see this. Once the remainder of the plumbing is in
> place I am sure we can get a proper screencast out and host it on the
> website. It REALLY simplifies things that is for sure.
>
> On Fri, May 20, 2016 at 2:13 AM, <
> dev-digest-h...@joshua.incubator.apache.org> wrote:
>
> >
> > From: Tom Barber 
> > To: dev@joshua.incubator.apache.org
> > Cc:
> > Date: Thu, 19 May 2016 23:31:01 +0100
> > Subject: Joshua Deployment with Juju
> > Hi guys
> >
> > I figured this was worth sharing as its what I was working on whilst sat
> > with Lewis and Kellen at ApacheCon.
> >
> > I'm looking at creating a Juju deployment for Joshua which people can
> > instantly attach to Hadoop to train models, but instead of using Hadoop
> on
> > a standalone mode, I want to be able to simply deploy the same code in
> the
> > cloud and scale up my training if required (I'm not a translation guy so
> I
> > don't know how that would work in real life performance, but to the sys
> > admin in me, it makes sense).
> >
> > Anyway, I figured I'd put together a sped up and cut up demo that shows
> the
> > deployment in AWS:
> >
> > https://www.youtube.com/watch?v=dnOQEVSMB-4&feature=youtu.be
> >
> > This deploys Joshua 6.0.5 on its own compute node, and also a multi node
> > hadoop cluster (which you can scale with 1 command), and associates the
> > two. I need to finialise the hadoop client plumbing but should be done
> > early next week.
> >
> > Anyway, if there is an appitite for this alongside whatever docker stuff
> > people are working on, I'll happily commit the charms( the code that runs
> > it) back to the Joshua git repo and we can maintain it in a more
> "official"
> > manner.
> >
> > Tom
> > --
> >
> >
>

Re: Joshua Deployment with Juju

[Tom Barber]

Oh also, with b) both me and Lewis were saying the support for multiple
language packs is pretty key.

So a user could

curl http://localhost/en/es/My%20English$20Phrase

but then on the same box do:

curl http://localhost/fr/en/Mon%20expression%20française
<http://localhost/fr/en/Mon%20expression%20fran%C3%A7aise>

That would be very useful!

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)

On 20 May 2016 at 10:23, Tom Barber  wrote:

> The idea is two fold really.
>
> a) From the docs:
>
> "If you have a Hadoop installation, make sure you’ve set $HADOOP to point
> to it. For example, if the hadoop command is in /usr/bin, you should type
>
> export HADOOP=/usr
> Joshua will find the binary and use it to submit to your hadoop cluster.
> If you don’t have one, just make sure that HADOOP is unset, and Joshua will
> roll one out for you and run it in standalone mode."
>
> So Joe User wants to train a model but doesn't want to sink their laptop
> in doing so, but similarly doesn't know how to deploy or doesn't want to go
> through the effort of deploying a multinode hadoop cluster. My
> understanding, having gone through the docs and having a chat with Lewis,
> is that Thrax will pass the job off to hadoop. So a setup like the video
> depicts would remove the need for Joshua rolling out a standalone Hadoop
> setup. Of course, I don't know how Thrax works under the hood, if it
> doesn't leverage a cluster, this is clearly not required, but as the docs
> mention the word cluster, I worked under the assumption that it did.
>
> b) If we ignore all you language geeks, consumers should be able to use
> Joshua in a variety of situations. I have the runtime version setup in
> another charm that allows users to spin it up, define a language pack to
> install, configure it and they can then chuck translations at it, again, in
> about 3 lines of code to the end user. This is like Google Translate in a
> box, but without going through the compilation rigmarole, again, something
> we should be aiming for with end users. That said, after discussing use
> cases with Lewis and seeing the talk of API's and stuff, one thing I will
> be working on in the coming months, is a web-ui for Joshua so when its spun
> up, users can just dump stuff into a box, or use CURL (I know there is some
> support there already), similarly, being able to dump Joshua into a Hadoop
> cluster for processing of data should be something we can do (we may be
> able to already, I've not looked, although the C stuff makes me wonder).
> Also being able to distribute the Joshua runtime over your cluster would be
> cool as well.
>
> Tom
>
> --
>
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
> goal, but you can always help by sponsoring the project
> <http://www.meteorite.bi/products/saiku/sponsorship>)
>
> On 20 May 2016 at 10:13, kellen sunderland 
> wrote:
>
>> Hey Tom, nice work.  I'll take a closer look soon but just had a question
>> about the use case.  Would the idea be that you could use Joshua to
>> translate text in a map during a hadoop job?
>>
>> -Kellen
>>
>> On Fri, May 20, 2016 at 12:31 AM, Tom Barber 
>> wrote:
>>
>> > Hi guys
>> >
>> > I figured this was worth sharing as its what I was working on whilst sat
>> > with Lewis and Kellen at ApacheCon.
>> >
>> > I'm looking at creating a Juju deployment for Joshua which people can
>> > instantly attach to Hadoop to train models, but instead of using Hadoop
>> on
>> > a standalone mode, I want to be able to simply deploy the same code in
>> the
>> > cloud and scale up my training if required (I'm not a translation guy
>> so I
>> > don't know how that would work in real life performance, but to the sys
>> > admin in me, it makes sense).
>> >
>> > Anyway, I figured I'd put together a sped up and cut up demo that shows
>> the
>> > deployment in AWS:
>> >
>> > https://www.youtube.com/watch?v=dnOQEVSMB-4&feature=youtu.be
>> >
>> > This deploys Joshua 6.0.5 on its own compute node, and also a multi node
>> > hadoop clus

Re: Joshua Deployment with Juju

[Tom Barber]

The idea is two fold really.

a) From the docs:

"If you have a Hadoop installation, make sure you’ve set $HADOOP to point
to it. For example, if the hadoop command is in /usr/bin, you should type

export HADOOP=/usr
Joshua will find the binary and use it to submit to your hadoop cluster. If
you don’t have one, just make sure that HADOOP is unset, and Joshua will
roll one out for you and run it in standalone mode."

So Joe User wants to train a model but doesn't want to sink their laptop in
doing so, but similarly doesn't know how to deploy or doesn't want to go
through the effort of deploying a multinode hadoop cluster. My
understanding, having gone through the docs and having a chat with Lewis,
is that Thrax will pass the job off to hadoop. So a setup like the video
depicts would remove the need for Joshua rolling out a standalone Hadoop
setup. Of course, I don't know how Thrax works under the hood, if it
doesn't leverage a cluster, this is clearly not required, but as the docs
mention the word cluster, I worked under the assumption that it did.

b) If we ignore all you language geeks, consumers should be able to use
Joshua in a variety of situations. I have the runtime version setup in
another charm that allows users to spin it up, define a language pack to
install, configure it and they can then chuck translations at it, again, in
about 3 lines of code to the end user. This is like Google Translate in a
box, but without going through the compilation rigmarole, again, something
we should be aiming for with end users. That said, after discussing use
cases with Lewis and seeing the talk of API's and stuff, one thing I will
be working on in the coming months, is a web-ui for Joshua so when its spun
up, users can just dump stuff into a box, or use CURL (I know there is some
support there already), similarly, being able to dump Joshua into a Hadoop
cluster for processing of data should be something we can do (we may be
able to already, I've not looked, although the C stuff makes me wonder).
Also being able to distribute the Joshua runtime over your cluster would be
cool as well.

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)

On 20 May 2016 at 10:13, kellen sunderland 
wrote:

> Hey Tom, nice work.  I'll take a closer look soon but just had a question
> about the use case.  Would the idea be that you could use Joshua to
> translate text in a map during a hadoop job?
>
> -Kellen
>
> On Fri, May 20, 2016 at 12:31 AM, Tom Barber 
> wrote:
>
> > Hi guys
> >
> > I figured this was worth sharing as its what I was working on whilst sat
> > with Lewis and Kellen at ApacheCon.
> >
> > I'm looking at creating a Juju deployment for Joshua which people can
> > instantly attach to Hadoop to train models, but instead of using Hadoop
> on
> > a standalone mode, I want to be able to simply deploy the same code in
> the
> > cloud and scale up my training if required (I'm not a translation guy so
> I
> > don't know how that would work in real life performance, but to the sys
> > admin in me, it makes sense).
> >
> > Anyway, I figured I'd put together a sped up and cut up demo that shows
> the
> > deployment in AWS:
> >
> > https://www.youtube.com/watch?v=dnOQEVSMB-4&feature=youtu.be
> >
> > This deploys Joshua 6.0.5 on its own compute node, and also a multi node
> > hadoop cluster (which you can scale with 1 command), and associates the
> > two. I need to finialise the hadoop client plumbing but should be done
> > early next week.
> >
> > Anyway, if there is an appitite for this alongside whatever docker stuff
> > people are working on, I'll happily commit the charms( the code that runs
> > it) back to the Joshua git repo and we can maintain it in a more
> "official"
> > manner.
> >
> > Tom
> > --
> >
> > Director Meteorite.bi - Saiku Analytics Founder
> > Tel: +44(0)5603641316
> >
> > (Thanks to the Saiku community we reached our Kickstart
> > <
> >
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> > >
> > goal, but you can always help by sponsoring the project
> > <http://www.meteorite.bi/products/saiku/sponsorship>)
> >
>

Joshua Deployment with Juju

[Tom Barber]

Hi guys

I figured this was worth sharing as its what I was working on whilst sat
with Lewis and Kellen at ApacheCon.

I'm looking at creating a Juju deployment for Joshua which people can
instantly attach to Hadoop to train models, but instead of using Hadoop on
a standalone mode, I want to be able to simply deploy the same code in the
cloud and scale up my training if required (I'm not a translation guy so I
don't know how that would work in real life performance, but to the sys
admin in me, it makes sense).

Anyway, I figured I'd put together a sped up and cut up demo that shows the
deployment in AWS:

https://www.youtube.com/watch?v=dnOQEVSMB-4&feature=youtu.be

This deploys Joshua 6.0.5 on its own compute node, and also a multi node
hadoop cluster (which you can scale with 1 command), and associates the
two. I need to finialise the hadoop client plumbing but should be done
early next week.

Anyway, if there is an appitite for this alongside whatever docker stuff
people are working on, I'll happily commit the charms( the code that runs
it) back to the Joshua git repo and we can maintain it in a more "official"
manner.

Tom
--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

[jira] [Closed] (JOSHUA-267) Java seems to swallow C exceptions

[Tom Barber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JOSHUA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom Barber closed JOSHUA-267.
-
Resolution: Invalid

> Java seems to swallow C exceptions
> --
>
> Key: JOSHUA-267
> URL: https://issues.apache.org/jira/browse/JOSHUA-267
> Project: Joshua
>  Issue Type: Bug
>    Reporter: Tom Barber
>Priority: Minor
>
> I compiled joshua on Ubuntu and copied it to another box of the same type, 
> but missing various C bits that were required at build time, but Joshua 
> doesn't run and tells me:
> Input 0:  berkeley works fine , but the pipeline fails in next steps 
> Input 0: Collecting options took 0.000 seconds
> Input 0: FATAL UNCAUGHT EXCEPTION: null
> java.lang.NullPointerException
> at joshua.decoder.phrase.Candidate.score(Candidate.java:214)
> at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:136)
> at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:19)
> at java.util.HashMap.compareComparables(HashMap.java:371)
> at java.util.HashMap$TreeNode.treeify(HashMap.java:1920)
> at java.util.HashMap.treeifyBin(HashMap.java:771)
> at java.util.HashMap.putVal(HashMap.java:643)
> at java.util.HashMap.put(HashMap.java:611)
> at java.util.HashSet.add(HashSet.java:219)
> at joshua.decoder.phrase.Stack.addCandidate(Stack.java:125)
> at joshua.decoder.phrase.Stacks.search(Stacks.java:166)
> at joshua.decoder.DecoderThread.translate(DecoderThread.java:113)
> at joshua.decoder.Decoder$DecoderThreadRunner.run(Decoder.java:218)
> Looking at the code its where it passes off to a decoder, which if it doesn't 
> appear, must surely throw some error that we don't see?



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

[jira] [Commented] (JOSHUA-267) Java seems to swallow C exceptions

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-267:
---

Okay so turns out, beginners mistake where I'm passing it english expecting 
spanish not spanish expecting english!

That said, I'm pretty sure it shouldn't throw an NPE just because it thinks I'm 
a moron ;)

> Java seems to swallow C exceptions
> --
>
> Key: JOSHUA-267
> URL: https://issues.apache.org/jira/browse/JOSHUA-267
> Project: Joshua
>      Issue Type: Bug
>Reporter: Tom Barber
>Priority: Minor
>
> I compiled joshua on Ubuntu and copied it to another box of the same type, 
> but missing various C bits that were required at build time, but Joshua 
> doesn't run and tells me:
> Input 0:  berkeley works fine , but the pipeline fails in next steps 
> Input 0: Collecting options took 0.000 seconds
> Input 0: FATAL UNCAUGHT EXCEPTION: null
> java.lang.NullPointerException
> at joshua.decoder.phrase.Candidate.score(Candidate.java:214)
> at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:136)
> at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:19)
> at java.util.HashMap.compareComparables(HashMap.java:371)
> at java.util.HashMap$TreeNode.treeify(HashMap.java:1920)
> at java.util.HashMap.treeifyBin(HashMap.java:771)
> at java.util.HashMap.putVal(HashMap.java:643)
> at java.util.HashMap.put(HashMap.java:611)
> at java.util.HashSet.add(HashSet.java:219)
> at joshua.decoder.phrase.Stack.addCandidate(Stack.java:125)
> at joshua.decoder.phrase.Stacks.search(Stacks.java:166)
> at joshua.decoder.DecoderThread.translate(DecoderThread.java:113)
> at joshua.decoder.Decoder$DecoderThreadRunner.run(Decoder.java:218)
> Looking at the code its where it passes off to a decoder, which if it doesn't 
> appear, must surely throw some error that we don't see?



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

[jira] [Commented] (JOSHUA-267) Java seems to swallow C exceptions

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-267:
---

Sure, I'm just trying to stand something up to wrap my head around things a bit 
better, but also build a deployment strategy for it.

I made some changes from this to make it run on Ubuntu but you can do exactly 
the same this way using all the defaults on Centos7:

Grab 6.0.5 and extract, build ignoring giza and syaml, but ensuring that kenlm 
builds.

Grab the en-es phrase pack from 
http://cs.jhu.edu/~post/language-packs/language-pack-es-en-phrase-2015-03-06.tgz

Run it using run-joshua-server.sh

Create a file called input.txt and run the 

cat input.txt | ./prepare.sh | nc localhost 5674

command.

testing testing 123 doesn't crash but anything more complex seems to.

Having cobbled together bits and pieces from different pages/test suites etc, 
I'm sure there's probably an element of beginners misunderstanding, mistakes, 
so if I'm doing something wrong/stupid, thats easily corrected, but also from a 
usability perspective throwing an NPE isn't great either. This stack I see from 
the mailing list and also on the google group, so its reasonably recurring as 
well it seems?

Tom

> Java seems to swallow C exceptions
> --
>
> Key: JOSHUA-267
> URL: https://issues.apache.org/jira/browse/JOSHUA-267
> Project: Joshua
>  Issue Type: Bug
>Reporter: Tom Barber
>Priority: Minor
>
> I compiled joshua on Ubuntu and copied it to another box of the same type, 
> but missing various C bits that were required at build time, but Joshua 
> doesn't run and tells me:
> Input 0:  berkeley works fine , but the pipeline fails in next steps 
> Input 0: Collecting options took 0.000 seconds
> Input 0: FATAL UNCAUGHT EXCEPTION: null
> java.lang.NullPointerException
> at joshua.decoder.phrase.Candidate.score(Candidate.java:214)
> at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:136)
> at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:19)
> at java.util.HashMap.compareComparables(HashMap.java:371)
> at java.util.HashMap$TreeNode.treeify(HashMap.java:1920)
> at java.util.HashMap.treeifyBin(HashMap.java:771)
> at java.util.HashMap.putVal(HashMap.java:643)
> at java.util.HashMap.put(HashMap.java:611)
> at java.util.HashSet.add(HashSet.java:219)
> at joshua.decoder.phrase.Stack.addCandidate(Stack.java:125)
> at joshua.decoder.phrase.Stacks.search(Stacks.java:166)
> at joshua.decoder.DecoderThread.translate(DecoderThread.java:113)
> at joshua.decoder.Decoder$DecoderThreadRunner.run(Decoder.java:218)
> Looking at the code its where it passes off to a decoder, which if it doesn't 
> appear, must surely throw some error that we don't see?



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

[jira] [Commented] (JOSHUA-267) Java seems to swallow C exceptions

[Tom Barber (JIRA)]

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

Tom Barber commented on JOSHUA-267:
---

Okay well the above still counts, we're clearly swallowing something. For the 
trainer, I don't know enough about joshua but I'm pretty sure if I input 

testing testing 123

if passes but if I run 

My Complex sentence that contains lots of words 

with

cat input.txt | ./prepare.sh | nc localhost 5675

An NPE probably isn't supposed to be the output :)

> Java seems to swallow C exceptions
> --
>
> Key: JOSHUA-267
> URL: https://issues.apache.org/jira/browse/JOSHUA-267
> Project: Joshua
>      Issue Type: Bug
>Reporter: Tom Barber
>Priority: Minor
>
> I compiled joshua on Ubuntu and copied it to another box of the same type, 
> but missing various C bits that were required at build time, but Joshua 
> doesn't run and tells me:
> Input 0:  berkeley works fine , but the pipeline fails in next steps 
> Input 0: Collecting options took 0.000 seconds
> Input 0: FATAL UNCAUGHT EXCEPTION: null
> java.lang.NullPointerException
> at joshua.decoder.phrase.Candidate.score(Candidate.java:214)
> at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:136)
> at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:19)
> at java.util.HashMap.compareComparables(HashMap.java:371)
> at java.util.HashMap$TreeNode.treeify(HashMap.java:1920)
> at java.util.HashMap.treeifyBin(HashMap.java:771)
> at java.util.HashMap.putVal(HashMap.java:643)
> at java.util.HashMap.put(HashMap.java:611)
> at java.util.HashSet.add(HashSet.java:219)
> at joshua.decoder.phrase.Stack.addCandidate(Stack.java:125)
> at joshua.decoder.phrase.Stacks.search(Stacks.java:166)
> at joshua.decoder.DecoderThread.translate(DecoderThread.java:113)
> at joshua.decoder.Decoder$DecoderThreadRunner.run(Decoder.java:218)
> Looking at the code its where it passes off to a decoder, which if it doesn't 
> appear, must surely throw some error that we don't see?



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

[jira] [Created] (JOSHUA-267) Java seems to swallow C exceptions

[Tom Barber (JIRA)]

Tom Barber created JOSHUA-267:
-

 Summary: Java seems to swallow C exceptions
 Key: JOSHUA-267
 URL: https://issues.apache.org/jira/browse/JOSHUA-267
 Project: Joshua
  Issue Type: Bug
Reporter: Tom Barber
Priority: Minor


I compiled joshua on Ubuntu and copied it to another box of the same type, but 
missing various C bits that were required at build time, but Joshua doesn't run 
and tells me:


Input 0:  berkeley works fine , but the pipeline fails in next steps 
Input 0: Collecting options took 0.000 seconds
Input 0: FATAL UNCAUGHT EXCEPTION: null
java.lang.NullPointerException
at joshua.decoder.phrase.Candidate.score(Candidate.java:214)
at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:136)
at joshua.decoder.phrase.Candidate.compareTo(Candidate.java:19)
at java.util.HashMap.compareComparables(HashMap.java:371)
at java.util.HashMap$TreeNode.treeify(HashMap.java:1920)
at java.util.HashMap.treeifyBin(HashMap.java:771)
at java.util.HashMap.putVal(HashMap.java:643)
at java.util.HashMap.put(HashMap.java:611)
at java.util.HashSet.add(HashSet.java:219)
at joshua.decoder.phrase.Stack.addCandidate(Stack.java:125)
at joshua.decoder.phrase.Stacks.search(Stacks.java:166)
at joshua.decoder.DecoderThread.translate(DecoderThread.java:113)
at joshua.decoder.Decoder$DecoderThreadRunner.run(Decoder.java:218)


Looking at the code its where it passes off to a decoder, which if it doesn't 
appear, must surely throw some error that we don't see?



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

Language Pack size

[Tom Barber]

Out of curiosity more than anything else I tested XZ compression on a model
instead of Gzip, it takes the Spain pack down from 1.9GB to 1.5GB, not the
most ever, but obviously does mean 400MB+ less in remote storage and data
going over the wire.

Worth considering I guess.

Tom
--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

Re: ApacheCon Meetup

[Tom Barber]

I went for a wander earlier and couldn't find anyone :)

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 13 May 2016 at 20:33, Henry Saputra  wrote:

> Looks like this is not happening?
>
> We could probably make it happen as Google hangout for next time.
>
> - Henry
>
> On Fri, May 13, 2016 at 11:34 AM, Henri Yandell  wrote:
>
> > We are? :)
> >
> > Work meetings came up as urgent for this morning, so only just noticed
> > this. :(
> >
> > Sorry,
> >
> > Hen
> >
> >
> > On Thu, May 12, 2016 at 12:32 PM, Lewis John Mcgibbney <
> > lewis.mcgibb...@gmail.com> wrote:
> >
> > > Hi Folks,
> > > Kellen, Henri and I are going to get together tomorrow 13th around
> > > lunchtime PST to talk everything Joshua.
> > > Would be great to have others online via GChat if possible.
> > > Let's say around 11am PST for the time being.
> > > See you then folks.
> > > Thanks
> > > Lewis
> > >
> > >
> > > --
> > > *Lewis*
> > >
> >
>

Re: ApacheCon Meetup

[Tom Barber]

I'd also like to discuss deployment for users (yeah I'm the boring guy).

I saw some docker stuff in the emails earlier, I've also got the majority
of a Juju charm ready, so users can do:
juju deploy joshua-decoder
juju action joshua-decoder/0 add-language-pack es-en-phrase

for example and they'll have a kickstarted server ready for them to use.
But clearly there must be a bunch more stuff I can do to enhance this for
the people wanting to train it etc.

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 12 May 2016 at 22:30, kellen sunderland 
wrote:

> Thanks for organizing Lewis,
>
> Here's some topics for discussion I've been noting while working with
> Joshua.  None of these are high priority issues for me, but if we are all
> in agreement on them it might make sense to log them.
>
> Boring code convention stuff: Logging with log4j, throw Runtime Exceptions
> instead of Typed, remove all system exits (replace with RuntimeExceptions),
> refactor some large files.
>
> Testing: Integrate existing unit tests, provide some good test examples so
> others can begin adding more tests.
>
> Configuration: We also touched on IoC, CLI args, and configuration changes
> that are possible.
>
> OO stuff: Joshua is pretty good here, but I would personally prefer more
> granular interfaces.  I wouldn't advocate radical changes, but maybe a
> little refactoring might make sense to better align with the interface
> segregation principle.
> https://en.wikipedia.org/wiki/Interface_segregation_principle
>
> JNI reliance:  We've found KenLM works really well with Joshua, but there
> is one issue with using it.  It requires many JNI calls during decoding and
> these calls impact GC performance.  In fact when a JNI call happens the GC
> throws out any work it may have done and quits until the JNI call
> completes.  The GC will then resume and start marking objects for
> collection from scratch.  This is not ideal especially for programs with
> large heaps (Joshua / Spark).  There's a couple ways we could mitigate this
> and I think they'd all speed up Joshua quite a lot.
>
> High level roadmap topics:
>
> *  Distributed Decoding is something I'll likely continue working on.
> Theres some obvious things we can do given usage patterns of translation
> engines that can help us out here (I think).
> *  Providing a way to optimize Joshua for low-latency, low-throughput calls
> could be interesting for those with near real-time use cases.  Providing a
> way to optimize for high-latency, high-throughput could be interesting for
> async/batch use cases.
> *  The machine learning optimization algorithms could be cleaned up a bit
> (MERT/MIRA).
> *  The Vocabulary could probably be replaced with a simpler implementation
> (without sacrificing performance).
>
> -Kellen
>
>
>
> On Thu, May 12, 2016 at 12:32 PM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
> > Hi Folks,
> > Kellen, Henri and I are going to get together tomorrow 13th around
> > lunchtime PST to talk everything Joshua.
> > Would be great to have others online via GChat if possible.
> > Let's say around 11am PST for the time being.
> > See you then folks.
> > Thanks
> > Lewis
> >
> >
> > --
> > *Lewis*
> >
>

Re: Using Jira for Issues

[Tom Barber]

Hi guys

Sorry I've not been of any use so far, day job(s) getting in the way and
ApacheCon. Once I'm back from Vancouver I can certainly help out with
licensing, docs and Jira org stuff.

Keep it up Lewis I've seen all the commits streaming past!

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 29 April 2016 at 14:47, Lewis John Mcgibbney 
wrote:

> Hi Matt,
> Dynamite. Thanks for taking notes action in the site. As you've seen I've
> been hammering through the licensing issues and will continue to do so as I
> look at more code in different languages.
> I'll scope site throughout the next week or so.
> Thanks
>
> On Friday, April 29, 2016, Matt Post  wrote:
>
> > Lewis, this sounds good to me.
> >
> > I'm in the process of moving the (hideous) Joshua web page over to
> > Confluence, and created a Developer page, where I added this to the
> > documentation.
> >
> > https://cwiki.apache.org/confluence/display/JOSHUA/Development
> >
> > Can you look this over and improve it (e.g., with links on the
> appropriate
> > instruction points?)
> >
> > matt
> >
> >
> >
> > > On Apr 29, 2016, at 7:13 AM, Lewis John Mcgibbney <
> > lewis.mcgibb...@gmail.com > wrote:
> > >
> > > Hi Folks,
> > > One of the things about our Jira instance, is that it is hosted by and
> at
> > > the ASF. Therefore all correspondence is always available to the ASF.
> > > If Github were ever to vanish, we would essentially loose all of the
> > > correspondence for all of the tickets issues created over there.
> > > Typically what I, and every other Apache project I am aware of does, is
> > to
> > > first open a ticket in Jira, then just title your pull request commit
> > > message after the Jira ticket.
> > > This way we also have comprehensive release reports, assignees, road
> > maps,
> > > etc etc etc.
> > > I would like to suggest that we start using Jira in this manner as
> > recently
> > > I've not really seen any tickets go in there.
> > > What do you think about this?
> > > Lewis
> > >
> > >
> > > --
> > > *Lewis*
> >
> >
>
> --
> *Lewis*
>

Re: Apologies for the late replies

[Tom Barber]

Hey Kellen

Good to have you onboard!

The moderated emails get sent to most of us and I've not seen any land, so
I have no idea where they are going unless the ASF decides to drop them on
the edge. Are you subscribed to any other ASF mailing lists with the
amazon.de address?

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 15 April 2016 at 12:01, kellen sunderland 
wrote:

> Looks like my emails from amazon.de are getting filtered (are they stuck
> in
> a moderation queue?), so sorry for the late replies everyone.
>
> First of all thanks to everyone for inviting me as a committer.  Great to
> be working on an interesting project.  Some quick background about me: I've
> been a developer for 10 years, currently working at Amazon full time on a
> machine translation project involving Joshua.  I'm originally from Western
> Canada (now living in Berlin) so I can help point people to good pubs for
> ApacheCon.
>
> -Kellen
>

Re: http://joshua.incubator.apache.org/

[Tom Barber]

Hi Igor

I believe in our case we got infra to setup a gitsubpub config for us.

Tom
On 14 Apr 2016 00:06, "Igor Katkov"  wrote:

> Hi fellow Apache incubation project devs,
>
> My name is Igor Katkov, dev@Omid
> http://incubator.apache.org/projects/omid.html
>
> I'd really appreciate if someone who put up
> http://joshua.incubator.apache.org or knows how to do it, advise me.
>
> *Question*: how to set-up the website? I can generate static html no
> problem, but where/how do I publish them?
>

Re: Cleaning up Jira

[Tom Barber]

For Jira can't we do a bulk change on all open/in progress task that's
fixed version is either No Version or Release Versions?

Or did I misunderstand?

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 4 April 2016 at 22:23, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> +1 I’ll take a look tonight
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++
>
>
>
>
>
>
>
>
>
>
> On 4/4/16, 5:17 PM, "Lewis John Mcgibbney" 
> wrote:
>
> >Hi Folks,
> >OK so Jira [0] is a bit of a mess with the following unresolved issue
> stats
> >for following versions
> >
> >5.0 23 6.0 7 6.1 2 Unscheduled 214
> >Basically, we need to close off all of the issues as resolved apart from
> >the ones currently assigned to 6.1 as unresolved.
> >
> >We then need to locate all of the issues mentioned at [1] and assign them
> >against 6.1
> >
> >This is going to be a bit of a PITA, but once it is done we can begin
> agree
> >upon a release cycle and development roadmap in the build up to ApacheCon
> >meetup.
> >Ta
> >
> >[0] https://issues.apache.org/jira/browse/JOSHUA
> >[1] https://github.com/joshua-decoder/joshua/issues
> >
> >--
> >*Lewis*
>

Joshua development strategy

[Tom Barber]

Moved over to dev@ with useful information still in place.

Yeah I don't think the ASF is onboard yet with git pull type workflows. Its
still mostly peer review through the reviewboard and pull request reviews.
I'm not saying we do away with them either, but I do think the ASF doesn't
make the best use of git with the forking strategy for established
committers.

Clearly if you don't have commit rights to the project it would need to be
a PR/reviewboard submission anyway, but from an entirely personal
perspective I much prefer people developing on the same repository instead
of github forks as it makes for much easier collaboration and keeping the
code in sync. Of course you can accept pull requests onto feature branches
etc as well.

As I said, it doesn't have to be set in stone either, as committers we just
make sure we don't commit to the master (or other named branch) that is for
releases.

Even on personal forks I tend to do git flow and just push back to the
correct branch for the project.

Anyway as I said just my 2 cents.

On 29 March 2016 at 20:26, Henry Saputra  wrote:

> We could bring this discussion back to dev@ list.
>
> I like the git flow model too, but I don't think any other ASF projects
> using develop branch concept. For now all PRs and patches are targeted for
> master.
>
> - Henry
>
> On Tue, Mar 29, 2016 at 12:06 PM, Tom Barber 
> wrote:
>
>> To keep code stable I'm a fan of "git flow" either using the tooling or
>> just using the methodology, that way you always have a stable branch to
>> work off.
>>
>> Master branch never gets commits to it and always reflects the latest
>> release
>> Development branch gets sporadic commits to fix stuff or add minor new
>> bits
>> Feature-XYZ is a major new feature branch branched from development.
>> Development gets merged into it to keep it in sync and when a feature is
>> complete and tests passing, it gets merged into development
>> Hotfix-XYZ is branched from Master to provide hotfix patches and gets
>> merged back into master and development.
>> Release-XYZ is a release branch, minor bug fixes go into this branch
>> prior to release, then gets merged back into master & development when its
>> done.
>>
>> This way you keep your codebase clean and works well when you have a
>> bunch of different development drives going on.
>>
>> For more information:
>> http://nvie.com/posts/a-successful-git-branching-model/
>>
>> Matt, over on OODT we generally do a code review process before merging
>> PR's back into the mainline anyway, but I think the above can add some more
>> protection whilst allowing people to develop reasonably freely without a
>> miriad of forked branches or local offline clones.
>>
>> Cheers,
>>
>> Tom
>>
>> --
>>
>> Director Meteorite.bi - Saiku Analytics Founder
>> Tel: +44(0)5603641316
>>
>> (Thanks to the Saiku community we reached our Kickstart
>> <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
>> goal, but you can always help by sponsoring the project
>> <http://www.meteorite.bi/products/saiku/sponsorship>)
>>
>> On 29 March 2016 at 19:53, Lewis John Mcgibbney <
>> lewis.mcgibb...@gmail.com> wrote:
>>
>>>
>>> https://builds.apache.org/view/H-L/view/Joshua/job/Joshua%20master%20build/
>>>
>>> On Tue, Mar 29, 2016 at 11:23 AM, Lewis John Mcgibbney <
>>> lewis.mcgibb...@gmail.com> wrote:
>>>
>>>> I'm creating a Jenkins build which will poll master branch every minute
>>>> and execute a build if a change has been made
>>>> It will be available and configurable from here
>>>> https://builds.apache.org/view/H-L/view/Joshua/
>>>> Ta
>>>>
>>>> On Tue, Mar 29, 2016 at 11:14 AM, Matt Post  wrote:
>>>>
>>>>> Okay, before voting myself, I'd like some discussion.
>>>>>
>>>>> I'm generally supportive of adding contributors . This does represent
>>>>> a shift away from the way things have been working, though — where there
>>>>> may be multiple contributors, but in effect, all commits have come from me
>>>>> or through pull requests.
>>>>>
>>>>> So I'd really like to have some formal processes in place that ensure
>>>>> that people don't start breaking things with their pushes. The way we've
>>>>> handled it so far is to have self-contained, fast (well under a minute) 
>>&g

Re: ApacheCon 2016 and Joshua

[Tom Barber]

I'm off to ApacheCon, but I'm far less interesting. I don't pretend to
understand how any of it works, but as lewis will explain, I like platform
evangalism, demoing tech to "non standard" users and other bits and pieces.
Plus I can code a bit if someone points me in the right direction :)

>From a personal perspective I find the tech interesting which is half the
reason I threw my hat in the ring, from an employment perspective, some of
my "business" clients would find "offline" translation that doesn't rely on
big vendor API's useful, also we have done work with the UK Armed Forces
who could do with this type of stuff for translation of intelligence
material gathered from the field and requiring processing.

Tom

On Mon, Mar 14, 2016 at 3:26 PM, Matt Post  wrote:

> Whoa! Lewis, can you give some more detail on this talk, what you
> proposed, and what you plan to talk about?
>
> I haven't ever been to ApacheCon, but am interested in going. I don't have
> much of a feel for what motivates folks outside the academic research
> community, and that would be good to have in laying out projects that might
> interest people.
>
> Regarding those project, I have a number of them. Perhaps it would be
> useful to flesh them out with some more detail, and perhaps post them, for
> those who are interested. First, with respect to Tommaso's question, the
> following:
>
> - Use cases. I'd really like to push machine translation as a black box,
> where people can download and use models, not caring how they work, and
> building on top of them. I think this could be transformative. I've just
> added to Joshua the ability to add, store, and manage custom phrasal
> translation rules, which would let people take a model and add their own
> translations on top of it, perhaps correcting mistakes as they encounter
> them. There's a JSON API for it (undocumented).
>
> Building this up would also require pulling together lots of different
> test sets, evaluating changes, and so on.
>
> - Neural nets. This is a huge research area. I think the advantages are
> that it could enable releasing models that are much smaller. However, on
> the down side, it's not clear what the best way to integrate these models
> into Joshua is. Fully neural attention models would require re-architecting
> Joshua, as they are essentially a new paradigm. Adding neural components as
> feature functions that interact with the existing decoding algorithm would
> be an intermediate step.
>
> For other projects, I'd love:
>
> - Better documentation, developer and end-user (probably I need to write a
> lot of this; if nothing else, it would be hugely useful to me in terms of
> prioritizing to know that people want it)
>
> - Rewriting certain components. The tuning modules, in particular, are a
> real mess, and should be synthesized and improved.
>
> - Replacing Moses components. Joshua can call out to Moses to build phrase
> tables; it would be nice to get rid of this (and wouldn't be that hard)
> with our own Java implementations. It would also be good to add a
> lexicalized distortion model to the phrase-based decoder.
>
> matt
>
>
>
>
>
>
> > On Mar 14, 2016, at 9:37 AM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
> >
> > Hi Kellen,
> > I'll be there for sure. I actually had a talk accepted which is an entire
> > overview of Joshua and will probably touch on what the roadmap is through
> > incubation and beyond.
> > In short I look forward to tagging up with you and any others are Ho will
> > be there/we can interest in the project.
> > A side note here is that more projects and talks at ApacheCon are
> becoming
> > increasingly relevant for science and healthcare so I hope we can do a
> real
> > justice to Joshua by undertaking a driven community building effort
> > @ApacheCon.
> > This being said, let's hash out here some objectives, must haves, would
> > likes, roadmap, etc if you like.
> > Thanks for brining this topic up.
> > Lewis
> >
> > On Monday, March 14, 2016, Tommaso Teofili 
> > wrote:
> >
> >> Hi Kellen,
> >>
> >> I won't be at ApacheCon unfortunately, however your idea sounds good if
> >> there's anyone else joining.
> >> Perhaps we can also discuss some of the topics you mention here on the
> >> list, and maybe that would be of help for f2f chats too.
> >>
> >> I'd particularly interested in discussing:
> >> - use cases
> >> - ideas around usage of neural networks for MT
> >>
> >> Regards,
> >> Tommaso
> >>
> >>
> >>
> >>
> >> Il giorno lun 14 mar 2016 alle ore 12:30 kellen sunderland <
> >> kellen.sunderl...@gmail.com > ha scritto:
> >>
> >>> Hello Joshua fans,
> >>>
> >>> I was wondering how many Joshua/Apache folks are going to be at
> ApacheCon
> >>> in May.  I was hoping if there's enough of us we could get together and
> >>> chat about development ideas for Joshua, discuss each others use cases,
> >>> etc.  I know that I for one would love to sync up on how the
> development
> >>> model for the project will work in the f

Re: which build tool

[Tom Barber]

I know some projects that do the same, continue to shift some of the
compilation to ant within maven, that way you generally get better tooling
and CI support and the more complex stuff is still done in Ant. Might be an
avenue worth pursuing in the not too distant future.

On Mon, Mar 14, 2016 at 1:32 PM, Lewis John Mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> Joshua builds with Ant. Justification for this right now is well versed,
> there are a number of more complex steps e.g. Compiling c++ GIZA code and
> also the thrax codebase also needs to be install IIRC.
> I took a look at porting the build to Maven literally 2 or 3 weeks ago but
> right now it seems like a bit of investment in time.
> If anyone fancies doing this however, last time I spoke to Matt he was game
> for porting the build to Maven.
>
>
> On Monday, March 14, 2016, Tommaso Teofili 
> wrote:
>
> > I also prefer Maven but I'm not against Ant if that proves to be working
> > already (let's keep it as simple as possible for the start), for sure I
> > would like to avoid having both as that is a pain to maintain (seen
> already
> > how annoying it is in Apache Lucene/Solr).
> >
> > Regards,
> > Tommaso
> >
> > Il giorno lun 14 mar 2016 alle ore 14:23 Tom Barber <
> > t...@analytical-labs.com >
> > ha scritto:
> >
> > > Oh please let it be maven! :)
> > >
> > > --
> > >
> > > Director Meteorite.bi - Saiku Analytics Founder
> > > Tel: +44(0)5603641316
> > >
> > > (Thanks to the Saiku community we reached our Kickstart
> > > <
> > >
> >
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> > > >
> > > goal, but you can always help by sponsoring the project
> > > <http://www.meteorite.bi/products/saiku/sponsorship>)
> > >
> > > On 14 March 2016 at 12:19, Tommaso Teofili  > >
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > I am having a look at the Joshua build and was wondering which tool
> we
> > > want
> > > > to support: Ant or Maven?
> > > > AFAICS from the README we should be using Ant for compiling, however
> I
> > > also
> > > > see a pom.xml and hence I'm a bit confused (BTW the Maven build fails
> > > with
> > > > compilation errors for me).
> > > >
> > > > Regards,
> > > > Tommaso
> > > >
> > >
> >
>
>
> --
> *Lewis*
>

Re: which build tool

[Tom Barber]

Oh please let it be maven! :)

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 14 March 2016 at 12:19, Tommaso Teofili 
wrote:

> Hi all,
>
> I am having a look at the Joshua build and was wondering which tool we want
> to support: Ant or Maven?
> AFAICS from the README we should be using Ant for compiling, however I also
> see a pom.xml and hence I'm a bit confused (BTW the Maven build fails with
> compilation errors for me).
>
> Regards,
> Tommaso
>