Create PR for 2022 goals discussion/review #163

vmbrasseur · 2022-01-13T19:09:47Z

Move the goals.md doc to a PR so we can more easily comment on things at a line level.

Silly me, I only changed one line so that's all that appeared in the diff. These are all no-op changes, purely to drop the proposed goals into the diff for ease of commenting.

vmbrasseur · 2022-01-13T19:23:01Z

goals.md

@@ -9,29 +9,29 @@ Based on this, we would like to bring the goals to the TODO Group for review and

 The goals will be revisited and updated yearly.

-## 2022
+## [PROPOSED] 2022


As I review the proposed 2022 goals, one thing that strikes me is that the audience for the goals is not clear. It reads more like a list of internal LF goals for the group than something that's drafted by and for the community itself. For instance, several of the items on the list ("Host first OSPOCon in APAC", "Improve and refresh TODO Website, increase traffic by 20%") are things over which the community has little control or input (aside, perhaps, in content).

Are we setting goals here for the LF staff? For the community? For us? All of the above? I'd like to have this clarified so we can track accountability more easily.

IMHO, I think goals.md should reflect a balance between all parties involved that helps to scale and sustain the TODO project. This includes TODO SC, TODO General Members, TODO Community, and LF staff goals.

having separate goals (lf and todo sc) but in the same document)

vmbrasseur · 2022-01-13T19:37:33Z

goals.md

-* Build out and run OSPO Survey 2022
-* Create and publish a OSPO Maturity Model
+- Release at least 6 new OSPO case studies
+- Launch 6 new OSPO guides


6 feels overly ambitious. 4?

We are having more folks interested in OSPOs this year + we are working on a contribution guideline and a process to make more clear and easier these contributions 👍 I like the idea to have an ambitious goal and take corrective actions by the end of the year if necessary, rather than reduce the number without trying it first 🙂

focus more on quality (not quantity). How to encourage people to submit case studies and ease contribution

Goal suggestion for Steering Committee: Make it easier to produce high quality TODO group guides and case studies

vmbrasseur · 2022-01-13T19:38:25Z

goals.md

-* Create and publish a OSPO Maturity Model
+- Release at least 6 new OSPO case studies
+- Launch 6 new OSPO guides
+- Host 12 OSPOlogy sessions


This leaves no wiggle room for holidays (mid-year and end of year).

Would it make more sense to set this to 10?

Goal suggestion for Steering Committee: Encourage more active participation in OSPOlogy sessions

reduce to 8

potential SC Goal: Encourage more active participation in OSPOlogy

Can we get updates on attendance #s and perhaps the following:

Is registration requirement a barrier?

Is it very well attended - do we need more time zone options?

do we ask for feedback about the session?

Sure! I can share the data from previous sessions and send it to the SC ML @ashleywolf 👍

vmbrasseur · 2022-01-13T19:40:11Z

goals.md

+- Launch 6 new OSPO guides
+- Host 12 OSPOlogy sessions
+- Build out and run OSPO Survey 2022
+- Create and publish a OSPO Maturity Model


This would largely duplicate the existing efforts of OSPO Alliance/OW2's Good Governance Initiative. It's probably better to collaborate on/contribute to those rather than reinventing the wheel.

@vmbrasseur I think the GGI from OW2 is a very useful resource for the open source community, but my impression is that the message and audience are more for individuals and organizations starting and advancing in open source and not necessarily running an OSPO in the organization.

On the other hand, there's some context that should be added to this topic: This idea comes from a bigger issue coming from the community that is the lack of structure, and context when looking at the wide diversity of TODO resources. (TODO Resources are super useful, but a recurrent feedback I get at meetings, surveys, or email threads is that there is no order nor a defined path for the OSPO Community to understand where, when, and how to use those resources) + There is a WIP OSPO research study with involvement from a bunch of OSPOs that has been under development since June - July AFAIK. Maybe @caniszczyk could add more details.

ospo survey: lf goal

ospo maturity model: lf goal

vmbrasseur · 2022-01-13T20:12:09Z

goals.md

-* Cultivate relationships with other OSPO adjacent communities like CHAOSS
-* Grow OSPO Ambassadors by 
+- Grow TODO membership by 20%
+- Cultivate relationships with other OSPO adjacent communities like CHAOSS


Could we please get more specific here? As-is, this goal is vague. Which communities exactly would we like to collaborate with and what does success look like for those collaborations?

I would also like to see more documentation about what those other communities get from the TODO Group. It looks like a logo exchange, which isn't particularly compelling for a lot of communities (like CHAOSS, for example).

This comes from the TODO community's request from last year about collaborating with other communities that add value to OSPOs in different ways, but do not (necessarily) have an OSPO so they are not able to apply for a TODO General Membership (e.g because they are open source communities, for instance).

Creating an OSPO Associates program is the action item that came from this need about cultivating relationships with other communities (in order to enhance cross-community collaboration + improve communication related to TODO's project efforts with other communities and vice versa).

Right now the documented requirements are somehow vague. I would suggest providing feedback to these requirements to better define this idea: https://github.com/todogroup/governance/blob/main/OSPO-Associate-Program.md

cultivate relationships with other communities: SC goal

vmbrasseur · 2022-01-13T20:12:44Z

goals.md

-* Grow OSPO Ambassadors by 
+- Grow TODO membership by 20%
+- Cultivate relationships with other OSPO adjacent communities like CHAOSS
+- Grow OSPO Ambassadors by 


by…?

Also: OSPO Ambassadors? We have those?

I think this is OSPO Associates (cc @caniszczyk to double-check). See my previous comment #163 (comment)

Right now there are three different interested communities where we have been exchanging some sync meetings to find ways to collaborate: OpenChain, FINOS, and LF Energy

delete this goal

vmbrasseur · 2022-01-13T20:15:09Z

goals.md


-## 3. Create value for all members
+## 3 Create value for all members


Re: @itprofjacobs & @tsteenbe's comments & related discussion at the 2022-01-11 call, we need to have a closer look at what "all members" means here. There may be different cohorts depending upon experience & maturity. The TODO Group value proposition for early stage OSPOs will be different than for OSPOs who have been around for a while.

vmbrasseur · 2022-01-13T20:16:09Z

goals.md

-* Host first OSPOCon in APAC
-* Break down silos and enhance communication across channels (slack, mailing lists, Social media)
+- Run at least 2 surveys to get feedback, >80% satisfaction
+- Improve and refresh TODO Website, increase traffic by 20%


Before we commit to this, I'd like more information about what constitutes a 20% increase. Is this realistic? A stretch goal? (which is to say: what's the current traffic?)

The goal "Improve and refresh TODO Website" comes from complaints from some community folks about the current website UX and UI. The website is old, resources are hard to find, some resources are outdated, contribution guidelines are not clear, it doesn't show the existing TODO Chapters such as the EU Chapter, and is not SEO optimized.

I think the 20% indicator is just a way to make a goal measurable and more specific. IMHO and overall speaking, if the website is updated and improves its UI and UX, we can ease access to OSPO resources and improve shareability to the broader community, breaking down silos between the TODO General Members and OSPO Community.

+1 to improving and refreshing the website to make it easier to use and help people quickly find the information they need. But, the 20% traffic increase feels a bit arbitrary. It seems to me that if the same numbers of people went to the website, but they found it more useful, that would still be a win.

Based on @geekygirldawn's last comment maybe this is more a topic of finding a way to measure visitor's engagement and not traffic. If that's the case, I see one possible approach:

Analyze specific page bounce rates (e.g number of people leaving todogroup.org/guides after visiting the page). If we get the bounce rate, we can easily get its inverse, the "engagement rate" (people that actually engage in the website)

Cons: TODO Website currently runs on netlify and uses Netlify Analytics (which does not show this metric, AFAIK).

delete increase traffic by 20%

vmbrasseur · 2022-01-13T20:16:48Z

goals.md

+- Run at least 2 surveys to get feedback, >80% satisfaction
+- Improve and refresh TODO Website, increase traffic by 20%
+- Host at least 2 OSPOCons
+- Host first OSPOCon in APAC


These two aren't really TODO Group goals, since the community doesn't really get any say into them. They're LF goals, aren't they?

AFAIK, Yes, OSPOCon events directly involve LF at some point, because of event logistics and promotion (cc @caniszczyk )

vmbrasseur · 2022-01-13T20:17:26Z

goals.md

+- Improve and refresh TODO Website, increase traffic by 20%
+- Host at least 2 OSPOCons
+- Host first OSPOCon in APAC
+- Break down silos and enhance communication across channels (slack, mailing lists, Social media)


This is vague and difficult to action. What is the desired outcome here? What does success look like?

This topic refers to two kinds of silos that TODO has:

Silos related with geographical location: Improve communication and reach out to TODO Community and contributors across different regions ( e.g not only having community meetings in an AMER or EMEA friendly timezone, but also in APAC; have multiple Touchpoint meetings in different hours or being organized by local moderators)

Silos related to organization's restrictions: For instance, some folks in the community can't access to TODO slack channel because of internal platform restrictions. That's why implementing actions that allow all the community to stay up to date about OSPO Discussions, TODO news, resources, and where to search for contribution guidelines are needed. This might include, improving website documentation, promoting OSPONews, posting frequent Community news and reminders in the TODO Mailing list, replicating slack discussions at OSPO Discussions GH channel, and more.

two separate goals (SC goals):

Increase geographical availability

Asses TODO tooling

As discussed during the last SC meeting, I've updated the SC goals structure dividing them between SC and LF Staff goals.

change strategic goals structure

anajsana · 2022-02-07T15:33:00Z

➡️ This is how the preview file looks like after making the discussed changes during the SC meeting

anajsana · 2022-02-10T10:30:26Z

Merging. If someone would like to make changes to the content (e.g reword a specific goal, or list specific actions for each of the goals) please open a new PR 👍

Create PR for discussion/review

50d1f11

Move the goals.md doc to a PR so we can more easily comment on things at a line level.

vmbrasseur requested a review from a team as a code owner January 13, 2022 19:09

vmbrasseur mentioned this pull request Jan 13, 2022

Review Strategic goals 2022 by Steering Committee #160

Closed

1 task

vmbrasseur changed the title ~~Create PR for discussion/review~~ Create PR for 2022 goals discussion/review Jan 13, 2022

Expose all 2022 goals in the PR

0bba470

Silly me, I only changed one line so that's all that appeared in the diff. These are all no-op changes, purely to drop the proposed goals into the diff for ease of commenting.

vmbrasseur commented Jan 13, 2022

View reviewed changes

anajsana added 3 commits February 4, 2022 13:09

change strategic goals structure

5ed4487

As discussed during the last SC meeting, I've updated the SC goals structure dividing them between SC and LF Staff goals.

make wording changes to the survey goal

1ea13c9

Merge pull request #179 from todogroup/anajsana-patch-7

9051866

change strategic goals structure

anajsana merged commit 6d5faa9 into main Feb 10, 2022

justaugustus deleted the issue-160 branch November 5, 2022 01:24


		## 3. Create value for all members
		## 3 Create value for all members

Create PR for 2022 goals discussion/review #163

Create PR for 2022 goals discussion/review #163

Conversation

vmbrasseur commented Jan 13, 2022

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ashleywolf Feb 2, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

anajsana Jan 17, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

anajsana Jan 14, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

anajsana commented Feb 7, 2022

anajsana commented Feb 10, 2022

ashleywolf Feb 2, 2022 •

edited

Loading

anajsana Jan 17, 2022 •

edited

Loading

anajsana Jan 14, 2022 •

edited

Loading