I didn’t follow very closely what Cristoph and Danielle did, do you @blipp / @bogdan-kulynych / @tommy39 if we can start using what they produced?
Discussing again about the mailing list
This message was deleted
I would say we create a Google Group for when we have the need, since many people will prefer it to keep up to date
So, summarizing. What do you think of this?
GitBook for theretical docs
ReadTheDocs for tecnical docs
GitHub issues as a tecnical forum as well
Gitter for quick chit chat
Google Groups as a mailing list for when we have the need for some other discussion
Project website as the main hub that showcase what we aim for, where we are at, and a hub that links to all the other sites and communication channels
if you give me green light I’ll communicate it to the mailing list of the hackathon and we abandon it for brighter shores (Google Groups :P)
and I create the accounts
I’ll be waiting for your feedback guyz
Daniele wrote the technical description which is now online on blindstore.github.io
For Cristophe, I'm not sure, will ask him on email
I'm totally fine with Google groups
+1 for a Google Group, we absolutely need a mailing list. Let's call it blindstore ;) And invite everyone from the Webfest as well.
+1 for GitBook.
+1 for ReadTheDocs. I think it is good to have the documentation of the software and the general documentation separated, as people might want to read only one of them, because they are only interested in the software or the principle
+1 for GitHub issues.
+1 for Gitter, this is really flexible, as IRC people still can use their existing infrastructure, like bouncers
+1 for how you describe the project website
Christophe worked on a part of the “theoretical documentation”, he uploaded it to the SharePoint: the use cases, the attacks, a malicious Blindstore server could carry out (I am not sure if he really wrote this down, if not, it should be done, because these were really important thoughts).
Another thing concerning GitHub issues: I was investigating how we can make them more comfortable. I was recommended to have a look at tools like Trello, https://www.zenhub.io/ and Asana. They provide a better overview on issues and integrate more or less with GitHub issues. Asana somehow doesn't look like the right thing as it does more than issues, and zenhub.io is only for Google Chrome right now. But I really want to try out Trello. Maybe this makes it easier to navigate through issues. As it completely integrates with GitHub, it's no problem to try and if it's not what we need, we can just drop it without loosing data. So, as far as I see it, this could just be a nicer view on the issues. I think I'll create an account an try how it works. What do you think?
Zenhub looks amazing!
We have been using Asana at work for some time, but since we moved the issues to GitHub we are barely using it
In our case, I don't know if we need to overcomplicate the task management
Are really milestones and labels not enough for us?
I'd go for Zenhub, if any, as it doesn't get in the way and is completely optional