Neither did I claim that implies you "could do whatever you like". That is not what open source means.
Actually, that's exactly what it means.
But in any case, like you said, having copies and copies of the same addons isn't good, it just clutters the system and makes no sense (and mods should not allow them, especially when they're clear copy pastes), so if a project is indeed abandoned AND needs updating (not just to change the TOC) then I think it's pretty much acceptable to take over it, preferably with the author's permission but that's not always something that one can get since many people just "disappear" you'll never get a reply from them.
You absolutely need the permission. Just because someone abandoned it doesn't mean they automatically relinquish their intelectual property rights on the code they wrote. The same applies to forking, unless the license specifically allows that, it requires explicit permission from the author, no matter if you can read the source files (which is inherently true for all script languages like Lua), or not.
When you linked your account, still use your previous CF username/password for repository access for now. The easiest way to do that on Windows is to use the Git Credentials Manager, which comes with recent versions of Git For Windows.
PS:
svn+ssh has been discontinued with the move to the new platform. All repository access is through HTTPS now.
All updates require moderator approval, unless the author of the project (ie. you) has been white-listed to be exempt from that - say for good behavior and observing the rules (both Curse's and the Blizzard AddOn Guidelines).
The version on curse contains a lot of data ready to go, if you don't see anything after importing, then either you imported the wrong thing or you just have the display of things disabled.
Furthermore, there's not really any excuse for making modifications (like changing line endings or making Unicode replacements) to existing code. If there's an "insert localization here" tag in a file, just insert the localization in place of the tag. If there's a block of code wrapped in "debug/end-debug" tags, just replace each tag with the appropriate symbols to start and end a block comment. If there's a "do-not-package" tag block, just delete the lines in between. No reason to touch any other lines in the file.
Thats not how file handling works, however.
To modify and/or delete lines in a file, you need to read at least everything after those lines and re-write it, for sake of sanity everyone would just read the entire file (instead of half of it), modify it in memory, and write it out again. Its easy enough to imagine someone making a mistake by using some generic text reader that results in such encoding changes - unintentionally.
Thanks for the feedback guys, when we had the sites in beta with the first iteration of the ticket system everyone hated the sidebar :P
I hated the sidebar on the beta because it had useless content, not because it was a sidebar.
It didn't have modification options for the issue you were currently viewing, like suggsted here, or like the one on old-wowace had (or how GitHub does it, or or or), instead it had navigation/filtering for the overall issue list, which is totally pointless to have when I'm viewing a specific single issue right now. It was misleading at best since using it on a single issue view would bring you back to the issue list.
But I gave that feedback on the beta too, several times. :)
I like the tags at the bottom. Its typical for me to also change the tags when I comment on an issue, so having them on the top would require quite a bit of scrolling - especially when there is a lot of comments already.
In fact, the majority of the time I would end up reading at the bottom of a ticket, so having controls there as well is better then at the top.
All absolute links get mangled like that. I tried to link to a API description page on one of my library projects, and it converts it into some relative link which doesn't work.
It should ideally leave all links untouched, really. Let us worry about them.
0
The name is different between Classic and Retail. There is no way currently to seperate that, so Retail translations are favored.
0
"preferably with permission" sounds to me like when you can't get it, you should do it anyway, which is a big no.
0
0
We're happy where we are. Its a developer chat, grown over years, unlikely to ever go anywhere else.
0.949379818974187
When you linked your account, still use your previous CF username/password for repository access for now. The easiest way to do that on Windows is to use the Git Credentials Manager, which comes with recent versions of Git For Windows.
PS:
svn+ssh has been discontinued with the move to the new platform. All repository access is through HTTPS now.
0
Which project is that? If its a WoWAce project, you may also need to call the API endpoint on the WoWAce domain, and not curseforge.
0.962264150943396
In fact, I already heard back, and your project was properly synced to Curse now.
0.962406015037594
I've let someone know to have your project looked at.
PS:
Your latest file was tagged as 2.3.25, this seems like a mistake. :)
0
All updates require moderator approval, unless the author of the project (ie. you) has been white-listed to be exempt from that - say for good behavior and observing the rules (both Curse's and the Blizzard AddOn Guidelines).
0
The version on curse contains a lot of data ready to go, if you don't see anything after importing, then either you imported the wrong thing or you just have the display of things disabled.
0
0
0
I like the tags at the bottom. Its typical for me to also change the tags when I comment on an issue, so having them on the top would require quite a bit of scrolling - especially when there is a lot of comments already.
In fact, the majority of the time I would end up reading at the bottom of a ticket, so having controls there as well is better then at the top.
0
0
All absolute links get mangled like that. I tried to link to a API description page on one of my library projects, and it converts it into some relative link which doesn't work.
It should ideally leave all links untouched, really. Let us worry about them.