These are notes from the FreedomBox Social Hack call on January 9, 2016.
The big theme of course is that FreedomBox provides has so many different uses cases and (happily) works on so many different kinds of hardware it can be overweljming to new users. The discussion was about trying to figure out how to present the project to new people without scaring them off with too much information.
- Not scaring people off with too much information has to be balanced with accurately portraying the level of flexibility a Freedombox provides. Basically we want people to understand how easy a freedombox is to use, but we don’t want to undersell the features or flexibility a freedombox provides.
To that end we talked about providing clear instructions for getting a FreedomBox up and running on a Raspberry PI, and for those people who wanted a hardware stack that is more powerful and free OLinuXino (or something similar.
We also want present clear instructions on how to get a FreedomBox up and running using a feature that is likely to have wide apeal and is well supported. Some suggestions were ?OwnCloud which appears to be widely used. A second use case might be Mumble or Privoxy. Both are well supported and work "out of the box."
- To illustrate the additional flexability the Freedombox provides we are going to brainstorm other features or roles that Freedombox can provide on the mailing list. The idea would be to present the range of features a freedombox offers in a visual way that illustrates the possibilities.
- There was general agreement that the concepts presented in Sunil's proposal should also be included too. (please add Missing link). The trick is going to be to include it all together.