Re: [racket-dev] Racket Survey 2020

[Stephen De Gabrielle]

On Tue, 23 Jun 2020 at 17:22, Sam Tobin-Hochstadt <sa...@cs.indiana.edu> wrote:

We’re taking a survey! We want to better understand the Racket
community, from people who have been contributing for decades to those
who have just joined us, and from seasoned programmers to those just
starting out.

One of our goals is to help bring in new contributors and make it
easier to become a part of the community.

Fill out the survey here: https://forms.gle/XeHdgv8R7o2VjBbF9

Completing the survey should take 10–15 minutes, and is anonymous
(unless you decide to include your name). The survey will be open
until July 31 and we will report on the results sometime after that.

Please help us spread the word by sharing the survey link on your
social network feeds, at conferences, around your office, and in other
communities.

If you have any questions, please let us know at sur...@racket-lang.org.

Stephen De Gabrielle & Sam Tobin-Hochstadt

--
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAK%3DHD%2BYS-H-WGUZBkBvMdd_LBd9AyMPEk6838rtRjmd_LYkWLg%40mail.gmail.com.

--

----

[Alex Harsanyi]

On Thursday, June 25, 2020 at 6:14:42 AM UTC+8, jos.koot wrote:

Questions and problem reports of users always are responded to very promptly.

It depends.  If the problem report starts with "racket crashes when I do X", it will be fixed within 24 hours.  For everything else, not so much.  A quick browse of the issues sections of the various packages in the Racket organization will show that there are many issues reported a long time ago which have no feedback.

While Stephens question in another thread is how we can encourage users to submit fixes themselves, there is also a lack of response when it comes to submitted pull requests.  You can browse the pull request section of various projects and see for yourself, but here is an example: https://github.com/racket/plot/pull/5 -- created in 2015, looks perfectly good and reasonable change, yet there is no feedback from the Racket team about this.  Why should this person ever attempt contribute again if she is ignored?

For my part, I have some spare time which I could dedicate to helping out the Racket project.  Given that my time is limited, I cannot pick up big tasks, but I could help diagnose and fix bugs (and I have done so a few times in the past).  However, my own experience is that, even if I submit a pull request, I need to prompt the developers to look at it and provide feedback, and it is unclear to me when I would cross the line and become nagging.

I understand that the core Racket team is busy, but they are the only ones who can clarify the criteria for merging a pull request and also only they can review and merge them -- if they don't have time to do that, it is useless to talk about user contributions.

Alex.

 

[Stephen De Gabrielle]

Hi

On Thu, Jun 25, 2020 at 5:34 AM Alex Harsanyi <alexha...@gmail.com> wrote:

I understand that the core Racket team is busy, but they are the only ones who can clarify the criteria for merging a pull request and also only they can review and merge them --

You made me think of the style guide, but when I looked it has a section on contributing PR's that I hadn't seen, read or remembered:

https://docs.racket-lang.org/style/branch-and-commit.html

This will be after i fix MY bad PR ! https://github.com/Metaxal/quickscript-extra/pull/9#discussion_r445376039

Didn't you compile and run the script before submitting? It should tell you there's an error.
When you make a PR (for any Racket project), always do the following:

• raco pkg setup [package]

• raco test [package]

I was caught out! I made a last minute change without testing.

Maybe we could look a expanding https://github.com/racket/racket/wiki/Propose-a-fix-or-enhancement 

to 

a) reference the style guide: https://docs.racket-lang.org/style/branch-and-commit.html
b) provide a little more detail
 

As for  https://github.com/racket/plot/pull/5 - I'll commit to having a go at reviewing it tomorrow AFTER I fix my bad PR.

Kind regards 

Stephen

(On the laptop in the garden because it is 10:50pm and it is too hot in house.)

--

----