Skip to content

Transfer this project to people who actually are maintaining it, or archive it #30

Open

Description

@Bobronium
A story

It's a beautiful project with a unique functionality that needs maintenance.

When @orsinium, it's author, realised that he wasn't going to maintain it, he did a great thing: called out for new maintainers.

@sgaynetdinov volunteered (orsinium/forks#1) and took over the project.

But after long absence of promised maintenance #25 appeared, where @mcarans had to contact @sgaynetdinov via email to get any response. It was closed with @sgaynetdinov stating "Yes, I will maintained this project.".

However It's been 5 months and only effort that has been made was changing theme in docs and removing various mentions of life4/flakehell from documentation, and only then merging one PR without even releasing it to PyPi.

It's alive!

There is a community fork that is actually being maintained (from #25 (comment) by @pwoolvett)

Hi @sgaynetdinov!

Together with @mcarans @lyz-code @jarojasm95

We have been working over at flakeheaven

  • The name change was required to publish on pypi, as requested by the original author, so we changed it everywhere
  • already merged several PRs
  • its being published on pypi
  • docs on read the docs

Would you like to join us? Or maybe the other way around, whichever you prefer...

@bergerx

Proposal

At this point, I think it would be better to archive this repo to show it's not going to be maintained.

@pwoolvett, would you like to use original name in case you will be able to have it?

Activity

  1. pwoolvett commented on May 9, 2022

    @pwoolvett

    Given both forks aim at just "maintaining" the project (as in no conflicting features), I still think we should keep efforts in one place, wherever. I'm slightly inclined to keep flakeheaven name just to make it evident for newcomers, but that opinion (1) mine, not of the other maintainers, and (2) not set in stone. Specially if gram decides to chime in every once in a while.

    https://www.youtube.com/watch?v=CxK_nA2iVXw

  2. mcarans commented on May 9, 2022

    @mcarans

    The flakeheaven name is helpful to distinguish from other forks. I agree it would be good if this repo were archived if it's not going to be maintained.

  3. blablatdinov commented on Jun 13, 2024

    @blablatdinov

    You can use ondivi Pypi Github. Is a Python script filtering coding violations, identified by static analysis, only for changed lines in a Git repo. You can use it with ruff, flake8, pylint, mypy and others.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions