Who will maintain this repo?

[brucearctor]

Now that I am no longer with ChartBoost, who will be maintaining this repo?

Perhaps we should give some permissions and/or redirect for the sake of the many users reliant on this?

ex, more than 1.2K public usages of 'chartboost/ruff-action' --> https://github.com/search?q=chartboost%2Fruff-action&type=code

https://github.blog/2013-05-16-repository-redirects-are-here/

[brucearctor]

@CB-GuangyaoXie ?

[ma-sadeghi]

Sorry for the off-topic comment: Could you please review/merge #24? Thanks :)

[brucearctor]

I'll take a look when at computer:

• unclear whether I still have permissions.

• need to look at your code, and consider risks if this introduces new dependencies

[brucearctor]

Update -- ya, def. don't have permissions.

I have suggested I am willing to accept transfer [ https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository ] to continue to maintain for the good of the community of users.

[ma-sadeghi]

Is there any point of contact at ChartBoost to initiate the transfer?

[augustelalande]

@charliermarsh would it make sense to pull this under the astral umbrella? Seems like a core functionality for the linter.

[charliermarsh]

Yeah, we can maintain an official GitHub Action.

[charliermarsh]

We can transfer it under Astral if someone has permissions to do so.

[augustelalande]

@daniel-barros ?

[zanieb]

👍 yeah I'm happy to maintain if it's transferred

[brucearctor]

Tbd if you need to fork, unclear that chartboost legal will be ok with transfer [ had requested ]

Great to also get in gh action marketplace, while I was employed there I failed at getting needed approvals to get gh developer license signed which was a prerequisite

Ideally transfer occurs to better serve/transition the community of users. That is why I hadn't forked myself... without transfer, the best place for this to fork/live is likely in Astral.

[charliermarsh]

I will give it a week or so. If we don't hear back, we'll just create a new repo in the Astral org.

[ffernandez92]

I had permission to merge the PR. I think there is a bit of risk in adding an extra dependency, but it seems to be working fine. I'd like to wait until the repo is transferred so we can generate the release. Let me know if I can help with anything

[vitaliyf]

Hopefully I'm not getting too ahead of myself - but can Astral also press the necessary buttons to become a "verified" publisher in the actions marketplace? One of the security options for GitHub actions within paid accounts is to restrict 3rd party actions to only those published by verified publishers, and some organizations require this for various supply-chain-security reasons.

They document the necessary steps here: https://docs.github.com/en/apps/github-marketplace/github-marketplace-overview/applying-for-publisher-verification-for-your-organization

[brucearctor]

@ffernandez92 -- ideally this winds up transferred to https://github.com/astral-sh ... I think GY has permissions to do that [ I imagine you do not? ] but perhaps waiting on [ lack of? ] legal approval?

There isn't anything company specific/proprietary in here. Transfer would be the cleanest way to save the company from maintenance, AND esp. be kindest to the community by way of redirect, etc... But 🤷 .

[zanieb]

Any updates from someone who works at ChartBoost? It'd be great to provide uninterrupted service for the users of this.

[brittag]

Thanks all for your thoughtful consideration of ensuring a smooth transition for this action! Just adding appreciation and encouragement as part of a team that uses it for our open source web application. :)

[nitishxp]

@charliermarsh Can you please help us on merging this https://github.com/ChartBoost/ruff-action/pull/29

[zanieb]

@nitishxp we cannot merge pull requests here — ChartBoost has not taken any action towards transferring the project.

[nitishxp]

@zanieb can we shift that repo under astra, that defect is literally blocking us for most of the things

[zanieb]

@nitishxp we do not have control over transfer of this repository, as discussed above — ChartBoost needs to take action for a seamless transition.

We'll create our own action eventually, if it comes to that.

[ma-sadeghi]

The action is released under Apache 2, which is fairly permissive. Why not fork it under astral?

[zanieb]

If the repository is transferred instead, there won't be an interruption for existing users (usage will be redirected).

[brucearctor]

Last I heard from employees [ I am no longer there ], this was going through legal approval process to transfer. I can ask whether stuck, a determination, or in-progress still. Also, I believe one guy who can merge/maintain is on vacation currently, so tbd. Forking is permitted, not the worst idea, but certainly much better if this can be transferred.

On Sat, Aug 10, 2024, 9:03 AM Amin Sadeghi @.***> wrote:

The action is released under Apache 2, which is fairly permissive. Why not fork it under astral?

— Reply to this email directly, view it on GitHub https://github.com/ChartBoost/ruff-action/issues/26#issuecomment-2282194925, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGMTJDAUUZYMUGJ7AQTMN3ZQY2UTAVCNFSM6AAAAABGF4AQJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGE4TIOJSGU . You are receiving this because you authored the thread.Message ID: @.***>

[charliermarsh]

I think if we find time to prioritize it before the transfer completes, and there's no clear timeline, we'll just fork. But if the transfer completes before we get to it, that's obviously preferable.