You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you explains status of this fork, please?
I mean, will we continue to install and update flakehell from PyPI by name flakehell or it would be some another package?
This is the only one acknowledged in the archived repo forks at https://github.com/orsinium/forks but the flakehell PyPI package still directs to the old archived repo.
It seems that both the docs and the pypi package are still directing to the archived one but as this repo has the group name and is the only acknowledged fork right now, I think this can be made to the "official work" by getting the pypi package to be updated by this repo and getting the documentation done from this repo too.
I think this group needs some more members with write access. @sgaynetdinov seems to be the only one making commits, but there's been little to no activity recently. There's no members defined of the flakehell group.
I think this group needs some more members with write access. @sgaynetdinov seems to be the only one making commits, but there's been little to no activity recently. There's no members defined of the flakehell group.
@sgaynetdinov Does your last comment still stand? I can see 3 PRs sitting idly without any comments, and 2 of them have been waiting for nearly a month.
The situation with the reported issues is not really much different. These facts almost give me the impression that this fork is not really governed/maintained.
I really appreciate your initiative to take action and create this fork to keep it going but, from a governing perspective, it's not ideal to have a single person with all permissions. I was expecting to hear something like the aim being to form a community to keep flakehell going. The original project is already abandoned by the only developer and we are here.
I think if we don't aim to build a set of members to govern the repo/organization, this fork can easily share the same fate on the day you can't dedicate enough time to check those incoming PRs or reported issues.
I think it would make sense to think a little bit more about the governance model for this repo since it is already under a flakehell GitHub organization rather than being placed under a plain user name. We can try to adopt a simpler form from the current communities like python maybe, or maybe a simpler model like pycqa project and team management.
Please don't get me wrong, I'm glad we now have a potential new home that a new community can show ownership. It's just my 2 cents.
Activity
Jaakkonen commentedon Mar 8, 2021
This is the only one acknowledged in the archived repo forks at https://github.com/orsinium/forks but the
flakehellPyPI package still directs to the old archived repo.It seems that both the docs and the pypi package are still directing to the archived one but as this repo has the group name and is the only acknowledged fork right now, I think this can be made to the "official work" by getting the pypi package to be updated by this repo and getting the documentation done from this repo too.
uSpike commentedon Apr 22, 2021
I think this group needs some more members with write access. @sgaynetdinov seems to be the only one making commits, but there's been little to no activity recently. There's no members defined of the
flakehellgroup.sgaynetdinov commentedon Apr 27, 2021
Hi, yes, I want the project to continue development. Now there is no new package in PyPi yet, if you have ideas by name, you can write them here!
sgaynetdinov commentedon Apr 27, 2021
You can apply changes through PR
bergerx commentedon Oct 13, 2021
@sgaynetdinov Does your last comment still stand? I can see 3 PRs sitting idly without any comments, and 2 of them have been waiting for nearly a month.
The situation with the reported issues is not really much different. These facts almost give me the impression that this fork is not really governed/maintained.
I really appreciate your initiative to take action and create this fork to keep it going but, from a governing perspective, it's not ideal to have a single person with all permissions. I was expecting to hear something like the aim being to form a community to keep flakehell going. The original project is already abandoned by the only developer and we are here.
I think if we don't aim to build a set of members to govern the repo/organization, this fork can easily share the same fate on the day you can't dedicate enough time to check those incoming PRs or reported issues.
I think it would make sense to think a little bit more about the governance model for this repo since it is already under a flakehell GitHub organization rather than being placed under a plain user name. We can try to adopt a simpler form from the current communities like python maybe, or maybe a simpler model like pycqa project and team management.
Please don't get me wrong, I'm glad we now have a potential new home that a new community can show ownership. It's just my 2 cents.