minor: start issue fetching

[nrmancuso]

python script to assign us randomly to review, and add “in review” label to allow filtering

[romani]

random is not ok, It imply that all reviewers are guaranty availbale.
opensource(at least in CS) is not a work, we are not available. I would rather have explicit assignments, as singnal that reviewer is taking responsibility on it and will track it.

is this is just a poc of some strategy - ok.
if you targeting this to CS, lets discuss.

[nrmancuso]

is this is just a poc of some strategy - ok.
if you targeting this to CS, lets discuss

We already discussed this at length during our summit, and agreed that we would randomly assign up to 20 open, unapproved issues at a time to begin to cut down our backlog.

[romani]

I was assignments for backlog issues review and reevaluation, but for this we don't need script.

[rnveach]

No one is going to want to assign 800 issues manually and once we start closing some page counters won't be accurate. We did talk about automation this and just do 20 each.

[romani]

There is bulk operations in GitHub

I can assign to both of you page of issues in few seconds.

In your repo you can do all that you what.
But assigning last page to me, page before to you, page before to rnveach. Is matter of 1 minute.
If we find time to finish this assignments, huge effort by the way, we can continue by pages further. I see no reason in overassignmets.

[nrmancuso]

I am not sure why you are back tracking on the agreement we had, but if you want to repeatedly manually assign each of us to 20 issues and apply labels, go for it.

[romani]

main part of agreement was to set labels and close PRs that abandoned and we see no value to keep to let others to finish.
thats is still very good goal.

and add “in review” label to allow filtering

as soon as PR is created it is "in review" without any label. I am no sure what value "in review" will add.