Anyone interested in proofing archives of Scripting News in Daytona?

Open
#350 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
content

Research direction

Review the archive files in blog/opml and blog/opmlOtherSources, then compare their date fields with the reports visible through Daytona. Identify malformed entries that produce NaN dates and verify that corrected archive data no longer causes those reports.

Written by the indexing model from the issue text.

Description

From time to time I get reports from users about weird stuff in Daytona, NaN's where a date should be.

I know about this. It's a flaw in the OPML file for the archive for that month.

It's something that could be iterated over and improved on.

I thought it might be an interesting project. If you're interested in doing this, post a note here, and I'll encourage people to post their reports here.

If you want to see what's involved, look in these folders

https://github.com/scripting/Scripting-News/tree/master/blog/opml

https://github.com/scripting/Scripting-News/tree/master/blog/opmlOtherSources

That's basically what's indexed in Daytona.

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.