Maintenance of the project

[leonardodepaula]

@trco, do you intend to maintain the project?

There are not new commits since septemper 2021 and some pull requests like #192 waiting just to be merged.

Can we help in any way?

[melotte25]

Seems like @trco may be unavailable for the project. I typically hate saying this, but since it's been so long, maybe creating a fork of the project and migrating to a community based repo (like Jazzband) might be best for the future of the project.

Can give it another week or two, and then move forward as this is a hang up on moving to Django 4 and off of jQuery.

[trco]

@leonardodepaula @melotte25 I have planned to respond to this thread in reasonable time, but as always time ran me over. Unfortunately I'm not able to maintain the project to meet the needs and be up to date, however I'm totally into opening it for collaborators. I was planning to research what would be the best option to do it, since I would like that some standards are still followed, but I didn't do the research yet.

Do you maybe have any suggestions, proposals or maybe a direct interest to become full time collaborator with valid permissions to maintain the project? In such case I would propose that we define some valid "rules" and then the action can start. If this is not the case, do you maybe know someone who would be interested and has valid and reasonable predispositions to maintain this repo?

I would be really flattered if community would push things forward. This would be open source at its finnest.

Waiting for your thoughts...

[melotte25]

@trco - Totally understand that and get it!

I've seen projects move to https://github.com/jazzband as they are a "collective" where people can be Project Leads for various projects, and should a project go stale, someone can step up at any time.

There are downsides where they are a little slow due to the main project owners being limited (like 2-3 people), but that beats a single point of contact.

Here's more information on what that entails and how to do it if that's a path you'd be interested in pursuing: https://jazzband.co/about/guidelines

I'm not sure if there are other ways to go about it, but more than happy to help moderate/run if you'd like to keep it on the trco organization.

[leonardodepaula]

@trco, first of all, thanks for the answer. We totally get that you don't have much time to maintain the project, it happens...

I rely on the project a lot. I don't know enough javascript to maintain that part of the project, specially, as @melotte25 mentioned, getting out of jQuery. But I can sure check compatibility with Django versions and help on the python side of the code.

I don't think that the project demands a lot of attention, as it's pretty much robust and stable.

I like the idea of regular collaborators and defined rules to follow. Jazzband's guidelines seems to be a good start.

Make sense to invite @christianwgd and @comfix to the conversation, as they are responsable for the main pull requests (#195, #169) pending. I vote that we analise and test their code to begin.

Make sense to invite @WillowMist and @virdiignis as well, as they've already contributed to the project.

[trco]

Hey guys,

I have been thinking about next steps and decided to dedicate some time to the project again. It's really motivating when I read your nice words about this project.

I would be more than happy if you would be able to check an issue or two so we would together lower the number. In the majority the issues are mainly questions and not real issues. Of course I'll also consider any pull requests. Let me know if you're interested to collaborate this way.

My plan is to start with mentioned pending pull requests (#195, #169) and than continue from there...

@leonardodepaula @melotte25 @christianwgd @comfix @WillowMist @virdiignis Please let me know if you're interested in having either Triage, Write or Maintain access to this repository. I would be flattered if anyone decides to join. Waiting for your reply.

[Dresdn]

Hey @trco! I'd be more than happy to assist with running the project. We use this pretty extensively for an internal project, so there's an interest there.

I think those PRs you called out would be a great start.

[trco]

#169 Bootstrap5 support merged and released 🎉

@Dresdn It would be great to first have a contribution or two before gaining permissions for the project? What do u think? 😉

[Dresdn]

@trco - I get it. I realized I’ve been using the account tied to my work while this is my personal.

With #169 merged, I’ll open a PR here shortly with something we added.

[leonardodepaula]

@trco, that's great news! It's very nice to read that you gained some motivation again.

Count me on the issues, I will start to dedicate some time for them ASAP.