-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Curation #150
Comments
🍔 |
@Arf375 thanks for the work so far! Some thoughts:
In general, we need to think more and more about how we can use public review systems, transparent profiles, and a high-bar to entry in order to ensure quality. We can't get into any process that is too onerous. Scalability is huge here. Note: Eventually, it might be possible to do some identity verification. |
2 cents: I was originally on board with the "safeness of location" checkbox, but I'd like to think that organizers entering requests are intelligent and reasonable people. Also, we don't want the anchor taking any liability, so it's on the organizer. |
Okay @Arf375 and @timothyfcook, I set up a "Getting Started" guide that overviews objective, curation, and guidelines here: 33e93d0 It is linked from our website's home page and our repo's README.md. Please let me know if your have any comments on it. Otherwise, we can close the issue. |
(Tim, I addressed some of your bullets points concisely in that doc) |
Closing! We can revisit this closer to a public launch, maybe after we get feedback from real users. |
awesome |
Curation Process
The following steps are to be performed by the Anchor Advisory Panel and optional crowd-sourcing.
#0. End-user Pages
Jr/rails bootstrap #1. Identify
Adds Gemfile.lock from bundle update #2. Gather
Adds postgresql #3. Review
Reviews inbound local learning opportunity instance requests (via manual consumption of existing opportunities and by virtue of marketing) on the admin dashboard.
Checklist:
...if criteria is met, add the opportunity instance. Else, reach out to submitting organization.
[0] will not apply to our MVP, but these tags will help when we have a universal badge API to support competencies and an associated scale. Matthew/Addison working on a mockup in the universal badge api repository
The text was updated successfully, but these errors were encountered: