We need a community effort to maintain unmaintained dub packages, suggestions

[aberba]

On Saturday, 23 May 2020 at 17:46:42 UTC, aberba wrote:
> On Saturday, 23 May 2020 at 17:10:27 UTC, mw wrote:
>> On Saturday, 23 May 2020 at 07:27:50 UTC, Luis wrote:
>>> Because this, I forked two small packages and get it under my 
>>> wing, with the self-compromise that at least I will keep it 
>>> working on future versions of D. However, I published they 
>>> with different names and changing the module name. Something 
>>> that should be totally unnecessary.
>>>
>>> And there are many packages with the same problem on the wild.
>>
>>
>> Right, people forked & fixed, but the fix cannot be 
>> contributed back to the D community.
>>
>> Other users are still getting the original buggy version from 
>> dub, and don't have an easy way to find new patches.
>>
>> So the main blocker is to get the write permission (of the 
>> unmaintained packages) of the dub system, this will solve lots 
>> of these problems.
>>
>> Or we should setup a new policy that any new dub packages 
>> should give write permission to dlang-community by default.
>
> How about putting every packages under dlang-community under a 
> repo maintained by community so anyone else can accept pull 
> request.
>
> If anyone else starts another decimal package, it'll also end 
> up the same way most likely.
>
> It's about time we have packages regarded as core with the 
> community in charge...so we can direct contributions to them. 
> Every fix gets submitted there...

The community here is very week. I've also talked to lack of 
focus on community building. Every open source endure needs a 
strong community to make things happen under a collective effort. 
Until there's official push and dedication to making that happen, 
we'll also be overruns by things to do.