tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (3980)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: @ApacheTika , and release related tweets question
Date Wed, 06 Apr 2016 14:10:51 GMT
++1 on all the feedback from you two below :)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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.mattmann@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/6/16, 9:08 AM, "Bob Paulin" <bob@bobpaulin.com> wrote:

>Hi Nick,
>
>This is awesome and I think should be great for the community!  I looked 
>to commons as an example https://twitter.com/ApacheCommons . Looks like 
>they tweet out the releases with a link to the mailing list comments.  
>Might be a good precedent to follow to bring attention to the fact that 
>there is a mailing list.  Other things to consider: CVE we'd need to 
>report publicly, committer/PMC updates, and perhaps PSAs of changes like 
>the SVN - > GIT change.  Thanks again!
>
>- Bob
>
>On 4/6/2016 7:41 AM, Nick Burch wrote:
>> Hi All
>>
>> Firstly, in case you haven't heard, we've setup a twitter account for 
>> the project! It's @ApacheTika - https://twitter.com/ApacheTika
>>
>>
>> One thing we'll want to use it for is project publicity, linking to 
>> interesting things going on around the project, such as today's post 
>> on how the panama papers investigation used Apache Tika and SOLR :)
>>
>> Another thing we can use it for is release announcements. That leads 
>> to a question though - which parts? Should we just tweet when there's 
>> a new release out, linking to the download and the changelog?
>>
>> Or would people prefer it if we tweeted when we start the countdown to 
>> a release (to give a chance to test / get last patches ready), again 
>> when the vote starts (to get a wider group testing and voting), and 
>> finally when the release is out?
>>
>> Thoughts?
>>
>> Nick
>>
>
Mime
View raw message