Determine issue management process

[kuwv]

Overview

This project is a fork of Mozilla/Red Hat Python-NSS project. VCS and issue management was previously managed by Mozilla but not fully supported. How issue management will be conducted and where specific issues will be addressed needs to be decided.

Acceptance

Decide which issues will be handled on GitHub if any. Decide which issues will be handled on Bugzilla if any.

Decision 1:

• No issues are handled on GitHub
• All issues are handled on Bugzilla Pros:
• One place for everything
• Direct interaction with NSS team Cons:
• Less community interaction between code and issue
• Additional system to interface

Decision 2:

• Development issues are handled on GitHub
• Feature/Maintenance issues are handled on Bugzilla Pros:
• Separation of concerns (respective to ownership)
• Direct interaction with NSS team Cons:
• Confusion between where to contribute
• May require additional automation
• Additional system to interface

Decision 3:

• All issues are handled on GitHub
• No issues are handled on Bugzilla Pros:
• No confusion about where issues are handled
• No dditional system to interface Cons:
• No interaction with NSS team
• Somewhat weak project manage tools selection

[kuwv]

@saper What are your thoughts ^^^

I'm leaning towards our development tools and processes living here. All features related to features between this project and NSS being handled by Bugzilla.