Page History

...

Github + Git	JIRA + Git
Less suited for project management reports (lack of dashboards etc per current setup of the report - Not easy for potential adopters to get a feel of the project) INFRA is required for every workflow change to GITHUB requires additional plugins to do stuff (ref #4) Legacy tools need to be kept (for history sake, etc.) Current setup only favours privileged contributors to participate in workflows.	Loosely coupled integration between JIRA+GIT

Questions and Answers

Things to check and clarify.

Question	Answer
1. What will be the process to give permissions to contributors on GitHub after they have filed their ICLA? see https://ofbiz.apache.org/getting-involved.html
2. How do we control the permissions for committers and contributors on GitHub?
3. What do we offer for contributors who are not able or willing to maintain their own repositories and follow the PR process? It is relatively easy to clone the official repo, change and create a patch through git diff but it might be a hurdle for people to take all necessary steps for the PR process.
4. When we publish a new release we update Jira versions to reflect the change. This information is useful to group Jira tickets by version. Is there a similar feature in GitHub?
5. Has GitHub tools alike elaborated search in Jira, e.g. with filters? Can existing filters/views be migrated from Jira to GitHub?