Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Discussion: Develop a peer-review process for campaign proposals #15

Closed
CooperSmout opened this issue Sep 16, 2020 · 1 comment
Closed
Labels
discussion Discussion topic about project strategy, direction, etc

Comments

@CooperSmout
Copy link
Member

Is your feature request related to a problem? Please describe.
The number of proposed campaigns is growing by the day, so it could be useful to formalise a peer-review process so that we can (a) strengthen proposals, and (b) choose the most appropriate campaigns to post on the website.

Describe the solution you'd like
Some kind of codified review process, ideally with metrics representing different qualities. At a first pass, these might be:

  • Novelty. How dissimilar is the proposal to other campaigns that have been proposed/posted on FOK?
  • Importance. If the campaign is successful, how beneficial will it be to the signatories and broader community?
  • Community-interest. This could be as simple as counting the number of likes and comments in the Github Issue thread.
  • Clarity. Is the proposed action simple and clearly specified? Is the target audience and threshold clearly specified?
  • Likelihood of success. What are the chances the campaign will reach the target threshold?
  • Accountability. Can the actions be monitored in some way to check compliance?

Describe alternatives you've considered
Alternatively, we could just post every campaign that gets proposed, see what kind of traction they get, and only leave up those that seem like they're getting community interest. One downside of this strategy is that we miss an opportunity to strengthen campaigns before posting to the website. Another is that we might overwhelm users by giving them too many options and/or dilute our 'brand' by posting poorly-conceived campaigns. I think that in the early days of the project at least, it's probably best to screen campaigns to some extent, and use the Github features to gauge community interest before posting.

Additional context
We'll also need to work out how to source peer-reviewers from the community and allocate them to campaigns

@CooperSmout CooperSmout added the enhancement New feature or request label Sep 16, 2020
@CooperSmout CooperSmout changed the title Developing a peer-review process for campaign proposals Issue: Develop a peer-review process for campaign proposals Sep 16, 2020
@CooperSmout CooperSmout added the help wanted Extra attention is needed label Sep 17, 2020
@dlholf
Copy link

dlholf commented Nov 5, 2020

Alternatively, we could just post every campaign that gets proposed, see what kind of traction they get, and only leave up those that seem like they're getting community interest.

If the campaigns route through the forum first anyway, that might just act as a 'first pass' (as mentioned in the community interest metric). People would likely gravitate towards discussing the campaigns they would like to support and (hopefully) offer suggestions as part of that.

Some kind of codified review process, ideally with metrics representing different qualities.

Would it make sense to work it into the proposal system itself? (i.e., the proposers need to say how each of the qualities are met within the proposal)

@CooperSmout CooperSmout changed the title Issue: Develop a peer-review process for campaign proposals Discussion: Develop a peer-review process for campaign proposals Dec 2, 2020
@CooperSmout CooperSmout added discussion Discussion topic about project strategy, direction, etc and removed enhancement New feature or request help wanted Extra attention is needed labels Dec 2, 2020
@FreeOurKnowledge FreeOurKnowledge locked and limited conversation to collaborators Aug 31, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
discussion Discussion topic about project strategy, direction, etc
Projects
None yet
Development

No branches or pull requests

2 participants