11# Developer's Guide
22
3- FLORIS is maintained at NREL's National Wind Technology Center .
3+ FLORIS is maintained by NLR .
44We are excited about community contribution, and this page outlines
55processes and procedures to follow when contributing to the
66source code. For technical questions regarding FLORIS usage, please
@@ -47,7 +47,7 @@ the [GitHub repository](http://github.com/nrel/floris). There,
4747[pull requests](http://github.com/nrel/floris/pulls) are managed,
4848questions and ideas are [discussed](https://github.com/NREL/floris/discussions),
4949and [new versions](http://github.com/nrel/floris/releases)
50- are released. It is the best mechanism for engaging with the NREL team
50+ are released. It is the best mechanism for engaging with the NLR team
5151and other developers throughout the FLORIS community.
5252
5353FLORIS development should follow " Git Flow" when interacting with the GitHub
@@ -58,7 +58,7 @@ process is detailed nicely [here](http://nvie.com/posts/a-successful-git-branchi
5858
5959# ## Syncing a local repository with NREL/FLORIS
6060The " main" FLORIS repository is continuously updated along with ongoing
61- research at NREL . From time to time, developers of FLORIS using their own
61+ research at NLR . From time to time, developers of FLORIS using their own
6262" local" repositories (versions of the software that exist on a local computer)
6363may want to sync with NREL/FLORIS. To do this, use the following git commands:
6464
@@ -290,7 +290,7 @@ Be sure to complete each step in the sequence as described.
290290
291291## Deploying to pip
292292
293- Generally, only NREL developers will have appropriate permissions to deploy
293+ Generally, only NLR developers will have appropriate permissions to deploy
294294FLORIS updates. When the time comes, here is a great reference on doing it
295295is available [here](https://medium.freecodecamp.org/how-to-publish-a-pyton-package-on-pypi-a89e9522ce24).
296296
0 commit comments