Opened 3 months ago

Last modified 2 months ago

#3278 new task

Consistent category / subcategory / presentation

Reported by: jive Owned by: jive
Priority: normal Milestone: Unplanned
Component: SysAdmin Keywords:
Cc:

Description (last modified by jive)

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

Change History (10)

comment:1 by jive, 3 months ago

Description: modified (diff)

comment:2 by jive, 3 months ago

For discussion:

  • Would projects prefer to to use their own branding color? Perhaps - it can be an option (rather than dark osgeo green).
  • What about discussion of other foss4g software, like leaflet? Do we wish to offer "forum" to these folks, like we did for the list server, or can we ask that they join the OSGeo community initiative first?

comment:3 by jive, 3 months ago

Description: modified (diff)

comment:4 by jive, 3 months ago

Description: modified (diff)

comment:5 by jive, 3 months ago

For discussion: top-level category for "Feedback" to collect sub-categories:

  • "OSGeo Website" Q&A feedback where topics can be answered as solved
  • "OSGeo Forum Feedback" Q&A feedback where topics can be answered as solved

comment:6 by jive, 3 months ago

Description: modified (diff)

comment:7 by Nick Bearman, 3 months ago

Thanks Jody - this all looks good.

I would lean to being flexible and the option of having a different colour sounds good.

I would say yes to offer the facility to other foss4g software, like Leaflet, etc.

comment:8 by jive, 3 months ago

We are getting some good feedback:

  • provide clear recommendations ("defaults") for projects rather than ask questions
  • projects may wish to adopt their own convention for subcategories (as was done for QGIS)
  • surprise: we could not use geonetwork-developers as a group name as it was too many characters; so geonetwork-devel was used.

Updating the ticket.

comment:9 by jive, 3 months ago

Description: modified (diff)
Owner: changed from sac-tickets@… to jive

comment:10 by jive, 2 months ago

There is some experimenting in muting / unmuting categories happening here: https://discourse.osgeo.org/t/should-we-set-mute-categories-by-default/110412/1

Based on these results, and the proposal above we should create a check-list or procedure or something.

Note: See TracTickets for help on using tickets.