November 27
On Wednesday, 27 November 2019 at 23:19:07 UTC, bachmeier wrote:
> On Tuesday, 26 November 2019 at 22:53:49 UTC, Laeeth isharc wrote:
>
>> I think often it's less about financial resources than a coordination problem.
>
> That's a good point. And as has been said before, once you have some money on the line, it forces you to get things in order. One problem of a volunteer system is that there's no incentive to make it work, even when money is not itself the issue.

Well there's clearly an incentive to take some steps towards making things work as a volunteer but it's an emotional one which means people will only take steps in a sequence that's in some way personally satisfying. The problem right now is I think just a coordination problem because the people using D in business likely aren't mature firms, or at least mature groups, which means they are short of time and attention.

>> Lots of people probably wouldn't mind fixing bugs or improving documentation to earn some extra money and maybe some people or companies would be willing to support the ecosystem through funding but unless somebody takes it upon themselves to organise a way to make it happen then it won't.
>>
>> It might be as simple as setting up a page where people can indicate their willingness to fix bugs and send email address along with the sort of daily rate they would need.  Then it's much easier to ask for support if someone will oversee that process.  You could allow people to channel money to bugs they care about provided they channel some to community bug fixing needs.
>
> I like that idea. College students would be prime candidates for this but they might avoid it because they wouldn't know what their rate should be. It might have to be stated as $X/day or a negotiated rate if that isn't enough.

Well you could make the rate optional and in such cases it could be negotiated.  Costs of living and market wages vary a great deal between different places, as does productivity of programmers.

> Sometimes it's unclear who's even in charge. Dub, for instance. I wish you could find the email address of the decision maker for a particular issue on the website.

Someone should send pull requests to add to the website after getting consent from relevant people.  I will try to help if we can but very busy right now.

Maybe next year a community development and documentation project could be part of SAoC?

SAoD..  of documentation.

I don't know if there would be any interest.  But we would certainly consider hiring people who can write good documentation (for internal purposes).

November 30
On Tuesday, 26 November 2019 at 09:11:33 UTC, S.G wrote:
> Fixing D bugs is a one way process so I don't even recommend doing this seriously, e.g on a daily basis, several hours per days. This will inexorably leads to frustration. Fix bugs if at work your company needs some particular fixes, fix bugs if you need some fixes for your own side-projects, fix bugs if this is required for your studies. But don't fix bugs just for the love of the D programming language.

If you don't regularly fix bugs they will mess up your schedule once you start working on a project and find yourself spending most of your time inside the debugger instead of coding your logic.

November 30
On Monday, 25 November 2019 at 16:53:43 UTC, berni44 wrote:
> [snip]
>
> I would also recommend to reduce the amount of "red" on the whole homepage. Red is associated with "danger" and that works subconciously. As D is percieved as the "red" language, that cannot be removed completely, and that's not necessary, but for example a red line between the main menu and the content is sufficent. Replace the main menu by something from white over gray to black. Or use #3931b0 as a secondary color.
>

Really, we could reduce the amount of red in the forum. I think red here signifies Mars but we earthlings are not used to see a lot of red everyday.

November 30
On Tuesday, 26 November 2019 at 05:05:09 UTC, Jab wrote:
> On Monday, 25 November 2019 at 16:53:43 UTC, berni44 wrote:
>> a) Remove bugs
>
>
> I feel this gets brought up a bit, how pull requests sit idle for years along with bug reports. People working on D work on whatever they want, fixing bugs and handling pull requests are just chores that no one wants to do.

Nicholas Wilson was doing great as a PR manager. There is both organizational and financial limits to the problem.

November 30
On Wednesday, 27 November 2019 at 23:49:55 UTC, Laeeth Isharc wrote:
> Maybe next year a community development and documentation project could be part of SAoC?
>
> SAoD..  of documentation.
>
> I don't know if there would be any interest.  But we would certainly consider hiring people who can write good documentation (for internal purposes).

I like that idea. Can't say I've ever heard of such an initiative before, but it could potentially be a selling point to have outstanding documentation.
November 30
On Saturday, 30 November 2019 at 00:21:13 UTC, Suleyman wrote:
> On Tuesday, 26 November 2019 at 09:11:33 UTC, S.G wrote:
>> Fixing D bugs is a one way process so I don't even recommend doing this seriously, e.g on a daily basis, several hours per days. This will inexorably leads to frustration. Fix bugs if at work your company needs some particular fixes, fix bugs if you need some fixes for your own side-projects, fix bugs if this is required for your studies. But don't fix bugs just for the love of the D programming language.
>
> If you don't regularly fix bugs they will mess up your schedule once you start working on a project and find yourself spending most of your time inside the debugger instead of coding your logic.

It's not about regularly fixing or not. Fixing bugs is not about pissing 5000 lines of code every day, it's more precision work. You can work during two hours and finally only one line of code will be written. It's maybe the reason why it's not well recognized, but truth is, if it was so simple there would be 10 bugfixs merged every day. Is this the case ? No, clearly not.
6 days ago
On Saturday, 30 November 2019 at 03:09:20 UTC, bachmeier wrote:
> On Wednesday, 27 November 2019 at 23:49:55 UTC, Laeeth Isharc wrote:
>> Maybe next year a community development and documentation project could be part of SAoC?
>>
>> SAoD..  of documentation.
>>
>> I don't know if there would be any interest.  But we would certainly consider hiring people who can write good documentation (for internal purposes).
>
> I like that idea. Can't say I've ever heard of such an initiative before, but it could potentially be a selling point to have outstanding documentation.

Google is doing a similar thing (in addition to GSoC):

https://developers.google.com/season-of-docs

I believe it was mentioned here on the NG before. If we can find enough
people to mentor etc., it might be a good idea for next year.

Next ›   Last »
1 2 3 4