Remove "Holding ourselves accountable"

We should, of course, hold ourselves accountable, but the conventions described in this section never took root and seem unlikely to.

An alternative to accepting this MR is to commit to using the structure written here.

I will merge after spotting a few approvals. This does not require an official Board Vote.

working-conventions.md

@@ -47,36 +47,6 @@ We therefore adopt the following working conventions:
     1. Discussion (details, analysis, and motivation)
     1. Call to action (please vote, specific deadline, etc.)
 
-## Holding ourselves accountable
-
-It frequently happens during meetings, Slack conversations, email threads, etc., that one
-of us steps up to complete a task. But then, sadly, the task gets lost. We are busy people,
-and many of us are volunteers, and so this is understandable. However, we should work
-together to keep each other accountable. If a task is left undone, this should be clear to all,
-in case someone else wants to pick up the task. Or, perhaps we decide that the task is better
-left undone: this may be a reasonable choice, but it's vastly better to choose not to complete
-a task than simply to overlook it.
-
-Accordingly, in order to support internal task management, we have a separate `internal`
-repo whose [Issues](https://gitlab.haskell.org/hf/internal/-/issues) tracker is used to track
-internal commitments. Here are our practices:
-
-1. When an HF person (that is, board member, employee, or volunteer) offers to perform
-   a task worth tracking, someone records this task by creating an [Issue](https://gitlab.haskell.org/hf/internal/-/issues)
-   on the `internal` repo.
-
-2. The Issue is assigned to the person who has offered to complete the task.
-
-3. Issue descriptions can be terse, in order so that the creation can be done quickly.
-
-4. When the task is complete, the person completing the task closes the Issue.
-
-5. It is acceptable for anyone to ping the person an Issue is assigned to, in
-   order to remind that person to complete the task, ask for help, put down the task,
-   or start a conversation about why the task is not worth doing.
-
-6. We will periodically, in Board meetings, review open Issues so that we do not lose tasks.
-
 ## Sub-groups
 
 The HF encompasses many people, and it can be challenging for large groups of people