#3278: Consistent category / subcategory / presentation
----------------------+------------------------
Reporter: jive | Owner: jive
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin | Resolution:
Keywords: |
----------------------+------------------------
Changes (by jive):
* owner: sac-tickets@… => jive
Old description:
Oh boy - quick proposal here to confirm with marketing committee.
Okay now we have some projects to learn from:
- top-level projects
- local chapters, committees, organizing committees, etc ..
Slugs are short and consistent:
- top-level: project name with dashes `qgis`, `geoserver, `geonetwork`
- top-level: initiatives `local-chapters`, `committees`, `community-
projects`, `geoforall`, ...
- top-level: "initiatives" to hold short term activities like `gsoc`,
`elections`, `travel-grant`, ...
- standard sub-categories for `user` / `developer`
- standard sub-category slugs for language: `user-fr`, `user-it`, `user-
es`
- category is singular: `user`, `developer`
Mailing list:
- formed by chaining together the slugs above: `pgrouting-developer`,
`geonetwork-developer`
Send email address to create a topic:
- match with slug and mailing list above: `geoserver-
user@discourse.osgeo.org`
- optional: maintain similar to previous lists server: `pgrouting-
dev@discourse.osgeo.org`
Group (match the slug above):
- group is plural for a group of people: `geoserver-users`, `pgrouting-
dev`
- by default user categories do not need a group (they are public
outreach)
- by default developer categories require joining a group to post a
topic, and joining the group will default to watching the category
- private groups are by invite only, and require being added to the group
in order to view (or post) a topic.
Title is the full text:
- Whatever is needed here, often this is the complete (internationalized)
text: `GeoServer User`, `pgRouting Developer`, `GeoInquietos`, `Usuario
de QGIS`
Logos and badges:
- Often groups have their own logo
- For projects a single logo on the top-level is often sufficient
- badges can be fun
Category colors:
- dark osgeo green for the committees
- dark osgeo green for osgeo projects (they are committees also)
- dark osgeo green for official osgeo chapters (although most have
icons)
- light osgeo green for osgeo community projects
- light osgeo green for groups and meetups
- foss4g red (from the ribbon) for events
- blue for private categories
New description:
Oh boy - quick proposal here to confirm with marketing committee.
Okay now we have some projects to learn from:
- top-level projects
- local chapters, committees, organizing committees, etc ..
Slugs are short and consistent:
- top-level: project name with dashes `qgis`, `geoserver, `geonetwork`
- top-level: initiatives `local-chapters`, `committees`, `community-
projects`, `geoforall`, ...
- top-level: "initiatives" to hold short term activities like `gsoc`,
`elections`, `travel-grant`, ...
- standard sub-categories for `user` / `developer`
- standard sub-category slugs for language: `user-fr`, `user-it`, `user-
es`
- category is singular: `user`, `developer`
Mailing list:
- formed by chaining together the slugs above: `pgrouting-developer`,
`geonetwork-developer`
Send email address to create a topic:
- match with slug and mailing list above: `geoserver-
user@discourse.osgeo.org`
- optional: maintain similar to previous lists server: `pgrouting-
dev@discourse.osgeo.org`
Group:
- group is plural for a group of people: `geoserver-users`
- group has a character limit: `geonetwork-devel`
- by default user categories do not need a group (they are public
outreach)
- by default developer categories require joining a group to post a topic,
and joining the group will default to watching the category.
- private groups are by invite only, and require being added to the group
in order to view (or post) a topic. Examples: `geoserver-admin`,
`pgrouting-psc`
- optional: maintain similar to previous list server: `pgrouting-dev`
Title is the full text:
- Whatever is needed here, often this is the complete (internationalized)
text: `GeoServer User`, `pgRouting Developer`, `GeoInquietos`, `Usuario de
QGIS`
Logos and badges:
- Often groups have their own logo
- For projects a single logo on the top-level is often sufficient
- badges can be fun for groups
Category color recommendation:
- dark osgeo green for the committees
- dark osgeo green for OSGeo projects (they are committees also)
- dark osgeo green for official osgeo chapters (although most have icons)
- light osgeo green for osgeo community projects
- light osgeo green for groups and meetups
- foss4g red (from the ribbon) for events
- blue for private categories
--
--
Ticket URL: <#3278 (Consistent category / subcategory / presentation) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.