Create architecture diagram for Kredits #6
Labels
No Label
bug
dev environment
docs
duplicate
enhancement
feature
idea
invalid
kredits-1
kredits-2
kredits-3
ops
question
security
ui/ux
wontfix
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/meta#6
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As an overview of all important parts of the current system.
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
As there wasn't any update here before today, I have started working on this.
Added a first version to the wiki:
Feedback very welcome.
@bumi What do you think? Was there anything missing or wrong from what you saw during my presenting it at DOTS?
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.)
@bumi Could you please give me your feedback, so we can either improve the diagram, or close the issue? Thanks!
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
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.