search

weblocks-framework / weblocks

Advanced web-framework for Common Lisp
http://weblocks-framework.info/
Other
7 stars 4 forks source link

Why not transfer repo from skypher/weblocks to weblocks-framework/weblocks instead of new repo, to preserve stars, etc? #1

Open Hexstream opened 7 years ago

Hexstream commented 7 years ago

Isn't this an official relocation of the project? Then @skypher should be able to transfer ownership of the repo to @weblocks-framework from the skypher/weblocks admin section, to preserve everything like stars, watchers, etc. I think the old URLs like https://github.com/skypher/weblocks will also transparently redirect to https://github.com/weblocks-framework/weblocks.

Edit: Github repo transfers documentation: https://help.github.com/articles/about-repository-transfers/

html commented 7 years ago

This is official relocation of the project. @skypher didn't respond to me on my last question so I've transfered repository without notifying him. I don't know if he will read my messages.

Hexstream commented 7 years ago

Hum. That seems like a confusing situation.

It seems to me that if the original repo owner is unwilling to cooperate with the transition, then this probably does not constitute an "official" relocation of the project...

I think one or more parties should probably explain their respective understandings of the situation in details somewhere...

Someone more involved than me (I've never used weblocks) might consider creating an issue about this on the original repo (possibly referencing this issue), where a lot more weblocks-interested people would see it...

html commented 7 years ago

Repo owner is not maintainer. I'm current maintainer. I think Leslie is just too busy on other stuff so he didn't respond. Currently I have write access to repository skypher/weblocks. I think nobody except you will react on this action. I'm open to comments and suggestions. Don't really understand about parties. Can you tell it in other words ? Are there any questions to discuss at the moment ?

Hexstream commented 7 years ago

This is getting more confusing by the minute.

Right now your repo seems like a random fork, but you're claiming that it's the "official" new repo, but there doesn't seem to be any evidence of that (although I haven't really researched this seriously), so basically your thing looks like a random hijacking attempt.

html commented 7 years ago

http://weblocks-framework.info/installation look at the bottom line. There is repository url. Search for current maintainer of Weblocks. See Weblocks commits to ensure I'm a maintainer.

html commented 7 years ago

If it is hijacking then Leslie also hijacked Weblocks to his account. But in fact he just moved Weblocks from bitbucket to github when he was responsible for Weblocks.

html commented 7 years ago

ok, I should write to Weblocks google group and tell others. Thanks.

Hexstream commented 7 years ago

If it is hijacking then Leslie also hijacked Weblocks to his account. But in fact he just moved Weblocks from bitbucket to github when he was responsible for Weblocks.

Maybe (or maybe not), but at 87 stars, 21 watchers, 22 forks VS 0 stars, 1 watcher, 0 forks, in the absence of strong signals to the contrary, I think most people would reasonably assume that the other repo is still the official one, not this one.

ok, I should write to Weblocks google group and tell others. Thanks.

Yeah, please clarify this situation...