Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-Tool RSS Feed Planning #48

Open
captn3m0 opened this issue May 31, 2019 · 4 comments
Open

Per-Tool RSS Feed Planning #48

captn3m0 opened this issue May 31, 2019 · 4 comments
Assignees
Labels
enhancement New feature or request good-first-issue Good for newcomers Hacktoberfest Issues that are good first picks for Hacktoberfest participants

Comments

@captn3m0
Copy link
Member

Assuming you subscribe to the PHP RSS Feed. I would want to get notified on the following scenarios:

  1. When a EoL date of any release is approaching (6 months, 5 months, 4 months, 3 months, 2 months, 1 month, 3 week, 2 week, 1 week, 6,5,4,3,2,1 days and today).
  2. When a new release is announced.

RSS Spec allows publication with dates in the future, but it is left to the tool:

If it's a date in the future, aggregators may choose to not display the item until that date.

It would be better to hide the element till the date>=today for that item, in which we case, uncomment it.

With that in place, (1) should be doable. But how do we get to (2)?

@captn3m0 captn3m0 self-assigned this May 31, 2019
@captn3m0
Copy link
Member Author

If we add a latestReleaseDate alongside latest in the build, and use that as the date of the release, it would work?

The issue is in case we add a release a few days late, and the release would show up with a publication date in the past, and feed readers may ignore it?

@captn3m0 captn3m0 added the enhancement New feature or request label May 31, 2019
@captn3m0
Copy link
Member Author

So Jekyll multi-layout is still an untackled problem: https://issuehunt.io/r/jekyll/jekyll/issues/3041

@captn3m0
Copy link
Member Author

captn3m0 commented Sep 27, 2021

Pick this if you know a little of Ruby. The intent here is to create a RSS file for each product, similar to how we do it for JSON files. RSS Feeds are easily generated using Jekyll, however the default is to create an RSS feed of all pages, which is not what we want.

Each RSS file should include all the dates known about that product. If there isn't enough information to create a RSS file (such as no dates on /iphone) - use a feed: false to turn off the RSS for that page.

Keep the page URLs as simple as possible: endoflife.date/feed/php.xml for eg.

Add a link to the RSS file in the product page as well, as the corresponding link in HTML so that anyone can subscribe to the feed easily.

Since RSS feeds are "notifications", we should provide a 7-day, 30-day, 90-day entry for all items. So if you subscribe to the PHP feed, you should get notified on the following dates:

  • 26 Nov 2022 - PHP 8.0 is no longer in Active Support
  • 26 Nov 2023 - PHP 8.0 is now End of Life
  • 27 Oct 2022 - PHP 8.0 Active Support runs out in 30 days
  • 26 August 2022 - PHP 8.0 Active Support runs out in 90 days
  • 21 Nov 2022 - PHP 8.0 Active Support runs out in 7 days.
  • 19 Nov 2023 - PHP 8.0 Security Support runs out in 7 days
  • 27 Oct 2023 - PHP 8.0 Security Support runs out in 30 days
  • 26 August 2023 - PHP 8.0 Security Support runs out in 90 days

(And similarly for the remaining PHP versions).

Make sure you read through CONTRIBUTING.md to understand the file structure. Also, please read through the HACKING.md file to setup the project locally. Reading these will help you get onboarded faster and make sure that your PR sees a speedy merge.

And finally, we have a very helpful guide for new contributors during Hacktoberfest as well.

There is a very similar issue for WebCalendar support that you might be interested in: #59

@marcwrobel
Copy link
Member

I someone is interested by this feature an example of a Jekyll Generator is available in #2080.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good-first-issue Good for newcomers Hacktoberfest Issues that are good first picks for Hacktoberfest participants
Projects
None yet
Development

No branches or pull requests

3 participants