Create architecture diagram for Kredits #6

Closed
opened 2019-11-17 13:38:25 +00:00 by raucao · 8 comments
Owner

As an overview of all important parts of the current system.

As an overview of all important parts of the current system.
raucao added this to the DOTS/i4policy Workshop milestone 2019-11-17 13:38:29 +00:00
Author
Owner

I have added a short, not-at-all-detailed summary of the high-level architecture to the wiki page: https://wiki.kosmos.org/Kredits#Concept_.26_Architecture

I have added a short, not-at-all-detailed summary of the high-level architecture to the wiki page: https://wiki.kosmos.org/Kredits#Concept_.26_Architecture
Author
Owner

As there wasn't any update here before today, I have started working on this.

As there wasn't any update here before today, I have started working on this.
raucao self-assigned this 2019-12-02 16:00:41 +00:00
Author
Owner
Added a first version to the wiki: * https://wiki.kosmos.org/Kredits#High-level_overview * https://wiki.kosmos.org/images/c/c1/High-level-architecture.svg Feedback very welcome.
Author
Owner

@bumi What do you think? Was there anything missing or wrong from what you saw during my presenting it at DOTS?

@bumi What do you think? Was there anything missing or wrong from what you saw during my presenting it at DOTS?
raucao added the
docs
kredits-2
labels 2019-12-10 02:44:02 +00:00
Author
Owner

FYI: uploaded the source files for the diagram straight to master of this repo. I used Dia to create it:

https://wiki.gnome.org/Apps/Dia

(Dia is free software and available for all of Linux, macOS, and Windows.)

FYI: uploaded the source files for the diagram straight to `master` of this repo. I used Dia to create it: https://wiki.gnome.org/Apps/Dia (Dia is free software and available for all of Linux, macOS, and Windows.)
Author
Owner

@bumi Could you please give me your feedback, so we can either improve the diagram, or close the issue? Thanks!

@bumi Could you please give me your feedback, so we can either improve the diagram, or close the issue? Thanks!
Owner

sorry for the late answer.
great diagram to see the high-lever interaction!

I was only thinking if we can label/link the parts to our components a bit more obvious.
e.g.
Contracts Client API -> kredits-contracts
Hubot Integration -> hubot + hubot-kredits

sorry for the late answer. great diagram to see the high-lever interaction! I was only thinking if we can label/link the parts to our components a bit more obvious. e.g. Contracts Client API -> kredits-contracts Hubot Integration -> hubot + hubot-kredits
Author
Owner

I think those are explained sufficiently clear in the software list under the diagram. There's not much space to work with, as it's pretty large and hardly legible in smaller sizes already.

I think those are explained sufficiently clear in the software list under the diagram. There's not much space to work with, as it's pretty large and hardly legible in smaller sizes already.
Sign in to join this conversation.
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/meta#6
No description provided.