Clowder 2.0 Breakdown of prioritization

Service Model Update (Business Office Meeting)

Slack Channel for Internal Use - Done. v2


Luigi talked about 2.0 and wants all to show exactly what they are working on so that we are all on the same page with the code and language in these meetings.

If you are working on 2.0 please join Clowder v2 channel so everyone can see questions/issues/updates immediately.

Design before we implement

Schedule for Clowder 2.0

Where do we want to track issues for 2.0? GitHub? Wiki? GITHUB!

Do a UI mockup or show diagrams where applicable.

Decide what licenses we need.

Create a metadata template.

Remember that Alpha 1 is the most complex task of all.

At this point, this is all internal, but once we get velocity and all team is on board, we will share with external collaborators.


  • Black python code for setup
  • Docker compose - technical discussion on code (traefik, MinIO, Mongo, nginx) (Rob, Mike, Luigi, Max)
  • API router technical discussion
  • issue with PyObject ID - get a fail
  • Test your PR's!!
  • Mike Lambert notes: I get this a lot with V1 Clowder…
  • Docker compose should be its own in the backend and create a new one for the frontend.
  • Should we put everything in one repository?
  • CAn we start to push to docker hub

Luigi1.19.4 release made yesterday. See discussion above
MaxMax did PR for Todd.  Simplified as some items are not implemented yet. Max will push and Todd will look at it this afternoon.
Mike L.

Apologies, I may have had a slightly older branch checked out… but once I pulled, it did break. Sadly, I can’t even see the actual commit hashes that were fetched b/c GitHub desktop is mean

Given overview of React - thank you Chen Wang 

Generating Open API v1 and Open API v2 clients to help with integration (Chen's advice is to focus on v2 for now, worry about v1 later) 

Looking into Docker compose and how to reuse the compose file from the fastapi git repo (instead of maintaining a separate copy)

Mike B.

OoO Nov17-23rd

Michael Jabsent

typescript PR ready to be reviewed and merge:

Wants to start a conversation next weekabout backend CRUD as it relates to minio.

Luigi suggests you start a list and share with everyone.

Tag it if you want to go back to it.

Chen suggests that API v1 there is a different code for API v2.  We will need an authentication client for v2

Katieout next week
Lisaout next week

Action Items/To Dos:

  •  Workbench Webinar in 2022 ending CDDR?