Ability to modify pages confirmed. Thanks for the prompt response!
On Thu, Mar 30, 2017 at 1:11 AM, Mattmann, Chris A (3010) <
chris.a.mattm...@jpl.nasa.gov> wrote:
> fixed
>
> ++
> Chris Mattmann, Ph.D.
> Principal Data Scie
fixed
++
Chris Mattmann, Ph.D.
Principal Data Scientist, Engineering Administrative Office (3010)
Manager, NSF & Open Source Projects Formulation and Development Offices (8212)
NASA Jet Propulsion Laboratory Pasadena, CA 91109
It is *KranthiGV* (https://wiki.apache.org/tika/KranthiGV).
On Thu, Mar 30, 2017 at 12:59 AM, Mattmann, Chris A (3010) <
chris.a.mattm...@jpl.nasa.gov> wrote:
> Sorry I can’t seem to figure out your username:
>
> https://wiki.apache.org/tika/ContributorsGroup
>
> Please tell me what to put
>
> ++
Sorry I can’t seem to figure out your username:
https://wiki.apache.org/tika/ContributorsGroup
Please tell me what to put
++
Chris Mattmann, Ph.D.
Principal Data Scientist, Engineering Administrative Office (3010)
Manager, N
Hello, developers!
I'm currently working a pull request regarding the improvement of Object
Recognition Parser (https://github.com/apache/tika/pull/163). I would like
to update the wiki at https://wiki.apache.org/tika/TikaAndVision once this
is merged.
Please grant me access to wiki so that I can
Hi
I have shared my draft proposal. Kindly review and comment so that I can
shape my proposal further.
Thanks
--
Regards,
Raunaq Abhyankar
+1 Y, thank you!
-Original Message-
From: Ken Krugler [mailto:kkrugler_li...@transpac.com]
Sent: Wednesday, March 29, 2017 2:07 PM
To: dev@tika.apache.org
Subject: Re: [DISCUSS] Contribution guide & style enforcement
Hi Konstantin,
Thanks for the thoughtful and detailed writeup.
And y
Hi Konstantin,
Thanks for the thoughtful and detailed writeup.
And yes, +1 to all 5 top-level suggestions.
— Ken
> On Mar 29, 2017, at 10:39am, Konstantin Gribov wrote:
>
> Hi, folks.
>
> Currently we have something like contribution guide parts in several places
> (I thought about [1] and [
Konstantin,
I’ve read through this and I am +1 to try. Trying to organize and make the code
base better makes sense to me. I don’t want to make it scary for people to
contribute, but based on the below, I think it’s guidelines and tools to help
us.
So this is great. +1
Cheers,
Chris
+
[
https://issues.apache.org/jira/browse/TIKA-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Gribov updated TIKA-2316:
Description:
Things to mention there:
- formatting guidelines (e.g. 4 spaces, no tabs, no com
Hi, folks.
Currently we have something like contribution guide parts in several places
(I thought about [1] and [2] and Chris also mentioned [3]) covering
different facets of contributing to Apache Tika.
One thing which make me upset is that we have very inconsistent codebase
with different style
[
https://issues.apache.org/jira/browse/TIKA-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947436#comment-15947436
]
Konstantin Gribov commented on TIKA-2316:
-
[~chrismattmann], thanks for addition.
[
https://issues.apache.org/jira/browse/TIKA-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947417#comment-15947417
]
Chris A. Mattmann commented on TIKA-2316:
-
👏🏻This makes sense to me. Also lots to p
Konstantin Gribov created TIKA-2316:
---
Summary: Write something like contribution guide in wiki and/or
site
Key: TIKA-2316
URL: https://issues.apache.org/jira/browse/TIKA-2316
Project: Tika
Konstantin Gribov created TIKA-2315:
---
Summary: Update logging page at wiki with actual info
Key: TIKA-2315
URL: https://issues.apache.org/jira/browse/TIKA-2315
Project: Tika
Issue Type: Tas
[
https://issues.apache.org/jira/browse/TIKA-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Gribov closed TIKA-968.
--
> tika-bundle missing org.apache.commons.logging.LogFactory
>
[
https://issues.apache.org/jira/browse/TIKA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Gribov closed TIKA-934.
--
> Tika in server mode stops responding and reports NPE over and over in logs
> ---
[
https://issues.apache.org/jira/browse/TIKA-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Gribov closed TIKA-403.
--
> Refactor log library usage in tika-parsers
> --
>
>
Konstantin Gribov created TIKA-2314:
---
Summary: Migrate logging to slf4j in 2.x branch
Key: TIKA-2314
URL: https://issues.apache.org/jira/browse/TIKA-2314
Project: Tika
Issue Type: Improveme
Sounds great, and understood. Please prepare your proposal and share with
Thamme and I for
feedback as your (potential) mentors.
Thanks much.
++
Chris Mattmann, Ph.D.
Principal Data Scientist, Engineering Administrative Offi
Hey Konstantin,
Your observation is spot on and also is the reason why there is an
advantage to having separate ones. The bundles are not meant to be used
outside of OSGi. The current tika-bundle has many entries in the
MANIFEST.MF due to the embedded dependencies. We also depend on maven to
re
[
https://issues.apache.org/jira/browse/TIKA-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947060#comment-15947060
]
Chris A. Mattmann commented on TIKA-2262:
-
Is there a PR associated with this, or d
[
https://issues.apache.org/jira/browse/TIKA-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946994#comment-15946994
]
ASF GitHub Bot commented on TIKA-2309:
--
GitHub user Shinobi75 reopened a pull request:
GitHub user Shinobi75 reopened a pull request:
https://github.com/apache/tika/pull/161
fix for TIKA-2309 contributed by Shinobi@75
Hello,
this is the pull requeste for JIRA Issue or Enhancement marked with
TIKA-2309.
I've added follows new classes:
tika-core/src/mai
[
https://issues.apache.org/jira/browse/TIKA-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946983#comment-15946983
]
ASF GitHub Bot commented on TIKA-2309:
--
Github user Shinobi75 closed the pull request
Github user Shinobi75 closed the pull request at:
https://github.com/apache/tika/pull/161
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Nick,
I see now why it was done: we use `Embed-Dependency` for tika-bundle in 1.x
and for tika-parser-*-bundle in 2.x so it produces fat/uber jar with some
dependencies inlined in them.
This is unsuitable for non-OSGi builds.
So I withdraw my "bright" idea about merging corresponding modules and
On Wed, 29 Mar 2017, Konstantin Gribov wrote:
I've been surprised by such separation, what was the reason to separate
them?
I think partly history (we split in 1.x), partly how the split was done
(osgi folks amongst the most keen), and partly a desire not to have
non-OSGi users getting a load
28 matches
Mail list logo
