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

[FEATURE] please add "How to" review section to wiki #242

Open
brandonnodnarb opened this issue Mar 8, 2021 · 4 comments
Open

[FEATURE] please add "How to" review section to wiki #242

brandonnodnarb opened this issue Mar 8, 2021 · 4 comments
Milestone

Comments

@brandonnodnarb
Copy link
Member

What is the criteria for a successful PR review?
From a more practical perspective, what are the actual steps?

@pbuttigieg
Copy link
Collaborator

pbuttigieg commented Mar 8, 2021

We're also noting that some classes, such as estuary have axioms that can be reasoned over. Is there a preferred reasoner to use when checking logic?

@pbuttigieg
Copy link
Collaborator

pbuttigieg commented Mar 8, 2021

The general guidance should also include an obsolescence workflow (xref #192)

@rduerr
Copy link
Contributor

rduerr commented Mar 8, 2021

Group discussion suggests using all reasoners (e.g., elk, pellet, Hermit, Fact).

@rduerr
Copy link
Contributor

rduerr commented Mar 8, 2021

Group discussion suggests that the solution to #192 be used in general to deal with obsolescence.

@brandonnodnarb brandonnodnarb added this to the 3.6.0 milestone Jul 14, 2022
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

3 participants