The more I think about, I believe you don't have to be concerned about accessing github for Apache NuttX.  Certainly, I respect your choice to keep your personal code out of "The Stack".  But NuttX will most likely be in the Stack and any changes you submit to NuttX will be in the Stack.  So it may be awkward for you, but I don't see any reason for you to avoid Apache NuttX in github while moving your personal code elsewhere.

Am I missing something?  You would probably like to make a clean break with github, but I think continuing to use the Apache NuttX repository (only) would be the more practical way to accomplished what you want to do.

On 3/21/2024 4:43 PM, Gregory Nutt wrote:
I think we need to continue to use PRs at some point in the process.  PRs are so tied into our CI that I don't think we could work around it.

Can you use another GIT repository?  If you create a PR on gitlab or bitbucket, someone could move the PR to github.  Or perhaps we could take commits from a local repository clone?  We haven't done it for a while, but patches could also be converted to github PRs with a little more effort.

I think there are options, but without PRs on github, I don't see how you could independently make changes.

On 3/21/2024 4:08 PM, Sebastien Lorquet wrote:
Hi,

I plan to leave github completely and delete my account, because of this: https://huggingface.co/spaces/bigcode/in-the-stack

It is the last of reasons that make me want to leave this place for good.

How can we imagine a process so I (and others) can continue to contribute to NuttX without using pull requests from github? or any public "forge" for that matter.

Sebastien

Reply via email to