add south korea flag to readme

[peterdudfield]

add south korea flag to readme- https://github.com/openclimatefix/open-source-quartz-solar-forecast?tab=readme-ov-file#global-model

[lambaaryan011]

Hi @peterdudfield I love to solve this. So can you assign to me

[DilsharaHerath]

I would love to contribute to this Mr. @peterdudfield !

[Saahi30]

Hey @peterdudfield ,we have got multiple PRs(#267 #266 #265 ) Addressing this issue...I believe we should go ahead to merge any of them and mark this issue as closed.

[lambaaryan011]

Hey @peterdudfield ,we have got multiple PRs(#267 #266 #265 ) Addressing this issue...I believe we should go ahead to merge any of them and mark this issue as closed.

but i think this is not a correct way to work in open source . Firstly you have to assign the issue and then start work on them, did you not read the developer guide

[Saahi30]

Hey @lambaaryan011, I don’t think I should have to explain this, but you learn from experience, so listen. Open-source projects, especially for minor issues like this, don’t always require formal assignments before submitting a PR. Approvals are meant to prevent duplicate efforts in larger, more complex issues by ensuring better workload distribution and work quality.

However, for such a small issue—a simple line change—a quick and working fix is always appreciated. Multiple people had already expressed interest, so it made sense to move forward with the best PR rather than waiting. The goal isn’t to collect approvals but to improve the project efficiently. If you think strict assignments should be enforced, it’s best to discuss that with the maintainers.

[lambaaryan011]

Hey @lambaaryan011, I don’t think I should have to explain this, but you learn from experience, so listen. Open-source projects, especially for minor issues like this, don’t always require formal assignments before submitting a PR. Approvals are meant to prevent duplicate efforts in larger, more complex issues by ensuring better workload distribution and work quality.

However, for such a small issue—a simple line change—a quick and working fix is always appreciated. Multiple people had already expressed interest, so it made sense to move forward with the best PR rather than waiting. The goal isn’t to collect approvals but to improve the project efficiently. If you think strict assignments should be enforced, it’s best to discuss that with the maintainers.

HI @Saahi30, It's not about "major" or "minor" issues. Open-source projects thrive on structure, and following the process ensures fairness and learning opportunities for everyone. And listen—people start by learning from small things before moving to bigger challenges. Ignoring the process just for speed? That’s not how we build a strong community. Hope you get that.

[peterdudfield]

Thank you everyone, i merged the PR that was made first. I thought that was the fairness. In general OCF does like to assign issues to stop multiple work being done