As much as I like the general idea to facilitate the edition of the
website, I have issues with the proposal.
In short:
+ Committers would be required to have/create a Google account
+ A company might earn money with displaying our project's content
(since the blog would be visible on it's own, right?)
+ If Google messed up the backup or decides to take the service down, we
potentially loose our content
+ This is for publishing 'official' content, only our website should be
authourative for.
+ The original problem (website change is time-consuming) is not resolved.
Danny Angus wrote:
Hi,
The thread "[Proposal] James News List & Feed" has come to a consensus
amongst robert Stefano and I, therefore would you please vote on the
following item:
James news is awkward to update, because it requires two xml files to
be edited, and the site to be generated and checked back in, then the
web server to be updated. Using an external blogging service will
considerably reduce that bar and possibly result in us publishing news
more often.
All things considered, my vote is
[X] -0 I do care, but won't hold up you guys, if you'd invest time in
doing this.
Bernd
