esmero / archipelago-deployment

Archipelago Commons Docker Deployment Repository
33 stars 15 forks source link

Archipelago Roadmap 2019: Beta1 #5

Open DiegoPino opened 5 years ago

DiegoPino commented 5 years ago

Archipelago 2019 Roadmap

This is our working enumeration of concrete tasks, per Component and Service, for public evaluation (and comments).

All tasks listed here are leading our full feature release end of 2019. Checked tasks are ready, unchecked are in progress or planned. Priority is not given by this order.

There are a lot more things involved and many are already done and coded, but i wanted to have a list that was closer to features checklist than the actual code milestones we are managing internally. Please feel free to comment, request more info or ask for clarification. Feature requests are also highly appreciated and taken in account (always, please!).

Strawberryfield

JSON representation and enrichment

Webforms integration

Media Displays

Field Formatters

API Ingest, Migration and backup

Service Architecture (Strawberry Runners)

SEO and API

ACL / Permissions

Deployment and DevOPS

Batch Operations

Future roadmap

Documentation:

DiegoPino commented 5 years ago

Note: This is an update from our original https://github.com/esmero/archipelago-aws-demo/issues/6 which we will keep for sanity/not-breaking links purpouses there too. That repo (not this) will contain specific to AWS deployment strategies, not version specific, like specially production almost-ready and performance optimized configurations and some demos on Multi tenant, Solr Cloud based deployments too. More on that later.

giancarlobi commented 5 years ago

@DiegoPino really really an intensive good work! thanks a lot for this schema and for all your work.

DiegoPino commented 5 years ago

@giancarlobi team effort! I totally feel worn out but happy we have our horizons clear. What i would like to see/make/have someone make is to create an ISSUE in each repository for each of these tasks to link this list to our work. It can be multiple issues, or larger ones, but they should explain the extend of the work required and where we are at, so we can mention those in each pull and advance. Once that is done i can update this description and add the links. Also, i will classify each of this tasks according to the effort or complexity. I need to figure a good label system. Means i need help here.