The majority of the jtorctl work in the past 10 years has happened on github, so tor's official repo should have a mirror there to keep it visible there.
It'd be fine to have the current torproject/jtorctl there to start with, as ancient as it is. Then hopefully, I can make the guardianproject/jtorctl be a fork of that one.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Thanks Hiro! Yes, please move the jtorctl repo out from the attic (it seems like we are giving it a second life). Please add sysrqb and sisbell in the group for write access.
Thanks Hiro! It seems that the sync is not pushing commits from https://gitweb.torproject.org/jtorctl to GitHub, because the GitHub project is still blank.
Thanks Hiro! It seems that the sync is not pushing commits from https://gitweb.torproject.org/jtorctl to GitHub, because the GitHub project is still blank.
The pusher requires write permissions to the repository to do a sync. I added the pushers group with the correct permissions. The next commit should trigger a sync.
If anyone wants to be able to handle pull requests or CI for the repository, they'll also need write permissions. Please let us know which GitHub users need write permissions, and we'll put them in the jtorctl-maintainers team on GitHub. (It has write permissions, but there's no-one in it.)
In the meantime, I turned off a bunch of optional features, like wikis and issues, to avoid spam. Let us know if you need them turned back on.
Right now, no one is able to push to the git.tpo repo, which means this is not maintained software. I've done a manual push to GitHub to establish the mirror with the latest version of what we have at git.tpo. This won't ever be updated (unless new maintainers appear), but you'll be able to fork it.