infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <>
Subject [jira] [Commented] (INFRA-14281) transfer to Apache
Date Thu, 08 Jun 2017 10:21:18 GMT


Greg Stein commented on INFRA-14281:

Note that we're talking about *static* content. The ASF wants TLP sites to be static, in order
to manage the load.

If the existing has dynamic content, then the planning will change.

Regarding the domain: we can move that at any time, and retain its pointers to
the old servers until they get migrated. To move the domain, two primary steps: unlock its
transfer, and send the transfer auth code to

> transfer to Apache
> -------------------------------
>                 Key: INFRA-14281
>                 URL:
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Website
>            Reporter: Geertjan Wielenga
> is currently running on an Oracle server and is explicitly something that
is listed as a resource that will be donated to Apache. Of course, the Oracle server itself
remains an Oracle server, while its content in this case, i.e.,, will move to
Apache. The domain itself will also be donated to Apache.
> The Apache NetBeans project has all the sources of available. So the questions
> 1. What needs to happen and where do those sources need to be moved.
> 2. What needs to be done for Apache to own the domain.
> Putting aside the question of the grant document, branding document, etc, which will
come from Oracle, before anything is transferred or done, what needs to happen on the technical
side, i.e., what actual physical steps need to be taken, to get the content and the domain
to work under Apache.

This message was sent by Atlassian JIRA

View raw message