Tracking improvement and document the new popup

[vecna]

[vecna]

[vecna]

possible improvement for the hackathon

1. usability / popup / signup process
2. promotion / explainability / marketing
3. mobilizon integration / improve mobilizon-poster
4. integrate librevent backend into mobilizon docker
5. security assessment
6. if there are event organizer, setup user interview "if we have one tool that with two clicks allow to reshare"

TODO

• we should list the material we need for the hackathon
• how to do promotion

Target of the promotion

1. we should not exclude|forget event organizers even if our target is the technologies
2. because they are the main "user" and final beneficial peoples

should be clarify the three stakeholder
should be clarify two use case or scenarios

[vecna]

TODOs

1. timeline of the hackathon, how would be divided
2. content of the promotion material
3. for the end a setup instruction on how to build the extension
4. wireframes?
5. in the event divide people by knowledge domain
6. a deliverable on responsabilities
7. a presentation, please contribute here with content ideas https://pad.riseup.net/p/mobilize-berlin-hackathon-2-presentation-TOC

[vecna]

https://twitter.com/_vecna/status/1560306176054665217
https://mobilize.berlin/events/d573f9fd-016a-4859-8410-db6732e86d08
https://mastodon.social/@Disappear_Doc/108844672055412610

[vecna]

Who-Does-What

• @chobeat: timeline of the hackathon (necessary for presentation and promotion)
• me: document how to setup a development box, document what and how things are working now
• joey: setup new mobilizon test box + double check the instruction on mac

[joeypatino]

Some ideas on a new UI for the extension. Questions remain about how to integrate the Server and enabled / disabled status.

https://www.figma.com/proto/sPPmuXegCe4sb16q315lph/librevent?page-id=0%3A1&node-id=4%3A16734&viewport=189%2C402%2C0.28&scaling=min-zoom

[vecna]

thanks, it is pretty nice!

there are two servers:

1. the backend (it can be accessible via "cog" icon, as it is an advanced settings). In the future the backend and mobilizon can be in the same server.
2. the mobilizon server (which seems only to be mobilize.berlin, because that appears in the header), so perhaps is also where we can handle the click to change it?

Still, FYI, I can't do such changes, I'm not that good with Material UI / CSS. But it is the kind of specifications might find traction at the hackathon