Contributor wanted to help with PRs/issues

Question

Contributor wanted to help with PRs/issues

dbohdan opened this issue 2 years ago · comments

I am looking for a contributor to resolve this repository's issues and PRs, since I am currently sick and unable to. I will give you contributor access to commit to this repository. You can resolve issues as well as add and update scripting languages independently. I have some requirements, which amount to "do the things I do":

Add languages to the table with the correct name, URL, license, GC type, and something helpful in the "Notes" column. If a PR has missing information, fill it in yourself. Remove marketing speak from the notes.
Make sure new languages that you add follow the rules in Contributing.
Do not change "Contributing". Part of value of this repository is that the projects listed are selected for being open source and maintained or mature.
Write useful commit messages. Add/update one language per commit when reasonable. (See the commit history.)

Comment if you are interested.

Matthew Asplund · Answer 1 · Sat Dec 31 2022 07:39:22 GMT+0800 (China Standard Time)

@dbohdan I am willing to help review and complete some PRs while you are out.

D. Bohdan · Answer 2 · Sat Dec 31 2022 21:56:05 GMT+0800 (China Standard Time)

@mwasplund Thanks for volunteering! :-) I have sent you an invite.

Matthew Asplund · Answer 3 · Sat Dec 31 2022 23:47:18 GMT+0800 (China Standard Time)

@dbohdan Thanks, quick question before I start to look at it. How do you feel about adding more columns to the table to indicate things like language type (OOP vs functional vs procedural) and type system (static vs dynamic)

D. Bohdan · Answer 4 · Sun Jan 01 2023 04:26:25 GMT+0800 (China Standard Time)

Go ahead! I support adding columns. (Though maybe you could put some of these things in the same column, like OOP and typing discipline? Up to you.)

D. Bohdan · Answer 5 · Mon Jan 02 2023 16:28:53 GMT+0800 (China Standard Time)

Also, feel free to push changes directly to the repository. You don't have to PR your own commits unless that is your preference.

Matthew Asplund · Answer 6 · Mon Jan 09 2023 04:32:22 GMT+0800 (China Standard Time)

I prefer creating PRs to allow others to provide feedback before merging the changes.

Simon Michael · Answer 7 · Sat Feb 04 2023 03:45:11 GMT+0800 (China Standard Time)

Thanks for this excellent list, and best wishes @dbohdan.

D. Bohdan · Answer 8 · Thu Aug 03 2023 23:13:57 GMT+0800 (China Standard Time)

My condition has improved enough that I can maintain my GitHub projects. I will handle the remaining open issues and PRs soon.

@mwasplund Thanks for your help! If you would like to continue working on this repo, you are very welcome. If you'd rather retire, that's perfectly fine, too; I'll take over from here. Please tell me your choice, because it will affect my process. (Whether I PR the switch to generating README.md from a data directory that I am considering.) Either way, I appreciate your contributions.

Matthew Asplund · Answer 9 · Fri Aug 04 2023 09:58:02 GMT+0800 (China Standard Time)

That is great to hear! Sorry, I have been a bit behind on this project, I also had medical issues that have been taking up a lot of my time. I would love to continue to contribute since I have an interest in the area. Feel free to @ mention me in PRs you want me to help review

D. Bohdan · Answer 10 · Fri Aug 04 2023 21:10:47 GMT+0800 (China Standard Time)

Thanks! I am sorry about your medical issues. I sincerely hope you improve soon. Of course, you are welcome to keep contributing! I'll mention you in the upcoming generator PR and the issue before if I open one.