Skip to content

Proposal for Tags that organize the Pyowa Handbook #2

@Automatez

Description

@Automatez

Note - main categories have a (none) as no item should be tagged that generally, use a subtopic tag
One thought - do we add the topics at the front of tags for better grouping - like gov_pep or ops_scmtgs?

  1. (none) Governance/Compliance
    a. [pep] PEP (Pyowa Enhancement Proposal)
    b. [sc] Steering Committee
    c. [finance] Financials (probably just a placeholder, can start to build out in case we ever need it)
  2. (none) Operations
    a. [mmmtgs] Monthly Member Meetings
    b. [scmtgs] Weekly Steering Committee Meetings
    c. [roles] Roles/Duties (probably a placeholder)
    d. [sponsors] Sponsors (how we promote them, how we handle donations, etc)
    e. (none) Efforts (not sure if this goes here or somewhere else)
    i. [community] Engaging the existing Python community in Iowa
    ii. [jobs] Promoting job listings (and eventually job seekers?)
    iii. [growth] Growing Python use in organizations in Iowa
    iv. (none) Future effort ideas (student education? tying into national programs? projects (donate time) driven by members?)
  3. (none) Community Presence
    a. (none) Interactive - public posting from Pyowa but also allows for public response and interaction
    i. [discord] Discord
    ii. [li] LinkedIn
    iii. [bluesky] BlueSky
    b. (none) Managed - also publically viewable Pyowa content, but no direct public response available here
    i. [sessionize] Sessionize
    ii. [website] Website
    iii. [github] Github
    iv. [youtube] YouTube
    v. [meetup] MeetUp?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions