Wild version 0.11.0 released
5 points by patchunwrap
5 points by patchunwrap
I'm a bit unsure if this conflicts with the new rule:
Pending an upcoming deploy, we no longer allow submissions which are code repositories. While, at first blush, this may seem odd for a community which is primarily centered around programming but it does eliminate the bulk of the "low effort, self promotional" submissions we've been seeing on the site. We've also found that being dropped into a new codebase doesn't start discussions because the reader has to have enough subject matter experience to immediately recognize what's novel or otherwise worth talking about. Instead, we are more interested in content around code bases which cover why it was created, the purpose it serves, the challenges overcome, and the reasons why it's a useful artifact in the ecosystem.
I assume it's okay since I'm linking to a release rather than the projects codebase. I also think this is directly applicable to macos developers specifically as it might improve their development experience (which seems on topic to me).
I'm curious what the admins say. I'm a fan of what Wild is doing but if we're going to have a ban on code repos I don't see why it would matter whether you're linking the root landing page or the release notes or anything else for that matter. Intuitively it seems to me either both are okay or neither are okay, and my understanding of the new policy is the latter. It's hard to see what the intrinsic difference is between linking release notes in the repo vs in a blog post, but sometimes that's how rules work.