On Jan 17, 2011, at 4:19 AM, Timo Härkönen wrote: > On Mon, 2011-01-17 at 13:30 +0200, Timo Mäkimattila wrote: >> On Fri, 2011-01-14 at 19:04 +0200, Foster, Dawn M wrote: >>> I would still like to see the QA tools posts on the meego.com blog. >>> Typically, the planet is used for informal, unofficial or general >>> information >>> about a topic, in this case, MeeGo. Having the information in the planet >>> will allow an excerpt to temporarily show up on the home page, but it >>> makes it much less likely for someone searching meego.com for >>> information about qa tools to find your information a few months later. >> >> Hi, >> >> Couple of concerns came up in the team: >> >> Writing the blog should be made easy. Writing to meego.com would have >> more bureaucracy (proof reading) that we have with our own current team >> blog. Things tend to change quickly: We need to able to update/fix blog >> writings without overhead. We do a lot of fast proof-of-concepts. >> >> How about having a summary of new qa-tool blog writings in the MeeGo >> blog? That way they could be accessed through meego.com and they would >> point out to our own blog with a link after the short summary for each >> blog entry? >> >> -Timo >> > > > Yep. at least I'd like us to use both blogs. We could write the more > "stable" things into the MeeGo blog and use our own blog as the team > blog for anything that the team feels like blogging. If we would only > use the MeeGo one I fear that I would reduce our activity in this front. > > For example a general post titled 'How MeeGo QA is done?' would go into > the MeeGo blog and something titled 'setting up you own ots worker' > would go into the team blog.
Most teams are using the wiki for the things that change frequently and need to iterate quickly and the more stable information gets published on the meego.com blog as an update. Again, my main concern is that having this Wordpress blog fragments the information and makes it more difficult for people to find. When someone searches the wiki or meego.com, they aren't going to find the information that you are putting on Wordpress. I see having this be separate as a bit damaging to the project as a whole, since it duplicates our existing infrastructure and makes it harder for people to find information about QA tools. I strongly recommend moving this information to the wiki and the meego.com blog. Dawn _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
