This idea is in the category of United Software Development: Problem Everywhere in a software development process knowledge is continuously created. Depending on size and complexity of the project a lot of that knowledge is a) either lost or forgotten over time as it wasn’t created in the most appropriate location, or b) increases the workload of the project team to transfer to a better location and review + reformulate / reformat. Examples are: Intricate discussions on an issue in th...

This idea is in the category of United Software Development I posted earlier on Lemmy and possible (far?) future roadmap item for the FedeProxy project, that aims to decentralize code forges (they are driving force behind the initiative to Federate Gitea).

In the post I outline an idea to easily gather knowledge that is generated in a software development project, as it is created in many different places, and ease the burden of maintenance. The use case outlined is an application of another idea, namely to Federate the Murmurations Protocol.

    • smallcirclesOPM
      1·
      3 years ago

      I did not know about these bots. A ‘problem’ I often see is that an issue after it is closed (or even while still open) is enormously long, filled with good discussion. Lot of that discussion is not on the mark for that issue, but still potentially relevant to the project. Also if a project is under-documented, you have many people explainging aspects of it to others. In that case you also might want the option as maintainer to mark the text and send it to a documentation queue for review and inclusion.