Mozilla.com:Meeting Notes/09-Dec-2005: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Zachlipton (talk | contribs) (restore page) |
||
Line 1: | Line 1: | ||
There: dria, beltzner, zak greant, steven garrity, polvi, pkim | |||
We met this morning to review updates for mozilla.com and mozilla.org. Here are the notes from our talk. | |||
-pkim | |||
---- | |||
*Adding awards to mozilla.com | |||
**Steven will try a couple of different treatments for this next week. | |||
*Redirects | |||
**Steven will review next week his list of links with sysadmins. | |||
**We need a list of pointers from mozilla.org content to new mozilla.com content (i.e., where we'd like .org content that is being taken down to point to on .com) | |||
*About content on .org | |||
**pkim will drive review of existing about content and work up a proposal for addressing migration to .com | |||
*Press center on .org | |||
**pkim will drive spec of new press center on .com | |||
**zak: look at setting up a private server that can push to a public server. Publish releases to a directory on the private server, then have a script push out to public via SFTP. | |||
**Should we leave an archive of old releases on .org? | |||
*Thunderbird 1.5 .com pages | |||
**Steven has this on the radar. pkim, steven and mscott to manage new content for Tbird 1.5 launch. | |||
*Process for web site updates | |||
**pkim and steven to collaborate on a document that outlines steps to pushing live new web content. Hopefully before the 2.0 launch starts in earnest. | |||
*Security content on .com | |||
**pkim to drive spec of security content for .com. | |||
*Support/How to content | |||
**What set of content do we want to move or redirect back to .org support/how-to content from .com? | |||
**beltzner: Involve David Tenser | |||
**dria: if we build "how to content", make it interactive | |||
*Steven's list of things that we didn't get to | |||
**Steven will post a list of web stuff that we didn't have time to do for the 1.5 launch, that we should attend to now. | |||
*mozilla.org | |||
**Who should own the site content moving forward? | |||
**zak: make it clear on the various sites: what the sites are for, and who they're for. | |||
*Localization strategy for .com | |||
**Raised as an issue on website-drivers@mozilla.org alias this morning | |||
**Part of a bigger discussion of how Mozcorp works with int'l affiliates | |||
**Should have more input from today's l10n meeting at Mozcorp. | |||
*Webmaster for .com? | |||
**pkim to review with cbeard and justin | |||
*Tone of content on .com | |||
**beltzner: we need a style guide for .com content - language, etc. | |||
*Foundation | |||
**zak: can we get a catalog of all the sites we own? | |||
**polvi: we have [[over 100 domains]] | |||
**polvi to send out domain list to this group for human review | |||
**zak: you can improve the way issues are handled by: | |||
***posting issues/discussions publicly | |||
***posting bugs for all our site changes | |||
***communication around changes to planet and mozillazine | |||
**zak: key things to get across with mozillafoundation.org: | |||
***who we are | |||
***what is our mandate | |||
***what can people expect from the foundation | |||
***Need to enable people to raise issues/track issues - be open/transparent |
Latest revision as of 21:34, 15 November 2006
There: dria, beltzner, zak greant, steven garrity, polvi, pkim
We met this morning to review updates for mozilla.com and mozilla.org. Here are the notes from our talk.
-pkim
- Adding awards to mozilla.com
- Steven will try a couple of different treatments for this next week.
- Redirects
- Steven will review next week his list of links with sysadmins.
- We need a list of pointers from mozilla.org content to new mozilla.com content (i.e., where we'd like .org content that is being taken down to point to on .com)
- About content on .org
- pkim will drive review of existing about content and work up a proposal for addressing migration to .com
- Press center on .org
- pkim will drive spec of new press center on .com
- zak: look at setting up a private server that can push to a public server. Publish releases to a directory on the private server, then have a script push out to public via SFTP.
- Should we leave an archive of old releases on .org?
- Thunderbird 1.5 .com pages
- Steven has this on the radar. pkim, steven and mscott to manage new content for Tbird 1.5 launch.
- Process for web site updates
- pkim and steven to collaborate on a document that outlines steps to pushing live new web content. Hopefully before the 2.0 launch starts in earnest.
- Security content on .com
- pkim to drive spec of security content for .com.
- Support/How to content
- What set of content do we want to move or redirect back to .org support/how-to content from .com?
- beltzner: Involve David Tenser
- dria: if we build "how to content", make it interactive
- Steven's list of things that we didn't get to
- Steven will post a list of web stuff that we didn't have time to do for the 1.5 launch, that we should attend to now.
- mozilla.org
- Who should own the site content moving forward?
- zak: make it clear on the various sites: what the sites are for, and who they're for.
- Localization strategy for .com
- Raised as an issue on website-drivers@mozilla.org alias this morning
- Part of a bigger discussion of how Mozcorp works with int'l affiliates
- Should have more input from today's l10n meeting at Mozcorp.
- Webmaster for .com?
- pkim to review with cbeard and justin
- Tone of content on .com
- beltzner: we need a style guide for .com content - language, etc.
- Foundation
- zak: can we get a catalog of all the sites we own?
- polvi: we have over 100 domains
- polvi to send out domain list to this group for human review
- zak: you can improve the way issues are handled by:
- posting issues/discussions publicly
- posting bugs for all our site changes
- communication around changes to planet and mozillazine
- zak: key things to get across with mozillafoundation.org:
- who we are
- what is our mandate
- what can people expect from the foundation
- Need to enable people to raise issues/track issues - be open/transparent