Moving to dlang-community

[wilzbach]

From dlang-community/D-Scanner#458 (comment)

Btw don't mind the test failure on dmd-nightly for now - it's a known regression in EMSI containers.
Anyway, I think we should also bring emsi_containers to the org, so we can more easily manage such issues.

@Hackerpilot what's your opinion on this?

[dushibaiyu]

It is great!

[wilzbach]

Ping @Hackerpilot

The last commit was nine months ago and there are a couple of good, pending PRs...

[Hackerpilot]

I checked with my managers and they don't have any strong feelings one way or the other.

[wilzbach]

I checked with my managers and they don't have any strong feelings one way or the other.

Great - this means there nothing is stopping us from moving this to dlang-community?
You still have the required permissions, correct?

[wilzbach]

Friendly piing @Hackerpilot

[WebFreak001]

ping @Hackerpilot

I think when the D community is able to merge PRs and close issues it would greatly benefit everyone because this is also used in some pretty important libraries like libdparse

[wilzbach]

Ping @Hackerpilot - the PRs are still open over more than one year and D community would be able to take of maintenance PRs.

[wilzbach]

Thanks a lot!

[Hackerpilot]

I have the URL on code.dlang.org updated, but nothing else has been updated.

[wilzbach]

I have the URL on code.dlang.org updated, but nothing else has been updated.

OK, I started e.g. here dlang-community/D-Scanner#551

BTW I don't want to appear greedy, but could we use this window of opportunity to move libddoc to dlang-community too?
D-Scanner which uses libddoc, is is part of the Jenkins Project Tester since a while now and while it rarely happens, but sometimes e.g. after fixed ugly compiler bugs, updates to some of the tested projects are necessary and then it's quite advantageous if multiple people have commit access.

[wilzbach]

Thanks. For now I did the following:

• enabled the repos on Travis
• configured dlang-bot for auto-merge
• updated the URL in the dub.sdl/json files
• fixed the URLs in the containers README

edit:

• enabled branch protection for master

[PetarKirov]

Thanks @Hackerpilot! Having all the repos under a single organization makes maintenance much easier and scalable for the community.