Hi @westurner. That is interesting about Gitflow and Hubflow; however, we're not seeking to make substantive changes to our workflow right now.
Cool. That's why - before i took the time to send that to you on my phone one day - I added "FWIW" before explaining that to you about git branching overhead. Larger teams require multiple maintainers to handle branch merging and tagging consistently.
Are you looking to build your GitHub profile? If so, I recommend being more mindful of how you propose changes in projects like this. I see you have opened several issues in other projects, similarly to this one, and they all seem to lack any clear explanation of the problem you are proposing to solve. They also don't look like you've made a sincere attempt to familiarize yourself with the projects before opening an issue. Such activity will not only waste the time of those projects' maintainers, but will also reflect poorly on your portfolio as an open source contributor. Contributions from volunteers, especially those eager to gain experience, are welcome here, but behavior like that is unhelpful, and will be reported as spam if it persists.
They also don't look like you've made a sincere attempt to familiarize yourself with the projects before opening an issue.
This is disrespectful to me. I took the time to explain to you that you do not have a link to the deployed copy of your PWA in your README and you've now insulted me by calling me a spammer and insinuating that my other contributions (which you claim to have reviewed) are not of value either.
When you make an argument, you should make the argument using premises founded on evidentiary claims: specific citations.
I will lock this issue now, but if you genuinely wish to contribute to this project in the future, I encourage you to take a little more time reading through the project history, reviewing the farmos.org website, and introducing yourself on the farmOS forum if you have more general interests and curiosity.
I could've sent you a PR when I got around to prioritizing where and why your README lacks a link to the deployed PWA, but now I'm not inclined to spend any more time on this than this letter because of false accusations that I've spammed you.
Thanks for understanding, and best of luck to you in your studies!
There was no other way of contacting you in reply other than to create this additional issue.
I will not create further issues for the farmos/ projects.
Cool. That's why - before i took the time to send that to you on my phone one day - I added "FWIW" before explaining that to you about git branching overhead. Larger teams require multiple maintainers to handle branch merging and tagging consistently.
You marked https://github.com/farmOS/field-kit/issues/510 as spam.
This is disrespectful to me. I took the time to explain to you that you do not have a link to the deployed copy of your PWA in your README and you've now insulted me by calling me a spammer and insinuating that my other contributions (which you claim to have reviewed) are not of value either.
When you make an argument, you should make the argument using premises founded on evidentiary claims: specific citations.
I could've sent you a PR when I got around to prioritizing where and why your README lacks a link to the deployed PWA, but now I'm not inclined to spend any more time on this than this letter because of false accusations that I've spammed you.