gelnior

Yep, French Open Source Software community is federating to build a strong alternative to major cloud services. It's getting very interesting.

We didn't stress test it so I don't know how it would react with big files and conflicts. It's a first version to say that we are compatible with it. If people shows interest in it, we'll improve it to handle edge cases if needed.

Whatever, I imagine you could find most of the answers to your question on the Remote Storage forum and website:

http://remotestorage.io

http://community.remotestorage.io/

Thank you guys for the feedback! About the ease of use we are working on it via partnerships with hosting companies and ISPs. If you can't wait, you can check cozycloud.cc too.

Hi Peter,

Thank you for the feedback. You can change the language in the settings page: https://demo.cozycloud.cc/#account

to be more constructive: would you accept contributions to build packages? Apart from this annoyance the project looks interesting!

Of course any contribution of this kind is greatly appreciated !

Thank you for your feedback, we'll fix that. I open an issue about it.

About the signing part, we definitely have to improve that. Thank you for mentioning.

About the channel, the (real) install script is based on Fabric and use SSH. So you can refer directly to this: http://cozy.io/host/install.html

How do you install new stuff on your machine without super user rights ? Do you have a specific user to run apt-get ?

Frenches don't really worry about that, they are already building the next generation of personal cloud ;) http://cozy.io

Thank your rdubigny for this awesome application for Cozy. Only the external contributions like yours can unleash the full potential of the platform.

Thank you 616c for your message! About the minimum hardware required, Cozy made some progress on the memory footprint (lighter framework and usage of javascript runtime instead of coffescript one). Now you can use it with only 512MB of RAM instead of 1024MB. You can make it run on a RaspberryPi (B model) too.

You are right. I worked as BI consultant before. In our company the three main challenges we had were :

* collecting data * having clean data * extracting the right indicators and analytics from the data

I think the problems remain the sames with QS. Actual QS solutions lack of interoperability, do not really allow experimentations and do wrong about privacy. That's why Cozy could help: it allows to build data collectors in a few hours, a data browser is available to clean wrong data, and the best of all it allows anyone to hack new stuff on top of this new set of data without compromising privacy.

disclaimer: Cozy member

You are definitely right. About the motivation, I think that when people can actively participate to the decisions and are responsible of a subject, they are more motivated. Because agile and specially Light Agile empower every member of the team, they act as good motivators.

awesome! I will look this week-end if I can contribute to your project and add an option to save the results into KYou.

We could maybe build a bridge between you app and KYou. Did you push it on Github?

Look like you know well this kind of product.

They are the easiest trackers to build. But I would like to add stuff like weather tracking (based on forecast API), number of posted tweets, number of github commits...

Cozy is free and open source, so you can host it at home on your NAS, your RasPi or an online server you rent. Cozy Cloud offers facilitators to host your cloud, if Cozy make bad things of your data, most of the users will leave and Cozy Cloud will probably close.

You can host it on your own machine. Even if you host it via an hosting provider, you can export all your data and your apps to any new servers like an home server for example!

Yeah there are plenty alternatives now like Cozy Cloud or Owncloud.

https://www.cozycloud.cc/

http://owncloud.org/

Locker project proposed to fetch all data from your cloud services. If I didn't miss something, that was not a web server. With Cozy, you can install any kind of app: photo manager, note manager, dashboards, external service aggregator... They share the same data store. So if you write your own web app, you can take advantage of other web apps data.

Thank you rjh29 for your feedbacks about the installation script. Here are some additional informations:

* The script installs with apt-get what is possible to install with this tools. The tarballs downloaded are not random tarballs, they are specific version of the required modules.

* About the debian package, that's really an hard job to set-up a proper package when so many modules are involved. But you're right it would make things cleaner.

* Remember that Cozy is a FOSS project. We'll be glad to discuss about it through our issue list. You can propose improvements via a pull request too.

You should have a look at this: http://cozy.io/

And how do you make a social app, you can use from anywhere with good UI without webserver/client ?

Moreover web servers are compatible with peer-to-peer and provide application agnostic connectors.

If you are comfortable with Scala and think it fits well for your project go for it. There are some frameworks like Lift or Play with which you can start quickly a web app.

Did you install mongodb ?

Thank you, README is good now.

Yes, I had the same problem. Ponyo (example application) code on github can give you some hints, I tried to make things clean and as light as possible. https://github.com/gelnior/ponyo

For client-only JS applications, have a look at Brunch framework. It is really good to structure your app (Ponyo client side is based on it). http://brunch.io/

Before doing BDD, like you I was working on backend first. Since I experiment BDD, when I work on backend, I have switched my mind from "what could be useful ?" to "what is really needed ?". Writing UI first helps me to find the answer.

I am not sure that writing UI first is a common practice, but it fits good with development of web application which relies a lot on UI.

I emphasize it because Git changed a lot my workflow since I use it. Before that I was a SVN user and I commit only once I finished a feature (or sometimes several features...) and I almost never did any branching either. Perhaps that saying DVCS instead of Git would have been better.