Confirmed users, Bureaucrats and Sysops emeriti
1,737
edits
| Line 1: | Line 1: | ||
[[Website_CMS|Website CMS]] » Meeting Notes | [[Website_CMS|Website CMS]] » Meeting Notes | ||
==January | ==January 17th== | ||
''' | '''Notes''' ([http://people.mozilla.org/~clouserw/logs/cms/20070117.log full transcript]) | ||
* How does the review process work? ie. what is the workflow from a writer modifying a page to it going live? | * How does the review process work? ie. what is the workflow from a writer modifying a page to it going live? | ||
** [http://people.mozilla.org/~clouserw/docs/cms/user_workflow.png A first draft] | ** [http://people.mozilla.org/~clouserw/docs/cms/user_workflow.png A first draft] | ||
* | * Can a leader approve their own changes? | ||
** | ** Yes. Smaller locales may not have multiple leaders to approve eachother's changes. | ||
** Everyone has permission to everything. We add an optional "security | |||
* Are PHP header/footer includes manually included in new files? | |||
** Yes. Pages are somewhat unique at this point, and automatic includes aren't part of the requirements. | |||
* Do we want to support file locking? | |||
** Yes. When a file is edited, it's locked until it is saved (or the lock is removed by an admin). When a file is saved, it's committed to SVN. | |||
* How should permissions be implemented? | |||
** Writers and leaders can only see/modify languages they know. | |||
** Everyone has permission to everything in the locale(s) they know. We add an optional "security" tag. If the file is tagged with that flag, no one can see it unless they are tagged with the same tag. We can do the same with a "marketing" group... | |||
* When we redid m.c's in-product pages we brought in design advice way to late. When is the proper time to do that? How long will it take? Who is the contact for that? | * When we redid m.c's in-product pages we brought in design advice way to late. When is the proper time to do that? How long will it take? Who is the contact for that? | ||
** Sgarrity is our design guy. | |||
** When framework is setup, sgarrity will use his prettification wand on html | |||
** Usability and simplicity are the focus here | |||
*(from email) | *(from email) This is software for the foundation: | ||
** Core Layer: CakePHP | ** Core Layer: CakePHP | ||
** File Management: SVN | ** File Management: SVN | ||
| Line 20: | Line 32: | ||
** User Management: CakePHP | ** User Management: CakePHP | ||
* Milestones/timeline/todo list [https://mozilla.grouphub.com/projects/809545/ setup] | * Milestones/timeline/todo list [https://mozilla.grouphub.com/projects/809545/ setup] | ||
** This is all still up for modifications, of course | ** This is all still up for modifications, of course | ||