Add docs on "Becoming a Flathub Team Member"#606
Conversation
Deploying documentation with
|
| Latest commit: |
f1d0a67
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bc7488ad.documentation-962.pages.dev |
| Branch Preview URL: | https://bbhtt-team-members.documentation-962.pages.dev |
| basis and may take additional factors into consideration and may be | ||
| denied. | ||
|
|
||
| ## Membership Criteria |
There was a problem hiding this comment.
We need to decide on some criteria for "Quality Moderation team" as well. Someone needs to give me something to put in similar style.
There was a problem hiding this comment.
i will add the following criteria to move this forward if it doesn't get a reply:
general knowledge / awareness about the linux app ecosystem, experience in app design, ui/ux and familiarity with Flathub guidelines.
|
|
||
| ## Team Membership Process | ||
|
|
||
| Please open an issue in <INSERT META REPO> linking relevant activity |
There was a problem hiding this comment.
decide where to process these.
There was a problem hiding this comment.
Can stay in flathub/flathub if we want to run this in the open.
There was a problem hiding this comment.
Yes it definitely should be in the open.
This was mainly about a flathub-meta repo here or using flathub/flathub.
If we set up some automation for this having a dedicated repo will help re tokens etc. and managing the volume of unrelated issues being opened and notifications etc..
We can automatically close spam issues too.
There was a problem hiding this comment.
Unless there are objections I will create an empty flathub-meta repo here and link to that.
We can do automation later if it becomes necessary but for now anyone should subscribe to it.
| maintenance efforts with adherence to proper maintenance practices. | ||
| * Familiarity with Flatpak, Flathub workflows, and related tooling. | ||
|
|
||
| ### Build Moderation Team |
There was a problem hiding this comment.
or we just implicitly make all reviewers members of that? I never thought of this as a separate team
There was a problem hiding this comment.
ok we can do that if someone wants to join.
Continuation of #317