Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: django-invitations #237

Closed
6 tasks done
brylie opened this issue Aug 24, 2021 · 16 comments
Closed
6 tasks done

Proposal: django-invitations #237

brylie opened this issue Aug 24, 2021 · 16 comments

Comments

@brylie
Copy link
Member

brylie commented Aug 24, 2021

Project Proposal

Please fill in the details below to confirm you adhere to the Jazzband Guidelines, and also add the package name to the issue title.

Project Details

django-invitations

Project Description

Generic invitations solution with adaptable backend and support for django-allauth. All emails and messages are fully customisable.

The original developer has expressed that they can no longer maintain the project. However, there are several open pull requests from community contributors.

Project Leads

Please list anyone who you would like to be made a project lead.

Confirmation of Guidelines

Please confirm the following:

@brylie
Copy link
Member Author

brylie commented Jan 13, 2022

Hei all. Can we please review this proposal? It has heart support but no reviewers.

@MrCordeiro
Copy link

@brylie, what should be the next steps here? Is there any Jazzband member we should contact?

@jezdez
Copy link
Member

jezdez commented Jan 27, 2022

I'm sorry this is stuck on the proposal backlog, I think the things that jump out that needs to be checked before a transfer can happen:

  • the docs are sparse and would need to be ported to a Sphinx project and hosted on Read The Docs. This can be done after the transfer but I need acknowledgement that this would happen
  • the package metadata doesn't contain data which license this is released under, while the LICENSE file is GPL3
  • the CI setup would need to be ported to GitHub Actions, but virtually all other Jazzband projects can be used as inspiration

@MrCordeiro
Copy link

Thanks, @jezdez!

@brylie, I see you have a PR going. Need any help? I could try adding to it.

@brylie
Copy link
Member Author

brylie commented Jan 27, 2022

Thanks, @MrCordeiro. Feel free to contribute to the PR in any way that would help the proposal move forward :-)

@MrCordeiro
Copy link

  • the CI setup would need to be ported to GitHub Actions, but virtually all other Jazzband projects can be used as inspiration

@jezdez, I was looking at the other projects and got a question. Should I just create a Test workflow for now and then the Release workflow when the project is moved, or do I create both now? Thanks!

@jezdez
Copy link
Member

jezdez commented Jan 28, 2022

  • the CI setup would need to be ported to GitHub Actions, but virtually all other Jazzband projects can be used as inspiration

@jezdez, I was looking at the other projects and got a question. Should I just create a Test workflow for now and then the Release workflow when the project is moved, or do I create both now? Thanks!

You can create both of them and just change the names in the release workflow, it'll be identical for this project and just needs the release key to enable it, that I'd do.

@MrCordeiro
Copy link

Done, @jezdez!
The only thing missing is to port the docs to a Sphinx project, be we can do this after the transfer, right?

@jezdez
Copy link
Member

jezdez commented Jan 31, 2022

@MrCordeiro Yep, totally fine. Feel free to transfer the repo with the usual repo transfer functionality, a ticket to track the rest of the TODOs will be opened automatically.

@MrCordeiro
Copy link

@brylie, have you had any news of the transfer?

@brylie
Copy link
Member Author

brylie commented Feb 10, 2022

@MrCordeiro, nope. I think @bee-keeper will need to initiate the transfer from their account.

@valberg
Copy link

valberg commented Mar 30, 2022

I guess that only @bee-keeper can do the transfer? Is forking the project a viable alternative if we do not hear from them?

@bee-keeper
Copy link
Member

Hi, sorry i've been slow on this. I just made the transfer now so should be all good?

@valberg
Copy link

valberg commented Mar 30, 2022

@bee-keeper Awsome! No need to be sorry - we all have stuff to do that gets in the way of other stuff :)

I can see django-invitations on the jazzband website now: https://jazzband.co/projects/django-invitations 👏

@MrCordeiro
Copy link

@bee-keeper You'll see that there is a checklist of things required to complete the transfer here, like changing the user for coveralls and adding the Jazzband bot as a project maintainer on Pypi, that only you'll be able to do.

@chrysle
Copy link

chrysle commented Jul 1, 2023

@jezdez Since the transfer has been completed, this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants