+1

On 08/02/2023 12:30, Glenn Adams wrote:
*Background*

At the present time, the following master repositories for the XMLGraphics
project are maintained on the ASF Subversion Service, as listed under
subversion
index of /xmlgraphics <http://svn.apache.org/viewvc/xmlgraphics/>:

    - batik <http://svn.apache.org/viewvc/xmlgraphics/batik/>
    - commons <http://svn.apache.org/viewvc/xmlgraphics/commons/>
    - fop <http://svn.apache.org/viewvc/xmlgraphics/fop/>
    - fop-pdf-images
    <http://svn.apache.org/viewvc/xmlgraphics/fop-pdf-images/>

In addition, read-only mirrors of these repositories
<https://github.com/search?q=org%3Aapache+xmlgraphics> were created by
INFRA on GitHub <https://github.com/apache> some time prior to 2011, and
remain in place today.

*Proposed Change*

It is proposed that these XMLGraphics Subversion repository masters be
migrated to GitBox <https://gitbox.apache.org/>, the ASF Writable Git
Service, at which point the existing Subversion repositories will be marked
as read-only.

Note: The existing GitHub read-only mirror repositories will be replaced
with writable repositories synchronized with GitBox, including the ability
to open/close/merge pull requests, address issues, and employ GitHub pages
<https://docs.github.com/en/pages> and actions
<https://docs.github.com/en/actions>.

*Visible Effects*

The primary end-user (i.e., project developer and committer) visible
effects of the proposed change are as follows:

    - Subversion commands that attempt to modify remote Subversion
    repository state will fail.
    - Git commands that attempt to modify remote Git (GitBox or GitHub)
    repository state will succeed (provided all necessary authentication,
    authorization, and other pre-conditions are met).

*Downstream Dependencies*

It is noted that the following project related processes currently depend
on or make reference to the existing Subversion repositories:

    - Jenkins build configurations used for nightly (or manual) CI
    processing;
    - Ant properties and build, publish, deploy files (e.g., see
version property,
    etc);
    - Maven pom files (e.g., scm element).

These dependencies will be updated to reflect the new repository locations,
e.g., changed to reference the writable GitHub repository locations.

Note: It is expected that Ant build use and support will be removed, with
Maven replacing Ant for all build, publish, and deploy activities. The
changes necessary to enable this migration from Ant to Maven will be the
subject to a separate vote to be considered after a Subversion to Git
migration is concluded.

*Voting*

Voting starts now, 2023-02-08 12:30Z, and ends at 2023-02-15 17:00Z. Lack
of a vote from a member or contributor will be recorded as +0.

Regards,
Glenn Adams



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to