Is there anyone reading who hasn't dealt with a merge conflict in an Xcode project file? Even if you work alone, you'll inevitably need to merge one as soon as you have two branches on the go. Wouldn't it be great if you didn't have to worry about all but the messiest and most complex ones? Enter this tool from Ben Yohay! The goal of the project is to cope with 99.9% of conflicts automatically. I'm not sure how close they are, but it's certainly going to be better than not having the tool!
Jesse Squires with a rather pessimistic view of Apple's new DocC documentation tool. He makes some good points, and he's right that it's pretty apparent Apple created this tool for themselves first and the community second. However, instead of looking at it as something that missed the mark. I think it's better to look at it as a promising start. I hope Apple isn't finished developing this tool, and as Jesse added in an update, there are options to build better processors for DocC output. In fact, immediately before publishing this issue, I noticed Helge Heß published a set of three new packages that look interesting. 🤔
Also, as Sven said on Twitter, helping to host open-source package documentation was already on our Swift Package Index radar. CocoaDocs was a fantastic resource, and expanding into that area would fit nicely alongside what we've already built.