If github is source... how do we handle issues?

[pirog]

We have talked about how best to handle this internally at Kalamuna but wanted to get your thoughts on the subject.

As you know we are very keen to move our D.o project to github but one tough issue ... is handling issues.

Ideally we'd like people to just use the github issue workflow and not d.o. You could turn issues off on d.o and direct people to github for issue handling but this is not 100% clear or obvious.

You could also turn issues from d.o into issues on github using something like https://zapier.com/zapbook/gmail/github/72/create-github-issue-email/ or another mechanism.

Any insight or vision here?

[helmo]

Turning off issues on D.o is a bad thing as it makes old issues very hard to find. For Drush I lobbied to get it re-enabled.

[pirog]

@helmo thanks for the insight here... and i agree re: old issues.

We have some new projects where we can probably get away with closing issues but old projects.. not so much.

[jonpugh]

This is a tough nut to crack. I'd say leave it up to developers to decide if they want to switch issue queues as well as code repos.

Unfortunately there is no right answer here.

[pirog]

I'm going to just say F it for right and turn off issues on a couple d.o projects with a request to post on github just to see what happens.

[jonpugh]

Hey, @pirog can you see this page?
https://github.com/organizations/drupalprojects/dashboard/issues/repos

It is the organization-wide issue list. Not sure if a non-owner can see this.

[jonpugh]

I see, the organization-wide issue list doesn't have things like tags. But that's not so bad.

[pirog]

@jonpugh yes! i can see it!