it is great, that you produced an overview, at the same time, I think we are reproducing a pattern, that does not help us, but sucks energy into streams, that are not core-relevant.
@Scrumteam1 could we agree on
- not deploy any other new infrastructure, that is not core to the deliverables, we currently face,
- for any not core deliverable communication infractructure focus on few, that are of high importance
- mailing list,
- keeping the protocoll infrastructures running.
As I was not so much aware of a crisis in Munich, that is mentioned in the project overview (which might be really good to have that in perspective), I wanted to have a look at the respective protocoll, ...
which is currently down, or simply not accessible anymore.
In the (yet another) new tool http://tm-tiddlers.apps.ecobytes.net/, an error message is displayed, which as some of the other tools takes time to mentain and bugfix. We simply loose so very much energy in the fixing of stuff we do not need. It is as having a big fleet of boats but just very vew captains and actually running another operation than boats.