For those of us resisting dropping old Trac in favour of other non-distributed solutions.

See https://trac.edgewall.org/

Yep that would be nice. It's quite far on the current roadmap though.

However, it's a great area to start contributing if you are willing. During the summer, @A-Hilaly improved the bridge core and developed the advanced features like clean cancel or this kind of things. Developing a new bridge would be mimicking what is done with Github and Gitlab but with another API.

Agreed adding new bridges won't be a big deal. I can't find the official documentation for https://trac.edgewall.org/ API. @strk any idea where i can find that ?

There is no native API for Trac, but an XMLRPC plugin exists: https://trac-hacks.org/wiki/XmlRpcPlugin

The xmlrpc endpoint seems to be used by the tracboat which implements Trac to GitLab migration.

Commandline tool for Trac also uses XmlRpc plugin: https://code.google.com/archive/p/tracshell/

Michael Muré (MichaelMure) added label area/bridge 6 years ago

Another alternative would be hooking on commandline tool that can already interact with trac, like I did to integrate Trac with Mutt: https://strk.kbt.io/blog/2015/11/11/trac-from-mutt/

That tool doesn't require XmlRpc plugin to be installed on the Trac server.

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten 11 months ago

github-actions (github-actions) removed label lifecycle/stale 11 months ago

sudoforge removed label lifecycle/dormant 7 months ago