Just going to state the obvious, an option is to hook into JIssues. It has internal project management abilities to tie in to additional repositories. The only admin requirement is that @jissues-bot has admin access to do all the things that the app can do now with the CMS tracker.

I think small projects can be directly handled from github. I don't see the problem on decentralising issues. That's what we are trying to do

For me it is 50/50 situation. From one side I agree with @mbabker to handle "Extras" under JIssues and have centralized bug handling process. From the other side I agree with @phproberto - small projects can be directly handled from GitHub, cause they do not need such a heavy bug workflow process like for the CMS. Anyway we definitely need to provide as much info as possible and point users to the right direction when submitting bugs. May be some notable alert messages or banners.

My concern is mostly about how to "funnel" users of these extensions to the right place, whatever the right place is going to be. I don't have a good answer for that yet.

Yeah that is one of the main problems... Since we can't show any additional info on the GitHub during bug submitting we can expect many open tickets related not to the CMS, but to the Extras. May be social media is the key? Constantly providing info about the changes we can "funnel" users of these extensions to the right place.

I see no problem with directing everyone to the tracker and saying "select the project that you want to contribute to from the drop down list"

It has GH integration, so no problem there if someone doesn't want to use the tracker. But in the long run easier for contributors, IMO.

Sent from my iPhone

On Apr 9, 2014, at 1:50 AM, Dmitry Rekun notifications@github.com wrote:

Yeah that is one of the main problems... Since we can't show any additional info on the GitHub during bug submitting we can expect many open tickets related not to the CMS, but to the Extras. May be social media is the key? Constantly providing info about the changes we can "funnel" users of these extensions to the right place.

—
Reply to this email directly or view it on GitHub.

I see no problem in that either Don. It guess it's more of a communication problem.

So @dongilbert you are for the centralizing it inside JIssues?

Yes. I think it makes the most sense.

Sent from my iPhone

On Apr 9, 2014, at 2:14 AM, Dmitry Rekun notifications@github.com wrote:

So @dongilbert you are for the centralizing it inside JIssues?

—
Reply to this email directly or view it on GitHub.

Closing issue. Centralise bugs with JIssues.