You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Kai Bösefeldt f16dea5365 #37 Fixed dangling link 6 months ago
Design #26, #27: Added documentation for contributors 8 months ago
Documents #43 Updated branching document and added issues.sh script for handling issue state for git branches 6 months ago
compiler #20 Updated license headers. 8 months ago
config #20 Updated license headers. 8 months ago
crypto #20 Updated license headers. 8 months ago
error #20 Updated license headers. 8 months ago
expr #20 Updated license headers. 8 months ago
gradle/wrapper Hello World App can be started with the lancher. 10 months ago
http #20 Updated license headers. 8 months ago
issues #31 Set issue DONE 8 months ago
jekyll #37 Re-added disappeared license file. 6 months ago
licenses_3rdParty #20 Checked 3rd party licenses and added according about info to the UI. 8 months ago
numbers #20 Updated license headers. 8 months ago
odo.api #20 Updated license headers. 8 months ago
odo.api.desktop #20 Updated license headers. 8 months ago
odo.boot/src/main #20 Updated license headers. 8 months ago
odo.cloud #20 Updated license headers. 8 months ago
odo.cloud.ipfs #34 Fixed missing dependency 8 months ago
odo.content #20 Updated license headers. 8 months ago
odo.hello #29 Added Hello app folder with app manifest. Also added documentation how to start the app. 8 months ago
odo.kernel #20 Updated license headers. 8 months ago
odo.kernel_it #20 Updated license headers. 8 months ago
odo.launcher #20 Updated license headers. 8 months ago
odo.loader #20 Updated license headers. 8 months ago
odo.loader_it #20 Updated license headers. 8 months ago
odo.ui #20 Updated license headers. 8 months ago
odo.ui.desktop #20 Fixed crash on app startup. 8 months ago
odo.ui.desktop.model #31 Enable running multiple instances 8 months ago
pages@32b99a8b29 #37 Re-added disappeared license file. 6 months ago
random #20 Updated license headers. 8 months ago
testing #20 Updated license headers. 8 months ago
units #20 Updated license headers. 8 months ago
utils #20 Updated license headers. 8 months ago
.gitattributes Initial project structure 1 year ago
.gitignore #20 Checked 3rd party licenses and added according about info to the UI. 8 months ago
.gitmodules #37 moved odo content to the odo subfolder 6 months ago
LICENSE added license and coding style 1 year ago
NOTICE #20 Checked 3rd party licenses and added according about info to the UI. 8 months ago
README.md #37 Fixed dangling link 6 months ago
build.gradle.kts #34 Set release software version + fixes of minor issues 8 months ago
gradle.properties * First shot implementation of bootstrapping of odo 1 year ago
gradlew Initial project structure 1 year ago
gradlew.bat Initial project structure 1 year ago
ipfs.sh #31 Enable running multiple instances 8 months ago
issues.sh #43 Updated branching document and added issues.sh script for handling issue state for git branches 6 months ago
listLibs.sh #20 Checked 3rd party licenses and added according about info to the UI. 8 months ago
run.sh #31 Enable running multiple instances 8 months ago
settings.gradle.kts * Cleaned up code to pass check 10 months ago

README.md

ODO Distributed Online

Breaking News: Proof-of-Concept Prototype released!!

From now on, the ODO project is open for contribution!! Please help!!

What is ODO?

Currently: Work in progress, pre-alpha, available only as proof-of-concept prototype.

What is the Vision behind ODO?

ODO wants to become the "swiss army knife" for the development of distributed communication apps. It will allow developing such apps for various platforms: mobile, desktop, server, maybe even IoT devices. A layered API will allow quick development of simple apps in a low-code-manner, or complex apps using all the features of modern software development environments.

Get rid of Backend Servers

One of the key ideas is to get rid of central servers, meaning the app is really just the app on the device it is running on, no backends, no serers. All data is encrypted and distributed over all devices having ODO installed (using IPFS). This means that an app with ODO can be run with minimal resources on the operator side, as you don't need AWS, Firebase, Azure or whatever.

Make Privacy and Security easy

One of the main goals of the layered API is to make it easy to develop secure apps with good privacy by design. Of course it is not possible, to have an API which technically prevents all possible security vulnerabilities and privacy problems. But an API can focus on privacy and security, and make these things easy. And while categories of privacy problems arising from a single entity controlling a central server, these kinds of problems simply does not exist with ODO.

Have a closer look at the top level design document for more info about the technical ideas.

When can I have it?

Please be patient ;-) We have the following milestones until the 1.0 release (checked=reached):

  • Proof-of-concept Prototype: We have a simple "Hello World" app with a first simple version of the ODO API. This app is distributed via IPFS and can be loaded and run by every ODO installation..
  • App: Project Chat: The first useful ODO app should be a simple chat app used by the ODO developers to organize their work. This way, they get a feeling for the API and see, what is needed most badly.
  • Pilot Apps: A few pilot apps, covering important basic use cases, should be developed. These pilot apps should cover most parts of the ODO API, so that it is oriented on the practial needs of app developers. These pilot apps could be developed for interested 3rd parties.
  • Stable API: Problems in the ODO API are identified and fixed and the API is reviewed and stabilized.
  • Release 1.0

I want to contribute!

If you would like to contribute, start with this document, and the go on with onboarding. Also have a look at your code of conduct.