[qgil]

Here is a first stab to the meego.com maintenance team and & process.

http://wiki.meego.com/Meego.com

Questions, feedback, ideas... now it's the right time for it.

[mshaver]

I've added a few details to the wiki page and to the Community Task list. One item that I think is key here is an overall architecture of the meego.com infrastructure. Getting a community document that can be referred to as we go forward will allow for growth without everything turning to chaos!

[qgil]

What is help.meego.com and is it part of the May release web content?

[dawnfoster]

Originally Posted by qgil

What is help.meego.com and is it part of the May release web content?

Instead of placing the user help in the build (where it is harder to change), all of the user help will be at help.meego.com. Noel Arnold from Intel is currently writing the user help for the May release, so she will be providing the content and structure for that section of the website. She's working closely with Mike Shaver to get the help section implemented.

The build will contain a small amount of help text mostly focused on troubleshooting and help getting connected to the Internet where they can find the rest of the user help.

Keep in mind that this is help for end users, not developer help, which will be located elsewhere.

I'll ping Noel to with this thread, and she can add to it if I missed anything important.

[mshaver]

Originally Posted by qgil

What is help.meego.com and is it part of the May release web content?

Sorry to spring that new piece of the meego.com puzzle on the community without a proper discussion! This has all developed rather quickly. Dawn's description is accurate at the high level though. Because of the tight timeline though, we need to get something out there and then have community participation in making it better.

[dneary]

Originally Posted by mshaver

Sorry to spring that new piece of the meego.com puzzle on the community without a proper discussion! This has all developed rather quickly. Dawn's description is accurate at the high level though. Because of the tight timeline though, we need to get something out there and then have community participation in making it better.

Thanks Mike!

Everyone understands tight timelines of course, but knowing the scope of what Noel is working on, and even just being aware that she's doing it, is useful. Is there any way to follow along with her work, or will that have to wait for a release?

Cheers,
Dave.

[dawnfoster]

Originally Posted by dneary

Everyone understands tight timelines of course, but knowing the scope of what Noel is working on, and even just being aware that she's doing it, is useful. Is there any way to follow along with her work, or will that have to wait for a release?

This is user help, which is based on the user experience, so this will have to come out after the code is released. Right now, this user help is focused on the netbook user interface.

[margie]

And we need to translate it as well.

[texrat]

What is the best page for referencing projects? This one?

If so, should Projects be on the same tier as Proposals? Or should working groups and projects both be types of proposals?

[dawnfoster]

Originally Posted by texrat

What is the best page for referencing projects? This one?

If so, should Projects be on the same tier as Proposals? Or should working groups and pojects both be types of proposals?

Since we'll probably start to have a lot more projects soon, maybe it makes sense to create a new Projects and Proposals page that we link to off of the main page?

I'm also thinking that we probably need to rework the main page as we approach the MeeGo 1.0 launch this month. Move the proposals off to a separate page, beef up the documentation links and make sure that new community members have enough information to get started quickly. We might want to include this in Quim's bigger website update plans?