@jan-cosmigo, can you please enable Travis CI for this repository?

https://travis-ci.com/

After the repo ownership transferal all Travis continuous integration operations are working via redirection, but I'll be updating all URLs and references from the old repository to the new one, which might break Travis CI validation and badge images if the cosmigo organization doesn't have a Travis CI account, or if it isn't set to allows Travis integration on all its repositories.

Enabling Travis on all the repos would allow any future ownership transferal to seamlessly carry over its Travis jobs without requiring manual intervention.

NOTE — Travis CI free accounts should now be created on travis-ci.com, and not travis-ci.org (in case you have an old Travis account).

In the past the latter was used for free accounts, and the former for paid customers; but this was changed in the course of time and old users from the ".org" domain were asked to migrate their accounts and repositories to the ".com" domain. The ".org" domain will shut down soon anyway.

Ownership of this repository was transfered to the newly created @cosmigo organization:

• https://github.com/tajmone/pmotion2svg (previous location)
• https://github.com/cosmigo/pmotion2svg (current location)

Replace all references to the old repository URL, form the @tajmone user account to the @cosmigo organization in:

• Repo settings comments.
• README.adoc.

In the plug-in source files:

• src\pmotion2svg.pb — the #Repository$ constant, used for creating the text strings for the About dialog and the URLs for the links menus.

TRAVIS CI NOTE — Travis CI validation (and its status badge) will not work until @cosmigo enables Travis on the repository (See #1). Since the badge is already broken on main branch, there's no need to wait for Travis enabling before merging these fixes.

PB CODE NOTE — The constant in the PureBasic code will have to updated separately, when a new release is created. In the meantime, old links will still work as before because they will automatically redirected to the new repository location; so there's no rush to release a plug-in update.

---

References

• GitHub Docs » Transferring a repository