Martin mentioned getting RSS feeds from the repo earlier; Tom Elliot subscribed the other day to the *releases* atom: https://github.com/TEIC/TEI/releases.atom which could still be useful to show on the teic website. Sadly, GitHub doesn't seem to have a RSS feed for issues, but we *could* build one via their API. Raff
I recall a discussion a while back about embedding a feed of new SF tickets on the www.tei-c.org homepage to show to people that things were actively happening with the TEI, but we never did ... perhaps because SF didn't provide such a feed. If anyone thinks a feed of releases should be advertised somewhere on tei-c.org, let me know and I can try to make it happen. Kevin On 10/27/15 10:39 AM, Raffaele Viglianti wrote:
Martin mentioned getting RSS feeds from the repo earlier; Tom Elliot subscribed the other day to the *releases* atom: https://github.com/TEIC/TEI/releases.atom which could still be useful to show on the teic website.
Sadly, GitHub doesn't seem to have a RSS feed for issues, but we *could* build one via their API.
Raff
Hi all, We found a way to get the information out of SF and embed it elsewhere and I think we did for awhile, but then SF changed platforms and it went away. That is my recollection at least but I've not had enough sleep tonight. -James On 02/11/15 16:25, Kevin Hawkins wrote:
I recall a discussion a while back about embedding a feed of new SF tickets on the www.tei-c.org homepage to show to people that things were actively happening with the TEI, but we never did ... perhaps because SF didn't provide such a feed.
If anyone thinks a feed of releases should be advertised somewhere on tei-c.org, let me know and I can try to make it happen.
Kevin
On 10/27/15 10:39 AM, Raffaele Viglianti wrote:
Martin mentioned getting RSS feeds from the repo earlier; Tom Elliot subscribed the other day to the *releases* atom: https://github.com/TEIC/TEI/releases.atom which could still be useful to show on the teic website.
Sadly, GitHub doesn't seem to have a RSS feed for issues, but we *could* build one via their API.
Raff
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
participants (3)
-
James Cummings -
Kevin Hawkins -
Raffaele Viglianti