Renames "droneapi" to "dronekit".

Author: tcr3dr

.gitignore

@@ -1,6 +1,6 @@
 .project
 .pydevproject
-droneapi.egg-info
+dronekit.egg-info
 dist
 build
 .vagrant

ELC.md

@@ -25,10 +25,10 @@ Working with releases
 
 The following PyPI commands are useful for working with different version of DroneKit Python: ::
 
-    pip install droneapi    # Install the latest version
-    pip install droneapi --upgrade    # Update to the latest version
-    pip show droneapi    # Find out what release you have installed
-    pip install droneapi=1.0.3    # Get a sepcific old release (in this case 1.0.3
+    pip install dronekit    # Install the latest version
+    pip install dronekit --upgrade    # Update to the latest version
+    pip show dronekit    # Find out what release you have installed
+    pip install dronekit=1.0.3    # Get a sepcific old release (in this case 1.0.3
 		
-See `Release History on the package ranking page <http://pypi-ranking.info/module/droneapi#release_history>`_  for a list of all releases available on PyPI.
+See `Release History on the package ranking page <http://pypi-ranking.info/module/dronekit#release_history>`_  for a list of all releases available on PyPI.
 

docs/about/release_notes.rst

@@ -5,7 +5,7 @@ DroneKit-Python API Reference
 =============================
 
 
-.. automodule:: droneapi.lib
+.. automodule:: dronekit.lib
    :members:
    :inherited-members:
    :exclude-members: Mission, get_mission, ConnectionInfo, web_connect, AuthInfo, delete

docs/automodule.rst

@@ -39,7 +39,7 @@ The steps to install this package and the most important add-on modules are:
    .. code:: bash
 
 	    pip uninstall python-dateutil
-	    pip install droneapi
+	    pip install dronekit
 
 The dependencies above are all that are required to build DroneKit-Python and the *MAVProxy command line* (i.e. the minimum needed for testing). 
 If you also want the *MAVProxy console* and map install:

docs/contributing/developer_setup_windows.rst

@@ -52,7 +52,7 @@ Looking at the code
 Using attribute observers
 -------------------------
 
-All attributes in DroneKit can have observers - this is the primary mechanism you should use to be notified of changes in vehicle state.  For instance, `drone_delivery.py <https://github.com/diydrones/droneapi-python/blob/master/examples/drone_delivery/drone_delivery.py>`_ calls:
+All attributes in DroneKit can have observers - this is the primary mechanism you should use to be notified of changes in vehicle state.  For instance, `drone_delivery.py <https://github.com/dronekit/dronekit-python/blob/master/examples/drone_delivery/drone_delivery.py>`_ calls:
 
 :: 
 

docs/examples/drone_delivery.rst

@@ -18,7 +18,7 @@ Before running this demo you'll need to make sure your computer has the gpsd ser
 
     apt-get install gpsd gpsd-clients
 
-You can then plug in a USB GPS and run the "xgps" client to confirm that it is working. If you do not have a USB GPS you can use simulated data by running *droneapi-python/examples/run-fake-gps.sh*.
+You can then plug in a USB GPS and run the "xgps" client to confirm that it is working. If you do not have a USB GPS you can use simulated data by running *dronekit-python/examples/run-fake-gps.sh*.
 
 Once your GPS is plugged in you can start follow-me by running the following command inside of MAVProxy:
 

docs/examples/follow_me.rst

@@ -123,11 +123,11 @@ After taking off (in guided mode using the ``takeoff()`` function) the example s
 The progress of the mission is monitored in a loop. The convenience function 
 :ref:`distance_to_current_waypoint() <auto_mode_mission_distance_to_waypoint>` 
 gets the distance to the next waypoint and 
-:py:func:`Vehicle.commands.next <droneapi.lib.CommandSequence.next>` gets the value of
+:py:func:`Vehicle.commands.next <dronekit.lib.CommandSequence.next>` gets the value of
 the next command.
 
 We also show how to move to a specified command using
-:py:func:`Vehicle.commands.next <droneapi.lib.CommandSequence.next>` (note how we skip the third command below):
+:py:func:`Vehicle.commands.next <dronekit.lib.CommandSequence.next>` (note how we skip the third command below):
 
 .. code:: python
 

docs/examples/mission_basic.rst

@@ -12,7 +12,7 @@ provided in the documentation for each example):
 
    .. code-block:: bash
 
-       git clone http://github.com/dronekit/droneapi-python.git
+       git clone http://github.com/dronekit/dronekit-python.git
 
    .. tip:: 
 
@@ -38,7 +38,7 @@ provided in the documentation for each example):
 
    .. code-block:: bash
 
-       module load droneapi.module.api
+       module load dronekit.module.api
 	   
 #. Once the *MAVProxy* console is running, start the example by entering: 
 

docs/examples/running_examples.rst

@@ -5,8 +5,8 @@ Example: Simple Go To (Copter)
 ==============================
 
 This example demonstrates how to arm and launch a Copter in GUIDED mode, travel to a number of waypoints, and then return 
-to the home location. It uses :py:func:`Vehicle.commands.takeoff() <droneapi.lib.CommandSequence.takeoff>`, 
-:py:func:`Vehicle.commands.goto() <droneapi.lib.CommandSequence.goto>` and :py:attr:`Vehicle.mode <droneapi.lib.Vehicle.mode>`.
+to the home location. It uses :py:func:`Vehicle.commands.takeoff() <dronekit.lib.CommandSequence.takeoff>`, 
+:py:func:`Vehicle.commands.goto() <dronekit.lib.CommandSequence.goto>` and :py:attr:`Vehicle.mode <dronekit.lib.Vehicle.mode>`.
 
 The locations used are centred around the home location when the :ref:`Simulated Vehicle <vagrant-sitl-from-full-image>` is booted; you can edit the latitude and longitude 
 to use more appropriate positions for your own vehicle. 
@@ -95,16 +95,16 @@ Takeoff
 -------
 
 To launch *Copter* you need to set the mode to ``GUIDED``, arm the vehicle, and then call 
-:py:func:`Vehicle.commands.takeoff() <droneapi.lib.CommandSequence.takeoff>`. The takeoff code in this example
+:py:func:`Vehicle.commands.takeoff() <dronekit.lib.CommandSequence.takeoff>`. The takeoff code in this example
 is explained in the guide topic :ref:`taking-off`.
 
 	
 Flying to a point - Goto
 ------------------------
 
 The vehicle is already in ``GUIDED`` mode, so to send it to a certain point we just need to 
-call :py:func:`Vehicle.commands.goto() <droneapi.lib.CommandSequence.goto>` with the target location, 
-and then :py:func:`flush() <droneapi.lib.Vehicle.flush>` the command:
+call :py:func:`Vehicle.commands.goto() <dronekit.lib.CommandSequence.goto>` with the target location, 
+and then :py:func:`flush() <dronekit.lib.Vehicle.flush>` the command:
 
 .. code-block:: python	
 

docs/examples/simple_goto.rst

@@ -18,7 +18,7 @@ The vehicle and DroneKit should be set up as described in :ref:`get-started`.
 
 If you're using a simulated vehicle remember to :ref:`disable arming checks <disable-arming-checks>` so 
 that the example can run. You can also `add a virtual rangefinder <http://dev.ardupilot.com/wiki/simulation-2/sitl-simulator-software-in-the-loop/using-sitl-for-ardupilot-testing/#adding_a_virtual_rangefinder>`_
-(otherwise the :py:attr:`Vehicle.rangefinder <droneapi.lib.Vehicle.rangefinder>` attribute may return values of ``None`` for the distance
+(otherwise the :py:attr:`Vehicle.rangefinder <dronekit.lib.Vehicle.rangefinder>` attribute may return values of ``None`` for the distance
 and voltage). 
 
 Once MAVProxy is running and the API is loaded, you can start the example by typing: ``api start vehicle_state.py``.