-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
Make bug tracker more accessible for newcomers #1077
Comments
cc: @MSanKeys963 (on his return from ⛰️) Thanks for the suggestions, @Saransh-cpp. We're definitely in a period of cleanup. If there are any issues that you have suggestions for labels/prefixes, feel free to let us know. (For GSoC, e.g., I spent some time updating help-wanted) Alternatively, if you want to open a PR for the YAML config or anything to help us along, it'd be very welcome. All the best, |
Thanks for the quick reply, @joshmoore! I'll definitely take up some work here! |
@joshmoore @Saransh-cpp I would like to work in this issue.Kindly assign me |
I think this has already been completed @h20200051. Apologies if you were misguided. Let me know if you want to work on another issue, and I'm happy to help you. |
Respected sir,
I would like to work under the issue of expose chunk and or slice
imformation (byte offse) and size to tje api and make it available to the
user #1113.Kindly assign me this
Github id:h20200051
…On Mon, 12 Sept 2022, 04:16 Sanket Verma, ***@***.***> wrote:
Closed #1077 <#1077>
as completed.
—
Reply to this email directly, view it on GitHub
<#1077 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2722CACA5OUKP45AYHJ4HDV5ZOL5ANCNFSM53TUUOBQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The issue/bug tracker right now has no labels, and most of the issues don't start with a keyword (example - "BUG: This is not working" or "DOC: Missing docs for this"). Therefore, newcomers have a hard time navigating through the issues, which discourages them from contributing.
Ideally, the issue template should be updated (the current one does not use the new
YAML
format), and more issue templates should be added, for example, feature request, CI improvement, etc.The issue can be labelled by an automated workflow based on the template from which it was created, or keywords can be added to the template titles. IMO they should be labeled by an automatic workflow, so that a newcomer can quickly search through the labels!
The text was updated successfully, but these errors were encountered: