forked from toolshed/docs.coopcloud.tech
docs: 22, 23 passed
This commit is contained in:
@ -1,28 +0,0 @@
|
||||
---
|
||||
title: "Resolution 022"
|
||||
---
|
||||
|
||||
- Topic: Ammar joins the Co-op Cloud Federation
|
||||
- Date: 31-08-24
|
||||
- Deadline: 14-09-2024
|
||||
- Size: Large
|
||||
|
||||
### Summary
|
||||
|
||||
> @ammaratef45:matrix.org
|
||||
|
||||
[@ammaratef45](https://git.coopcloud.tech/ammaratef45) is a software engineer and has:
|
||||
|
||||
- Used Co-op Cloud for self-hosting libre apps.
|
||||
- Advocated for self hosting in his community in Seattle.
|
||||
- Participated in [https://matrix.to/#/#coopcloud-tech:autonomic.zone](our community) chats.
|
||||
- Some small contributions/fixes/bug reports for some Co-op Cloud stuff.
|
||||
- Published an abra recipe for photo prism.
|
||||
|
||||
### Details
|
||||
|
||||
I, Ammar Hussein, believe in the vision of Co-op Cloud and been invested in the
|
||||
success of similar initiatives. I would love the opportunity to fomrmally
|
||||
become a member of the federation and happy to contribute membership dues.
|
||||
|
||||
[Be Water](https://bewater.contact) is happy to vouch.
|
@ -1,51 +0,0 @@
|
||||
---
|
||||
title: Resolution 023
|
||||
---
|
||||
|
||||
- Topic: Feedback gathering and content architecture for the new Co-op Cloud website
|
||||
- Date: 04-09-2024
|
||||
- Deadline: 18-09-2024
|
||||
- Size: Large
|
||||
|
||||
### Summary
|
||||
|
||||
There is general interest in a new public-facing website for Co-op Cloud which can:
|
||||
|
||||
- Motivate new helping hands to join in
|
||||
- Attract diverse funding for the project (which is not based purely on technical implementation)
|
||||
|
||||
It hasn't been reworked in quite some time (guestimate: 2 years).
|
||||
|
||||
This proposal describes a way to do this and includes a budget for doing so.
|
||||
|
||||
### Details
|
||||
|
||||
The current state of the splash page consists of the following contents:
|
||||
|
||||
- **Introduction** (Broad explanation)
|
||||
- **Benefit** (Why use it)
|
||||
- **Frequently Asked Questions**
|
||||
- **Groups which use it**
|
||||
- **Involved groups and funders**
|
||||
|
||||
The goal would be to collect feedback from the community and compile it into different requirements and tasks.
|
||||
|
||||
We believe the first 2 tasks to get started are as follows:
|
||||
|
||||
- **Collect feedback**: Create forms or markdown based questionares and motivate members, users, enthusiasts to answer these.
|
||||
|
||||
- **Content architecture**: Design what is written where and why so that visitors can quickly grasp the big picture and get excited about it.
|
||||
|
||||
Once feedback and architecture work is wrapped up, we're in a good place to work on the remaining tasks: copywriting, design and finally, the frontend development work. More proposals will follow.
|
||||
|
||||
## Budget
|
||||
|
||||
Budget details:
|
||||
|
||||
| Item | Cost | Who? |
|
||||
| ---- | ---- | ---- |
|
||||
| Feedback | 8 hours | `@kimble` |
|
||||
| CA/UX | 10 hours | `@kimble` |
|
||||
|
||||
|
||||
**Total: 18 hrs * 20 EUR = 360 EUR**
|
Reference in New Issue
Block a user