summaryrefslogtreecommitdiffstats
path: root/documentation/overview-manual/development-environment.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/overview-manual/development-environment.rst')
-rw-r--r--documentation/overview-manual/development-environment.rst22
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/overview-manual/development-environment.rst b/documentation/overview-manual/development-environment.rst
index 9a2997d9fc..011a479578 100644
--- a/documentation/overview-manual/development-environment.rst
+++ b/documentation/overview-manual/development-environment.rst
@@ -40,7 +40,7 @@ project is the Windows family of operating systems developed by
40Microsoft Corporation. 40Microsoft Corporation.
41 41
42Wikipedia has a good historical description of the Open Source 42Wikipedia has a good historical description of the Open Source
43Philosophy `here <http://en.wikipedia.org/wiki/Open_source>`__. You can 43Philosophy `here <https://en.wikipedia.org/wiki/Open_source>`__. You can
44also find helpful information on how to participate in the Linux 44also find helpful information on how to participate in the Linux
45Community 45Community
46`here <https://www.kernel.org/doc/html/latest/process/index.html>`__. 46`here <https://www.kernel.org/doc/html/latest/process/index.html>`__.
@@ -291,7 +291,7 @@ While each development environment is unique, there are some best
291practices or methods that help development run smoothly. The following 291practices or methods that help development run smoothly. The following
292list describes some of these practices. For more information about Git 292list describes some of these practices. For more information about Git
293workflows, see the workflow topics in the `Git Community 293workflows, see the workflow topics in the `Git Community
294Book <http://book.git-scm.com>`__. 294Book <https://book.git-scm.com>`__.
295 295
296- *Make Small Changes:* It is best to keep the changes you commit small 296- *Make Small Changes:* It is best to keep the changes you commit small
297 as compared to bundling many disparate changes into a single commit. 297 as compared to bundling many disparate changes into a single commit.
@@ -368,12 +368,12 @@ commands.
368.. note:: 368.. note::
369 369
370 - For more information on Git, see 370 - For more information on Git, see
371 http://git-scm.com/documentation. 371 https://git-scm.com/documentation.
372 372
373 - If you need to download Git, it is recommended that you add Git to 373 - If you need to download Git, it is recommended that you add Git to
374 your system through your distribution's "software store" (e.g. for 374 your system through your distribution's "software store" (e.g. for
375 Ubuntu, use the Ubuntu Software feature). For the Git download 375 Ubuntu, use the Ubuntu Software feature). For the Git download
376 page, see http://git-scm.com/download. 376 page, see https://git-scm.com/download.
377 377
378 - For information beyond the introductory nature in this section, 378 - For information beyond the introductory nature in this section,
379 see the ":ref:`dev-manual/start:locating yocto project source files`" 379 see the ":ref:`dev-manual/start:locating yocto project source files`"
@@ -507,7 +507,7 @@ you can manage with a small set of basic operations and workflows once
507you understand the basic philosophy behind Git. You do not have to be an 507you understand the basic philosophy behind Git. You do not have to be an
508expert in Git to be functional. A good place to look for instruction on 508expert in Git to be functional. A good place to look for instruction on
509a minimal set of Git commands is 509a minimal set of Git commands is
510`here <http://git-scm.com/documentation>`__. 510`here <https://git-scm.com/documentation>`__.
511 511
512The following list of Git commands briefly describes some basic Git 512The following list of Git commands briefly describes some basic Git
513operations as a way to get started. As with any set of commands, this 513operations as a way to get started. As with any set of commands, this
@@ -614,10 +614,10 @@ and Free Software has an interesting history. If you are interested in
614this history, you can find basic information here: 614this history, you can find basic information here:
615 615
616- `Open source license 616- `Open source license
617 history <http://en.wikipedia.org/wiki/Open-source_license>`__ 617 history <https://en.wikipedia.org/wiki/Open-source_license>`__
618 618
619- `Free software license 619- `Free software license
620 history <http://en.wikipedia.org/wiki/Free_software_license>`__ 620 history <https://en.wikipedia.org/wiki/Free_software_license>`__
621 621
622In general, the Yocto Project is broadly licensed under the 622In general, the Yocto Project is broadly licensed under the
623Massachusetts Institute of Technology (MIT) License. MIT licensing 623Massachusetts Institute of Technology (MIT) License. MIT licensing
@@ -626,9 +626,9 @@ license is distributed with that software. MIT is also compatible with
626the GNU General Public License (GPL). Patches to the Yocto Project 626the GNU General Public License (GPL). Patches to the Yocto Project
627follow the upstream licensing scheme. You can find information on the 627follow the upstream licensing scheme. You can find information on the
628MIT license 628MIT license
629`here <http://www.opensource.org/licenses/mit-license.php>`__. You can 629`here <https://www.opensource.org/licenses/mit-license.php>`__. You can
630find information on the GNU GPL 630find information on the GNU GPL
631`here <http://www.opensource.org/licenses/LGPL-3.0>`__. 631`here <https://www.opensource.org/licenses/LGPL-3.0>`__.
632 632
633When you build an image using the Yocto Project, the build process uses 633When you build an image using the Yocto Project, the build process uses
634a known list of licenses to ensure compliance. You can find this list in 634a known list of licenses to ensure compliance. You can find this list in
@@ -646,11 +646,11 @@ the developer to resolve potential licensing issues.
646 646
647The base list of licenses used by the build process is a combination of 647The base list of licenses used by the build process is a combination of
648the Software Package Data Exchange (SPDX) list and the Open Source 648the Software Package Data Exchange (SPDX) list and the Open Source
649Initiative (OSI) projects. `SPDX Group <http://spdx.org>`__ is a working 649Initiative (OSI) projects. `SPDX Group <https://spdx.org>`__ is a working
650group of the Linux Foundation that maintains a specification for a 650group of the Linux Foundation that maintains a specification for a
651standard format for communicating the components, licenses, and 651standard format for communicating the components, licenses, and
652copyrights associated with a software package. 652copyrights associated with a software package.
653`OSI <http://opensource.org>`__ is a corporation dedicated to the Open 653`OSI <https://opensource.org>`__ is a corporation dedicated to the Open
654Source Definition and the effort for reviewing and approving licenses 654Source Definition and the effort for reviewing and approving licenses
655that conform to the Open Source Definition (OSD). 655that conform to the Open Source Definition (OSD).
656 656