The D foundation is planning to add a way for us to pay for changes we'd like to see in D and its ecosystem, rather than having to code everything we need ourselves or find and hire a D dev to do it:

"[W]e’re going to add a page to the web site where we can define targets, allow donations through Open Collective or PayPal, and track donation progress. Each target will allow us to lay out exactly what the donations are being used for, so potential donors can see in advance where their money is going. We’ll be using the State of D Survey as a guide to begin with, but we’ll always be open to suggestions, and we’ll adapt to what works over what doesn’t as we go along."
https://dlang.org/blog/2018/07/13/funding-code-d/

I'm opening this thread to figure out what the community would like to pay for specifically, so we know what to focus on initially, whether as part of that funding initiative or elsewhere. I am not doing this in any official capacity, just a community member who would like to hear what people want.

Please answer these two questions if you're using or would like to use D, I have supplied my own answers as an example:

1. What D initiatives would you like to fund and how much money would you stake on each? (Nobody is going to hold you to your numbers, but please be realistic.)

$50 - Parallelize the compiler, particularly ldc, so that I can pass it -j5 and have it use five cores _and_ not have the bloat of separate compiler invocation for each module/package, ie taking up more memory or time.

$30 - Implement H.S. Teoh's suggestion of having an automated build system to periodically check which dub packages are building with official compiler releases:

https://forum.dlang.org/post/mailman.3611.1536126324.29801.digitalmars-d@puremagic.com

$25 - Enable GC for the DMD frontend, so that dmd/gdc/ldc use less memory

I would also stake smaller amounts on various smaller bugs, if there were a better interface than bountysource and people were actually using it, ie users knew about and were staking money and D core devs were fixing those bugs and claiming that money.

2. Would you be okay with the patches you fund not being open-sourced for a limited time, with the time limit or funding threshold for open source release specified ahead of time, to ensure that funding targets are hit?

Yes, as long as everything is open-sourced eventually, I'm good.

On 05/09/2018 7:00 PM, Joakim wrote:
> The D foundation is planning to add a way for us to pay for changes we'd like to see in D and its ecosystem, rather than having to code everything we need ourselves or find and hire a D dev to do it:
> 
> "[W]e’re going to add a page to the web site where we can define targets, allow donations through Open Collective or PayPal, and track donation progress. Each target will allow us to lay out exactly what the donations are being used for, so potential donors can see in advance where their money is going. We’ll be using the State of D Survey as a guide to begin with, but we’ll always be open to suggestions, and we’ll adapt to what works over what doesn’t as we go along."
> https://dlang.org/blog/2018/07/13/funding-code-d/
> 
> I'm opening this thread to figure out what the community would like to pay for specifically, so we know what to focus on initially, whether as part of that funding initiative or elsewhere. I am not doing this in any official capacity, just a community member who would like to hear what people want.
> 
> Please answer these two questions if you're using or would like to use D, I have supplied my own answers as an example:

I have $50USD to spend upon shared library support to be designed (not just patching bugs) and implemented.Sadly that is my limit. I wish it was more given how much of a blocker it can be (and has shown to be).

> $25 - Enable GC for the DMD frontend, so that dmd/gdc/ldc use less memory

The only thing I believe required for this is [0]. This depends upon a decision from Walter and should be pretty straight forward to do. But the frontend will not be in any way ready to be used as a library.

During DConf I did attempt to get the frontend ready to be actually usable. After my first PR sitting for like 3 months and is now looking like its dead, I won't be the one handling that anymore.

[0] https://issues.dlang.org/show_bug.cgi?id=18811

On Wednesday, 5 September 2018 at 07:00:49 UTC, Joakim wrote:
> Please answer these two questions if you're using or would like to use D, I have supplied my own answers as an example:
>
> 1. What D initiatives would you like to fund and how much money would you stake on each? (Nobody is going to hold you to your numbers, but please be realistic.)

I'll throw $200 at issue 5710. It's already got $200 on bountysource, and it's the one issue I consistently bump into. And yes, you can hold me to this.


> 2. Would you be okay with the patches you fund not being open-sourced for a limited time, with the time limit or funding threshold for open source release specified ahead of time, to ensure that funding targets are hit?

Sure, as long as they're eventually open-sourced.

--
  Simen

On Wednesday, 5 September 2018 at 07:32:54 UTC, Simen Kjærås wrote:
> On Wednesday, 5 September 2018 at 07:00:49 UTC, Joakim wrote:
>> Please answer these two questions if you're using or would like to use D, I have supplied my own answers as an example:
>>
>> 1. What D initiatives would you like to fund and how much money would you stake on each? (Nobody is going to hold you to your numbers, but please be realistic.)
>
> I'll throw $200 at issue 5710. It's already got $200 on bountysource, and it's the one issue I consistently bump into. And yes, you can hold me to this.
>
>
>> 2. Would you be okay with the patches you fund not being open-sourced for a limited time, with the time limit or funding threshold for open source release specified ahead of time, to ensure that funding targets are hit?
>
> Sure, as long as they're eventually open-sourced.
>
> --
>   Simen

I'll pledge another $100 USD to that one. Ditto on the open source question.

On Wednesday, 5 September 2018 at 07:00:49 UTC, Joakim wrote:
> [...]

If I had money I'd pay for DLL support. Maybe I'll need to start saving. I think this is a good idea though.

On Wednesday, 5 September 2018 at 07:00:49 UTC, Joakim wrote:
> The D foundation is planning to add a way for us to pay for changes we'd like to see in D and its ecosystem, rather than having to code everything we need ourselves or find and hire a D dev to do it:
>
> "[W]e’re going to add a page to the web site where we can define targets, allow donations through Open Collective or PayPal, and track donation progress. Each target will allow us to lay out exactly what the donations are being used for, so potential donors can see in advance where their money is going. We’ll be using the State of D Survey as a guide to begin with, but we’ll always be open to suggestions, and we’ll adapt to what works over what doesn’t as we go along."
> https://dlang.org/blog/2018/07/13/funding-code-d/
>
> I'm opening this thread to figure out what the community would like to pay for specifically, so we know what to focus on initially, whether as part of that funding initiative or elsewhere. I am not doing this in any official capacity, just a community member who would like to hear what people want.
>
> Please answer these two questions if you're using or would like to use D, I have supplied my own answers as an example:
>
> 1. What D initiatives would you like to fund and how much money would you stake on each? (Nobody is going to hold you to your numbers, but please be realistic.)
>
> $50 - Parallelize the compiler, particularly ldc, so that I can pass it -j5 and have it use five cores _and_ not have the bloat of separate compiler invocation for each module/package, ie taking up more memory or time.
>
> $30 - Implement H.S. Teoh's suggestion of having an automated build system to periodically check which dub packages are building with official compiler releases:
>
> https://forum.dlang.org/post/mailman.3611.1536126324.29801.digitalmars-d@puremagic.com
>
> $25 - Enable GC for the DMD frontend, so that dmd/gdc/ldc use less memory
>
> I would also stake smaller amounts on various smaller bugs, if there were a better interface than bountysource and people were actually using it, ie users knew about and were staking money and D core devs were fixing those bugs and claiming that money.
>
> 2. Would you be okay with the patches you fund not being open-sourced for a limited time, with the time limit or funding threshold for open source release specified ahead of time, to ensure that funding targets are hit?
>
> Yes, as long as everything is open-sourced eventually, I'm good.


$500.00 to fix these three together - they may well be essentially the same bug:

https://issues.dlang.org/show_bug.cgi?id=19179
https://issues.dlang.org/show_bug.cgi?id=5570
https://issues.dlang.org/show_bug.cgi?id=13957

Can delay fix if you wish if it's ultimately open-sourced.

On Thursday, 6 September 2018 at 01:24:35 UTC, Laeeth Isharc wrote:

> $500.00 to fix these three together - they may well be essentially the same bug:
>
> https://issues.dlang.org/show_bug.cgi?id=19179
> https://issues.dlang.org/show_bug.cgi?id=5570
> https://issues.dlang.org/show_bug.cgi?id=13957

According to BountySource (https://www.bountysource.com/teams/d/issues?tracker_ids=383571) Issue 5570 already has a bounty of $445.  With the addition of your $500 that would make the bounty $945, which isn't bad.

Mike

On Wednesday, 5 September 2018 at 07:00:49 UTC, Joakim wrote:
> The D foundation is planning to add a way for us to pay for changes we'd like to see in D and its ecosystem, rather than having to code everything we need ourselves or find and hire a D dev to do it:
>
> "[W]e’re going to add a page to the web site where we can define targets, allow donations through Open Collective or PayPal, and track donation progress. Each target will allow us to lay out exactly what the donations are being used for, so potential donors can see in advance where their money is going. We’ll be using the State of D Survey as a guide to begin with, but we’ll always be open to suggestions, and we’ll adapt to what works over what doesn’t as we go along."
> https://dlang.org/blog/2018/07/13/funding-code-d/
>
> I'm opening this thread to figure out what the community would like to pay for specifically, so we know what to focus on initially, whether as part of that funding initiative or elsewhere. I am not doing this in any official capacity, just a community member who would like to hear what people want.
>
> Please answer these two questions if you're using or would like to use D, I have supplied my own answers as an example:
>
> 1. What D initiatives would you like to fund and how much money would you stake on each? (Nobody is going to hold you to your numbers, but please be realistic.)

I'd be willing to pay at least $100 each for these two:

https://issues.dlang.org/show_bug.cgi?id=19159
https://issues.dlang.org/show_bug.cgi?id=18788

Quite honestly, though, I probably wouldn't do it myself for $100.  These bounties really need to be $500 or more.

If D is to be funded by individuals, there needs to be some way to organize individuals around common interest and raise funds for those tasks.  For example, the D Language Foundation has a "Corporate Bronze" offer on its OpenCollective page that includes 3 priority bug fixes per month for $12,000.  If we could get 24 like-minded people, willing to contribute $500 each, and vote on priority bugs, that could potentially get things moving in the right direction.  That would be 1 1/2 bugs per contributor.  I don't think that's bad.  I'd be willing to join such a collective if I got at least 1 priority bug fix out of it.

Even better, IMO, it'd be nice if the "Individual Sponsor" or "Organizational Sponsor" offers on the OpenCollective page included at least 1 priority bug fix.

Mike

On Friday, 7 September 2018 at 05:31:22 UTC, Mike Franklin wrote:
> On Wednesday, 5 September 2018 at 07:00:49 UTC, Joakim wrote:
>> The D foundation is planning to add a way for us to pay for changes we'd like to see in D and its ecosystem, rather than having to code everything we need ourselves or find and hire a D dev to do it:
>>
>> "[W]e’re going to add a page to the web site where we can define targets, allow donations through Open Collective or PayPal, and track donation progress. Each target will allow us to lay out exactly what the donations are being used for, so potential donors can see in advance where their money is going. We’ll be using the State of D Survey as a guide to begin with, but we’ll always be open to suggestions, and we’ll adapt to what works over what doesn’t as we go along."
>> https://dlang.org/blog/2018/07/13/funding-code-d/
>>
>> I'm opening this thread to figure out what the community would like to pay for specifically, so we know what to focus on initially, whether as part of that funding initiative or elsewhere. I am not doing this in any official capacity, just a community member who would like to hear what people want.
>>
>> Please answer these two questions if you're using or would like to use D, I have supplied my own answers as an example:
>>
>> 1. What D initiatives would you like to fund and how much money would you stake on each? (Nobody is going to hold you to your numbers, but please be realistic.)
>
> I'd be willing to pay at least $100 each for these two:
>
> https://issues.dlang.org/show_bug.cgi?id=19159
> https://issues.dlang.org/show_bug.cgi?id=18788
>
> Quite honestly, though, I probably wouldn't do it myself for $100.  These bounties really need to be $500 or more.
>
> If D is to be funded by individuals, there needs to be some way to organize individuals around common interest and raise funds for those tasks.

Yes, that's the point of the funding targets mentioned in the quoted blog post and this thread, to see who's interested in collectively pooling towards certain common goals. Obviously no one's person contribution would be enough to get any non-trivial goal funded.

Given the anemic response to this thread and the Opencollective so far, I suspect we wouldn't raise much though. OTOH, maybe the people who would pay don't read the forum.

> For example, the D Language Foundation has a "Corporate Bronze" offer on its OpenCollective page that includes 3 priority bug fixes per month for $12,000.  If we could get 24 like-minded people, willing to contribute $500 each, and vote on priority bugs, that could potentially get things moving in the right direction.  That would be 1 1/2 bugs per contributor.  I don't think that's bad.  I'd be willing to join such a collective if I got at least 1 priority bug fix out of it.

Yes, these types of paid bugfix schemes are what I describe above too.

> Even better, IMO, it'd be nice if the "Individual Sponsor" or "Organizational Sponsor" offers on the OpenCollective page included at least 1 priority bug fix.

That would make sense for the latter offer.

Btw, if anyone is under any illusion that I'm offering to implement any of this for the money, I have zero interest in doing this work. I _am_ interested in paying others to do it. I may tinker with enabling the GC on the DMD frontend some day, but that wouldn't be for any bounties, just OSS.

On Wednesday, 5 September 2018 at 07:00:49 UTC, Joakim wrote:
> The D foundation is planning to add a way for us to pay for changes we'd like to see in D and its ecosystem, rather than having to code everything we need ourselves or find and hire a D dev to do it:

I would donate again to DFoundation towards the administration and proper handling of the development process. Let me clarify - I expect D Foundation to oversee the D development process in the same fashion the JCP (Java Community Process) works. - That is an example of how professionals handle these things.

The D Foundation should, in my humble opinion, start the design (and perhaps the development) of commonly used APIs that may or may not be part of Phobos (APIs yes, the implementation should be separate library).

The following APIs come first to my mind:
- Crypto API
- Networking API (supporting all major protocols, and giving nice set of interfaces to implement own - look at protocol handlers in Java, or similar)
- Graphics (2D and 3D)
- GUI API (a rock-solid, scene based like JavaFX)
- Database API
- TUI (console UI)
- Security API (Role-base Access, etc)
- VFS API (Look at Apache Commons VFS)

Again Phobos should only contain interfaces - refecence implementation should be in the libphobos-<api> (example: libphobos-crypto.so)

The design and the development (or coordinating the development) of these APIs should be the D Foundation responsibility. Also future improvements should be part of the the improvement process that is also governed by the D Foundation (look at Python PEPs)...

I talked about this on IRC many times with other D programmers. Rich set of APIs is why languages like Java, Python, JavaScript, Go, etc gained so much popularity.

The more I see the D Foundation do these things, the more I will be willing to donate.