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

How to guide a non-(fully-)conforming projects maintainer to improve the situation? #2

Open
hoijui opened this issue Dec 26, 2022 · 0 comments

Comments

@hoijui
Copy link
Owner

hoijui commented Dec 26, 2022

It just dawned on me, that I did not think about this so far.

So we have a project, we compare it to all or one specific standard,
figuring out which directories and files are used as specified, and which not,
and then ... what?

We just tell the user to fix it, without giving any clues?
How could we give clues?

Ideas:

  1. see if files/dirs outside of the standard are covered by an other standard,
    and then suggest a mapping (we do not yet have enough info for this in the spec, I think).
  2. Just look at the file extensions, see if they appear somewhere in the spec, and suggest moving the files there.
  3. see if directory names would be covered in an other location by the same spec, and suggest moving them there (could be multiple places!)
  4. NOTE: Do not duplicate work done in other tools, like unwanted files (handled by osh-tool directly).
@hoijui hoijui changed the title How to guide a non-(fully-)conforming projects maintianer to improve the situation? How to guide a non-(fully-)conforming projects maintainer to improve the situation? Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant