Fix github, discord links (#61)

.github/CONTRIBUTING.md

@@ -23,10 +23,10 @@ For general `venvstacks` discussion (not specific to its use in LM Studio), ther
 
 For questions specifically related to the Python environment stacks used in LM Studio,
 the team is available through the `#dev-chat` channel within the
-[LM Studio Discord server](https://discord.gg/pwQWNhmQTY).
+[LM Studio Discord server](https://discord.gg/aPQfnNkxGC).
 
 ## Development Documentation
 
-Our [development documentation](https://lmstudio-ai.github.io/venvstacks//development/)
+Our [development documentation](https://lmstudio-ai.github.io/venvstacks/development/)
 contains details on how to get started with contributing to `venvstacks`,
 and details of our development processes.

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 LM Studio
+Copyright (c) 2024 Element Labs Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

docs/conf.py

@@ -7,7 +7,7 @@
 # https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information
 
 project = "venvstacks"
-copyright = "2024, LM Studio"
+copyright = "2024, Element Labs Inc."
 author = "LM Studio"
 release = "0.1"
 
@@ -56,7 +56,7 @@
 # -- Options for extlinks -------------------------------------------------------------
 
 extlinks = {
-    "issue": ("https://github.com/lmstudio/venvstacks/issues/%s", "#%s"),
-    "pr": ("https://github.com/lmstudio/venvstacks/pull/%s", "PR #%s"),
+    "issue": ("https://github.com/lmstudio-ai/venvstacks/issues/%s", "#%s"),
+    "pr": ("https://github.com/lmstudio-ai/venvstacks/pull/%s", "PR #%s"),
     "pypi": ("https://pypi.org/project/%s/", "%s"),
 }

docs/development/index.rst

@@ -23,7 +23,7 @@ available on `GitHub`_.
 
 .. code-block:: console
 
-    $ git clone https://github.com/lmstudio/venvstacks
+    $ git clone https://github.com/lmstudio-ai/venvstacks
     $ cd venvstacks
 
 
@@ -279,8 +279,8 @@ After release:
 * Bump the version in ``pyproject.toml`` and add a ``.dev0`` suffix
 
 .. _`Getting Started`: https://pip.pypa.io/en/stable/development/getting-started/
-.. _`open an issue`: https://github.com/lmstudio/venvstacks/issues/new?title=Trouble+with+development+environment
+.. _`open an issue`: https://github.com/lmstudio-ai/venvstacks/issues/new?title=Trouble+with+development+environment
 .. _`rich CLI`: https://docs.pytest.org/en/stable/how-to/usage.html#specifying-which-tests-to-run
-.. _`GitHub`: https://github.com/lmstudio/venvstacks
+.. _`GitHub`: https://github.com/lmstudio-ai/venvstacks
 .. _`testing README file`: https://github.com/lmstudio-ai/venvstacks/blob/main/tests/README.md
 .. _`misc/tag-release.sh`: https://github.com/lmstudio-ai/venvstacks/blob/main/misc/tag-release.sh

docs/overview.rst

@@ -168,7 +168,7 @@ the following Discord channels are the best way to get directly in touch with th
 * Discuss ``venvstacks`` in general in the ``#venvstacks`` channel on the
   `PyPA Discord Server <https://discord.com/invite/pypa>`__.
 * Discuss the use of ``venvstacks`` in LM Studio in the ``#dev-chat`` channel on the
-  `LM Studio Discord Server <https://discord.gg/rDk28gC7nv>`__.
+  `LM Studio Discord Server <https://discord.gg/aPQfnNkxGC>`__.
 
 The `"Packaging" category <https://discuss.python.org/c/packaging/14>`__ on
 `discuss.python.org <https://discuss.python.org/>`__ is also a reasonable place to provide feedback.