-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix the Issue Tracker section of the README and label issues #32235
Comments
@kdmccormick what are your thoughts on this. I'm reluctant to point people to the edx-platform issues page given that we don't currently monitor the issues for incoming reports from the community and generally ask them to post to discourse instead. We could remove this section, or we provide details saying the issue tracker is used internally by the community and we're not currently accepting bug reports here, or something else? |
Hm, I think long-term we should definitely use the edx-platform issues page and have some system of delegating issues to app maintainers for triage. If we're not ready for that, though, we could just say that edx-platform issues are for internal use, and point the community at Discourse for bugs and feature requests. @jmbowman , as maintainer, which would you rather do right now? |
Arch-BOM plans to soon document and follow an official triage process for GitHub issues in the repos it maintains: edx/edx-arch-experiments#291 . The rate of new issues looks manageable so far, I'm ok with pointing people to GitHub Issues and only reconsidering if the volume becomes a problem. |
Fixes #32235 Ideally, we'd update the whole readme to better match the new maintainers standards and we should still do that but for now we'll just update this egregiously incorrect section quickly.
I made a quick update to correct the issue tracker section: #32354 |
* docs: Update the issue tracker section of the README. Fixes #32235 Ideally, we'd update the whole readme to better match the new maintainers standards and we should still do that but for now we'll just update this egregiously incorrect section quickly. Co-authored-by: Robert Raposa <[email protected]>
* docs: Update the issue tracker section of the README. Fixes openedx#32235 Ideally, we'd update the whole readme to better match the new maintainers standards and we should still do that but for now we'll just update this egregiously incorrect section quickly. Co-authored-by: Robert Raposa <[email protected]>
* docs: Update the issue tracker section of the README. Fixes openedx#32235 Ideally, we'd update the whole readme to better match the new maintainers standards and we should still do that but for now we'll just update this egregiously incorrect section quickly. Co-authored-by: Robert Raposa <[email protected]>
Description
fix the Issue Tracker section of the README., presently it is pointing contributors to the jira page for issue tracking and reporting.
TODO
The text was updated successfully, but these errors were encountered: