An user community of Thalos is needed in order to receive feedback on its behavior.

Roadmap

With this project we intend to

• Provide simple and secure storage in untrusted environments for everyone in the internet.
• Provide the software so that everyone can set up his own Thalos storage system in few minutes

In order to do that we are building a portable internet service that provides a simple management of a remote encrypted virtual file system.

What we need to do

This issue is our roadmap. It's a place to start to investigate the myriad of issues that you can contribute to. Check out the different milestones listed below, but feel free to explore the issues by label too.

Please check out our code of conduct to help you get started, and the README for an overview if you haven't read it yet!

Milestone: Web Front end Improvements

Fixing architectural pattern violations and making the service portable builidng a web frontend independent from the service server

#4 1 Front end migration

Milestone: Community and contributors

Building a community of users #3
Building a community of contributors #4

Milestone: Mozilla Festival 2017

Activity we need to carry out to have a fully functional demo by october 27

Build a Roadmap #5

Document Service APIs #2

Well documented API are needed mainly for two reasons

Everyone should be free to build its own thalos client.
The actions Thalos performs on file must be clear to everyone in order to guarantee user privacy.

Well documented API are needed mainly for two reasons

• Everyone should be free to build its own thalos client.
• The actions Thalos performs on file must be clear to everyone in order to guarantee user privacy.

At this time the web pages of the user interface are supplied by the same NodeJS server (trough its view engine) used for back-end elaborations.
According to the client-server architecture model it is would be a good practice to separate the two codes.
What we want to do within this milestone is building an html frontend able to exchange information with the thalos server just using its REST APIs

In order to avoid spam and fake users, people must activate their accounts just after the registration.
At this time the activation link is temporarily provided by a HTML page just after the registration process.
We should implement as soon as possible a function to send the activation link to the user email address.

the title speak for itself
Full stack Javascript developers are welcomed here in order to move this project forward.
Also Python and Java developer are welcomed since we intend to design much client as possible capable in using thalos apis.

Allow users to have multiple keys in order to access their files from multiple devices