i wont use this because the author sucks up all justfiles files with no way for a user to opt out and isnt fully clear on this. use it on some private or company thing that accidentally goes public, oops he has your file now in his repo.
if it was opt-in to him monitoring i might be more open. maybe i should fork and change the filename to keep this from happening
the issue is they are very arbitrary in what they accept. an example: a couple articles i updated to add commands for new os, not changing content other than command blocks (to be clear they allow this and have a submission form for updates or new os for exist articles), were rejected due to "grammar and spelling mistakes". i also had gotten "your commands do not work" despite in some cases them being slightly tweaked, if not the same, to already posted articles. in any case the original articles were still posted and not even getting updates. i took my edits or new articles and gave them to multiple others who found no issues from proofread or running the command. this made me stop even trying to contribute to them, so i image the same will be true of others. making the comp to DO a tough sell.
This bugs are still open, so there’s no reason to talk about them in a release announcement. If they were fixed, and made it into a release, then there’d be more to talk about.
Interestingly they also tell the person asking about it to not be rude which they don't seem to be, and the original email has a quote from an OpenBSD dev that is much worse.
They also did what was expected and try to hand wave it away for unknown reasons. Like when they wouldn't update the count of remote vulns on their home page due to made up reasons. Potentially to save their rep.
They admitted the policy needs rewording, and it has since been changed. IMO, Porter should have left it at that.
Demanding work from people or dropping it their lap, while you have no relation to them nor are they paid for it, would (IMO) be impolite, even if a policy somewhere stated they will give their firstborn to the first one that asks.
What if the maintainer didn't submit them simply because they just don't want to, this is deliberate with no technical reason this shouldn't be shared, still contradicting the first sentence. At that point I don't think its impolite anymore that someone else does the work with or without their permission. It was the maintainer's choice to leave the work to another person or team to upstream, in turn increasing their own burden to deal with cleaning up or adding patches later.
If OpenBSD doesn't want to be a good FOSS citizen they should state as much and not try to hide behind word games. Nor should they throw stones calling questions or discussion rude when other statements by their own team are worse, yet they seem exempt from their own guidelines, etc.
if it was opt-in to him monitoring i might be more open. maybe i should fork and change the filename to keep this from happening