userli

[t2d]

Project Lead: t2d

Mentor: triaslucia

Welcome to OL7, Cohort A! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training :tada:.

---

Before Week 1 (Jan 29): Your first mentorship call

• [x] Complete the OLF self-assessment (online, printable). If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
• [x] Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (Feb 5): First Cohort Call (Open by Design)

• [x] Complete Assignment 'Write Your Vision or Mission Statement'. Leave a comment on this issue with your draft vision statement & be ready to share this on the call.
• [x] Watch 'Mozilla & Working Open'.
• [x] Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Feb 12): Mentorship call

• [x] Look up two other projects and comment on their issues with feedback on their vision statement.
• [x] Complete your Open Canvas (instructions, canvas). Comment on this issue with a link to your canvas.
• [x] Start your Roadmap. Comment on this issue with your draft Roadmap.

Before Week 4 (Feb 19): Cohort Call (Build for Understanding)

• [x] Look up two other projects and comment on their issues with feedback on their open canvas.
• [x] Pick an open license for the work you're doing during the program.
• [x] Use your canvas to start writing a README, or landing page, for your project. Link to your README in a comment on this issue.

Week 5 and more

• [x] Create a repository for your project. New to GitHub? You can fork our templates.
• [x] Add Contributing Guidlines
• [x] Add a Code of Conduct
• [x] Submit your project to Mozilla Pulse, add the tag #mozsprint
• [ ] Invite new contributors to into your work!

This issue is here to help you keep track of work as you start Open Leaders. Please refer to the OL7 Syllabus for more detailed weekly notes and assignments past week 4.

[t2d]

Vision statement: I'm working with privacy enthusiasts to create a web front-end for encrypted mailboxes. With this system, hackers and server administrators wouldn't have the possibility to read users mails.

[triaslucia]

Hi great that you started! It wuold be nice if you could describe a bit more what ' privacy enthusiasts ' are in this context. From what I understood so far, there is a specific type of 'enthutiasts' that your project need to involves, e.g. concerning tech knowing, isn't it? That'll help both, your team and people not to feel frustrated by not matching each other :)

[t2d]

[annefou]

That's not my topic so my comments/questions are most likely stupid... Your project seems to me very interesting; does your project aim at increasing the number of "Privacy enthusiasts"? I mean do you plan to also explain why it is so important and why it matters; trying to convince those who do not know.

[t2d]

README with License

[foretia]

Vision statement: I'm working with privacy enthusiasts to create a web front-end for dovecot with encrypted storage so end-user don't have to worry about server administrators reading their mail.

I find it very difficult to understand your vision statement, please can you breakdown some of terms for layman understanding

[Botsyoelily]

The vision is a good one. What of if the server administrators reading the mail could avoid hacking attempts since they will be detected by the administrators

[triaslucia]

Great that you did the O.Canvas. Looks way more organized and clear!

I was wondering, Could you explain a bit more on the Unique Value. Why wuold I like to run my own copy of the system? maybe it would be usefull to explain the benefits of Userli , I think there is were actually your UVP is, and its important that "your user" get's it as clear as possible.

[t2d]

Code of Conduct: https://systemli.github.io/userli/development/code_of_conduct/

[t2d]

Persona 1:

Adriana is a systems administrator. She works for an NGO and is tasked to administer a mail server. The NGO has decided, they don't want to be able to surveil their employees and co-workers. Therefore, they look into mailbox encryption. Adriana has some experience with Debian Linux and scripting languages.

Persona 2: Bertha is using a Userli instance. She picked a mail provider that encrypts her mailbox because she values her privacy. She's involved in an environmental campaign and is worried someone might try to access her mail. She tried to use GPG, but has failed. Her fellows didn't share the enthusiasm. So she had no-one to write to. She has no experience with and interest in coding.

[t2d]

does your project aim at increasing the number of "Privacy enthusiasts"? I mean do you plan to also explain why it is so important and why it matters; trying to convince those who do not know.

@annefou Thank you for your feedback. The only plan we currently have, is to motivate users that are already on the platform (for whatever reason) to enhance their security and security. The idea was to provide little steps and nudge users to go them. For example: "Create your first alias address to protect from inter-platform tracking"

[t2d]

What of if the server administrators reading the mail could avoid hacking attempts since they will be detected by the administrators

@Botsyoelily Thank you for checking out this topic. I have trouble understanding your question. Do you think it could be bad to encrypt mail, because the administrator can't check for bad content?

[t2d]

I find it very difficult to understand your vision statement, please can you breakdown some of terms for layman understanding

@foretia Thank you for your feedback. I tried to use a little bit easier wording and shorter sentences. Do you thinks it's better now?

[t2d]

Project Mission & Summary

Userli is a web-frontend that allows to (self-) manage mail users and encrypt their mailboxes.

Milestone Easier Installation (2.1.0)

• Create Ansible Role
• Update install instructions
• public/bundles missing from release

Milestone User Testing

• Conduct three in-person user testing sessions
• Create five simple tasks and let five people try them and messure how much time they took
• What would people like to do with the system or expect it to be capable?

Milestone More security options

• Allow to switch to TLS-only connection
• Incorporate feedback from Milestone User Testing

(atm, we're doing this only with GitHub Milestones, so I'm posting this draft roadmap here directly)