What is a tool?

[j12y]

An objective of the resource aggregation working group is to create a directory of software and tools that are of value to practitioners.

This raises some questions.

What is considered a tool?

My interpretation of the expectation is that this includes any product that assists in the activities of Developer Relations. Should this include things such as backpack, microphones, lighting setups, travel accessories, computer monitors, etc?

Are there limits to how deep a tool directory should go into a category?

Is the directory exhaustive or is there a point of diminishing returns when it is no longer providing value. For example, is a programming language like Python a software tool used by DevRel? Probably, but should that mean also listing PHP, COBOL, and LISP? Or should none of them be listed because it is too niche or too general.

This may work itself out organically.

Is a name and description enough?

If I'm looking for a piece of software, is it important to know when it is Windows-only or does not work on Linux?

Is identification of the list enough to prompt additional exploration from official sources without additional filtering criteria?

How much detail is needed in order to achieve additional value for the community over just "googling" it?

Is DevRel practitioner feedback and reviews part of the value?

What I find valuable about the #tools-i-use channel of the DevRel Collective Slack was not just the identification of tools and software related to a problem, but some general guidance on why the tool was good or not.

This is highly subjective.

Schema

The schema could easily grow to include details that may change over time too:

• tool name
• description
• company
• problem category (travel, working remotely, live streaming, podcasting, crm, newsletters, content distribution, etc.)
• operating system
• features
• pros / cons
• price range / budget

[j12y]

There is already a good aggregation of resources here:
https://github.com/devrelcollective/awesome-devrel

What does this working group aim to do different or that adds substantive value to what has already been done by many contributors?

Also see #13