[RFC] for-team-members: add info on what they are and how to become one #317
Conversation
Probably the team docs sounds fine.
Nope just GitHub access depending on which Github team they are added to and access to Flathub.org moderation (quality, permission etc.). |
| In consequence, they can be seen as the auditors and moderators of our | ||
| community. As such, they play a big role in the decision-making process. | ||
| They are also an important part of the Flathub and Flatpak trust model. The fact | ||
| that applications permissions are audited by the community is a warranty to |
There was a problem hiding this comment.
| that applications permissions are audited by the community is a warranty to | |
| that application's permissions are audited by the community is a warranty to |
There was a problem hiding this comment.
"by the community" - maybe "by the moderators"?
There was a problem hiding this comment.
I guess it's up to you if you want to use one or the other. Applied the suggestion, but keep this open for the community/moderators discussion
| ## Becoming a team member | ||
|
|
||
| Since auditing apps and permissions is a great task, we are always in need of | ||
| more hands. If you want to be part of our team, help out and enjoy the benefits, |
There was a problem hiding this comment.
There are not many "benefits" so as to speak of #317 (comment)
| * Review current apps to request and update permissions access. | ||
| TODO: Is there a public place where this is done that people can contribute | ||
| to? Or maybe just look at some existing apps? |
There was a problem hiding this comment.
This is going from repo to repo right now and there is no easy way to figure out what to report unless you are a user of the app and notice something.
A better thing to add would be just contributing in general: doing runtime updates, contributing to infra related repos, doing app updates, anything.
I'd avoid making the process too complicated.
pabloyoyoista
force-pushed
the
becoming-a-team-member
branch
from
9bfe5a6
to
a915a59
Compare
|
Pushed most of the comments, left open those that probably need more feedback or are in the TODOs |
pabloyoyoista
force-pushed
the
becoming-a-team-member
branch
from
a915a59
to
23553d6
Compare
| TODO: For how long should have people contributed? How many apps should they | ||
| have reviewed? |
There was a problem hiding this comment.
I think not putting any limit is better. The current team can decide on case by case basis.
| to? Or maybe just look at some existing apps? | ||
| * Open an issue in the [flathub](https://github.com/flathub/flathub/) repo, | ||
| listing your contributions and why you want you become a member. | ||
| TODO: Maybe in the flathub repo? An issue template could help? |
There was a problem hiding this comment.
First todo seems done. Just needs the issue template if we decide on that. We aren't that big on having issue templates but I don't mind either way.
pabloyoyoista
force-pushed
the
becoming-a-team-member
branch
from
23553d6
to
bf95772
Compare
|
Applied all suggestions regarding the wording, kept those related to TODOs as I guess you need to discuss that among yourselves and not with me :D And if I didn't say it before, thanks a lot for the reviews! Certainly my writing style is not the best |
This is written from an external contributor point on view, as we discussed this during FOSDEM that you could get help with a process to get people onboarded into the team. I come from a bit of a different background, so might totally be that this is not what you want, and I'm very happy to iterate or help you do it.
I think one thing missing would be to list the current team members somewhere, but certainly I do not know which place should that be. Also, are there any other benefits you get from being a team member? In postmarketOS we give people an inbox, for example, but that's also because it's sort of needed. Just wondering because some of those small things sometimes motivate people when they're already thinking about it.