Implement Jazzband guidelines for django-revproxy about django-revproxy HOT 24 CLOSED

I think first task is asking for updating related repositories which are linking the old repo url. Last task could be considered as done.

Anyway, I can publish some PRs in order to keep updated this library.

• Drop python 2.7, 3.5 and 3.6
• Add support for python 3.11
• Add support for Django 4.0 and 4.1

from django-revproxy.

@brianmay Welcome and thanks for working on those items. I've accepted the PyPI invite and deleted the service hooks from the services we don't use for Jazzband projects.

from django-revproxy.

I proposed myself as project lead. It may resolve all tasks. See jazzband/help#333

from django-revproxy.

Closing as I think all steps are done.

from django-revproxy.

@thatsed @seocam This project was now been transferred...

from django-revproxy.

Done

from django-revproxy.

@jezdez Can you please help with releasing a new version that is already in the master?
Thanks.

from django-revproxy.

@andruten Done!

@mihalikv I've made @andruten project lead, he's the first person to get in touch with.

from django-revproxy.

I think I setup all the accounts as required. PyPI still pending on invite being accepted. If I got something wrong, please let me know.

from django-revproxy.

CI is with travis, probably this needs to be converted to use github actions I think.

from django-revproxy.

There are a number of services listed here:

https://github.com/jazzband/django-revproxy/settings/hooks

I suspect I don't have access to many. Might just want to delete these.

readthedocs was not listed (huh?) - hoping I correctly added it.

from django-revproxy.

Unfortunately I lack the expertise to help setup GitHub Actions for the project, should we ask on the members' team if there's someone available to help with that?

from django-revproxy.

@thatsed Sounds good to me. This probably should be done (if possible) by somebody with experience with other JazzBand projects.

from django-revproxy.

Hey @brianmay, could you tick both lines about the badge and CONTRIBUTING file (if the #139 PR is ok, of course)?

from django-revproxy.

I will take a look into the first check that's related to the README, and check why the docs setup is failing to me (maybe I just messed up). @brianmay you're going to setup the Codecov pipeline? Or other maintainer will? (Your doc is working fine?)

from django-revproxy.

Not really sure how jazzband configures codecov, and don't have a lot of time to investigate. Might be better if somebody more experienced with Jazzband supplies the github CI.

from django-revproxy.

README links have been updated and .github/workflow/release.yml has been created based on django-formtools ones but there is now a broken link related to tests:

.. image:: https://github.com/jazzband/django-revproxy/workflows/Test/badge.svg
   :target: https://github.com/jazzband/django-revproxy/actions
   :alt: GitHub Actions

Also added run section in .coveragerc

Upload coverage step says:

==> GitHub Actions detected.
    Env vars used:
      -> GITHUB_ACTIONS:    true
      -> GITHUB_HEAD_REF:   add-release-workflow
      -> GITHUB_REF:        refs/pull/154/merge
      -> GITHUB_REPOSITORY: jazzband/django-revproxy
      -> GITHUB_RUN_ID:     3409647564
      -> GITHUB_SHA:        fc417770cb2ca7edd5687f[29](https://github.com/jazzband/django-revproxy/actions/runs/3409647564/jobs/5681140262#step:8:30)1d0ab4114e1a6db9
      -> GITHUB_WORKFLOW:   Python package
    project root: .
    Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml
==> Running gcov in . (disable via -X gcov)
==> Python coveragepy not found
==> Searching for coverage reports in:
    + .
--> No coverage report found.
    Please visit http://docs.codecov.io/docs/supported-languages

I've been trying to locate that yaml file in several jazzband repos but I couldn't find it.

Can you please check this? @brianmay @jezdez

from django-revproxy.

README links have been updated and .github/workflow/release.yml has been created based on django-formtools ones but there is now a broken link related to tests:

Does this help? https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge

Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml

I am not familiar with any of this, but guessing you might need to create a new file from scratch using above instructions.

from django-revproxy.

Thank you @brianmay. I've published a PR for solving the link :). #155

from django-revproxy.

I think points 1, 4 and 5 can be marked as done. Am I right?

from django-revproxy.

Probably. Sounds good to me. Assume you can do it, otherwise let me know and I will do it.

from django-revproxy.

I see them as read-only, sorry. Can you please update them?

What do you think about remaining tasks?

from django-revproxy.

Done.

Review project if other services are used and port them to Jazzband

Not really sure what this is asking.

Decide who is project lead for the project (if at all)

Needs somebody with time. Not me :-)

Set up CI for Jazzband project releases if needed and open ticket if yes

Not sure I understand. Maybe this was done?

from django-revproxy.

Hi @jezdez! We've solved almost all tasks. There is a remaining issue related to publishing a release. It seems JAZZBAND_RELEASE_KEY is not set so release action is failing. I've opened an issue in the jazzband/help repository. Could you please help me? :)

from django-revproxy.