SPCK/SSG News Archives

Dave Walker has compiled an index of news reports and correspondence about the SPCK/SSG saga in the Church Times blog, which helpfully supplements his own Save the SPCK section. To that I’d like to add the UKCBD SPCK/SSG News Section, this site’s reports and reflections and the various reports in the Bookseller: 
SPCK | SSG | St Stephen the Great. Should probably also add this rather long and meandering thread at Ship of Fools, “SPCK” bookshops.

Taken all together that’s a huge amount of information with considerable overlap, but it leaves no one with any excuse to say they didn’t know what was going on.

One of the things we (that is, Dave, Phelim and myself: not sure whether anyone else was in on the conversation) discussed briefly at the SPCK Booksellers Get-together back in May was the idea of setting up a dedicated SPCK/SSG blog. This would take some of the pressure off Dave, especially in July when he’s going to be busy blogging and cartooning Lambeth (brilliant cartoon in today’s Church Times, btw: had me in stitches. thanks, Dave!), and will help keep a continuous spotlight on the situation, which neither Dave nor I can necessarily do with our respective blogs.

I’m quite happy to set the blog up at WordPress, although anyone reading is equally capable of doing that: WordPress really does make blogging incredibly simple. But what I can’t do is run it single-handed: I think it needs a team of three or four people, possibly more.

So, do we have any volunteers from amongst our readership? You’ll need a WordPress ID: signing up for that will take you less time than it’s taken me to type this sentence. Then you’ll need to leave a comment using your WordPress sign up email address (this will not be made public) so that you can be set up as an author/contributor. SSG/ENC moles need not apply!!

Over to you, people…

---

Update 27/6/2008: Originally I said ‘let me know your WordPress ID’. What I actually need is your WordPress sign up email address: just use it as normal when leaving a comment. Apologies for any confusion/misunderstanding!