governance issueshttps://dev.funkwhale.audio/funkwhale/governance/-/issues2019-08-22T08:38:46Zhttps://dev.funkwhale.audio/funkwhale/governance/-/issues/1Adopt a Code of Conduct (and decide how we enforce it)2019-08-22T08:38:46ZAgateAdopt a Code of Conduct (and decide how we enforce it)I think it's a required step to ensure everyone feels safe and welcomed in the community. We have to think about common issues that can arise between members, and how we want to tackle them.
There are probably a lot of CoC out there we ...I think it's a required step to ensure everyone feels safe and welcomed in the community. We have to think about common issues that can arise between members, and how we want to tackle them.
There are probably a lot of CoC out there we can get inspiration from.
As I have no prior experience in choosing a CoC and enforce it, I'd really appreciate any input about this, especially from people who beneficiate from such CoC: what do you expect from a CoC? What is mandatory?https://dev.funkwhale.audio/funkwhale/governance/-/issues/2Appoint moderators/community managers for the discussion spaces2018-12-06T08:36:47ZAgateAppoint moderators/community managers for the discussion spacesWe have a few spaces for the community :
- The Funkwhale Community and rooms on Matrix.org (https://riot.im/app/#/group/+funkwhale:matrix.org)
- The Gitlab group and projects (https://code.eliotberriot.com/funkwhale)
- Mastodon's Funkw...We have a few spaces for the community :
- The Funkwhale Community and rooms on Matrix.org (https://riot.im/app/#/group/+funkwhale:matrix.org)
- The Gitlab group and projects (https://code.eliotberriot.com/funkwhale)
- Mastodon's Funkwhale account (https://mastodon.eliotberriot.com/@funkwhale)
In the future, a dedicated forum or long-lived discussion space could also be set-up.
There is no real community management and moderation position right now: I'm doing most of it, and some people also answer newcomers on the Matrix rooms. Having one or more dedicated people for this task would help considerably to:
- Ensure everyone is given a warm welcome
- Redirect users to the proper rooms/documentation/repositories for their questions
- Adress possible CoC violations, if needed (see #1)
This is not necessarily a really time-consuming job, given the small size of the community, but this would really help reducing the load (and the power that goes with it) on me.https://dev.funkwhale.audio/funkwhale/governance/-/issues/3Write a mission statement for Funkwhale2018-06-10T14:35:43ZAgateWrite a mission statement for FunkwhaleThis should be a concise and clean document we can refer to when we need to know about:
- What is Funkwhale?
- What is *not* Funkwhale?
- Why does Funkwhale exists?
- What problems do we want to solve?
I'll try to put some ideas togeth...This should be a concise and clean document we can refer to when we need to know about:
- What is Funkwhale?
- What is *not* Funkwhale?
- Why does Funkwhale exists?
- What problems do we want to solve?
I'll try to put some ideas together and write a basic draft we can iterate on.AgateAgatehttps://dev.funkwhale.audio/funkwhale/governance/-/issues/4Investigate alternative products/solution for project management2019-08-22T08:38:55ZAgateInvestigate alternative products/solution for project managementWe can't do anything on Gitlab as it's not really intended for that. Someone mentionned Loomio, which seems to be a great product: https://github.com/loomio/loomio (and self-hostable).
Possibly needed features include:
- take decisions...We can't do anything on Gitlab as it's not really intended for that. Someone mentionned Loomio, which seems to be a great product: https://github.com/loomio/loomio (and self-hostable).
Possibly needed features include:
- take decisions together
- meeting notes
- polls
- messaging (although we may use a dedicated channel for that)
- ?https://dev.funkwhale.audio/funkwhale/governance/-/issues/5Meeting 1: organization / discussion2018-12-06T08:34:36ZAgateMeeting 1: organization / discussionAs discussed recently (and suggestd by @troll), we're going to have a meeting to discuss about Funkwhale development, roadmap, organization, etc.
To ensure this meeting is productive, I'd like to set a few goals and targets:
- The meet...As discussed recently (and suggestd by @troll), we're going to have a meeting to discuss about Funkwhale development, roadmap, organization, etc.
To ensure this meeting is productive, I'd like to set a few goals and targets:
- The meeting will take 1h, at most, and ttake place on Riot/Matrix, using the audio feature, or on Jitsi
- The goal of this meeting is to gather Funkwhale community, get to know each other, and synchronize around the project
- Prior to the meeting, an agenda will be built and shared publicly, and anyone will be able to submit discussion topics
- Priori to the meeting, a Doodle / framadate will be shared publicly to ensure we pick the best possible moment for the meeting
Content
-------
1. At the beginning of the meeting, someone will be named moderator for the duration of the meeting, and responsible to go through the agenda, animate the discussion and ensure the discussion is productive. A different person will also be responsible to take notes of the discussion
2. During the meeting, we'll go through each agenda item and discuss, 10 minutes before the end of the meeting, we'll keep an open moment for attendants to ask questions and discuss topics that were not covered in the agenda.
3. After the meeting, notes will be edited and shared publicly
As a rule of thumb for topics put in the agenda, we should focus on high-level, non-technical items. This is *not* a meeting about Funkwhale's UI, software or bugs. It's a discussion about the project, its roadmap, community, events, goals, values, etc.
Examples of relevant discussion topics:
- Should we appoint moderators for the community spaces, and how?
- How can we make it easier for people to join the community?
- What should be the short-term, mid-term, long-term roadmap?
- How do we finance the project?
- What have been done by contributors in the last month?
About language
--------------
Ideally, every discussion could occur in english, however, this is not practical for everyone. The first meeting will occur in french, as it's the language the most used by Funkwhale contributors. However, notes and agenda will be published in english, and we'll discuss about a long-term solution for this.https://dev.funkwhale.audio/funkwhale/governance/-/issues/6Migrate to a dedicated gitlab instance2018-12-10T19:59:20ZAgateMigrate to a dedicated gitlab instanceI'm going to migrate Funkwhale's codebase and repositories to a dedicated GitLab instance very soon. We're currently using `code.eliotberriot.com`, which is my personnal instance, and as the project grows, it becomes less and realistic t...I'm going to migrate Funkwhale's codebase and repositories to a dedicated GitLab instance very soon. We're currently using `code.eliotberriot.com`, which is my personnal instance, and as the project grows, it becomes less and realistic to keep it on my tiny Gitlab instance.
I've rented a dedicated server and spin up a VM to host the new Gitlab instance, which will be available at https://dev.funkwhale.audio. Code.eliotberriot.com will remain available
The migration workflow will be:
1. Stop code.eliotberriot.com
2. Backup code.eliotberriot.com
3. Restore the backup on dev.funkwhale.audio
4. Start dev.funkwhale.audio
5. Restart code.eliotberriot.com
At this point, we'll have a fork: two instances with the same database. People will be able to login on both instances. Then:
6. Setup a redirection from https://code.eliotberriot.com/funkwhale to https://dev.funkwhale.audio/funkwhale
7. Add a warning / description on code.eliotberriot.com to inform people about the migration
8. Close signups on code.eliotberriot.com
9. Add CI servers on dev.funkwhale.audio
10. Ensure emails are working
11. Ensure oauth on weblate is working from dev.funkwhale.audio
12. Ensure login from GitLab.com / Github is working properly
13. Ensure pages for Funkwhale project are served properly
14. Update all references to code.eliotberriot.com to dev.funkwhale.audio (documentation, contribute guides, readme, website, etc.)
15. Ensure backups are working
I've already tested steps 1 to 5 (which is why you can see a server up at https://dev.funkwhale.audio), so I'm pretty confident this will work :)AgateAgate2018-12-10