Merge pull request #36 from NovelaNeuro/user/wmerynda/ndx_relaease_0.1.004

release 0.0.004

Author: MarcinAtNovela

NEXTSTEPS.md

@@ -1,8 +1,8 @@
-# Next Steps for ndx-fl-novela Extension for NWB:N
+# Next Steps for ndx-franklab-novela Extension for NWB:N
 
 ## Creating Your Extension
 
-1. In a terminal, change directory into the new ndx-fl-novela directory.
+1. In a terminal, change directory into the new ndx-franklab-novela directory.
 
 2. Add any packages required by your extension to `requirements.txt` and `setup.py`.
 
@@ -14,15 +14,15 @@ and any other packages required by your extension.
     - If you want to create any custom classes for interacting with the extension,
       add them to the `src/pynwb`.
       - If present, the `src/pynwb` folder MUST contain the following:
-        - `ndx-fl-novela` - Folder with the sources of the NWB extension
-        - `ndx-fl-novela/__init__.py` - Python file that may be empty
+        - `ndx-franklab-novela` - Folder with the sources of the NWB extension
+        - `ndx-franklab-novela/__init__.py` - Python file that may be empty
       - If present, the `src/pynwb` folder MAY contain the following files/folders:
         - `test` - Folder for unit tests for the extensions
         - `jupyter_widgets` - Optional package with custom widgets for use with Jupyter
 
 5. Run `python src/spec/create_extension_spec.py` to generate the
-`spec/ndx-fl-novela.namespace.yaml` and
-`spec/ndx-fl-novela.extensions.yaml` files.
+`spec/ndx-franklab-novela.namespace.yaml` and
+`spec/ndx-franklab-novela.extensions.yaml` files.
 
 6. You may need to modify `setup.py` and re-run `python setup.py install` if you
 use any dependencies.
@@ -32,7 +32,7 @@ use any dependencies.
 
 1. Install the latest release of hdmf_docutils: `python -m pip install hdmf-docutils`
 
-2. Start a git repository for your extension directory ndx-fl-novela
+2. Start a git repository for your extension directory ndx-franklab-novela
  and push it to GitHub. You will need a GitHub account.
     - Follow these directions:
   https://help.github.com/en/articles/adding-an-existing-project-to-github-using-the-command-line
@@ -48,12 +48,12 @@ your extension.
 
 7. Add a license file. Permissive licenses should be used if possible. **A [BSD license](https://opensource.org/licenses/BSD-3-Clause) is recommended.**
 
-8. Make a release for the extension on GitHub with the version number specified. e.g. if version is 0.1.0, then this page should exist: https://github.com/NovelaDevops/ndx-fl-novela/releases/tag/0.1.0 . For instructions on how to make a release on GitHub see [here](https://help.github.com/en/github/administering-a-repository/creating-releases).
+8. Make a release for the extension on GitHub with the version number specified. e.g. if version is 0.1.0, then this page should exist: https://github.com/NovelaDevops/ndx-franklab-novela/releases/tag/0.1.0 . For instructions on how to make a release on GitHub see [here](https://help.github.com/en/github/administering-a-repository/creating-releases).
 
 9. Publish your updated extension on PyPi.
     - Follow these directions: https://packaging.python.org/tutorials/packaging-projects/
     - You may need to modify `setup.py`
-    - If your extension version is 0.1.0, then this page should exist: https://pypi.org/project/ndx-fl-novela/0.1.0
+    - If your extension version is 0.1.0, then this page should exist: https://pypi.org/project/ndx-franklab-novela/0.1.0
 
    Once your GitHub release and ``setup.py`` are ready, publishing on PyPi:
     ```bash
@@ -67,13 +67,13 @@ repository.
 11. Clone the fork onto your local filesystem.
 
 12. Copy the directory `staged-extensions/example` to a new directory
-`staged-extensions/ndx-fl-novela`:
+`staged-extensions/ndx-franklab-novela`:
 
     ```bash
-    cp -r staged-extensions/example staged-extensions/ndx-fl-novela
+    cp -r staged-extensions/example staged-extensions/ndx-franklab-novela
     ```
 
-13. Edit `staged-extensions/ndx-fl-novela/ndx-meta.yaml`
+13. Edit `staged-extensions/ndx-franklab-novela/ndx-meta.yaml`
 with information on where to find your NWB extension.
     - The YAML file MUST contain a dict with the following keys:
       - name: extension namespace name
@@ -87,28 +87,28 @@ with information on where to find your NWB extension.
 
   You may copy and modify the following YAML that was auto-generated:
 ```yaml
-name: ndx-fl-novela
+name: ndx-franklab-novela
 version: 0.0.5
-src: https://github.com/NovelaDevops/ndx-fl-novela
-pip: https://pypi.org/project/ndx-fl-novela/
+src: https://github.com/NovelaDevops/ndx-franklab-novela
+pip: https://pypi.org/project/ndx-franklab-novela/
 license: BSD 3-Clause
 maintainers:
   - NovelaDevops
 ```
 
-14. Edit `staged-extensions/ndx-fl-novela/README.md`
+14. Edit `staged-extensions/ndx-franklab-novela/README.md`
 to add information about your extension. You may copy it from
-`ndx-fl-novela/README.md`.
+`ndx-franklab-novela/README.md`.
 
   ```bash
-cp ndx-fl-novela/README.md staged-extensions/ndx-fl-novela/README.md
+cp ndx-franklab-novela/README.md staged-extensions/ndx-franklab-novela/README.md
 ```
 
 15. Add and commit your changes to Git and push your changes to GitHub.
 ```
 cd staged-extensions
-git add ndx-fl-novela
-git commit -m "Add new catalog entry for ndx-fl-novela" .
+git add ndx-franklab-novela
+git commit -m "Add new catalog entry for ndx-franklab-novela" .
 git push
 ```
 
@@ -117,17 +117,17 @@ Mac, and Linux. The technical team will review your extension shortly after
 and provide feedback and request changes, if any.
 
 17. When your pull request is merged, a new repository, called
-ndx-fl-novela-feedstock will be created in the nwb-extensions
+ndx-franklab-novela-feedstock will be created in the nwb-extensions
 GitHub organization and you will be added as a maintainer for that repository.
 
 
 ## Updating Your Published Extension
 
-1. Update your ndx-fl-novela GitHub repository.
+1. Update your ndx-franklab-novela GitHub repository.
 
 2. Publish your updated extension on PyPi.
 
-3. Fork the ndx-fl-novela-feedstock repository on GitHub.
+3. Fork the ndx-franklab-novela-feedstock repository on GitHub.
 
 4. Open a pull request to test the changes automatically. The technical team
 will review your changes shortly after and provide feedback and request changes,

README.md

@@ -1,7 +1,7 @@
-# ndx-fl-novela Extension for NWB
+# ndx-franklab-novela Extension for NWB
 
 # About
-ndx-fl-novela is a python package containing NWB custom extensions.
+ndx-franklab-novela is a python package containing NWB custom extensions.
 
 # Extensions
 

conda_upload.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 
-export PKG_NAME=ndx-fl-novela
+export PKG_NAME=ndx-franklab-novela
 export VERSION=$(python setup.py)
 export ANACONDA_API_TOKEN=$CONDA_UPLOAD_TOKEN
 export CONDA_BUILD_PATH=/home/travis/miniconda/envs/test-environment/conda-bld

docs/source/conf.py

@@ -17,12 +17,12 @@
 
 # -- Project information -----------------------------------------------------
 
-project = 'ndx-fl-novela'
+project = 'ndx-franklab-novela'
 copyright = '2020, NovelaDevops'
 author = 'NovelaDevops'
 
 # The short X.Y version
-version = '0.0.003'
+version = '0.0.004'
 
 # The full version, including alpha/beta/rc tags
 release = 'alpha'

docs/source/conf_doc_autogen.py

@@ -9,10 +9,10 @@
 spec_input_spec_dir = '..\spec'
 
 # Name of the YAML file with the specification of the Namespace to be documented
-spec_input_namespace_filename = 'ndx-fl-novela.namespace.yaml'
+spec_input_namespace_filename = 'ndx-franklab-novela.namespace.yaml'
 
 # Name of the default namespace in the file
-spec_input_default_namespace = 'ndx-fl-novela'
+spec_input_default_namespace = 'ndx-franklab-novela'
 
 
 # -- Options for customizing the locations of output files

docs/source/format.rst

@@ -1,8 +1,8 @@
 
-.. _ndx-fl-novela:
+.. _ndx-franklab-novela:
 
 ********************
-ndx-fl-novela
+ndx-franklab-novela
 ********************
 
 Version |release| |today|

docs/source/index.rst

@@ -1,4 +1,4 @@
-Specification for the ndx-fl-novela extension
+Specification for the ndx-franklab-novela extension
 ==================================
 
 .. toctree::

environment.yml

@@ -1,4 +1,4 @@
-name: ndx-fl-novela
+name: ndx-franklab-novela
 channels:
   - conda-forge
   - defaults

meta.yaml

@@ -1,11 +1,11 @@
 {% set data = load_setup_py_data() %}
 
 package:
-  name: ndx-fl-novela
+  name: ndx-franklab-novela
   version: {{ data.get('version') }}
 
 source:
-  git_url: https://github.com/NovelaNeuro/ndx-fl-novela
+  git_url: https://github.com/NovelaNeuro/ndx-franklab-novela
 
 build:
   number: 0

setup.py

@@ -1,5 +1,5 @@
 # -*- coding: utf-8 -*-
-version = "0.0.003"
+version = "0.0.004"
 print(version)
 
 import os
@@ -23,7 +23,7 @@
     readme = ""
 
 setup_args = {
-    'name': 'ndx-fl-novela',
+    'name': 'ndx-franklab-novela',
     'version': version,
     'description': 'NovelaNeurotechnologies Namespaces',
     'long_description': readme,
@@ -39,8 +39,8 @@
     'packages': find_packages('src/pynwb'),
     'package_dir': {'': 'src/pynwb'},
     'package_data': {'ndx_fl_novela': [
-        'spec/ndx-fl-novela.namespace.yaml',
-        'spec/ndx-fl-novela.extensions.yaml',
+        'spec/ndx-franklab-novela.namespace.yaml',
+        'spec/ndx-franklab-novela.extensions.yaml',
     ]},
     'classifiers': [
         "Intended Audience :: Developers",
@@ -51,8 +51,8 @@
 
 
 def _copy_spec_files(project_dir):
-    ns_path = os.path.join(project_dir, 'spec', 'ndx-fl-novela.namespace.yaml')
-    ext_path = os.path.join(project_dir, 'spec', 'ndx-fl-novela.extensions.yaml')
+    ns_path = os.path.join(project_dir, 'spec', 'ndx-franklab-novela.namespace.yaml')
+    ext_path = os.path.join(project_dir, 'spec', 'ndx-franklab-novela.extensions.yaml')
     dst_dir = os.path.join(project_dir, 'src', 'pynwb', 'ndx_fl_novela', 'spec')
 
     if not os.path.exists(dst_dir):