Skip to content

Commit 38b2e12

Browse files
committed
s/diydrones\/dronekit-python/dronekit\/dronekit-python/
1 parent ee7ef44 commit 38b2e12

25 files changed

+72
-72
lines changed

ELC.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ sudo pip install --upgrade droneapi
2727
git clone https://github.com/diydrones/ardupilot.git
2828

2929
# We will be referring to some example code included in the git repository
30-
git clone https://github.com/diydrones/dronekit-python.git
30+
git clone https://github.com/dronekit/dronekit-python.git
3131

3232
# We would like mavproxy to automatically load the DroneAPI module
3333
# when it starts

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
# DroneKit-python (formerly DroneAPI-python)
22

33
[![Windows Build status](https://img.shields.io/appveyor/ci/3drobotics/dronekit-python.svg?label=windows)](https://ci.appveyor.com/project/3drobotics/dronekit-python/branch/master)
4-
[![OS X Build Status](https://img.shields.io/travis/diydrones/dronekit-python.svg?label=os%20x)](https://travis-ci.org/diydrones/dronekit-python)
5-
[![Linux Build Status](https://img.shields.io/circleci/project/diydrones/dronekit-python.svg?label=linux)](https://circleci.com/gh/diydrones/dronekit-python)
4+
[![OS X Build Status](https://img.shields.io/travis/dronekit/dronekit-python.svg?label=os%20x)](https://travis-ci.org/dronekit/dronekit-python)
5+
[![Linux Build Status](https://img.shields.io/circleci/project/dronekit/dronekit-python.svg?label=linux)](https://circleci.com/gh/dronekit/dronekit-python)
66

7-
[![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/diydrones/dronekit-python?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
7+
[![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/dronekit/dronekit-python?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
88

99
This package contains the python language bindings for the drone API and the associated MAVProxy module.
1010

1111
## Users wanted!
1212

13-
We'd love your [feedback and suggestions](https://github.com/diydrones/dronekit-python/issues) about this API and are eager to evolve it to meet your needs.
13+
We'd love your [feedback and suggestions](https://github.com/dronekit/dronekit-python/issues) about this API and are eager to evolve it to meet your needs.
1414

1515
For documentation on how to use this API please see:
1616

docs/about/github_latest_release.txt

+18-18
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
.. This document was auto-generated by the get_release_notes.py script using latest-release information from github
2-
3-
Release 1.4.0 (July 24, 2015)
4-
=============================
5-
1+
.. This document was auto-generated by the get_release_notes.py script using latest-release information from github
2+
3+
Release 1.4.0 (July 24, 2015)
4+
=============================
5+
66

77
**Features:**
88

@@ -21,26 +21,26 @@ Release 1.4.0 (July 24, 2015)
2121
* Added information about clearing ROI (#172)
2222
* Explicitly documented issues about `Vehicle.commands.clear()` (#213)
2323

24-
Commits
25-
-------
26-
24+
Commits
25+
-------
26+
2727

2828
The commits relevant to this release `are listed here <https://github.com/diydrones/dronekit-python/compare/v1.3.1...v1.4.0>`_ (Github)
2929

30-
Bug fixes
31-
---------
32-
30+
Bug fixes
31+
---------
32+
3333

3434
The bugs that were closed in this release `are listed here <https://github.com/diydrones/dronekit-python/issues?utf8=%E2%9C%93&q=is%3Aclosed+created%3A%3E2015-07-07+is%3Aissue+>`_ (Github).
3535

36-
Merged pull requests
37-
--------------------
38-
36+
Merged pull requests
37+
--------------------
38+
3939

4040
The pull requests merged into this release `are listed here <https://github.com/diydrones/dronekit-python/pulls?utf8=%E2%9C%93&q=is%3Amerged+created%3A%3E2015-07-07+is%3Apr+>`_ (Github).
4141

42-
Notes
43-
-----
44-
42+
Notes
43+
-----
44+
4545

46-
Thanks to @hamishwillee, @mrpollo, @tcr3dr
46+
Thanks to @hamishwillee, @mrpollo, @tcr3dr

docs/about/license.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Open Source Licence
33
=======================
44

5-
DroneKit-Python is licensed under the *Apache License Version 2.0, January 2004 (http://www.apache.org/licenses/). This is present in the `LICENSE <https://github.com/diydrones/dronekit-python/blob/master/LICENSE>`_ file in the source tree, and reproduced below:
5+
DroneKit-Python is licensed under the *Apache License Version 2.0, January 2004 (http://www.apache.org/licenses/). This is present in the `LICENSE <https://github.com/dronekit/dronekit-python/blob/master/LICENSE>`_ file in the source tree, and reproduced below:
66
77
.. include:: ../../LICENSE
88
:literal:

docs/about/overview.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Open source community
1212

1313
DroneKit-Python is an open source and community-driven project.
1414

15-
You can find all the source code on `Github here <https://github.com/diydrones/dronekit-python>`_ and check out our permissive :doc:`Apache v2 Licence <license>`.
15+
You can find all the source code on `Github here <https://github.com/dronekit/dronekit-python>`_ and check out our permissive :doc:`Apache v2 Licence <license>`.
1616
If you want to join the community, then see our :doc:`contributing section <contributing>` for lots of ideas on how you can help.
1717

1818

@@ -46,7 +46,7 @@ Technical support
4646
This documentation is a great place to get started with developing DroneKit Python APIs.
4747

4848
If you run into problems, the `best place to ask questions is Stack Overflow <http://stackoverflow.com/questions/tagged/dronekit-python>`_.
49-
If your problem turns out to be a bug, then it should be `posted on Github <https://github.com/diydrones/dronekit-python/issues>`_.
49+
If your problem turns out to be a bug, then it should be `posted on Github <https://github.com/dronekit/dronekit-python/issues>`_.
5050

5151

5252

docs/about/release_notes.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Latest release
1818
All releases
1919
============
2020

21-
For information about all past releases, please see `this link on Github <https://github.com/diydrones/dronekit-python/releases>`_.
21+
For information about all past releases, please see `this link on Github <https://github.com/dronekit/dronekit-python/releases>`_.
2222

2323
Working with releases
2424
=======================

docs/contributing/contributions_api.rst

+5-5
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,13 @@ This article provides a high level overview of how to contribute changes to the
99
.. tip::
1010

1111
We highly recommend that changes and ideas are `discussed with the project team
12-
<https://github.com/diydrones/dronekit-python/issues>`_ before starting work!
12+
<https://github.com/dronekit/dronekit-python/issues>`_ before starting work!
1313

1414

1515
Submitting changes
1616
==================
1717

18-
Contributors should fork the main `diydrones/dronekit-python/ <https://github.com/diydrones/dronekit-python>`_
18+
Contributors should fork the main `dronekit/dronekit-python/ <https://github.com/dronekit/dronekit-python>`_
1919
repository and contribute changes back to the project master branch using pull requests
2020

2121
* Changes should be :ref:`tested locally <contributing-test-code>` before submission.
@@ -78,7 +78,7 @@ Good unit tests should:
7878

7979
Create any file named :file:`test_XXX.py` in the :file:`tests/unit` folder to add it as a test. Feel free to copy from existing tests to get started. When *nosetests* is run, it will add your new test to its summary.
8080

81-
Tests names should refer directly to a Github issue (for example, ``test_12.py`` would refer to `issue #12 <https://github.com/diydrones/dronekit-python/issues/12>`_ or describe fully what functionality they encompass (for example, ``test_waypoints.py`` would describe a unit test for the waypoints API).
81+
Tests names should refer directly to a Github issue (for example, ``test_12.py`` would refer to `issue #12 <https://github.com/dronekit/dronekit-python/issues/12>`_ or describe fully what functionality they encompass (for example, ``test_waypoints.py`` would describe a unit test for the waypoints API).
8282

8383
Avoiding printing any data from your test. Instead, use assertions to test your code is consistent. You can use the built-in Python ``assert`` macro as well as ``assert_equals`` from the ``nose.tools`` module:
8484

@@ -137,7 +137,7 @@ You can write a new integrated test by adding a file with the naming scheme :fil
137137
138138
This checks to see that the parameter object is of type `float`.
139139
140-
Tests names should refer directly to a Github issue (for example, ``test_12.py`` would refer to `issue #12 <https://github.com/diydrones/dronekit-python/issues/12>`_ or describe fully what functionality they encompass (for example, ``test_waypoints.py`` would describe a unit test for the waypoints API).
140+
Tests names should refer directly to a Github issue (for example, ``test_12.py`` would refer to `issue #12 <https://github.com/dronekit/dronekit-python/issues/12>`_ or describe fully what functionality they encompass (for example, ``test_waypoints.py`` would describe a unit test for the waypoints API).
141141
142142
Avoiding printing any data from your test. Instead, use assertions to test your code is consistent. You can use the built-in Python ``assert`` macro as well as ``assert_equals`` from the ``testlib`` module:
143143
@@ -157,7 +157,7 @@ Web client tests
157157
.. warning::
158158
159159
The web client library is being rewritten. Please `discuss with the project team
160-
<https://github.com/diydrones/dronekit-python/issues>`_ if you intend to develop with or for the present version of the web client.
160+
<https://github.com/dronekit/dronekit-python/issues>`_ if you intend to develop with or for the present version of the web client.
161161
162162
Web client tests use *nosetests*. To run these, you will need to sign up for API keys from `cloud.dronekit.io <https://cloud.dronekit.io/>`_.
163163
With these, export a variable named ``DRONEAPI_KEY`` with a value in the format ``<id>.<key>`` to your environment.

docs/contributing/contributions_documentation.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ the documentation system, how to build the documents locally, and how to submit
1111
Documentation system overview
1212
=============================
1313

14-
The documentation source files are `stored in Github <https://github.com/diydrones/dronekit-python/tree/master/docs>`_.
14+
The documentation source files are `stored in Github <https://github.com/dronekit/dronekit-python/tree/master/docs>`_.
1515
The content is written in plain-text files (file-extension :file:`.rst`) using
1616
`reStructuredText <http://sphinx-doc.org/rest.html>`_ markup, and is compiled into HTML using the
1717
`Sphinx Documentation Generator <http://sphinx-doc.org/index.html>`_.
@@ -42,7 +42,7 @@ The instructions below explain how to get the documentation source, and build it
4242
* `Download and install VirtualBox <https://www.virtualbox.org/wiki/Downloads>`_.
4343
* `Download and install Vagrant for your platform <https://www.vagrantup.com/downloads.html>`_ (Windows, OS-X and Linux are supported).
4444

45-
* `Fork the official dronekit-python repo <https://github.com/diydrones/dronekit-python#fork-destination-box>`_
45+
* `Fork the official dronekit-python repo <https://github.com/dronekit/dronekit-python#fork-destination-box>`_
4646
* Clone your fork of the Github repository anywhere on the host PC: ::
4747

4848
git clone https://github.com/YOUR-REPOSITORY/dronekit-python.git

docs/contributing/developer_setup_linux.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ then build and install your own fork of DroneKit, as discussed below.
1414
Fetch and build DroneKit source
1515
===============================
1616

17-
#. Fork the `dronekit-python <https://github.com/diydrones/dronekit-python>`_ project on Github.
17+
#. Fork the `dronekit-python <https://github.com/dronekit/dronekit-python>`_ project on Github.
1818

1919
#. Run the following commands to clone and build DroneKit (in the directory of your choice):
2020

docs/contributing/developer_setup_windows.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ then build and install your own fork of DroneKit, as discussed below.
1414
Fetch and build DroneKit source
1515
===============================
1616

17-
#. Fork the `dronekit-python <https://github.com/diydrones/dronekit-python>`_ project on Github.
17+
#. Fork the `dronekit-python <https://github.com/dronekit/dronekit-python>`_ project on Github.
1818

1919
#. Open the *WinPython Command Prompt*. Run the following commands to clone and build DroneKit (in the directory of your choice):
2020

docs/contributing/getting_started.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ How you can Contribute
55
=======================
66

77
One of the best ways you can contribute is to simply *use the API* and share your
8-
`bug reports and enhancement suggestions on Github <https://github.com/diydrones/dronekit-python/issues>`_.
8+
`bug reports and enhancement suggestions on Github <https://github.com/dronekit/dronekit-python/issues>`_.
99
These can cover anything: from APIs that don't work properly through to needed features or documentation.
1010

1111
If you want to take a more active role, then a good place to start is with the project's
12-
`open issues <https://github.com/diydrones/dronekit-python/issues>`_ on Github. In particular,
12+
`open issues <https://github.com/dronekit/dronekit-python/issues>`_ on Github. In particular,
1313
:ref:`documentation issues <contributing-to-documentation>` can be resolved without a deep knowledge of the code,
1414
and will help you learn more about the project.
1515

docs/examples/drone_delivery.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ Next we'll look at the basics of using the webservice and the local vehicle API
8484
Source code
8585
===========
8686

87-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/drone_delivery/drone_delivery.py>`_):
87+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/drone_delivery/drone_delivery.py>`_):
8888

8989
.. include:: ../../examples/drone_delivery/drone_delivery.py
9090
:literal:

docs/examples/flight_replay.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ Next we'll work with existing Linux services (gpsd) to add a new drone based fea
9595
Source code
9696
===========
9797

98-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/flight_replay/flight_replay.py>`_):
98+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/flight_replay/flight_replay.py>`_):
9999

100100

101101
.. literalinclude:: ../../examples/flight_replay/flight_replay.py

docs/examples/follow_me.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Next, take a look at the full :ref:`api_reference` for more information.
4242
Source code
4343
===========
4444

45-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/follow_me/follow_me.py>`_):
45+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/follow_me/follow_me.py>`_):
4646

4747
.. include:: ../../examples/follow_me/follow_me.py
4848
:literal:

docs/examples/guided-set-speed-yaw-demo.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -344,7 +344,7 @@ ArduPilot version:
344344
Source code
345345
===========
346346

347-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/guided_set_speed_yaw/guided_set_speed_yaw.py>`_):
347+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/guided_set_speed_yaw/guided_set_speed_yaw.py>`_):
348348

349349
.. literalinclude:: ../../examples/guided_set_speed_yaw/guided_set_speed_yaw.py
350350
:language: python

docs/examples/running_examples.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ Running the Examples
33
====================
44

55
To run the examples you will need to set up DroneKit as described in :ref:`get-started`.
6-
Once you have the `source code <https://github.com/diydrones/dronekit-python/tree/master/example>`_, examples are
6+
Once you have the `source code <https://github.com/dronekit/dronekit-python/tree/master/example>`_, examples are
77
started as described in the *Getting Started* section :ref:`getting-started-running_examples`.
88

99
.. note::

docs/examples/simple_goto.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ To return to the home position and land, we set the mode to ``RTL``:
133133
Source code
134134
===========
135135
136-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/simple_goto/simple_goto.py>`_):
136+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/simple_goto/simple_goto.py>`_):
137137
138138
.. literalinclude:: ../../examples/simple_goto/simple_goto.py
139139
:language: python

docs/examples/vehicle_state.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -112,19 +112,19 @@ Provided that the vehicle is connected and able to arm, it should run through to
112112
Two cases where you may observe issues are:
113113

114114
* You will see an error ``Timeout setting THR_MIN to 10.000000``. This can be ignored because the value is actually set.
115-
See `#12 Timeout error when setting a parameter <https://github.com/diydrones/dronekit-python/issues/12>`_ for information.
115+
See `#12 Timeout error when setting a parameter <https://github.com/dronekit/dronekit-python/issues/12>`_ for information.
116116
* When the observer sets the mode callback, it waits two seconds after changing the mode before removing the observer
117117
(to ensure that the callback function is run before the observer is removed). In this time you may see the callback being
118118
called twice even though the mode is only changed once.
119-
See `#60 Attribute observer callbacks are called with heartbeat until disabled - after first called <https://github.com/diydrones/dronekit-python/issues/60>`_
119+
See `#60 Attribute observer callbacks are called with heartbeat until disabled - after first called <https://github.com/dronekit/dronekit-python/issues/60>`_
120120
for more information.
121121

122122

123123

124124
Source code
125125
===========
126126

127-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/vehicle_state/vehicle_state.py>`_):
127+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/vehicle_state/vehicle_state.py>`_):
128128

129129
.. literalinclude:: ../../examples/vehicle_state/vehicle_state.py
130130
:language: python

docs/get_release_notes.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
Github API doc for getting latest release: https://developer.github.com/v3/repos/releases/#get-the-latest-release
1212
GET /repos/:owner/:repo/releases/latest
1313
14-
Where our release is: https://github.com/diydrones/dronekit-python/releases/tag/1.1.1
14+
Where our release is: https://github.com/dronekit/dronekit-python/releases/tag/1.1.1
1515
"""
1616

1717
import requests # for making API requests

docs/guide/copter/guided_mode.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -353,9 +353,9 @@ The *home location* is updated immediately in ArduPilot, but the change may not
353353
Command acknowledgements and response values
354354
--------------------------------------------
355355

356-
ArduPilot typically sends a command acknowledgement indicating whether a command was received, and whether it was accepted or rejected. At time of writing there is no way to intercept this acknowledgement in the API (`#168 <https://github.com/diydrones/dronekit-python/pull/168>`_).
356+
ArduPilot typically sends a command acknowledgement indicating whether a command was received, and whether it was accepted or rejected. At time of writing there is no way to intercept this acknowledgement in the API (`#168 <https://github.com/dronekit/dronekit-python/pull/168>`_).
357357

358-
Some MAVLink messages request information from the autopilot, and expect the result to be returned in another message. At time of writing you can send the request (provided the message is handled by the AutoPilot in GUIDED mode) but there is no way to intercept the response in DroneKit-Python (`#169 <https://github.com/diydrones/dronekit-python/issues/169>`_).
358+
Some MAVLink messages request information from the autopilot, and expect the result to be returned in another message. At time of writing you can send the request (provided the message is handled by the AutoPilot in GUIDED mode) but there is no way to intercept the response in DroneKit-Python (`#169 <https://github.com/dronekit/dronekit-python/issues/169>`_).
359359

360360

361361
.. _guided_mode_copter_useful_conversion_functions:

docs/guide/debugging.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ That said, it is possible to effectively debug DroneKit apps. The main methods a
1818
.. note::
1919

2020
We are actively working to improve debugging on DroneKit-Python! You can track progress and suggestions
21-
on `Github Issue #118 <https://github.com/diydrones/dronekit-python/issues/118>`_.
21+
on `Github Issue #118 <https://github.com/dronekit/dronekit-python/issues/118>`_.
2222

2323

2424
Print/log statements

0 commit comments

Comments
 (0)