-
-
Notifications
You must be signed in to change notification settings - Fork 18
Contributing Blog #31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I haven't thought about it that way, but now I get what you were up to. A blog article from a "new developer" to other new developers about your contributing experience (even though I personally consider you being an old hand at contributing rather than a new developer 😉). A nice idea! It could encourage others to contribute. @TomWFox what do you think? I can't really see the blog post content on mobile, but maybe we can re-use some of the text for the new contribution guide. Maybe we want to wait with review and merging until we overhauled the contribution guide with parse-community/parse-server#7075, if that makes sense? We may then also link the blog post in the new contribution guide. |
Love the idea! |
Thanks lads. The main motivation is to highlight that even regular contributors like myself still need to ask for help, and sometimes need help with creating features. I found contributing rather intimidating at first considering this is the first package I’ve contributed to, so I guess the intent is to try to let new developers know that it’s okay to not know everything. I chose the afterFind issue as I figure it’s not an overly complicated new feature conceptualisation, just a simple bug. As you’ve said in the past @mtrezza, there are a lot of these that remain unfixed mostly because the reporter has never contributed before. I would be more than happy to try to continue to encourage / support new developers in contributing. |
That's great, every help in parse-community/parse-server#7075 would be appreciated. |
Now parse-community/parse-server#7075 has been merged shall we move forward with this post? |
Two points:
Good to publish I'd say 👍 |
This should be a PR though, not a direct main branch merge? I also changed this in the branch permissions, in accordance to our other repos. |
Could you elaborate? This is a PR 🧐 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Did you run it locally to check it's rendering ok? I've been trying and failing.
This probably highlights the importance of a formal version because the reason I haven't added it is because I don't know how to do it myself. I normally just set |
In a formal version we should add this and more, but your blog post is fine as it is IMO, but feel free to add if you like. I think your post is a good entry point and easily digestible. I see it more as an anecdote. That's why I separated the blog post from the official documentation in my earlier comment. |
Just to add, in future if you want, editing a blog post is as simple as editing the file. |
I managed to run the site locally, for some reason it was stuck on a 'yanked' version of jekyll-paginate-v2, but anyway it looks all good. @dblythy I'm happy to publish if you are? I've bumped the date today. |
Happy to go if you are mate. |
I'll tweet it from @ParsePlatform later 🚀 |
@mtrezza the reason I worked on 7078, thought the walkthrough could help some people.
Tried to keep it informal so contributors know that they can always ask for questions and help. But can re-write in a different format.
Reminding you all that I am a noob too so pls correct my terminology if it's incorrect.
Will review typos tomorrow.