It wouldn't be too hard to set something like that up, but I wonder if we could just do something more "direct". For example, I've thought that it might be interesting to have something like...
@Deimos, how difficult would it be to configure a recurring topic to pull the Markdown source of a wiki page and create the topic from that?
It wouldn't be too hard to set something like that up, but I wonder if we could just do something more "direct".
For example, I've thought that it might be interesting to have something like ~tildes.changelog that automatically creates a new topic whenever there's a new commit to the site repo. That would allow people to follow and discuss Tildes updates on the site itself, even when they're not significant enough for a ~tildes.official post. I think it would probably be too granular to be shown to everyone by default though, since a lot of it isn't very interesting, and it could be annoying to have a lot of topics when there's more active development happening. So I think we might need some better ability to discover/follow groups before something like that could work well.
We could also look at doing something that's scheduled but doesn't need a wiki page or anything involved, like something that just creates a list of commits over the last month/week. It would probably still need some manual editing, but a lot of it could probably be handled automatically.
Wouldn't a new topic per commit be too much? I've quickly thought of two alternatives off of my head, but I expect them to have some issues: Post topics when merge requests and issues with...
that automatically creates a new topic whenever there's a new commit to the site repo.
Wouldn't a new topic per commit be too much?
I've quickly thought of two alternatives off of my head, but I expect them to have some issues:
Post topics when merge requests and issues with specific labels (e.g. Feature Request, Bug, Important etc...) get merged
Have a weekly "this week's changes" post to list all commits of that week.
Hey man, thanks for your years of work! As a self-proclaimed internet historian, your logs are a really easy to digest way to record the history of the site, particularly in its early days, and if...
Hey man, thanks for your years of work! As a self-proclaimed internet historian, your logs are a really easy to digest way to record the history of the site, particularly in its early days, and if it's still running in 15 years, people are going to come back to it and be able to read the evolution for themselves. And that makes me really happy :)
On that note, it's also been just over 2 years since I joined as well, it feels like we just passed our 1 year anniversary yesterday!
Sad to see it come to an end, but thanks for all your efforts working on it over the years, @Bauke. ❤️❤️❤️
It wouldn't be too hard to set something like that up, but I wonder if we could just do something more "direct".
For example, I've thought that it might be interesting to have something like ~tildes.changelog that automatically creates a new topic whenever there's a new commit to the site repo. That would allow people to follow and discuss Tildes updates on the site itself, even when they're not significant enough for a ~tildes.official post. I think it would probably be too granular to be shown to everyone by default though, since a lot of it isn't very interesting, and it could be annoying to have a lot of topics when there's more active development happening. So I think we might need some better ability to discover/follow groups before something like that could work well.
We could also look at doing something that's scheduled but doesn't need a wiki page or anything involved, like something that just creates a list of commits over the last month/week. It would probably still need some manual editing, but a lot of it could probably be handled automatically.
Wouldn't a new topic per commit be too much?
I've quickly thought of two alternatives off of my head, but I expect them to have some issues:
Feature Request,Bug,Importantetc...) get mergedHey man, thanks for your years of work! As a self-proclaimed internet historian, your logs are a really easy to digest way to record the history of the site, particularly in its early days, and if it's still running in 15 years, people are going to come back to it and be able to read the evolution for themselves. And that makes me really happy :)
On that note, it's also been just over 2 years since I joined as well, it feels like we just passed our 1 year anniversary yesterday!