Update RFCs docset

[pointlessone]

The docset file: RFCs.tgz.

[github-actions]

Test result: PASS 🟢

[Kapeli]

The link points to a file that does not exist (error 404).

[pointlessone]

Sorry, fixed.

[Kapeli]

The docset should be directly inside the archive (i.e. don't archive any enclosing folder). In your archive the docset is inside a dist folder.

I've remade the archive. If you can, please make sure to archive the docset directly on your next submission.

Sorry for the inconvenience!

[pointlessone]

Thank you. Absolutely.

[weppos]

@Kapeli @pointlessone I used to be the maintainer of the RFC docset (see #2480), that was originally created by @willnorris

The repo was not updated for a few years as the RFCs were migrated. Last month all the issues were cleared, and I started the process to get the docset ready for publishing.

However, as I came here today, I noticed that last week the repo was replaced with a new one in this PR.

How do you want to move forward in addressing the conflict? Any preference?

[Kapeli]

@weppos Can you point me to a downloadable docset with @Tenzer's changes? My preference would be towards users getting the version of the docset with the least issues, so I'd start by comparing the 2 docsets. As I'm not familiar with this docset, any help / suggestions are greatly appreciated.

[weppos]

Sure thing. Please give me until next week, this one I have limited connectivity.

[weppos]

@Kapeli I uploaded the file, you can find it at https://storage.googleapis.com/rfcdash/RFCs.docset-v2.0.0.tgz

Also referenced in https://github.com/willnorris/rfcdash/blob/master/RFCs.xml

[weppos]

Hi @Kapeli, did you have the chance to take a look? Anything I can help with?

[Kapeli]

Sorry, I missed your previous comment.

The docsets seem to be very similar.

The docset by @pointlessone has table of contents support for the RFCs that have the nicer page styling. See screenshots.

Can you find any issues/shortcomings in the docset by @pointlessone?

[pointlessone]

My code is in Ruby so it's not exactly compatible with @weppos script. I'm fine if it's being used as reference (it's under Apache license) if @weppos is willing to maintain it and update the docset once in a while.