Skip to content

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

@hoijui

Description

@hoijui

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions