From 300f798c29f5614aeab515c13b649d14e27f87b2 Mon Sep 17 00:00:00 2001
From: Monty Taylor <mordred@inaugust.com>
Date: Fri, 19 Apr 2019 13:46:21 +0000
Subject: [PATCH] Update opendev website to be more present tense

Since we're doing the rollout, talking about it in the future tense
is no longer necessary.

Change-Id: Ia9ce9c11d8e38d003095047fa9dff300a147021c
---
 docker/gitea/custom/templates/home.tmpl | 22 +++++-----------------
 1 file changed, 5 insertions(+), 17 deletions(-)

diff --git a/docker/gitea/custom/templates/home.tmpl b/docker/gitea/custom/templates/home.tmpl
index 6541a33c44..50a69934fe 100644
--- a/docker/gitea/custom/templates/home.tmpl
+++ b/docker/gitea/custom/templates/home.tmpl
@@ -22,22 +22,10 @@
 
                         <h1 id="current-status">Current Status</h1>
 
-                        <p>We are still very early in the process of building this out. We have DNS servers
-                        and this website running to start.</p>
-                        <p>Most of the services we plan to run will be inherited and rebranded from the
-                        existing community run OpenStack Infrastructure. This means that we do already
-                        have services running, but until we transition them into OpenDev they may say
-                        “OpenStack” across the top or in their URLs.</p>
-
-                        <h1 id="changes-we-plan-to-make">Changes we plan to make</h1>
-                        <p>There are far too many things to capture here so we’ll go after the highlights instead:</p>
-                        <ul>
-                                <li>Move existing services like Gerrit and Etherpad under the opendev.org domain. Remove OpenStack branding as necessary.</li>
-                                <li>For the code review and CI toolchain treat the services as multitenant. This will likely involve moving code repos around.
-                                <ul>
-                                        <li>We’ll need to build better project renaming and provisioning tools.</li>
-                                </ul></li>
-                        </ul>
+                        <p>We are still early in the process of building this out.</p>
+                        <p>Most of the services we run were inherited and rebranded from the
+                        existing community run OpenStack Infrastructure. This means that while we do already
+                        have many services running, there may still be some services branded as "OpenStack" while we complete the rebranding.</p>
 
                         <h1 id="join-us">Join Us</h1>
                         <p>As mentioned previously the OpenDev services themselves are open source software managed on top of Opendev itself. This means that in addition to using OpenDev to host your software development activities you can help us run OpenDev with all of the same tools.</p>
@@ -46,7 +34,7 @@
                         <h1 id="faq">FAQ</h1>
 
                         <h2 id="isnt-this-just-openstack-infrastructure-rebranded">Isn’t this just OpenStack Infrastructure rebranded?</h2>
-                        <p>It is more than that. We want to make this toolset available to others that would find it helpful. OpenStack would become one of the OpenDev tenants, but other tenants like Zuul or $gizmo would be just as important.</p>
+                        <p>It is more than that. We want to make this toolset available to others that would find it helpful. OpenStack is one of the OpenDev tenants, but other tenants like Zuul or $gizmo would be just as important.</p>
 
                         <h2 id="can-i-host-my-project-on-opendev">Can I host my project on OpenDev?</h2>
                         <p>Yes! However, as noted above it is still early days yet and the early experience might be a bit bumpy. Certain things may still say “OpenStack” on them as we figure out the transition. And while any moves should come with appropriate redirects, we may have some inadvertent misses.</p>