Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
This page is a (currently, I am sure, woefully incomplete) "Mozilla Activity Map". The aim is to get a snapshot of the full range of activities undertaken under the umbrella of the Mozilla project. This will be used as input into an effort in 2013 to revitalize Mozilla's community governance structures. The result may or may not look like the current "module" system, but fundamentally it will be "making people responsible for stuff", and to do that, we want to start by working out what "stuff" there is. | This page is a (currently, I am sure, woefully incomplete) "Mozilla Activity Map". The aim is to get a snapshot of the full range of activities undertaken under the umbrella of the Mozilla project. This will be used as input into an effort in 2013 to revitalize Mozilla's community governance structures. The result may or may not look like the current "module" system, but fundamentally it will be "making people responsible for stuff", and to do that, we want to start by working out what "stuff" there is. | ||
The aim is for this page to describe what Mozilla does at approximately a "module" level of granularity. However, err on the side of more detail if unsure. | The aim is for this page to describe what Mozilla does at approximately a "module" level of granularity. However, err on the side of more detail if unsure. There are doubtless many ways you could split the Mozilla project's activities into chunks. Nothing here is set in stone; in particular, this is not a list of "future modules". Completeness is more important than organizational method; high-level completeness is more important than low-level. Some of this data comes from legacy systems; if you are sure we are no longer doing a thing, remove it. If you think things should be organized differently, use caution and look for consensus with others working in that area. | ||
There are doubtless many ways you could split the Mozilla project's activities into chunks. Nothing here is set in stone; in particular, this is not a list of "future modules". Completeness is more important than organizational method; high-level completeness is more important than low-level. Some of this data comes from legacy systems; if you are sure we are no longer doing a thing, remove it. If you think things should be organized differently, use caution and look for consensus with others working in that area. | |||
Please include only activities, not the names of people who do (or who you think should) own them. | Please include only activities, not the names of people who do (or who you think should) own them. |