-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contributions? #22
Comments
It's also quite confusing that there are two bug/patch trackers at the moment (GitHub and Trac). I suggest closing one of them (and moving all content to the other one), as this added fragmentation is not helping anyone. |
If transmission developers decide to go with GitHub, I believe it would be consequent, to backup and re-create the repository and move all issues from Trac into GitHub, so that the numbering remains exactly, then re-add newer issues from backuped GitHub. Otherwise referring will be confusing (for old ones and for new ones), since there are a lot of opened issues on Trac. |
Any updates on the matter? |
What is the status here? Any comment from the developers/maintainers would be much appreciated. |
I'd like to help as well. Just looking at how many pull requests there are that haven't been merged yet is concerning: https://github.com/transmission/transmission/pulls Maybe @mikedld has something to say or can shed some light on how we can help become involved either as developers or PMs |
What is the current status of contributions to Transmission?
Is there anything anyone can do to make more development happen, or increase the pace? Are more maintainers needed? Seems like Trac is filled to the brim with patches that are long overdue, but no significant commits to code have happened since April.
It's really hard to figure this project and its status out at the moment, so some sort of update from the developers would be helpful.
The text was updated successfully, but these errors were encountered: