ajwillia-ms pushed a commit to branch master.

http://git.enlightenment.org/website/www-content.git/commit/?id=6b5f70c23fda76fdd531e6cc3dc986f9b8ea0c4f

commit 6b5f70c23fda76fdd531e6cc3dc986f9b8ea0c4f
Author: Andy Williams <a...@andywilliams.me>
Date:   Fri Oct 20 16:20:16 2017 +0100

    Revert "Move docs about contributing to new /contrib namespace"
    
    This reverts commit 3ffe6fe95f790926c63487825327e716f9e16a33.
---
 pages/contact.txt                                    | 2 +-
 pages/{contrib/patching.txt => contact/arcanist.txt} | 0
 pages/{contrib/start.txt => contribute.txt}          | 0
 pages/debugging/apps_efl_debugging.txt               | 4 ++--
 pages/{contrib => debugging}/report_bugs.txt         | 0
 pages/docs.txt                                       | 6 +++---
 pages/start.txt                                      | 2 +-
 7 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/pages/contact.txt b/pages/contact.txt
index dd12d34f..d44ca77e 100644
--- a/pages/contact.txt
+++ b/pages/contact.txt
@@ -126,6 +126,6 @@ wiki here is newer, replacing static web pages.
 
 ==== Patches ====
 
-On [[https://phab.enlightenment.org|Phabricator]] the 
[[https://phab.enlightenment.org/differential|Differential]] tool is used for 
patch submission and review. You will need an account to submit patches. You 
will also need to use the Arcanist tool to do this - please see the 
[[contrib/patching|Arcanist documentation]] about how to do this.
+On [[https://phab.enlightenment.org|Phabricator]] the 
[[https://phab.enlightenment.org/differential|Differential]] tool is used for 
patch submission and review. You will need an account to submit patches. You 
will also need to use the [[contact:arcanist|Arcanist]] tool to do this. Please 
see the [[contact:arcanist|Arcanist documentation]] as to how to do this.
 
 While the above is the preferred method, you can also send patches using 
Phabricator directly. If you are unable to use Phabricator for whatever reason, 
please resort to sending a patch to the mailing list, or contacting the 
developers on IRC.
diff --git a/pages/contrib/patching.txt b/pages/contact/arcanist.txt
similarity index 100%
rename from pages/contrib/patching.txt
rename to pages/contact/arcanist.txt
diff --git a/pages/contrib/start.txt b/pages/contribute.txt
similarity index 100%
rename from pages/contrib/start.txt
rename to pages/contribute.txt
diff --git a/pages/debugging/apps_efl_debugging.txt 
b/pages/debugging/apps_efl_debugging.txt
index 1bc4cb7d..c1a84c17 100644
--- a/pages/debugging/apps_efl_debugging.txt
+++ b/pages/debugging/apps_efl_debugging.txt
@@ -7,7 +7,7 @@
 
 This tutorial's goal is to help you debug your EFL applications with several 
use cases that you can reproduce. It gives you approaches to know if the bug 
comes from your application or from the EFL libraries.
 
-Then, if you are sure the bug does not come from your application, you can 
[[/contrib/report_bugs|report a bug]].
+Then, if you are sure the bug does not come from your application, you can 
[[/debugging/report_bugs|report a bug]].
 
 In this tutorial we'll cover log levels and tracing the sources of bugs:
 
@@ -485,4 +485,4 @@ In the result below, you see that all the objects are 
visible and you see that w
 
 For example in yellow, it is the Elm_box which is an Evas_box composed of an 
Evas_rectangle, an Elm_Label and an Elm_Button.
 
-A Button widget is an Edje_Object which is composed of 4 Evas_rectangle, one 
Evas_image and 2 Evas_text.
+A Button widget is an Edje_Object which is composed of 4 Evas_rectangle, one 
Evas_image and 2 Evas_text.
\ No newline at end of file
diff --git a/pages/contrib/report_bugs.txt b/pages/debugging/report_bugs.txt
similarity index 100%
rename from pages/contrib/report_bugs.txt
rename to pages/debugging/report_bugs.txt
diff --git a/pages/docs.txt b/pages/docs.txt
index 5cbc155b..ce86fb6e 100755
--- a/pages/docs.txt
+++ b/pages/docs.txt
@@ -72,13 +72,13 @@ We are really excited that you would like to get involved 
in EFL and
 Enlightenment development! If you followed the instructions in
 "Getting Started" then you are most of the way to being part of the team.
 To start with it's easiest to see which area you would like to work on and
-get involved in bug reporting, fixing or other types of 
[[contrib/|contributing]]. From there you can get to know the
+get involved in bug reporting or fixing. From there you can get to know the
 team, how we work, and earn a place on the team as a core developer :)
 
 === Feedback ===
 
-  * [[contrib/report_bugs|Report bugs on Phabricator]]
-  * [[contrib/patching|Submit patch on Phabricator]]
+  * [[debugging/report_bugs|Report bugs on Phabricator]]
+  * [[contact/arcanist|Submit patch on Phabricator]]
 
 === Debugging ===
 
diff --git a/pages/start.txt b/pages/start.txt
index 5b7a6d94..1b1b17ca 100644
--- a/pages/start.txt
+++ b/pages/start.txt
@@ -10,7 +10,7 @@
 
 {{  :shot-enlightenment.png?nolink&320}}
 
-[[:about-enlightenment|Enlightenment]] started as a project to build a Window 
Manager for X11. That was way back in 1996. It has grown much since. It still 
produces this Window Manager, but it has evolved to also cover Mobile, Wearable 
and TV UI needs for projects such as [[http://www.tizen.org|Tizen]] as well as 
the traditional "desktop" UI. We still push out releases, so see our 
[[:download|download]] page for more details on the latest releases, or see our 
[[contrib/|contribute]] page [...]
+[[:about-enlightenment|Enlightenment]] started as a project to build a Window 
Manager for X11. That was way back in 1996. It has grown much since. It still 
produces this Window Manager, but it has evolved to also cover Mobile, Wearable 
and TV UI needs for projects such as [[http://www.tizen.org|Tizen]] as well as 
the traditional "desktop" UI. We still push out releases, so see our 
[[:download|download]] page for more details on the latest releases, or see our 
[[:contribute|contribute]] p [...]
 
 It also is in the transition from [[http://www.x.org|X11]] to 
[[http://wayland.freedesktop.org|Wayland]]. We are fully committed to moving to 
Wayland eventually as this is definitely the future of the graphical display 
layer on Linux.
 

-- 


Reply via email to