8 votes

Topic deleted by author

2 comments

  1. [2]
    Deimos
    (edited )
    Link
    Thanks as always, Bauke! I was thinking about asking this on GitLab (or maybe just to you and @cfabbro directly since it'll probably be mainly the two of you that care), but maybe this is a good...

    Thanks as always, Bauke!

    I was thinking about asking this on GitLab (or maybe just to you and @cfabbro directly since it'll probably be mainly the two of you that care), but maybe this is a good place to do it instead:

    As I mentioned, I'm going to do a full pass through all the issues soon, so this is a good opportunity to move over to a better system for labeling and categorizing them. What do you think we should do differently? These are a few specific things I want to decide:

    • Should some of the current labels be eliminated or replaced?
    • Should we use the "Weight" field as complexity, or priority? And what range (1-5? 1-3?) should we use for it?
    • Should we do something special to try to highlight issues that might be good candidates for people that want to try contributing to the open-source code, or could a combination of priority and low complexity handle that?
    • Do you think we should try to label which technologies will be involved in each issue, so that people can look for python-only ones, js-only ones, etc.?
    6 votes
    1. [2]
      Comment deleted by author
      Link Parent
      1. cfabbro
        Link Parent
        All that sounds like a good idea to me too, @deimos... although "good first issue" is a bit of a mouthful and if we're going to use weight for complexity, it's a bit redundant. The only other...

        All that sounds like a good idea to me too, @deimos... although "good first issue" is a bit of a mouthful and if we're going to use weight for complexity, it's a bit redundant. The only other suggestion I can think of is adding a "meta" label too, which is something we are lacking.

        2 votes