System components

[fsmanuel]

As far as I understand the situation we have the following components in our system:

• IPFS
• uPort
  • identity
• truffle-kredits
  • ETH blockchain access
  • ETH smart contracts deployment
  • smart contracts
  • proxy contracts
  • migratable contracts via proxy
  • testing
• kosmos-schemas
  • JSON schemas for IPFS data
• hubot-kredits
• kredits-web
  • frontend/gui

Please add everything I forgot!

[bumi]

This is documented in the wiki: https://wiki.kosmos.org/Kredits#Software - which we should extend/update.

• IPFS is the system to store larger files.
• uPort is not used right now - it could be an contributor identity provider.

missig is hubot-kredits which is handling github webhooks to create proposals and has IRC integration.

[fsmanuel]

Thanks! I updated the list and will read the wiki.

[raucao]

The wiki should always be the most up-to-date source of information for all our stuff. Let's make sure to update it early and often!

You can even use it for documentation-driven development, before even writing code, which we already did there in some places. :)

[fsmanuel]

Yeah! I think we can update the wiki as a first task next week. I'll just use the issues to get a better understanding and ask all the questions.

[fsmanuel]

Is the parity server on https://parity.kosmos.org:8545 also part of the system?

[raucao]

It's running our current beta chain that we use with the deployed system that's in place. If a PR is merged or an issue closed with a kredits label attached, hal8000 will create proposals on that chain for example.

[raucao]

Yeah! I think we can update the wiki as a first task next week. I'll just use the issues to get a better understanding and ask all the questions.

I just updated the wiki page to be more or less up to date. But there's still some information missing. Earn you some Kovan kredits and help me add more content! :)

Closing this issue in favor of the wiki page.