Problems with having external github repos for projects

[HrishabhMittal]

Problem

All github repos that are linked in docs are personal repos of the people who are already part of this community. This can cause problems as:

• these people if they ever decide to delete/private these repos due to their own reasons, then the code for future reference is basically lost
• all code us not readily available in the community repos, which also makes the community itself look barren.

Solution

• Make repos for each project and ask the repo owner to also add a new remote url to the git repos

git remote add qc <qc-github-repo-url>
git push -u qc main # or whatever the branch name is

[arhamaneeq]

Hey, Hrishabh.

A policy we intend to adhere to in the Club is for individuals to retain full ownership over their work/writing/etc. While all of the projects listed in this repository are related to the Club by virtue of its members, each project was undertaken by a subset of the members, not the entire club as a whole.

Currently adding a second upstream to create a mirror gives no indication of the original repository, as far as I can tell.

That said, we're open to creating an automation that forks all repositories with a topic such as qc-iiti since forks directly link to the original repository.

The current arrangement works decently, (though could be improved by some sort of automation). You're welcome to weigh in though, the Club page does feel empty and that is concerning.