Hi all,
The move to GitHub source and PRs was IMO a success: it was simple enough to carry on; and some new people have contributed since then. We'll never know if the move to GitHub was a trigger for those new contributions, but I have some belief it does.
So what about the next step: moving to GitHub issues?
I'd like to start this discussion to first know whether there is a majority of committers who think going to GitHub issues would be profitable (count me as one of them).
And then, we need to find what the best implementation would be. One proposal would be that we start opening GitHub issues right now and start using it. we comment all open issues with "m2e has moved to GitHub issue tracker. If this issue is still happening on latest release and is still relevant to anyone, please create a new ticket to
https://github.com/eclipse-m2e/m2e-core/issues with title being the title of this bug and description containing a link to this bug"; and then we close them all and ask webmasters to make the bugzilla component read-only.
What do you think?
