> My son and other homeschool kids, and online at the moment (before Covid it was at my house)
>
> -Steve

Very cool.

On Friday, 12 March 2021 at 21:45:48 UTC, Siemargl wrote:
> DUB supports hosting sites for libs other than github? Some people don't like MS.

It supports github, bitbucket, and gitlab.

On Thursday, 11 March 2021 at 22:17:59 UTC, Steven Schveighoffer wrote:
> Everyone has seen this happen sometimes. An open-source author deletes their account or the repository, and then the source is gone. The latest is this project:
>
> https://code.dlang.org/packages/raylib-d
>
> Which I have been using to teach a class.
>
> But of course, it's open source, so we can continue.
>
> What does one do when the project is deleted from view? I can register a copy of it, but it seems rather annoying if one has to do this kind of stuff. Plus, now I have to come up with a different name (and have projects update all their dependencies).
>
> Should it be possible to "take over" a project in dub once the maintainer has deleted all their stuff? I have a copy of the repo (thanks to WebFreak), so I could do it, but I wonder if dub shouldn't have a way to mitigate this type of problem.

This wouldn't be a problem if the Dub registry wasn't directly tied to GitHub (or other similar services). It would be better if it was more difficult to remove a package from the Dub registry.

With RubyGems, a package is not tied to GitHub but it's instead an artifact that has been uploaded. If the user closes the GitHub account the package will still be available in the RubyGems registry.

I think it's becoming more and more problematic with the Dub being directly tied to GitHub.

--
/Jacob Carlborg

On Wednesday, 17 March 2021 at 10:04:46 UTC, Jacob Carlborg wrote:
> On Thursday, 11 March 2021 at 22:17:59 UTC, Steven Schveighoffer wrote:
>> [...]
>
> This wouldn't be a problem if the Dub registry wasn't directly tied to GitHub (or other similar services). It would be better if it was more difficult to remove a package from the Dub registry.
>
> With RubyGems, a package is not tied to GitHub but it's instead an artifact that has been uploaded. If the user closes the GitHub account the package will still be available in the RubyGems registry.
>
> I think it's becoming more and more problematic with the Dub being directly tied to GitHub.
>
> --
> /Jacob Carlborg

Agreed, I've said before we should have a buffer/backup

On Wednesday, 17 March 2021 at 10:14:39 UTC, Imperatorn wrote:
> On Wednesday, 17 March 2021 at 10:04:46 UTC, Jacob Carlborg wrote:
>> On Thursday, 11 March 2021 at 22:17:59 UTC, Steven Schveighoffer wrote:
>>> [...]
>>
>> This wouldn't be a problem if the Dub registry wasn't directly tied to GitHub (or other similar services). It would be better if it was more difficult to remove a package from the Dub registry.
>>
>> With RubyGems, a package is not tied to GitHub but it's instead an artifact that has been uploaded. If the user closes the GitHub account the package will still be available in the RubyGems registry.
>>
>> I think it's becoming more and more problematic with the Dub being directly tied to GitHub.
>>
>> --
>> /Jacob Carlborg
>
> Agreed, I've said before we should have a buffer/backup

In case anyone needs it, I always have a backup of all packages so you can message me if you are missing something deleted.

On Wednesday, 17 March 2021 at 20:07:40 UTC, WebFreak001 wrote:
> On Wednesday, 17 March 2021 at 10:14:39 UTC, Imperatorn wrote:
>> On Wednesday, 17 March 2021 at 10:04:46 UTC, Jacob Carlborg wrote:
>>> [...]
>>
>> Agreed, I've said before we should have a buffer/backup
>
> In case anyone needs it, I always have a backup of all packages so you can message me if you are missing something deleted.

Splendid, that's good to know! 🍀

On 3/12/21 11:18 AM, Steven Schveighoffer wrote:
> On 3/11/21 5:17 PM, Steven Schveighoffer wrote:
>> Everyone has seen this happen sometimes. An open-source author deletes their account or the repository, and then the source is gone. The latest is this project:
>>
>> https://code.dlang.org/packages/raylib-d
>>
> 
>> Also, if anyone has any information about why this happened, let me know (you can email me if you want to speak privately), I want to make sure the original author really meant to do this before I register a copy of their stuff.
> 
> FYI, I registered raylib-d2, which has been updated with all tags to use the new name (so all you need to do if you depend on raylib-d, is to change it to raylib-d2)
> 
> As long as the original author does not respond, I'll maintain that library, but probably not actively.
> 
> https://github.com/schveiguy/raylib-d2

I did not get a response, but the maintainer (or someone else) must have logged in and redirected to my repo for raylib-d.

So raylib-d will live on under my account! I'll make the repo archived and note that in the README (probably put in a pragma(msg) to tell people to switch).

I'll release raylib-d v3.0.4 with the latest stuff (there was some code that hadn't been released).

-Steve

On 3/19/21 10:47 AM, Steven Schveighoffer wrote:
> I'll make the repo archived and note that in the README (probably put in a pragma(msg) to tell people to switch).

Oof, I meant the *raylib-d2* repo. Not the raylib-d repo!

-Steve