Implement Jazzband guidelines for prettytable

[hugovk]

This issue tracks the implementation of the Jazzband guidelines for the project prettytable.

See the TODO list below for the generally required tasks, but feel free to update it in case the project requires it.

(Based on the list at jazzband/tablib#378.)

Feel free to ping a Jazzband roadie if you have any question.

TODOs

• Fix all links in the docs (and README file etc) from old to new repo
• Add the Jazzband badge to the README file -> Add badges #20
• Add the Jazzband contributing guideline to the CONTRIBUTING.md or CONTRIBUTING.rst file
• Check if continuous testing works (e.g. Travis-CI, CircleCI, AppVeyor, etc) -> https://travis-ci.org/jazzband/prettytable
• Check if test coverage services work (e.g. Coveralls, Codecov, etc) -> https://codecov.io/gh/jazzband/prettytable
• Add jazzband account to PyPI project as maintainer role (e.g. URL: https://pypi.org/manage/project/prettytable/collaboration/)
• [n/a] Add jazzband-bot as maintainer to the Read the Docs project (e.g. URL: https://readthedocs.org/dashboard/prettytable/users/)
• [n/a] Add incoming GitHub webhook integration to Read the Docs project (e.g. URL: https://readthedocs.org/dashboard/prettytable/integrations/)
• Fix project URL in GitHub project description -> No URL
• [n/a] Review project if other services are used and port them to Jazzband -> there's a Fussy Fox integration that's not set up: https://github.com/jazzband/prettytable/runs/188061304. I've not used this service before, do we need it here?
• Decide who is project lead for the project (if at all)
• Set up CI for Jazzband project releases if needed and open ticket if yes

[hugovk]

I've updated all those I'm able to.

Ping @flaper87 and @jezdez for the others.

[flaper87]

prettytable has not been published on RTD yet so the whole setup should be done from scratch. I've given jazzband permissions on pypi and we should be able to automate releases.

[hugovk]

I've marked the RTD tasks as [n/a] because there is no RTD yet, and created #25 to import the old docs from the Google Code Archive wiki. If we need RTD in the future, we can set it up. Not a blocker.

I've also marked the "other services" one as [n/a], as the Fussy Fox thing doesn't seem essential right now, and not a blocker. We can deal with it later if needed.

@jezdez Please can you: "set up CI for Jazzband project releases if needed and open ticket if yes"?

When ready, I'd like to make a new release soon. I'll post a plan in #18.

[hugovk]

I've posted a request for help at jazzband/help#202. If nothing happens, another option to consider is a PEP 541 transfer.

[jezdez]

To enable the Jazzband releases we need to have a project lead first, so they can confirm releases pushed to the Jazzband package index. @hugovk Do you want to be project lead?

[hugovk]

@jezdez Sure, I can do that, at least to get a few new releases out the door. Thanks!

[hugovk]

Also, not sure if @flaper87 is interested at this time, but as a courtesy, would you @flaper87 also like to be a project lead?

[flaper87]

Also, not sure if @flaper87 is interested at this time, but as a courtesy, would you @flaper87 also like to be a project lead?

It would not be responsible for me to sign up to maintain this project knowing my current availability. I'm not actively working on this project anymore. I don't mind being around but I'd rather not be the Project Lead or main point of contact 🤗

[jezdez]

I'm just going to assume it'll be @hugovk only for now, but the roadies (me at the moment) will get release mails as well and can act as fallbacks. Better would be multiple leads of course, but that's a situations that some projects simply aren't in.

[jezdez]

This is done now. 🎊