Racket glossary

[sschwarzer]

@benknoble

I do agree with everyone's points about the barrier to entry; OTOH, I can see sschwarzer's points as fairly normal for the open-source community. This is one of the reasons I like hacktoberfest in its origins: it encouraged folks to learn how to contribute, sometimes by working with people that could guide them. It's not that open-source wants to have a high barrier to entry, per se, but that open-source has high standards, perhaps?

I saw your post only now after writing my reply to posts further up.

I so agree with what you wrote. When I enter a PR for a project, I consider it completely normal that it won't be the final version. For me it's natural that a PR goes through potentially several iterations; it's part of the contribution process.

On the other hand, I now have more empathy with people who feel different about this and I'm willing to adapt, at least regarding the notes file.

Edit:

@hendrikboom3

Maybe a wiki would help?

I thought about this before making the glossary a repository. My experience is that the Racket wiki rarely comes up in web searches. The best glossary isn't useful if it can't be found by those who need it. Finding the glossary on the Racket documentation page is much more likely. (I haven't submitted the glossary to the package server yet. I plan to do this once the "basic" category is mostly complete.)

Moreover, I'd like to have some coherence in the writing style between the glossary entries, which would be quite difficult to achieve in a wiki, I think.