Pilot ready branch

Hey @paulamlb @santisiri @medied

With @LucasIsasmendi we thought that it might be interesting to work on a pilot ready branch of Sovereign.

The idea behing this would be to enable easy customization of Sovereign for the local context that people might use it. Lots of things are already available in the settings.json file, collective name, url etc.

Our idea is to make the geo.json located inpublic/data easy to adapt to a local context by allowing several data structures :

• Universities : Oxford, Cambridge, LSE etc.
• Cities : London, Brighton etc.
• Region : South East, West Midland etc.

What do you guys think ?

[LucasIsasmendi]

@santisiri @paulamlb

I think that for countries we should have a special filter that lists proposals from people of the given country. so vote.democracy.earth/nation/france would list all proposals posted by french members.

The concept of ~scope could help to not only address national debates, also regional and local ones, check the architecture-repo for more details. Example: scope order: ~earth -> ~france -> ~paris -> ~university|neighborhood|club|etc

@AlexJupiter 1000% with Build, Measure, Learn cycle (we need metrics, A/B test, ranking features)

[AlexJupiter]

@santisiri @paulamlb

Aren’t we consolidating pilots on the main instance to prevent silos and harness network effects?

A couple of points on my end in terms of supporting this idea of a pilot ready branch, interested to know what you think:

• Venezuelans will be expected to be interacting with a Spanish product, a branch would allow us to create a Spanish product in a really simple way.
• After scoping out this pilot we will probably find that there will be small changes to Sovereign that will make this pilot more successful, but these changes don’t make sense to be on the main branch.
• By having branches it means that we can experiment on a micro level with the pilots, due to us being able to process the data easier, and then take these successful experimentations and eventually consolidate in the master branch.
• Building, measuring, and learning (and repeating) I think is going to be difficult to do whilst trying to harness network affects, piloted branches might help us move faster in this regard. The cross proliferation between Venezuelans and Stanford Uni students (for example) is going to be small and we might run the risk of good content getting lost in a sea of bad content with how the UX is at the moment. We will get there in time though!