roll back some Codeberg-related changes

This commit is contained in:
adam j hartz 2025-09-27 13:23:49 -04:00
commit 7d2a2ac0b1
Signed by: hz
GPG key ID: B63A0A59F5C82493
7 changed files with 22 additions and 24 deletions

View file

@ -46,11 +46,11 @@ See <https://catsoop.org/website/docs/contributing/hacking>
CAT-SOOP incorporates pieces of third-party software. Licensing information
for the original programs is available in the
[`LICENSE.included_software`](https://codeberg.org/catsoop/catsoop/src/branch/main/LICENSE.included_software)
[`LICENSE.included_software`](https://catsoop.org/git/catsoop/catsoop/src/branch/main/LICENSE.included_software)
file.
The CAT-SOOP distribution also includes several pieces of third-party software.
Licensing information for these programs is included in this distribution, in
the
[`LICENSE.bundled_software`](https://codeberg.org/catsoop/catsoop/src/branch/main/LICENSE.bundled_software)
[`LICENSE.bundled_software`](https://catsoop.org/git/catsoop/catsoop/src/branch/main/LICENSE.bundled_software)
file.

View file

@ -6,15 +6,13 @@
\__=( o_O )=
(__________)
|_ |_ |_ |_
CAT-SOOP
</pre>
</center>
<center style="margin-top: 2em;">
<a class="btn btn-catsoop" href="COURSE/docs">Documentation</a>
<a class="btn btn-catsoop" href="https://codeberg.org/catsoop">Code</a>
<a class="btn btn-catsoop" href="https://codeberg.org/catsoop/catsoop/issues">Bug Tracker</a>
<a class="btn btn-catsoop" href="https://catsoop.org/git/catsoop">Code</a>
<a class="btn btn-catsoop" href="https://catsoop.org/git/catsoop/catsoop/issues">Bug Tracker</a>
</center>
@ -38,7 +36,7 @@ few elsewhere. Read more about CAT-SOOP at [this page](COURSE/docs/about).
* `catsoop-dev@mit.edu` for development-related discussion (subscribe [here](http://mailman.mit.edu/mailman/listinfo/catsoop-dev))
* Git Repository:
* <https://codeberg.org/catsoop/catsoop>
* <https://catsoop.org/git/catsoop/catsoop>
## CAN I USE IT FOR MY COURSE?

View file

@ -1,4 +1,4 @@
cs_long_name = "API"
cs_title = cs_content_header = "CAT-SOOP API"
source_view_url_root = "https://codeberg.org/catsoop/catsoop/src/branch/main"
source_view_url_root = "https://catsoop.org/git/catsoop/catsoop/src/branch/main"

View file

@ -8,7 +8,7 @@ thank you!
It's also worth mentioning that contributing to CAT-SOOP does not necessarily
mean writing code; there are lots of other ways to help out, too. The easiest
and best way to contribute to CAT-SOOP is to use it, to [report any issues you
find](https://codeberg.org/catsoop/catsoop/issues), and to tell your
find](https://catsoop.org/git/catsoop/catsoop/issues), and to tell your
friends/colleagues about it if you think they'd like it!
But please see below for some guidelines about contributing more directly to
@ -27,7 +27,7 @@ We're happy to help! The best way to get help is to send a message to
With the exception of security issues (see below), there are two main ways to
submit bug reports or feature requests: using the [issue
tracker](https://codeberg.org/catsoop/catsoop/issues/) directly, or sending
tracker](https://catsoop.org/git/catsoop/catsoop/issues/) directly, or sending
a message to `catsoop-dev@mit.edu`. When reporting a bug, please be as
descriptive as you can, and please try to include an example that demonstrates
the issue if possible. Among other things, it is helpful to know what version

View file

@ -15,23 +15,23 @@ setting up a local testing copy and for contributing changes back to CAT-SOOP.
<catsoop-subsection>Cloning the Repository</catsoop-subsection>
CAT-SOOP's source code is hosted on [Codeberg](https://codeberg.org), a
software forge powered by Free Software ([why not
github?](https://sfconservancy.org/GiveUpGitHub/)). Codeberg uses a similar
CAT-SOOP's source code is hosted on a local, self-hosted
[Forgejo](https://forgejo.org/) instance at <https://catsoop.org/git> ([why not
github?](https://sfconservancy.org/GiveUpGitHub/)). Forgejo uses a similar
workflow to other modern source forges. While we do accept patches via e-mail
to `catsoop-dev@mit.edu`, the preferred method for contributing to catsoop is
outlined below.
The first step is to create a 'fork' of the catsoop repository by going to
<https://codeberg.org/catsoop/catsoop>, logging in (after creating an account),
creating a 'fork' of the main repository by clicking on the "Fork" button in
the upper-right corner of the page, [adding an SSH key to your
<https://catsoop.org/git/catsoop/catsoop>, logging in (after creating an
account account), creating a 'fork' of the main repository by clicking on the
"Fork" button in the upper-right corner of the page, [adding an SSH key to your
account](https://docs.codeberg.org/security/ssh-key/), and then cloning your
fork of the repository, which will look something like:
```nohighlight
git clone git@codeberg.org:YOUR_USERNAME/catsoop
git clone git@catsoop.org:YOUR_USERNAME/catsoop
```
<catsoop-subsection>Installing CAT-SOOP for Development</catsoop-subsection>
@ -84,7 +84,7 @@ clone the sample course if you do not already have another course to work with,
using the following command:
```nohighlight
git clone https://codeberg.org/catsoop/sample_course ~/.local/share/catsoop/courses/sample_course
git clone https://catsoop.org/catsoop/sample_course ~/.local/share/catsoop/courses/sample_course
```
(or you could similarly fork the `sample_course` repository if you want to make
@ -106,7 +106,7 @@ process and restarting it.
If you don't already have an idea in mind, some issues in the issue tracker are
marked as potential good opportunities for a first dive into the codebase. You
can view these issues [here](https://codeberg.org/catsoop/catsoop/issues?labels=17),
can view these issues [here](https://catsoop.org/git/catsoop/catsoop/issues?labels=17),
or by manually searching for them from the catsoop issue tracker. Feel free
to reach out if you need help!
@ -179,8 +179,8 @@ Before sending your changes, please:
<catsoop-subsection>Preparing and Sending Patches</catsoop-subsection>
Roughly speaking, any way you want to get your changes to us is fine! But our
preferred method is via a pull request on repository on Codeberg. Codeberg has
some instructions for making pull requests at
preferred method is via a pull request on the Forgejo instance. Codeberg
(which also runs on Forgejo) has some instructions for making pull requests at
<https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/>.
If it's easier for you, though, we also accept patches over e-mail to

View file

@ -51,7 +51,7 @@ $ pip3 install catsoop
Alternatively, you can clone the repository with Git:
```
$ git clone https://codeberg.org/catsoop/catsoop
$ git clone https://catsoop.org/git/catsoop/catsoop
```
After you have a local copy, you can then run:
@ -94,7 +94,7 @@ If you're not sure what to put there, a decent place to start is with the
the following, using Git:
```
$ git clone https://codeberg.org/catsoop/sample_course ~/.local/share/catsoop/courses/sample_course
$ git clone https://catsoop.org/git/catsoop/sample_course ~/.local/share/catsoop/courses/sample_course
```
<catsoop-section>Start CAT-SOOP</catsoop-section>

View file

@ -2,7 +2,7 @@ cs_auth_required = False
cs_long_name = "CAT-SOOP"
cs_content_header = ""
source_link = "https://codeberg.org/catsoop/catsoop"
source_link = "https://catsoop.org/git/catsoop/catsoop"
cs_footer = """The content of this page is Copyright &copy; 2016-2025 by the CAT-SOOP Developers.<br/>
This content is licensed under the <a href="BASE/_util/license" target="_blank">GNU Affero General Public License, version 3</a>, as is CAT-SOOP itself.<br/>