[Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Suggestions and discussion of future versions
Post Reply
darkred
Member
Member
Posts: 12
Joined: Mon May 06, 2019 4:57 pm

[Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Post by darkred »

Greetings

I'd like to make two suggestions to Deluge's developers, please:
  • Make use of the new 'GitHub Actions'.
    Here is the new 'GitHub Actions' announcent: https://github.blog/2019-08-08-github-a ... rts-ci-cd/
    Currently beta: you sign up for it here https://github.com/features/actions and so you get in a queue, and you'll get notified once you have access.
    I believe it will facilitate a lot in automating Deluge's builds, across all platforms.
    I'm mentioning this very interesting announcement, in case it might have slipped your attention.
  • Currently Deluge uses: I find that the Trac system is dated, bloated and inconvenient, so, my suggestion is to consider migrating the issue tracker to the GitHub repo. I think that by migrating wiki and issue tracker to GitHub, i.e. by having the whole project hosted in GitHub, it would help in getting more attention to the project and more people to actively contribute in Deluge's development.

    Here is a (old but hopefully still useful) StackOverflow question in which the various ways to make the migration are listed : How to export Trac to Github Issues (For reference, the current count of active tickets is 446)
PS. I hope my two suggestions might especially help Why is there no Deluge 2.0 exe for Windows.
Last edited by darkred on Fri Apr 17, 2020 7:18 pm, edited 5 times in total.
darkred
Member
Member
Posts: 12
Joined: Mon May 06, 2019 4:57 pm

Re: [Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Post by darkred »

Regarding 'GitHub Actions':
it's been announced today that GitHub Actions is now out of beta, i.e. generally available:
Starting today, GitHub Actions is generally available. GitHub Actions are free for all public repositories, and every plan gets included storage and runner minutes for private repositories.
https://github.blog/changelog/2019-11-1 ... available/
darkred
Member
Member
Posts: 12
Joined: Mon May 06, 2019 4:57 pm

Re: [Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Post by darkred »

Starting today the GitHub Actions API is also generally available and out of beta.
https://github.blog/changelog/2020-03-2 ... available/
OpenDeluge
New User
New User
Posts: 4
Joined: Mon Nov 06, 2017 11:08 am

Re: [Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Post by OpenDeluge »

Good Idea, I can help with migration.
darkred
Member
Member
Posts: 12
Joined: Mon May 06, 2019 4:57 pm

Re: [Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Post by darkred »

Also, 3 weeks now, 'GitHub Discussions' are available as a public beta:
GitHub Discussions is now available as a public beta, providing you with a dedicated space for your community to ask and answer questions, and have conversations that are separate from issues in your repository.

Discussions work a lot like issues. However, with discussions you can also:
  • Mark questions with an answer
  • Convert issues into discussions
  • Categorize discussions – fully customizable
  • Have threaded conversations
  • Pin up to 4 discussions
https://github.blog/changelog/2020-12-0 ... blic-beta/
darkred
Member
Member
Posts: 12
Joined: Mon May 06, 2019 4:57 pm

Re: [Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Post by darkred »

'GitHub Discussions' is finally out of beta:

https://github.blog/changelog/2021-08-1 ... t-of-beta/
Cas
Top Bloke
Top Bloke
Posts: 3679
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: [Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Post by Cas »

Hey darkred, thank you for making these suggestions. I have considered moving to GitHub in the past and at the time it was not as feature-full as it is now. As well as having concerns about putting everything in one place with no control over it.

Yes Trac is not perfect and I recently had to require GitHub login due to spam but Trac does mostly work for what we need although we can have self-hosted GitLab as an open-source alternative. The barrier to moving to a new ticket system is the huge amount of time and effort to convert these existing systems, we tried moving to Redshift many years ago which didn't go anywhere...

For the wiki I have already made progress with moving a lot of content to the docs but more work is required.

The use of GitHub discussions is interesting but this forum does fulfil the task. In the meantime I could add one of the phpBB extensions: https://www.phpbb.com/customise/db/exte ... st_answer/

I don't think not whether or not Deluge fully uses Github is a major barrier to contributions. What I do see is an issue with the quality of contributions so Deluge remains maintainable but more automation and guidance might help.

In summary, yes I am aware it could be better but it just about works and I don't think it adversely affects the project.
darkred
Member
Member
Posts: 12
Joined: Mon May 06, 2019 4:57 pm

Re: [Suggestions] Make use of 'GitHub Actions' + Migrate issue tracker from Trac to GitHub

Post by darkred »

Thank you for responding both in GitHub and in here. I really appreciate that you've answered in details.


I just have one question:
I see the tremendous ongoing work in the repo, and the various runs of the Package workflow (automated or manual), last being 2 days ago
that generates the following artifacts, 4 executables, every time:

Code: Select all

deluge-py3.9-lt1.2.15-x64.exe
deluge-py3.9-lt1.2.15-x86.exe
deluge-py3.9-lt2.0.5-x64.exe
deluge-py3.9-lt2.0.5-x86.exe
So, is it in your plans to make a 'stable' 2.x release in github (I mean in the 'Releases' tab in the GitHub repo) and add it in the windows mirror site (last one is from 2017) ?
Post Reply