-
Notifications
You must be signed in to change notification settings - Fork 54
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
Transfer the repository to @sass organization? #108
Comments
Plus: although it might be somewhat off-topic, |
AFAIK @hcatlin would be the right contact. Easiest probably by our slack channel. |
Any update on this? |
I'm not entirely convinced. The current repositories contain bindings maintained by the core libsass maintainers. This repository doesn't quite fit that as well |
Wonder if the binding maintainers became core libsass maintainers, or core libsass maintainers also made bindings as well. |
@asottile would you like to give this another shot. You definitively would have my support. Unfortunately the perl bindings (which I maintain) are not as popular as your python binding (due to obvious reasons, perl5 just isn't the cool kid on the block anymore 😉). BTW. would really love to ask if you'd be willing to try to integrate native libsass plugins as I did with perl-libsass!? If you're willing to give it a shot either way, count on my support. I really admire what you achieved with the LibSass API so far. Well Done 👍 👏 |
I'd be happy to join the org, I'm not sure why I had concerns before but I don't have any now :) @dahlia owns the repository and would be the contact for transferring it. Looking forward to the org 🎉 As for native extensions, I'll check out how the perl bindings does them and see if we can fit them in here too! |
Cool. For the native extensions: They basically just need to be compiled with the same toolchain and the same main libsass dependency into dynamic objects to be loaded via plugin paths. But to conserve disk space it makes sense to have all parts link to the same shared libsass library (was the hardest part in perl-libsass build, but static linking also works). |
//CC @nex3 @chriseppstein @xzyfer for transfer to the sass org! |
I can take care of this tonight.
…On 12 Jan. 2018 12:45 pm, "Marcel Greter" ***@***.***> wrote:
//CC @nex3 <https://github.com/nex3> @chriseppstein
<https://github.com/chriseppstein> @xzyfer <https://github.com/xzyfer>
for transfer to the sass org!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#108 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWBo1h2e0hUhHBtibgn4jngZ8-mKBks5tJrkegaJpZM4GvBXS>
.
|
Had a look. I think the owner/admin of this repo needs to request the transfer, then I can accept it. |
Sorry for late response. I've just tried to transfer ownership to @sass, but it failed with an error message: Is there an other way to “request” the transfer? |
Ok cool. I'll add you to the sass org in my morning.
|
Still working on this. I haven't forgotten.
|
Looks like the easiest way to do this may be to add me as a collaborator and I should be able to do a transfer requests. |
Collaborator won't have access to that setting -- would need to be added as an owner |
Aha ok I managed to the Sass org permissions sorted out. @dahlia you should have an invite to join the Sass org. |
I've just received the invitation and joined the org now. I'll transfer the repo right now. |
Hmm… it still says:
even though I now belong to the @sass org. |
Ok try now. |
Weird. Still the same error occurs:
|
There isn't anything else I can seemingly do in the Sass org. Maybe try
logging out of GitHub?
Otherwise all I can think of is making me an owner of this repo so tasty I
can the transfer.
…On 19 Jan. 2018 3:05 am, "Hong Minhee" ***@***.***> wrote:
Weird. Still the same error occurs:
You don’t have the permission to create repositories on sass
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#108 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWE0sBK5M6__BynDW5AOUGOYEfdHXks5tL2vkgaJpZM4GvBXS>
.
|
We have this setting off. I have enabled it for this transfer and will disable it after it's complete. |
Aha. Thanks @chriseppstein. I've been fumbling around the GH UI for a while now :/ |
🎉
…On Thu, Jan 18, 2018 at 8:09 PM Hong Minhee ***@***.***> wrote:
Closed #108 <#108>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#108 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAHL19xUnxyRTE_L7vz7HzHX09WAajzks5tMBVmgaJpZM4GvBXS>
.
|
Thanks everyone! Welcome to the team @dahlia |
🎉 (do I get an invite too? 😆) |
@asottile aha I thought you were already in the org because of your work LibSass. I've added you to the sass/libsass-python team. Check your inbox :) |
We have now more than one maintainers, so I’m not sure whether this repository still should belong to @dahlia. There's the official organization named @sass, which consists of libsass upstream itself, and several bindings of it e.g. node-sass, perl-libsass, ruby-libsass. I think @sass would be the best place to transfer this repository to, but wonder others' opinions about the idea. Also, I have currently no idea how we can even if we want to do it.
The text was updated successfully, but these errors were encountered: