Closed favour-chibueze closed 1 month ago
@fakela the issue is no-code contributors do not have issues/bug reports in GitHub to work from in many cases so it won't be visible in the overall project board, and they don't typically make a PR to contribute (e.g. marketing, design etc). So I was thinking that for those, they could make a PR to this repository to add their no-code contribution, which would mean that PR is then tracked and eligible for Hacktoberfest to count. Unless there's other ways around it, maybe?
Docs/Dev Docs would not need to do this as they make PRs, but knowledgebase, marketing, design, etc would all need a way for their contribution to be counted.
@fakela the issue is no-code contributors do not have issues/bug reports in GitHub to work from in many cases so it won't be visible in the overall project board, and they don't typically make a PR to contribute (e.g. marketing, design etc). So I was thinking that for those, they could make a PR to this repository to add their no-code contribution, which would mean that PR is then tracked and eligible for Hacktoberfest to count. Unless there's other ways around it, maybe?
Docs/Dev Docs would not need to do this as they make PRs, but knowledgebase, marketing, design, etc would all need a way for their contribution to be counted.
Oh I get it now. What your suggested should work to track their contributions
@fakela the issue is no-code contributors do not have issues/bug reports in GitHub to work from in many cases so it won't be visible in the overall project board, and they don't typically make a PR to contribute (e.g. marketing, design etc). So I was thinking that for those, they could make a PR to this repository to add their no-code contribution, which would mean that PR is then tracked and eligible for Hacktoberfest to count. Unless there's other ways around it, maybe?
Docs/Dev Docs would not need to do this as they make PRs, but knowledgebase, marketing, design, etc would all need a way for their contribution to be counted.
Oh I get it now. What your suggested should work to track their contributions
We can have the no-code contributors create/submit issues themselves on this repository, detailing their planned contributions (e.g., marketing, design work).
Once the issue is reviewed and accepted, we can add the Hacktoberfest label, assign the issue, and have them make a PR that reflects their completed work. This way, the contributions are verified and tracked properly, ensuring they count for Hacktoberfest while keeping everything organized.
cc: @fakela @RCheesley
@RCheesley I think this PR is good to go and can be merged.
cc: @fakela
Congratulations @favour-chibueze, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm2fsgix5195240cmfeyoiwa8l
This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!
@RCheesley the holopin stickers now work. 🎉 https://github.com/mautic/hacktoberfest-no-code/pull/1#issuecomment-2423620630
Yahoo! What did we do wrong?
Yahoo! What did we do wrong?
Just added the alias as a label
I thought we are labelling PRs we want people to work on with hacktoberfest. If yes, do we still need them to add it to a table. I think Hacktoberfest automatically picks up merged PRs from people who contributed to organizations participating in the program