Replies: 8 comments 1 reply
-
|
@kyamagu If you are okay with it, that's good with me. I was going to ask if you mind me appending myself to the author list (in |
Beta Was this translation helpful? Give feedback.
-
|
@kyamagu I seems to remember having gone through such a personal to org transfer before, and surprised that nothing broke. Apparently github would automatically set up redirections, and existing clones will continue to work . HTH. https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository |
Beta Was this translation helpful? Give feedback.
-
|
@HinTak Great, and thanks for the information. Yes, definitely, you should list your name on the author list. I'll be setting up the skia-python organization. |
Beta Was this translation helpful? Give feedback.
-
|
@HinTak Or, if you think I'm blocking any development process by late responses, you can initiate the organization setup. |
Beta Was this translation helpful? Give feedback.
-
|
@kyamagu there is no rush, do it when you have time. According to that github page (and also my past experience, I think), existing clones both online and off in somebody's hard disk continue to work. It is as if there is a auto-redirection from the old location under your account to the new; so there is probably no need to worry about telling everyone that the location has changed. As for further dev, skia m140 should be out in about a weeks' time. I am a bit busy right now for skia-unrelated things, and there is a whole pile of semi-broken auto-generated skia-related code from AI copilot in my example repo waiting to be fixed (basically AI copilot assumes that skia-python has the same APIs / calling convention / capability as other skia-bindings, such as the much older SkiaSharp, the newer rust-skia, and the quite complete skia4delphi, which skia-python isn't). I'll possibly do a m140-public pull just to keep up; but likely we did in the past, which is that we only do a release when it is more than "merely" keeping-up. Btw, I am surprised we haven't been overwhelmed with "things broke after I upgrade to 138" reports. Almost too quiet ;-). |
Beta Was this translation helpful? Give feedback.
-
|
Sure, perhaps we can start the organization setup when there isn't much work to do. And thank you for all your efforts in making the very successful m138 stable release. I hope m140 won't incur too much work |
Beta Was this translation helpful? Give feedback.
-
|
@HinTak I'm starting to set up the new organization https://github.com/skia-python |
Beta Was this translation helpful? Give feedback.
-
|
@kyamagu seems to have gone ahead okay. And fetch from the old location to update existing forks seem to continue to work too. I think the main thing now is just a v144.1 (or v144.0.post3) to pypi and online docs when it happens, before closing this as done. |
Beta Was this translation helpful? Give feedback.
-
|
PR #372 should update the remaining things, and the new docs URL https://skia-python.github.io/skia-python/ seems to be working ok now. (Actions). Please check the PR, and if that looks ok to you, proceed to the next step |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
@HinTak Thanks for all your efforts in skia-python maintenance!
Given the limited time, I will likely not be able to get involved much in skia-python development in the future, as I have been so far. I am now wondering if we should create a GitHub organization for skia-python and transfer the repository ownership there. That way, the project is shown to have been developed by multiple developers in the community, and I hope your contributions receive more recognition.
The short-term side effect is that the repository URL must be updated accordingly in all relevant locations.
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions