Replies: 2 comments
-
+1 especially for improve our testing environment. A playground would also be nice: a pREST instance running with its database, configs, and source open to the public. That's nice when people try to understand parts of the codebase they haven't touched yet. |
Beta Was this translation helpful? Give feedback.
-
Thank you for bringing this up @avelino! I think this PR is being blocked a lot because we don't have a good set of testing environments and patterns, with this in mind I really think we could write down contribution requirements inside the PR template, so people could observe those sets of rules and infuse them in their contribution. A good example of Development Guidelines is Django's Also, this PR delay is related to another thing: I'm a newbie to Golang and its patterns, so I'm still on the learning curve. Probably, if I were more senior to Go, we would be able to cut half of the time.
On the playground side, it would really be cool to have it, and it would ease the showcase for new companies and teams, onboarding them better and quicker. |
Beta Was this translation helpful? Give feedback.
-
I feel that I am blocking contributions from new contributors, and this has made me feel powerless (my professional life is more hectic than I would like).
We need to make our contribution environment more fluid and give more autonomy to the people who want to contribute.
How do I imagine solving this problem?
also contribute
Why am I writing this thread?
Seeing this relatively simple (PR) contribution take more than 3 weeks to merge hurts my heart #750
Beta Was this translation helpful? Give feedback.
All reactions