Starting a 2025 work plan

Last year our budget request was not met, in part because we did not have a clear plan of exactly what website improvements would be required. This is a bit of an egg and chicken problem as sorting out what was needed is often step one.

I have started a work plan document to:

  • Address some usability gaps @scottmchale has been collecting
  • Fix easy things (like Mastodon and Discourse logos)
  • Look at areas our community struggle to maintain

Thanks @jive this is a great list.
You allude to the wiki, but one potential concrete action might be link each wiki page back to the relevant website page so if people end up on the wiki, they can find the relevant page on the website.
Secondly, possibly to add to the Contact - OSGeo page, a link/email for “If you have a question about the website content, e.g. I can’t find X, or Y is wrong, please contact X” or similar.
Just a couple of quick thoughts.

Thanks, Jody.

A couple of wiki pages that I work with do have such a link back to the website, but nothing consistent. Can you add your idea to a “content” heading as I would like to see this plan cover “user experience” challenges we intend to peruse with our community.

For feedback there is a page contact in the header that details about how to contact the organization including a form.

And the footer:

The “mailing lists” link to communication which is about contacting the osgeo community.

A challenge we have is there is three stories to be told, people end different places and confused.

  1. Formal: “who is responsible” and that is the board and officers page like an org chart. This page is simple but incomplete with contact details missing for many individuals.
  2. Informal: Contact us page with is probably the good place for feedback. This page keeps getting complicated in an attempt to redirect technical questions or formal requests. I think we should keep this simple and expect we will get a constant stream of requests to redirect.
  3. Everything: communication page is the only page that should be complicated as we have many options for communication and they change over time.

The Getting Started page also starts to overlap with “communication” as inviting people in is part of it.

@scottmchale this kind of process review / optimization is more your thing? What should we do?

Thanks Jody, will do. I have requested edit access to the document.

And yes I agree - simple is better, where possible.

Wiki & website relationship session added to doc.

1 Like

Hi all,

great to work on a plan for 2025.

About the budget for 2024

Outreach 2025

I started the budget page to finalize the ideas there

1 Like

The generic “Graphics Designer support for website updates” line item did not go over well last time. In response I set up a OSGeo Website Workplan with more specific deliverables. This will need to be a mix of finical and in-kind contribution; the workplan has the details of what is needed so far.

I also filled in numbers for ?? to start the conversation.

  • marking sprint: propose colocate prior to a foss4g or regional event, use funds to assist with early accommodation for participants
  • What was our 2024 spend on collateral in support of regional events?
  • What are we spending on foss4g booth in Belem? Do we need to setup an entire booth in 2025 (or will NZ regional group have space)
  • Podcast, found email history of $250 per episode, guess $2000 or eight over the course of the year?

Jody, sorry for the delay in getting back on this.

Could we do something as simple as:

“ContactUs” page with a basic table of Position | Contact Method (form / obsfucated email) | Reasons to Contact (i.e. briefly, the types of questions or proposals that should go to this role/group).

We could still include the physical mailing address already present, leave the “general feedback form” as an option but generally push everyone to engage on the discourse forum. I wouldn’t even mind turfing the feedback form and simply having a link that takes them right to General in Discourse.

The Communications page could then be tightened significantly to only those channels in which there is two-way engagement, rather than the visitor seeking out a particular answer or person to field a specific request.

All good ideas Scott.

The system admin committee was experimenting with sending the form results straight to discourse so they could be placed into the appropriate category (which would often be general).

aside: Can you look at the Marketing Committee Budget 2025 - OSGeo where I have proposed “Implement usability improvements” as I really think we need some cross committee initiative to work on the “usability issues” you started gathering last year.

I will be in transit during the marketing meeting this Friday, and we need this document, and a solid budget request for the board. They have a face-to-face meeting on Sunday.