Grammar fix Signed-off-by: Stan Grishin <stangri@melmac.net>

[web.git] / development.txt

diff --git a/development.txt b/development.txt
index 088bdb32722464402e46873084be6aa1a972010c..e4fb09b768c0cc45bff0b16f0e139cdb241c6aa6 100644 (file)
--- a/development.txt
+++ b/development.txt
@@ -3,8 +3,6 @@
 Development
 ===========
 
-include::menu.inc[]
-
 == The Source Code
 
 The LEDE project source code starts off with OpenWrt revision r49258. The code
@@ -13,7 +11,7 @@ by OpenWrt. While importing the sources the tree was normalised and some
 minor tweaks were made to committer names and mail addresses.
 
 All repositories can be browsed online through
-http://git.lede-project.org/[Gitweb] as well.
+https://git.lede-project.org/[Gitweb] as well.
 
 === Getting The _LEDE_ Code
 
@@ -21,7 +19,7 @@ Any _LEDE_ development happens in the main +source.git+ repository which is
 accessible via both HTTP and HTTPS:
 
 ----
-git clone http://git.lede-project.org/source.git
+git clone https://git.lede-project.org/source.git
 ----
 
 You can find a mirror of the repository on Github:
@@ -41,10 +39,10 @@ repositories mapping the various SVN directories and tags to proper Git
 branches.
 
 ----
-git clone http://git.lede-project.org/openwrt/source.git
-git clone http://git.lede-project.org/openwrt/packages.git
-git clone http://git.lede-project.org/openwrt/feeds.git
-git clone http://git.lede-project.org/openwrt/docs.git
+git clone https://git.lede-project.org/openwrt/source.git
+git clone https://git.lede-project.org/openwrt/packages.git
+git clone https://git.lede-project.org/openwrt/feeds.git
+git clone https://git.lede-project.org/openwrt/docs.git
 ----
 
 === The Web Presence
@@ -54,7 +52,7 @@ http://www.methods.co.nz/asciidoc/[AsciiDoc] suite. Any changes made to the
 projects web site will be reflected in our +web.git+ repository:
 
 ----
-git clone http://git.lede-project.org/web.git
+git clone https://git.lede-project.org/web.git
 ----
 
 === Submitting Patches
@@ -62,19 +60,27 @@ git clone http://git.lede-project.org/web.git
 The biggest difference is that we now accept pull requests. The tree that shall
 be pulled from needs to be hosted publicly. Small fixes and minor patches can
 also be submitted via the
-http://lists.infradead.org/mailman/listinfo/lede-dev[development mailing list].
+https://lists.infradead.org/mailman/listinfo/lede-dev[development mailing list].
 Submissions should follow these rules
 
 . TBD
 
-All patches need to be sent in a format that they are listed in http://patchwork.ozlabs.org/project/lede/list/[patchwork].
+All patches need to be sent in a format that they are listed in https://patchwork.ozlabs.org/project/lede/list/[patchwork].
 If the patch does not get listed in patchwork then it won't get processed.
 
 
+=== Staging Trees
+
+To create yourself a staging tree on git.lede-project.org:
+----
+ssh git@git.lede-project.org "create lede/yournick/staging"
+ssh git@git.lede-project.org "desc lede/yournick/staging Staging tree of Your Name"
+----
+
+
 === Reporting Bugs
 
-. *All* bug reports need to be submitted via the
-  http://lists.infradead.org/mailman/listinfo/lede-dev[development mailing list]
+. Please report your bugs using our https://bugs.lede-project.org/[issue tracker]
 . When reporting bugs please make sure to
   .. Name the tree/revision
   .. Name the affected device
@@ -85,13 +91,8 @@ If the patch does not get listed in patchwork then it won't get processed.
 . Reporting a bug means that you reported a bug. It does not constitute a claim that
   anyone has to work on fixing it.
 . Pointless/vague/silly/... bugs reports will be ignored
-. Feature requests are not Bugs. They will also be ignored.
 . The better your bug report, the more likely it is that it will be worked on.
 
-All bug reports need to be sent in a format so that they are listed in the issue
-tracker (__LINK__). If the bug report does not get listed in the issue tracker then
-it won't get processed.
-
 
 === Patch Merging And Tree Life Cycle