Re: hosting release files

2016-04-05 Thread Mattmann, Chris A (3980) 
FYI:
https://issues.apache.org/jira/browse/INFRA-11602


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 4/5/16, 3:46 PM, "Mattmann, Chris A (3980)"  
wrote:

>You got it thanks 
>
>Sent from my iPhone
>
>> On Apr 5, 2016, at 3:44 PM, Daniel Gruno  wrote:
>> 
>>> On 04/05/2016 09:36 PM, Mattmann, Chris A (3980) wrote:
>>> Nowhere near OOo its normal range so can you Increase our limit to say 5gb 
>>> per upload to be safe? Thanks DG
>> 
>> I would, except it's nearly 10PM here and I'm playing the role of Arno
>> Dorian, mysterious assassin in Paris! Could you please file a JIRA for
>> this? :)
>> 
>> With regards,
>> Daniel.
>> 
>>> 
>>> Sent from my iPhone
>>> 
 On Apr 5, 2016, at 3:31 PM, Daniel Gruno  wrote:
 
 The actual size of the releases don't matter much - we just need a
 heads-up so we can increase your 'upload limit'. What will matter is how
 many downloads you estimate will happen per month. Are we talking a few
 hundred? thousand? million?
 
 If it's within 'normal range', then there's nothing to worry about. If
 it's OpenOffice figures, then we need to discuss hosting.
 
 With regards,
 Daniel.
 
> On 04/05/2016 09:23 PM, Matt Post wrote:
> Hi,
> 
> To add to this, there could easily be many tens of such files. We 
> currently have three language packs (for Chinese, Arabic, and Spanish), 
> but plan to add many of them over the coming months.
> 
>   http://joshua-decoder.org/language-packs/
> 
> Matt
> 
> 
>> On Apr 5, 2016, at 2:19 PM, Mattmann, Chris A (3980) 
>>  wrote:
>> 
>> Thanks Matt.
>> 
>> I’m copying infrastruct...@apache.org on this email. Infra@ what
>> are your thoughts on the Apache Joshua (Incubating) podling being
>> able to release our language packs - which are on order of 1gb-3gb
>> each? Can you suggest any gotchas in doing so - I realize the concern
>> about release size, but these language packs are more than just 
>> convenience binaries, they help make Apache Joshua a complete product.
>> 
>> Please advise.
>> 
>> Thx.
>> 
>> 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 4/5/16, 2:17 PM, "Matt Post"  wrote:
>>> 
>>> The Joshua release is just a hundred megabytes or so. If we exclude 
>>> Hadoop and other tools used for building (which I think we should do), 
>>> the release is more like tens of megabytes.
>>> 
>>> For language packs, I think a reasonable expectation is 2--3 gigabytes 
>>> each.
>>> 
>>> matt
>>> 
>>> 
 On Apr 5, 2016, at 2:09 PM, Mattmann, Chris A (3980) 
  wrote:
 
 Yep absolutely. When we *release* Apache Joshua (FYI here is a 
 guide to creating an Incubator release [1]), we can also release
 large tarballs as well. If the files are >1 GB we need to inform
 Apache infrastructure as the files are mirrored around the world.
 
 What are the expected release sizes, and what is our overall 
 expectation for the contribution of each language pack to the 
 release?
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Chief Architect

Re: hosting release files

2016-04-05 Thread Matt Post 
The Joshua release is just a hundred megabytes or so. If we exclude Hadoop and 
other tools used for building (which I think we should do), the release is more 
like tens of megabytes.

For language packs, I think a reasonable expectation is 2--3 gigabytes each.

matt


> On Apr 5, 2016, at 2:09 PM, Mattmann, Chris A (3980) 
>  wrote:
> 
> Yep absolutely. When we *release* Apache Joshua (FYI here is a 
> guide to creating an Incubator release [1]), we can also release
> large tarballs as well. If the files are >1 GB we need to inform
> Apache infrastructure as the files are mirrored around the world.
> 
> What are the expected release sizes, and what is our overall 
> expectation for the contribution of each language pack to the 
> release?
> 
> 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 4/5/16, 1:57 PM, "Matt Post"  wrote:
> 
>> Does Apache provide a place to host releases, language packs, and other 
>> (potentially large) files? Right now, they're all under my home directory at 
>> Hopkins, and it would be nice to put them in a more formal location (where 
>> I'm not pushing up against a quota).
>> 
>> matt

hosting release files

2016-04-05 Thread Lewis John Mcgibbney 
Yes.
All of this can be hosted at Apache
http://apache.org/dev/#releases

On Tuesday, April 5, 2016, Matt Post > wrote:

> Does Apache provide a place to host releases, language packs, and other
> (potentially large) files? Right now, they're all under my home directory
> at Hopkins, and it would be nice to put them in a more formal location
> (where I'm not pushing up against a quota).
>
> matt



-- 
*Lewis*