On Jan 20, 2011, at 3:57 AM, Timo Mäkimattila wrote: > On Mon, 2011-01-17 at 18:07 +0200, Foster, Dawn M wrote: >>> 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. > > I agree and share your concern about that. > > Would it be possible to give one of our team members the admin rights to > the blog? The team is worried that doing admin tasks (adding users, > adding/removing/updating posts) will be slow if we need to make requests > for every action and wait for someone outside of our team to take the > action. At least everyone in our team should have an easy access to > submit stories. > > We would be willing to join the official blog, but we need some time to > rearrange the stuff we have in wordpress to our wiki. And to figure out > what kind of information goes to wiki and to the blog. Most of our blog > writings have been sort of "hands on" tutorials for our end users. >
Can you file a bug requesting access and assign it to Mike Shaver with a cc to me? We'll need to figure out the best way to give your team access, but this will be easier to track as a bug. You'll want to include a list of team members needing access. Also, before we start posting to the MeeGo blog, we need to think about which posts belong in the wiki, instead. Usually hands-on tutorials will go in the wiki where anyone can already add and update posts. It might make more sense to use the blog for a regular update linking to all of the tutorials and other information posted in the wiki - maybe weekly or every other week? Thanks, Dawn _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
