Kristian Rickert created OPENNLP-1924:
-----------------------------------------
Summary: ADDONs - refactor + publish setup
Key: OPENNLP-1924
URL: https://issues.apache.org/jira/browse/OPENNLP-1924
Project: OpenNLP
Issue Type: Epic
Reporter: Kristian Rickert
Assignee: Kristian Rickert
After a discussion in the mailing list, we are expanding the addons repo more
formally:
[https://github.com/apache/opennlp-addons]
This will keep it's original intent but push artifacts to m2. As part of this
ticket we will come up with an formalize:
# Boundaries of what belongs in addons vs core vs sandbox
** sandbox - unpublished, experiemental
** addons - published + maintained
** core - core interfaces and some reference implementations of those
interfaces
# Release train for addons
# Versioning scheme
# Compatibility rules (we pretty much said that if you build it here it should
be compatible with the latest core)
# Retirement rules (given it should have a higher cadence of features than
core, decide some basic guidelines and rules of retiring defunct code /
outdated)
# "Graduation" rules (a highly downloaded / popular / dependent jar that
should become part of core)
# API addition rules - should a new feature go into add-ons, when to discuss
bringing the API into core but leave the functionality/instance in addons.
.. and anything else we can have on the discussions
Please note: this has been spec'ed over email so far- we expect the
requirements to change based on the team's full review.
We'll keep this ticket open until all tasks related to it are completed.
Here are some of the good examples of what we have went over so far:
* Model-required features
* a new provider for already existing functionality (tokenizer, embeddings,
chunking, etc)
* components that are in development but highly experiemental. (i.e. the java
implementation of model2vec, turboquant)
Finally - dependencies would only be bought in very rare instances. Even in
those cases, if one is added, it may never go into core.
There are a lot more points to add, and we'll comment/edit this story to
represent those changing reqirements.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
