Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insufficient guidance to allow collaboration #3

Open
eritain opened this issue Sep 5, 2016 · 4 comments
Open

Insufficient guidance to allow collaboration #3

eritain opened this issue Sep 5, 2016 · 4 comments

Comments

@eritain
Copy link

eritain commented Sep 5, 2016

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

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.

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

@cdchapman
Copy link
Member

Привіт, шановний друже! Давно так! Я радiю за те, що ти мене знайшов.

I am so excited to hear from you at this particular time, I'd love to tell you more, but I'm going to bed and will tell you tomorrow. 😄

@cdchapman
Copy link
Member

@eritain, I am so happy that you are sympathetic to the cause and want to pitch in. We are trying to create tooling that is natural to humans (and machines). You're right, I have not done very well at describing why we are using specifications to reach these high-minded goals. Part of creating the aforementioned tooling includes creating specifications so that the way that we structure the knowledge design process is open for anyone to participate.

I have updated the project README to explain more about the repo, and how to contribute. I'm sure I've left something out, so if anything is lacking clarity, let me know.

While I have a good feel for where we need to go, really, there is a lot that is underspecified and even undertheorized right now. I am preparing to start a the first project that will drive the development and adoption of research cases, so I have needed to turn my attention to ironing out some of my questions with modeling this approach to doing research. Do you have any experience in the area of modeling discourse and argumentation?

@eritain
Copy link
Author

eritain commented Oct 3, 2016

Well, I model explanatory text. Argumentation and particularly discourse are more complex and not my specialty, but I think I know who to ask and where to look.

@cdchapman
Copy link
Member

That's great @eritain. Do you have something in mind already for how would you like to help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants