Idea: Internal tooling WG

[nanorepublica]

The framing of this idea is the typical role that an IT admin would play in a company, who would allow the use/denial of certain services/tools.

This WG would probably be one that would be around for a short while if it gets started and then close until needed again.

Currently from a just Communications perspective, the community uses the following tools:

• Trac
• Forum
• GitHub
• Discord
• Slack
• Mailing lists
• IRC

There would be other categories to consider as well.

While they all have their specific differences and unique nuances, there might be an opportunity for streamlining the tools we use so more people are gathered on a single platform and where appropriate align what is available on each tool (eg forum categories to Discord categories)

The WG would make proposals for wider community acceptance as well as help to either action the required changes or nudge those with privileges to do so.

If there is any budget is spent on these tools, the WG could consider any savings that might be made by consolidating any tooling.

Finally, the WG could look to research the full potential of each tool we use as a community through automations or bots etc.

[thibaudcolas]

I like the idea! Not sure about it as a working group, but it’d certainly be good to have a more cohesive plan on what each tool is for and coordinate what’s available in different tools so they complement one-another rather than just causing fragmentation.

[thibaudcolas]

@nanorepublica is this now effectively going ahead with #23?

[nanorepublica]

I would say in partially. The example I gave above is around communication and #23 is currently dealing with a subset of the platforms listed.

I would assume there are other areas (eg issue tracking - has been a recent topic of discussion). Perhaps this issue is a not a single WG idea, but a mechanism or lens to identify other WG's or Teams that could be formed in future?