Jannis Leidel

@pmclanahan and me are interested in that as well after talking to @fmarier a bit (spec coauthor).

@neithere 1. Yeah, this is desirable assuming you follow the [guidelines](https://jazzband.co/about/guidelines). django-autoslug seem to be well-suited for that. 2. Once you transferred the repo to the Jazzband organization via [GitHub's...

@justinmayer Thank you for the offer to help. Anything that you need, please let me know. PS: I just opened #75 to document the process of repo transfer better.

As another data point, pandas has their supporters listed on their website: https://pandas.pydata.org

Interesting! I like that idea. It would assume that it'd require a join/leave UI on the Jazzband site since I can't offer org admin permissions to join/leave teams for all...

To be clear you're not proposing to actually assign different repos to each team and by that limiting the access permissions again for members "outside of their skillset"?

@untitaker Hey there again, took me a while but I've been thinking about this more recently since I want to improve the unassisted releases to PyPI which in turn requires...

So in https://github.com/jazzband/website/commit/8bac98e1a824989d2c464ccd91fdf6ba2290555d I've added per-project memberships, which I will map to GitHub teams so it's easier to be notified per-project with @jazzband/my-project etc. The UI hasn't been updated to...

@untitaker Ah, bummer, thanks for the idea though, together with the [per-team-discussion boards](https://github.com/blog/2471-introducing-team-discussions) this could be a neat thing to do.

> @Alir3z4 I don't think it would be a good idea to host it with the jazzband organization. @jezdez seems generally non-responsive to requests and does not have the availability...