-
Notifications
You must be signed in to change notification settings - Fork 347
Add your solution! #3
Comments
Nice! I submitted a swift version of fizz buzz, could you check it out? |
Amazing platform for coding |
I would like to work on this using python |
i would like to work on this |
interesting lets do that |
I would like to work on this using C++. |
I would like to work on this using C,C++,Python. |
I have added a one-liner using python lambda and map functions. |
Please check my PR. It was the 1st single line solution |
making a function of this on python |
Sir I have made a pull request after adding a folder for Cpp |
I would like to work in Python |
Just for clarification: |
I will try to do it in Ruby |
Added fizzbuzz with go routines #171 |
I would like to work on this using Ruby one-liner |
Can I help? |
@JossJoestar Any, as stated in the readme :) |
let me in, I give it a try. |
can i work on this project? |
@nldev, I guess it will be good if this issue is |
I would like to work on this using python |
I'd love to work on this repo with javascript π― |
While your project may not go against Hacktoberfest's "values", it's clearly not an existing OS project but designed solely to accept Hacktoberfest-related PRs. The repo name alone says as much, no need to read the README. So my point stands: your project is not in the spirit of Hacktoberfest, which has always been about making open source better. It's not about getting people to submit their solutions for exercises, that's what Computer Sciences courses are for, it's about giving back to OS. |
But since you linked to the official website: I wouldn't agree this project meets the fourth and last point in the "Quality Standards" section.
Individual PRs might meet that requirement, and PRs are, in fact, what the section focuses on, but I'd argue that's a limited reading of the rules (or, if you will, a failing on Hacktoberfest's part to not spell this out more clearly for people who nitpick over words rather than overall meaning). |
This might have been the "spirit" of Haktoberfest. However the website clearly states:
Don't get me wrong. I know what you mean. Yes, the hacktoberfest is meant to support existing open source projects that need help. However, anyone is welcome to participate and this repository isn't hurting anyone. It's not like everyone would just contribute to "serious" open source project if this repository here wouldn't exist.
Again, the website states the it's mean for learning as well.
As I said, I manually review every single PR and attempts to effortlessly +1 will be labeled as invalid. There have been a lot of creative solutions so far. For instance, someone wrote the first and only FizzBuzz implementation in the esoteric language OMGROFL with instructions on how to build it. Sure, this doesn't do much for the poor OSS community. Still no need in taking the fun out of it.
Thankfully, this isn't for you to decide. Cheers. |
I'm on @nldev side here |
Good on ya, I guess... |
I will try@NLDev it's opportunity to prove myself |
please assign this to me i will use python 3 to solve the aforesaid problem |
i will use python 3 in this |
@nldev I've added my solution using Segment Tree. |
Thank you for participating! |
π Hacktoberfest 2020 FizzBuzz
Please consult the ReadMe for information on what this repository is about and how to contribute!
β READ BEFORE CONTRIBUTING
THIS REPOSITORY IS IN COMPLIANCE WITH THE HACKTOBERFEST VALUES AND RULES:
We cannot and will not accept every PR and label invalid one's accordingly! Examples are off-topic contributions, duplicated solutions, copy-paste solutions as well as obvious +1 attempts.
We are searching for interesting/creative/abstract/unique/extraordinary/weird solutions to FizzBuzz. Only one normal solution per language is permitted!
This repository aligns with the values of the Hacktoberfest as it is meant as a fun challenge as well as a platform to learn (experiment with different solutions, challenging yourself to come up with creative solutions to a unique problem).
Denied PR's can be found here.
Happy hacking!
The text was updated successfully, but these errors were encountered: