You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@uwlib-cams staff is not able to provide support or ongoing updates to the software, so we'd like to make the shaclgen repo a public archive. Effects of this include for example:
Once a repository is archived, you cannot add or remove collaborators or teams. Contributors with access to the repository can only fork or star your project.
When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. To make changes in an archived repository, you must unarchive the repository first.
Tagging the creator of this software @alexiskeely , and those who have made pull requests and submitted issues @white-gecko@mielvds and @Remya-Ramachandran in the event that discussion is needed prior to taking this action.
The text was updated successfully, but these errors were encountered:
Dear @briesenberg07 thank you for your notice. I would not like to see this repository being archived but I understand you not having the capacity to maintain it and want to clean up.
I would not have a lot of capacity to put into the repository but if I can keep it from being archived, I could suggest to move the repository to the aksw group. https://github.com/AKSW/ Would that be an option for you?
Hello @white-gecko
We appreciate your offer to transfer the repository to ASKW and would like to do so. Let's discuss next steps? My email address is [email protected].
@uwlib-cams staff is not able to provide support or ongoing updates to the software, so we'd like to make the shaclgen repo a public archive. Effects of this include for example:
Tagging the creator of this software @alexiskeely , and those who have made pull requests and submitted issues @white-gecko @mielvds and @Remya-Ramachandran in the event that discussion is needed prior to taking this action.
The text was updated successfully, but these errors were encountered: