Adds .ics endpoints for calendars, topics and posts

[xfalcox]

No description provided.

[jtaylor69]

Just wondering if you had an update with regards to this PR being implemented?

[xfalcox]

Just wondering if you had an update with regards to this PR being implemented?

Thanks for the ping @jtaylor69. I forgot about doing this 😅

I will try to get it merged.

[gungora]

I’m looking forward to iCal support as well 😊

[guilhem]

Gentle ping for this PR.
How can we help? :)

[0xPetra]

Is there a way to pull funds into tasks for Discourse's OSS?

It would be a great way to fund the features we need, and get funding to build them!

What's the status of this PR? Does it need something to get merged @jjaffeux?

[rsmithlal]

Hi folks, I'd love to see this implemented.

Pavilion's Discourse Events plugin is broken at the moment after the 3.2 upgrade.

Is there anything I can do to help?

[RaitoBezarius]

@jjaffeux Could we have an official answer from maintainers of this repo on the way to go to make this PR land? I am willing to spend time fixing it, etc. But it'd be nice to understand if this repo is willing to accept such a contribution at all.

[ZogStriP]

@xfalcox is this still relevant? 🤔

[pedro-nonfree]

Let me try to summarize the situation (so I am not going to introduce new information, just put it all together closer)

@ZogStriP can you publicly clarify what happened to just close after your question that if it is still relevant?

Let me try to respond, according to the public information available:

1. Is it popular? yes, this feature has 11 thumbs up and 4 hearts. It is the most upvoted PR in this repository check it here (most upvoted is 2). It is also the most upvoted PR comparing it to the discourse main repo check it here (most upvoted is 5).
2. Does it introduce relevant features? Yes, @RaitoBezarius and the NixOS community are complaining that the discourse calendar, without the ics feature, is a silo. In other words, this PR solves that situation.

Given the situation, it would be nice to know what happened, because this is a relevant issue that some people would like to know what happened.

Specially, on two questions:

1. Is discourse going to pursue the development of this feature or a similar one?
2. Is discourse willing to accept a similar feature developed by the community?

[ZogStriP]

@ZogStriP can you publicly clarify what happened to just close after your question that if it is still relevant?

This was just me cleaning up old PRs.

1. Is discourse going to pursue the development of this feature or a similar one?

Not as far as I'm aware no.

2. Is discourse willing to accept a similar feature developed by the community?

Provided it's in a mergeable state (this one wasn't) and has tests, sure 👍

If that's the case, do not hesitate to ping me so I can have a look 👀

[RaitoBezarius]

2. Is discourse willing to accept a similar feature developed by the community?

Provided it's in a mergeable state (this one wasn't) and has tests, sure 👍

If that's the case, do not hesitate to ping me so I can have a look 👀

Thank you for the confirmation! I will try to do my best to clean it up, add tests and ping you :).