You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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).
Just look at the file extensions, see if they appear somewhere in the spec, and suggest moving the files there.
see if directory names would be covered in an other location by the same spec, and suggest moving them there (could be multiple places!)
NOTE: Do not duplicate work done in other tools, like unwanted files (handled by osh-tool directly).
The text was updated successfully, but these errors were encountered:
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
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:
and then suggest a mapping (we do not yet have enough info for this in the spec, I think).
The text was updated successfully, but these errors were encountered: