On Mar 17, 2010, at 2:15 PM, Chad Spears wrote: > Marcin Sołtysiak wrote:
> I like this. Design/art could be added under community when needed. Off > topic could be placed at the bottom of the top level forums if that is > more suitable. I prefer device type over company/product. > > (This is my interpretation, the original was posted by Marcin Soltysiak.) > > * Community > + General <- announcements, releases, gatherings & events etc > + Users <= Voice of Customers, usage discussions etc. EU perspective > + Design/Art > * Development > + Core I don't see core development moving out of the mailing list and into a forum. I also don't want those conversations happening in both places. > + Applications > + L10N <= may require further divisin if language teams find it suitable > * Devices > + Mobile > + Netbook > + (the other device types listed individually) > * Off-Topic > We need to be careful not to over-define the structure initially. I've made this mistake in the past, and we ended up with several forums that were sparsely populated. It's easier to go with a very simple forum structure and grow organically as we need to separate the conversations. By creating too much separation initially, it just becomes more difficult to manage and hard to follow the conversations. I still think we're better off with something like this (no subforums until we decide that we need them): Community Using MeeGo Application development Devices Off-Topic This would allow us to grow as we need it rather than trying to guess what we are going to need. At this point, we're very early in the project, and at least some of our assumptions about what people want to talk about will probably be wrong. Dawn _______________________________________________ Meego-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
