Skip to content

Insufficient guidance to allow collaboration #3

@eritain

Description

@eritain

Привіт! Давно не побачилися.

I am profoundly sympathetic to the governing concept: "Research should be re-democratized through clarity, context, and collaboration. It is a natural and necessary human activity made unnatural and inaccessible by the lack of good tooling." But I cannot find a public description of the goals, constraints, judgments, and speculations that connect that concept down to the concrete activity of writing specifications.

I'd love to pitch in, and I have a little experience in knowledge engineering and spec authoring, but I can't unless you'll throw out a little more information about what you're specifying and why.

I note that the Github issue mechanism itself is used by other projects to host the multi-stranded "thinking aloud" and "thinking together" process that eventually produces implementable consensus designs. It seems well suited for it, in fact.

Всього доброго!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions