Lexicon Community Working Group Template

Lexicon Community Lexicon Community Templates
1

Name

[Proposed name of the working group]

Representatives

  • Lexicon Community TSC: [point of contact]

The Lexicon Community TSC representative is not required to attend WG meetings, but acts as a point of contact between the two. The TSC representative is expected to:

  • Keep an eye on progress by keeping in touch with the WG lead

  • Provide updates to the TSC on the WG status

  • Recognize if the WG has stopped making progress, and either help it select a new lead or disband it

  • WG Lead: [point of contact]

The Working Group lead is not expected to be the most experienced member on the topic of the WG, but is in charge of:

  • Providing updates to the TSC representative about progress made
  • Make sure that WG progress is happening regularly, or (if it’s not happening) that there is a defined plan for when work will restart
  • CONSIDERATION: implementer role

Objective

The broad objective of the working group, in 1-3 sentences, to be expanded upon with actual deliverables in the Aims section.

Keep in mind:

  • What question is driving the working group?
  • What does success look like?

Aims & Deliverables

[Last updated: xx/xx/xx]

The aims of the working group (what it sets out to achieve), as “crisp”/well-defined as possible. These should be questions or projects that are reasonable to answer or deliver within a reasonable timeframe unit (e.g. 1-3 months). There can be multiple aims, but ideally it would be less than 5.

Deliverables do not need to be a finished product ready for production use. However, it should be clear to anyone reading this document what the expected format of the deliverable should be, and what will be included in it at minimum.

  • :cross_mark: Bad Example:

Explore location data on ATProto

  • Deliverable: A set of recommendations for location data on ATProto
  • :white_check_mark: Good Example:
    • Research current data types used by geographic applications like 1) Maps (e.g. Google Maps, Apple Maps, Open Maps) 2) Venues (e.g. Foursquare) 3) …
      • Deliverable: A document including API responses definitions for each service
      • Status: Done [Link to deliverable]
    • Create a set of geographic Lexicon that cover the following use cases 1) Addresses 2) Single-point Coordinates 3) Complex locations (e.g. venues)
      • Deliverable: A set of Lexicons in the Lexicon Community repo
      • What is this trying to solve?
      • Status: In Progress
    • Create a test AppView that uses the previous Lexicons….
      • Deliverable: A repository on a GitHub-like service
      • Status: In progress [link to repo]

Timeline

[Last updated: xx/xx/xx]

What is a good estimate of how long each Aim will take? This doesn’t have to be for all aims if it’s hard to estimate, but it should always be clear what timeline the group is targeting for its short-term work. Example:

  • Research phase: 1 month
  • Lexicon definitions: 2 months, once research is done
  • AppView Demo: 3 months, can start in parallel with research phase once we find a volunteer

Current Members

[Last updated: xx/xx/xx]

Who is currently in the WG?

Meeting Details and How to Join

[Last updated: xx/xx/xx]

  • Where: Where does the WG meet?
  • When: How often does the WG meet? Who should be reached out to if the meeting hasn’t happened in a while?
  • How: Can people join the WG? How? Where do they go to catch up?
  • Who: What is the WG looking for? What makes a good member?
    • :cross_mark: Bad: Anyone is welcome! (most people will self-select out)
    • :white_check_mark: Good: We’re looking for people who are passionate about Geographic data, or want an excuse to try building an AppView. We have a few experts in the field (more are welcome!), but we’re missing people who have built practical applications and are interested in creating test (or production) applications.

Stretch Goals and Long-term Explorations

Other explorations that the working group might want to take on long term, once the current aims are delivered or have been declared no longer relevant. Alternatively, “stretch goals” questions that would be nice to get an answer to, but that there’s currently no resources to dedicate to.

Additional Notes and References

  • Anything else
A community app lexicon
A community app lexicon