You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to Haskell and would like to take on some of the more "beginner" tasks that Corrode has as I learn the language. I see that #94 is marked with the "easy" tag, and is the obvious choice for me to start, but I was wondering if you'd be willing to tag more issues with size and priority labels?
(Shameless plug) I personally like the tagging scheme chosen here https://github.com/awslabs/s2n/labels, and think it would be helpful if Corrode had a roughly similar tagging scheme that expressed the size and the priority of the open GitHub issues in an easy to understand way to newcomers.
size/{small, medium, large}
priority/{low, normal, high}
I would like to attempt some of the GitHub Issues that are on the smaller/easier side but aren't a low priority, but since I'm not too familiar with Corrode or Haskell it is hard for me to make those judgments on my own. I think that tagging more issues with this info would also help others when determining which issues to help with and work on.
The text was updated successfully, but these errors were encountered:
Hello,
I'm new to Haskell and would like to take on some of the more "beginner" tasks that Corrode has as I learn the language. I see that #94 is marked with the "easy" tag, and is the obvious choice for me to start, but I was wondering if you'd be willing to tag more issues with size and priority labels?
(Shameless plug) I personally like the tagging scheme chosen here https://github.com/awslabs/s2n/labels, and think it would be helpful if Corrode had a roughly similar tagging scheme that expressed the size and the priority of the open GitHub issues in an easy to understand way to newcomers.
I would like to attempt some of the GitHub Issues that are on the smaller/easier side but aren't a low priority, but since I'm not too familiar with Corrode or Haskell it is hard for me to make those judgments on my own. I think that tagging more issues with this info would also help others when determining which issues to help with and work on.
The text was updated successfully, but these errors were encountered: