Who is maintaining this package now ?

[VianneyMI]

Who is maintaining this package now ? Is it actually still actively maintained ?

[AlexVonB]

@chrispy-snps and I do, sorry for letting some of you folks wait.

[VianneyMI]

Great job guys, 1.8k stars is impressive !
It would be nice to move this to a dedicated organization is the original author isn't maintaining anymore. What do you think ?

[AlexVonB]

Genuine question: what would be the benefits of that? Depending on those that could be something to consider. Besides, that would be up to @matthewwithanm to decide.

[VianneyMI]

The main benefits would be:

• Visibility & Trust: Moving to an org would signal active maintenance, which is important for a package with 1.8k stars. Right now, it might look abandoned to new users (at least that's how I felt), even if it’s not.

• Collaboration: Easier to add/maintainers, manage permissions, and distribute the workload. How much control do you and @chrispy-snps have on the repo now ?

• Longevity: If the original author is no longer involved, an org ensures the project isn’t tied to a single person’s availability.

What do you think ?

[chrispy-snps]

@AlexVonB - thanks for fielding this question, plus all your other recent work! I've been a bit caught up with my day job recently, but I hope to spend more time here soon.

@VianneyMI - is there a financial cost to forming this organization? As @AlexVonB says, he and I are recent contributors with sufficient privileges to spin releases, but this project ultimately belongs to @matthewwithanm and higher-level decisions are up to him.

[matthewwithanm]

Sorry I'm not really getting it. Why would an org signal active maintenance? Either way you'd be looking at recent activity right? (I'm also not sure what would've led you to think it was abandoned given that there are recent commits.)

I'm not strongly against, but right now I just don't see any benefits.