3 ms·
What would happen if some Apple developers moved their collective feedback to a Github repo where their bug reports were licensed as CC-BY-4.0, i.e. a license t
by walterbell 3y ago
What would happen if some Apple developers moved their collective feedback to a Github repo where their bug reports were licensed as CC-BY-4.0, i.e. a license that would allow Apple to migrate content from the public repo to their internal radar? This would allow developers to have a public database of de-duped and triaged bugs, and it would allow Apple to either respond publicly (same as Webkit?) or maintain status quo.
- latexr 3y agoNothing would happen. Websites and GitHub repos for posting Apple bug reports publicly have existed for over a decade. https://openradar.appspot.com/ https://openradar.appspot.com/
- pronoiac 3y agoI'm aware of an open collection of Apple Feedback Assistant reports on GitHub - https://github.com/feedback-assistant/reports/issues https://github.com/feedback-assistant/reports/issues > Apple Feedback Assistant reports are not public. To help other developers discover existing reports, copy-paste your submitted Feedback Assistant report into a new issue. Make sure you include everything. > This is similar to Open Radar, but it's easier to fill out the report and GitHub has better search. Also, Open Radar doesn't yet support Feedback Assistant. > Instead of voting on issues opened here (which Apple won't see anyway), file a new Feedback Assistant report and copy-paste the contents of the report you found here and link to the original report. Apple encourages duplicates.
- walterbell 3y ago> have existed for over a decade Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you! Those look like a public mirror of some Radars filed at Apple, i.e. Apple already has that information. If enough developers stop submitting feedback (topic of this HN thread) and start posting bugs into a public repo FIRST, with a CC-BY-4.0 license allowing Apple to mirror the public bugs, then a boycott would have the positive side effect of showing-by-example how the feedback process could be improved. > nothing would happen As a counterpoint, there is a public Bugzilla for Webkit bugs, where the keyword "InRadar" indicates whether the bug has been mirrored to Apple's internal bug reporting system. If enough developers boycott Apple Feedback, could they use a Bugzilla instance for iOS and macOS bug reporting? If enough Apple users start referencing Bugzilla URLs for iOS/macOS production issues and purchasing decisions, could that influence Apple? https://bugs.webkit.org/buglist.cgi?bug_status=__open__&content=security&no_redirect=1&order=changeddate%20DESC%2Cpriority%2Cbug_severity&query_format=specific https://bugs.webkit.org/buglist.cgi?bug_status=__open__&cont...
- ayewo 3y agoYou mean something like this https://github.com/feedback-assistant/reports https://github.com/feedback-assistant/reports ?
- walterbell 3y agoThat is yet another public mirror of private Apple feedback reports. The suggestion is a public Bugzilla of iOS/macOS bug reports, similar to Webkit, that could be selectively mirrored by Apple to private radars, https://news.ycombinator.com/item?id=38166908 https://news.ycombinator.com/item?id=38166908