Hi,
Am 29.03.2013 12:53, schrieb Maruan Sahyoun:
<SNIP>
I think some wiki pages should be good. This discussion already
started but as mails in the list or maybe jira tickets lost in the
flow.
There is an apache wiki [1], but I found nothing on PDFBox, a good way
occasion to start.
Once we migrated our site to the Apache CMS we'll have some sort of wiki, so
that we IMHO don't have to ask for other one.
I do not have many more ideas. According to me, having different
modules for PDF parsers, PDF makers and PDF viewers is an important
one.
This is one of my favourites, too. Let's see what'll come up. At least we don't
only need people who are interested in some features but also in implementing
it ;-)
We might be able to split into modules based on the current code and rearchitect
> the individual parts later. E.g the command line tools could easily be
separated
> as well as PDFDebugger, PDFReader.
Yes, there are some easy ones and others will be more complicated
One thing to consider is how we handle releases afterwards. Will we always
release
> all modules as part of a release (like Apache Camel does) or do releases
> seperately (as Apache Sling does).
That's a good point, but it'll depend on the details. AFAIK Sling is OSGI based
so that all components should be independent, which makes it easier to release
them separately.
I'm happy to help with implementation/rearrangement as soon as the transition
to the CMS is done
Cool!
BR
Andreas Lehmkühler
