Hi Mukul,
It might be also possible to convert an entire SVN history to Git history:
https://docs.github.com/en/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository
It would also be interesting to find out if projects hosted by Apache
allow pull requests made only with a "sign-off" comment or they require
proposed changes to be taken into account only if made by certain
allowed contributors.
Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 4/26/24 14:57, Mukul Gandhi wrote:
Hi Radu,
Thanks for the thoughts.
On Thu, Apr 25, 2024 at 11:16 AM Radu Coravu wrote:
I think that the possibility of moving Apache Xerces as a GitHub project
would be great, the issues list could also be maybe moved to GitHub and
maybe the development could pick up especially if the project would
accept pull requests.
I've been able to do few things as follows earlier today, for trying
to migrate Apache Xerces-J project codebase to GitHub,
Successfully created GitHub repos with name 'xerces-j' within asf's
work area. My asf Xerces project credentials seems to have allowed me
to do this.
I've copied over everything from Xerces-J svn branch
'xml-schema-1.1-dev' to https://github.com/apache/xerces-j (on the
branch 'main'. there's this only branch currently available on this
GitHub repos).
The Xerces-J svn trunk's contents are available within an archive file
named "xerces-java-trunk_asf_svn_backup_2024-04-25.zip" within
https://github.com/apache/xerces-j (just as backup of Xerces-J svn
trunk contents as of now).
I've copied over necessary XML Schema 1.0 and 1.1 test suites as well
within GitHub repos https://github.com/apache/xerces-j.
I'm not sure how to copy existing Xerces-J issues list from asf jira
to GitHub. May be, we should continue managing Xerces-J's project
issues on asf jira itself. We may use GitHub as well to discuss
Xerces-J issues.
Xerces-J's existing svn url
https://svn.apache.org/repos/asf/xerces/java/ has all the things as
previously, and also nothing has been changed on Xerces-J project web
site https://xerces.apache.org/xerces2-j/. Let's keep all of this, as
it is. If Xerces-J's migration to GitHub is approved by Xerces team,
may be we should at-least make the web location
https://svn.apache.org/repos/asf/xerces/java/ readonly.
IMHO, I'm curious how Michael Glavassevich (he's asf Xerces project's
PMC chair) feels about what has been done as mentioned above within
this mail. I'm willing to undo all of this what has been done, if
Michael or anyone else thinks so.
Many thanks.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
