Current state

[COM8]

Current state

[jpbernius]

Update: I just checked with the "Renaming a repository" documentation and it looks like GitHub pages will not redirect.

In the mean time, I did setup travis for my fork and merged all open pull request.

[kordianbruck]

Here we go: https://github.com/TUM-Dev/eat-api

I've also sent invites to everyone in here with write access. srehwald@ has admin access. If @COM8 wants to lead the project, that is also fine by me.

[kordianbruck]

I've proposed to move this repository to github.com/TUM-Dev to increase its visibility and allow more people to contribute. Back then srehwald mentioned that it might be quite cumbersome to move it and change the name of the repo location due to how the setup works. I'm happy to host the project or a fork at TUM-Dev any time.

srehwald is currently a bit busy from what I know.

[jpbernius]

Moving the repo should lead to GitHub creating redirects, I can try to verify it that is also the case for GitHub pages.

Otherwise, setting up a fork primarily requires to set up Travis with a secret / ssh key to push to gh-pages

[raabf]

Currently, I am personally in the finishing phase of my master thesis. So for long term maintenance I am probably not suitable any more. However, a team like TUM-Dev to maintain the project sounds not bad.

[srehwald]

@COM8 thanks for opening up that issue!
Well, I'd definitely love to actively maintain this project, but I am lacking time to reasonably do so. So, it's about time to fix that!
Personally, I like @kordianbruck's suggestion of migrating to TUM-Dev most as this might ensure that people currently studying at TUM get to know this project and contribute to it. Since @kordianbruck has already moved several projects to TUM-Dev from what I know: How would you transfer this repository? Would that be a fork? I think it makes sense to set it up in parallel to ensure a smooth transition for all other applications currently using it.

[jpbernius]

I think you can use GitHubs "Archive" feature for this repository.

When you archive a repository, you are letting people know that a project is no longer actively maintained.

We recommend that you close all issues and pull requests, as well as update the README file and description, before you archive a repository

-- "GitHub Help: About archiving repositories"

I created a test repo to find out how archiving affects pages. So far it is looking good, but let's see how this looks tomorrow.

---

Edit: Despite from what I said, this repo should not be archived, as this would prevent the daily build process and therefore stop updating for all projects currently using the known api endpoint.

[COM8]

@kordianbruck sure, why not.