*Background* At present, the issues (bug) tracking facility for the following XMLGraphics projects make use of the Apache Jira Service <https://issues.apache.org/jira/secure/Dashboard.jspa>.
- batik <https://issues.apache.org/jira/issues/?filter=-4&jql=project%20%3D%20BATIK%20ORDER%20BY%20key%20ASC> - commons <https://issues.apache.org/jira/issues/?filter=-4&jql=project%20%3D%20XGC%20ORDER%20BY%20key%20ASC> - fop <https://issues.apache.org/jira/issues/?filter=-4&jql=project%20%3D%20FOP%20ORDER%20BY%20key%20ASC> - fop-pdf-images <https://issues.apache.org/jira/issues/?filter=-4&jql=project%20%3D%20FOP%20AND%20text%20~%20%22%5C%22fop-pdf-images%5C%22%22%20ORDER%20BY%20key%20ASC> (*) (*) Issues for the fop-pdf-images project (repository) are presently tracked in the fop Jira project. *Proposed Change* With the recent migration of XMLGraphics projects from Subversion to Git (via GitHub/GitBox) and upcoming changes to Apache's use of Jira, it is now desirable to enhance the integration among project repositories and their associated issue management service. Accordingly, it is proposed that the issue management of XMLGraphics projects be migrated from Jira to GitHub Issues <https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues> . *Visible Effects* The primary end-user (i.e., project developer and committer) visible effects of the proposed change are as follows: - Existing XMLGraphics project Jira issues will be imported into their associated GitHub repository as GitHub issues, where each imported issue will be bidirectionally linked with its corresponding source Jira issue. - Upon completion of importation of issues into GitHub, the XMLGraphics Jira projects will be marked as read only. - New, post-import issues will be created in GitHub. *Voting* Voting starts now, 2028-04-28 12:00Z, and ends at 2023-05-05 17:00Z. Lack of a vote from a member or contributor will be recorded as +0. Regards, Glenn Adams
