link feeds/patreon/github releases to project releases

[illume]

ED: patreon posts could be linked to projects, as "project updates".

---

This way people can link up their patreon, their github, or blog and have things go up on the site without adding extra work for people to do.

So yeah... linking patreon to pygame website. I think that'd work ok... Each post is a release. There's no rss/feed but converting it to an rss feed is trivial. Then that same rss/feed code could be used for github/bitbucket/blog. https://github.com/splitbrain/patreon-rss

Maybe it could just take the first paragraph and link back. Options would be...

feed_url: str
""" eg. https://www.patreon.com/inversephase/posts?tag=tracker """
post_summary: bool
""" (first paragraph) """

Oh. Except most github pygame projects don't seem to use the release tags. Of the ones that do, fewer still put a description in there. Maybe it'd be better to find chunks of work in a list of commits. Or keep them separate.

[illume]

[15:10:09]  <illume>	So yeah... linking patreon to pygame website. I think that'd work ok... Each post is a release. There's no rss/feed but converting it to an rss feed is trivial. Then that same rss/feed code could be used for github/bitbucket/blog.  
[15:13:16]  <illume>	Maybe it could just take the first paragraph and link back. Options would be... feed_url: str, post_summary: Boolean (first paragraph)
[15:13:31]  <illume>	Oh. Except most github pygame projects don't seem to use the release tags.
[17:01:15]  <P2E>	illume: as long as it isn't labeled a release to the viewer, I think that'd be fine
[17:03:55]  <illume>	Yeah, they can be different things sort of. But I think there should be room for "here is an update", without the stress and extra work of a "release".
[17:04:31]  <P2E>	yeah, that sounds more apt
[17:04:57]  <P2E>	would it go to a master project page, where I could give a summary of the tracker software?
[17:05:11]  <P2E>	(or supply you with it, I guess, if you need)
[17:06:54]  <illume>	I'm not sure exactly. I guess it would go on a project page. And then project pages could have "update posts" on there. A patreon/blog tag could be associated with a project... which could then fill "update posts" from there.
[17:07:33]  <illume>	But then that would require making a project page... and giving the thing a name even.
[17:08:03]  <illume>	Which I guess people sort of have names for things when they post about them mostly... so that's fine.
[17:10:03]  <illume>	At least a few people have patreons or blogs for their projects. So it'd be worthwhile just for these. The github releases match up nicely to project releases... so that would be a different thing.
[17:10:13]  <illume>	(sorry to take you on this journey... lol)