Re: xercesj project suggestion
Hi Radu, Thanks for valuable information. That helps me. On Mon, Apr 29, 2024 at 10:06 AM Radu Coravu wrote: > This part of the Xerces project describes how decisions are made and > contributions are accepted: > > https://xerces.apache.org/charter.html Thanks for references, to these details, and surely XercesJ team needs to adhere to these guidelines. I'm personally fine been told, if I'm unknowingly violating any of points of Apache Xerces project's charter, and I'll be happy to correct my future contributions to this project to adhere correctly to Apache Xerces project's charter. > It's interesting there is also this xerces2-j project which seems to be > or to have been a mirror of the Apache Xerces project, the last commit > made about 5 years ago: > > https://github.com/apache/xerces2-j Thanks for reference as well, to this github project. It seems to me that, Sam Ruby (as far as I know, Sam is director of Apache Software Foundation and has been co-editor of HTML specs as well and therefore we need to have his interest in ASF Xerces project) and few other people as well are contributors to this GitHub project (i.e, https://github.com/apache/xerces2-j). But these gentlemen haven't communicated details about these tasks to Apache Xerces team on our discussion forums here. It seems to me that, https://github.com/apache/xerces2-j is a mirror of XercesJ's project. But this mirror site doesn't seem to be setup to sync with XerceJ commits that we currently do on XercesJ's current active codebase. The XercesJ project's repos https://github.com/apache/xerces-j that I've created, seems to sync correctly with Apache XercesJ repos. I've already yesterday imported XercesJ svn trunk's content with all relevant commit history, which is now available as git repos at https://github.com/apache/xerces-j. I'm now trying to do XercesJ import of its svn's other codebase branches, tags etc within the github location https://github.com/apache/xerces-j. Until all of these activities are completed that I'm trying to do as of now, none-of XercesJ svn contents shall be altered by myself in an away. In-fact personally, I don't wish to alter XercesJ svn contents in any way. I do actually wish to setup the codebase location https://github.com/apache/xerces-j, with all necessary imports of XercesJ svn's code and other artifacts. I'll inform this list, when I've completed these mentioned tasks. 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
Re: xercesj project suggestion
Hi Mukul, This part of the Xerces project describes how decisions are made and contributions are accepted: https://xerces.apache.org/charter.html Maybe you could keep the project private while you await feedback from Michael. It's interesting there is also this xerces2-j project which seems to be or to have been a mirror of the Apache Xerces project, the last commit made about 5 years ago: https://github.com/apache/xerces2-j Regards, Radu Radu Coravu Oxygen XML Editor On 4/27/24 16:56, Mukul Gandhi wrote: Hi Radu, On Fri, Apr 26, 2024 at 6:10 PM Radu Coravu wrote: I'm not sure why my mailer shows your email id as @...invalid, when I get your mail via this mailing list. 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 I do find this thought interesting, and shall try to implement this. 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. Any of your contributions to this project are most welcome. - To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: j-dev-h...@xerces.apache.org
Re: xercesj project suggestion
Hi Radu, On Fri, Apr 26, 2024 at 6:10 PM Radu Coravu wrote: I'm not sure why my mailer shows your email id as @...invalid, when I get your mail via this mailing list. > 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 I do find this thought interesting, and shall try to implement this. > 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. Any of your contributions to this project are most welcome. -- Regards, Mukul Gandhi - To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: j-dev-h...@xerces.apache.org
Re: xercesj project suggestion
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
Re: xercesj project suggestion
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
Re: xercesj project suggestion
Hi Mukul, Indeed I see xerces-c is on GitHub: https://github.com/apache/xerces-c 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. Regards, Radu Radu Coravu Oxygen XML Editor On 4/25/24 08:23, Mukul Gandhi wrote: Hi all, I've been having, following two Xerces-J related activities within my mind, that could be done, 1) Archiving (sort, of creating a zip or tar.gz archive) Xerces-J codebase and all other contents from Xerces-J svn trunk location (this svn trunk location, shall be empty after this activity). Afterwhich, we may move Xerces-J codebase and all other contents from Xerces-J svn branch xml-schema-1.1-dev to trunk. The new trunk contents shall also have trunk's previous content's archive zip/tar.gz file. I belive that, these activities were informally agreed upon few years ago on Xerces-J mailing list. I think, this shall ease maintaining Xerces-J codebase going forward. 2) After step 1) above is achieved, I think it'll be good if we may move XercesJ project repos to Apache git infra (Xerces-C already has that). It'll be nice if we could have thoughts and possible go-ahead about above mentioned activities, from other members of Xerces committers and pmc members. Many thanks. - To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: j-dev-h...@xerces.apache.org
