Well, I'll just say it:

- Please consider registering an account at issues.dlang.org and take a look. I just did so myself!

Maybe you can contribute be solving an issue? Even if it's just reporting a duplicate issue, it's invaluable to the community. A tip if you don't know where to start, is to filter using the "bootcamp" keyword. Those are bite-sized issues that should be reasonably easy to solve.

Here's the link:
https://issues.dlang.org/

Thanks! :)

On Monday, 21 September 2020 at 21:59:09 UTC, Imperatorn wrote:
> Well, I'll just say it:
>
> - Please consider registering an account at issues.dlang.org and take a look. I just did so myself!
>
> Maybe you can contribute be solving an issue? Even if it's just reporting a duplicate issue, it's invaluable to the community. A tip if you don't know where to start, is to filter using the "bootcamp" keyword. Those are bite-sized issues that should be reasonably easy to solve.
>
> Here's the link:
> https://issues.dlang.org/
>
> Thanks! :)

Anyone?

On Wednesday, 23 September 2020 at 20:40:56 UTC, Imperatorn wrote:
> On Monday, 21 September 2020 at 21:59:09 UTC, Imperatorn wrote:
>> Well, I'll just say it:
>>
>> - Please consider registering an account at issues.dlang.org and take a look. I just did so myself!
>>
>> Maybe you can contribute be solving an issue? Even if it's just reporting a duplicate issue, it's invaluable to the community. A tip if you don't know where to start, is to filter using the "bootcamp" keyword. Those are bite-sized issues that should be reasonably easy to solve.
>>
>> Here's the link:
>> https://issues.dlang.org/
>>
>> Thanks! :)
>
> Anyone?

Most people here have probably already fixed a bug at one point or another. People that probably have never touched a compiler before, doing so out of necessity. From my experience a hacky workaround is a more palatable experience (sadly).

On Wednesday, 23 September 2020 at 23:01:39 UTC, Avrina wrote:
> On Wednesday, 23 September 2020 at 20:40:56 UTC, Imperatorn wrote:
>> On Monday, 21 September 2020 at 21:59:09 UTC, Imperatorn wrote:
>>> [...]
>>
>> Anyone?
>
> Most people here have probably already fixed a bug at one point or another. People that probably have never touched a compiler before, doing so out of necessity. From my experience a hacky workaround is a more palatable experience (sadly).

Understandable. Just trying to engage people 🍀

On Wednesday, 23 September 2020 at 20:40:56 UTC, Imperatorn wrote:
> Anyone?

IMHO, some "readme" or "howto" for beginners with example how to to make PR will be helpfull.
I am not expert, but may be, some begiiners like me can fix small issues.

But from other side, then read forum and see "ah, this this bug, i made PR at 2009" and see then it still not merged... may be my language barrier prevent me from understand this...

On 9/24/20 11:06 AM, novice2 wrote:
> On Wednesday, 23 September 2020 at 20:40:56 UTC, Imperatorn wrote:
>> Anyone?
> 
> IMHO, some "readme" or "howto" for beginners with example how to to make PR will be helpfull.

https://wiki.dlang.org/Get_involved

> But from other side, then read forum and see "ah, this this bug, i made PR at 2009" and see then it still not merged... may be my language barrier prevent me from understand this...

Pinging interested parties on old PRs that are still open would be a helpful contribution as well! Maybe they get closed, or maybe they get brought up to speed.

I have 100s of emails from github a day, relating to D. I delete most of them, because I don't have time to deal with them all. I can also contribute something to a PR (like a review), and forget about it after that, never merging. Pinging periodically is useful as a reminder.

-Steve

On Thursday, 24 September 2020 at 15:17:32 UTC, Steven Schveighoffer wrote:
> On 9/24/20 11:06 AM, novice2 wrote:
>> On Wednesday, 23 September 2020 at 20:40:56 UTC, Imperatorn wrote:
>>> Anyone?
>> 
>> IMHO, some "readme" or "howto" for beginners with example how to to make PR will be helpfull.
>
> https://wiki.dlang.org/Get_involved
>
>> But from other side, then read forum and see "ah, this this bug, i made PR at 2009" and see then it still not merged... may be my language barrier prevent me from understand this...
>
> Pinging interested parties on old PRs that are still open would be a helpful contribution as well! Maybe they get closed, or maybe they get brought up to speed.

Yep. Someone had an initiative related to issues last year and it reminded me of one (very simple, related to documentation) that I never finished.

On Thursday, 24 September 2020 at 15:06:25 UTC, novice2 wrote:
> On Wednesday, 23 September 2020 at 20:40:56 UTC, Imperatorn wrote:
>> Anyone?
>
> IMHO, some "readme" or "howto" for beginners with example how to to make PR will be helpfull.
> I am not expert, but may be, some begiiners like me can fix small issues.

You can indeed, in the documentation if not the code. I've submitted PRs every so often related to documentation and unit tests. It's not that hard. You can go through old issues and do things like reproduce the bug or confirm that it's no longer relevant.

> But from other side, then read forum and see "ah, this this bug, i made PR at 2009" and see then it still not merged... may be my language barrier prevent me from understand this...

Those are typically bigger PRs. When I submit small things like documentation or an update to a unit test, they're merged within a day or a few days at the most.

On Thu, Sep 24, 2020 at 06:09:42PM +0000, bachmeier via Digitalmars-d wrote:
> On Thursday, 24 September 2020 at 15:06:25 UTC, novice2 wrote:
[...]
> > But from other side, then read forum and see "ah, this this bug, i made PR at 2009" and see then it still not merged... may be my language barrier prevent me from understand this...
> 
> Those are typically bigger PRs. When I submit small things like documentation or an update to a unit test, they're merged within a day or a few days at the most.

Yes, I recently submitted a couple of small PRs that got merged pretty quickly.  The ones that get stuck generally have one or more of the following challenges:

- The PR fails to pass the autotesters and CIs, and the submitter is
  slow to respond and/or not responding, so there's not much we can do
  about it;

- The changeset is large, therefore hard to review, so most reviewers
  (who are volunteers with limited free time) are less inclined to
  review them;

- The change requires expertise in a particular area to review correctly
  (e.g., deals with tricky concurrency issues, or OS details, or tricky
  pointer/memory manipulations or involves some complex spec like
  parsing some DSL, or floating-point algorithms that are tricky to
  write in a way that won't risk catastrophic loss of precision or wrong
  behaviour in corner cases).  If the area is too specialized, many
  reviewers feel unqualified to review it (probably rightly so), so it
  tends to get less attention that it should.

- The PR introduces some controversial bits of code that one or more
  reviewers may not agree on, or it breaks existing code in some way, or
  requires approval from the leadership (which generally takes a long
  time, and unfortunately requires a lot of persistence on the part of
  the submitter).


T

-- 
MAS = Mana Ada Sistem?