Do something about the OSPR survey
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the OSPR bot behavior and the linked openedx-webhooks pull request #253, along with issues or changes #299 and #301. A maintainer must first decide whether to recreate and continue the survey or remove the survey functionality; done means implementing that decision and updating the survey link or bot behavior accordingly.
Written by the indexing model from the issue text.
Description
Background
OSPRs, when closed or merged, ask the author to fill out a survey: https://github.com/openedx/edx-platform/pull/33204#issuecomment-1711606520
- Fortunately, we still have access to the data, and it's still coming in (private Google Sheets link): https://docs.google.com/spreadsheets/d/15qkfy2Df2TjggKg1pYExZzaEyhN0ac3_Wx36rogUYJM/edit#gid=104229719
- As of right now, we're not using the data.
- We don't have admin access to the form itself. It's probably in the retired edX Google account. @nedbat confirmed that 2U IT could not recover it.
Questions & tasks
- Do we (Axim, or maybe a working group) want to keep doing the survey?
- If yes ->
- Re-make the survey in Axim's Google account, and then update the OSPR bot with the new survey link.
- Revert #299
- Revert #301
- Think: How should we use the results?
- Note: if anyone except Axim can see the survey data, we should make that clear in the survey.
- If no ->
- Remove the survey functionality from the bot. We had started doing this but stopped once we found the survey data
- If yes ->
- Dominant language
- Python
- Stars
- 13
- Forks
- 22
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 6
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openedx/openedx-webhooks
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
openedx/openedx-webhooks#469 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
openedx/openedx-webhooks#391 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
openedx/openedx-webhooks#319 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
openedx/openedx-webhooks#312 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
openedx/openedx-webhooks#285 ·
Maintainers usually reply within 1 day
All issues in openedx/openedx-webhooks
Similar issues
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·
-
Internal ErrorOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
frappe/frappe_docker#2071 ·
Maintainers usually reply within 1 day
-
bug python
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
traceloop/openllmetry#4717 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
The-Pocket/PocketFlow#161 ·
-
comp/desktop P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#157702 ·
Maintainers usually reply within 1 day