Hi, I can't speak for others, but personally, I have no interest in this. We never asked for a GitHub mirror to begin with. I wonder why infra created these things (without input from the project) if they weren't going to maintain them or at least properly shut them down. If Apache is creating mirrors for Git users that's great for that audience but that's not something we've owned.
Thanks. From: Carsten Pfeiffer <carsten.pfeif...@gebit.de> Sent: September 19, 2022 9:13 AM To: j-dev@xerces.apache.org Subject: [EXTERNAL] AW: Resurrect github mirror of xerces-j Hi, Is the silence to this post just caused by lack of time or is there no interest in the github mirror? IMHO, a broken mirror is worse than no mirror, I'd propose asking infra to either shut down the current broken mirror or let them recreate a new one. I would gladly assist in any way, but they need an official word from a maintainer (just add a comment to https://issues.apache.org/jira/browse/INFRA-23643). Speaking of lack of time -- there is a crucual issue https://issues.apache.org/jira/browse/XERCESJ-1689 (which actually got me here), which is already fixed, but not released. Is there anything I could do to help getting it released? Thanks and best regards, Carsten ________________________________ Von: Carsten Pfeiffer Gesendet: Freitag, 2. September 2022 11:17 An: j-dev@xerces.apache.org<mailto:j-dev@xerces.apache.org> <j-dev@xerces.apache.org<mailto:j-dev@xerces.apache.org>> Betreff: Resurrect github mirror of xerces-j Hi, the xerces2-j github repository at https://github.com/apache/xerces2-j is currently out of sync with the canonical svn repository (see https://blogs.apache.org/infra/entry/subversion-to-git-service-git for the reasons). This wastes time of users/other developers who think that the github repository is in a working state. I've asked apache infrastructure to get the mirror working again, but this needs to be requested from the xerces-j maintainers. So, I would like to kindly ask you, the maintainers, to request this mirror to be activated again. There is already a Jira issue for this at https://issues.apache.org/jira/browse/INFRA-23643 Thanks for your consideration and your work on xerces-j, Carsten
