Replies: 2 comments 1 reply
-
Initial discussion within the Resources Working Group, we thought that articles, blog posts, etc. would already be incorporated in other working groups efforts to create documents and deliverables. For example, the Metrics group could leverage the tools catalog for identifying software, but as far as defining metrics, identifying tutorials, etc. those could show up within their own documents. Similarly, the Professional working group might already plan to identify things like job boards, professional podcasts, newsletters, etc. aligned with professional development, but those wouldn't be in the same place as metrics. Unless all resources are combined into a single collection, then we just need to decide on expanding the scope of the Resources working group to include this. Thoughts? |
Beta Was this translation helpful? Give feedback.
-
Thanks for this question. My initial reaction/thoughts to this -- I would propose that we scope and define 'resources' to refer to resources/tools used by a DevRel practitioner in their day-to-day job (e.g., persona library, tools catalog, and event directory catalog/library). I would avoid expanding 'resources' to be all information from the Foundation, or you risk mixing the focus/charter of the working group and not accomplishing the primary goal. If we need someone to focus on a wiki or knowledge base, I would propose we form a new working group or program group that focuses on gathering/publishing the information from across the Foundation. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The original themes for this working group explicitly called out resources like personas, events, and tools.
Where would a resource such as a blog post titled "What is Developer Relations" fit in?
5 votes ·
Beta Was this translation helpful? Give feedback.
All reactions