-
Notifications
You must be signed in to change notification settings - Fork 31
README: add note about development moved to the new repo. #85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Oops , we forgot this part in crédits |
Right, I missed that one... I will just delete that line and make one more update. |
github has a button "transfer ownership" which is IMO better than what you're doing here - people visiting the old url get automatically redirected to the new one. another alternative is to create a new organization and transfer the repo there, and administer permissions as needed. could also be preferable over transfering the ownership from one personal repo to the other. if at some point another maintainer takes over, people still can rely on the old "official looking" url. |
I just tried, but there is a conflict with your copy of adflib
Télécharger BlueMail pour Android
Le 20 févr. 2025, 17:34, à 17:34, rofl0r ***@***.***> a écrit:
…rofl0r left a comment (adflib/ADFlib#85)
github has a button "transfer ownership" which is IMO better than what
you're doing here - people visiting the old url get automatically
redirected to the new one.
--
Reply to this email directly or view it on GitHub:
#85 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
right. that only works if the receiving end of the transfer doesn't have a repo of the same name already. doing the transfer would require some cooperation between the 2 of you. |
@lclevy, hold-on. Let's not rush it... For the transfer - I was certain that there will be a conflict since I have the forked repo (with the same name), so for sure I have to move it out of the way (either delete it or rename it - if its possible...). Since we are discussing this, maybe we can see what are the proposed options. @rofl0r, thanks for the tips. TBH, I do not use GH that much to know its every feature, I consider this mostly just repo hosting + some CI. What is better to do depends somewhat on what we want to do. We discussed some other possibilities and so far we decided to keep this repository as legacy (and possibly use it as a backup for released code). For me, it seems the safest solution. If, for instance, I would decide to move it to other hosting service, there would be a similar redirection anyway. You can see it in many cases, so this is not something particularly unusual. Nevertheless, I had a look at what you propose - if I see well, For ADFlib, would see probably something like GitLab's project, but on GH project is a bit something else... Creating an "organization" for just one project (not that big and dynamic...) seems an overshot. But, true, later we could create there separated repos for, for instance, some related tools. However, this all depends what perspectives are seen for it, regarding projects, people etc.... For now we have just one project and repo... @rofl0r, do you have an example of a project that you use it with an "organization"? At the moment, for sure the simplest way to preserve things (exactly as they are) would be to just make transfer. If we decide so, I will move my fork away so that the repo can be transferred. |
when you click on my profile, below the "avatar" image you see some icons for organizations.
probably just ADFlib.
at least in tinyproxy, we use some features like review requests and some sort of branch protections. though i personally see those protections as nuisance and can do even better without them. one can also give fine-grained permissions to contributors. i only use the free plan. |
OK. Thanks for info. Actually, this can make sense regarding the website. There is very useful documentation created by Laurent (relatively widely used, I saw it linked in Wikipedia and in other Amiga or OS/filesystems related sites), for which we can create a separated repo and make available on GH as webpage. I will make couple of tests and come back here. |
@rofl0r, to conclude - as you can see, we moved the repo to a dedicated organization. |
I put the note on the top of README, so that users can quickly notice this.