wwlwpd

Sounds good; I will produce an audit with this information plus some initial recommendations.

@jasonfleming one thing that I think will make this difficult to some degree is that we use `run.properties` as a communication medium - i.e., any time a called script reads...

Quick list of `run.properties` that contain `$USER`: ``` config.file operator path.adcircdir path.scriptdir path.inputdir path.outputdir path.scratchdir monitoring.rmqmessaging.script monitoring.rmqmessaging.scriptrp monitoring.rmqmessaging.ncohome monitoring.logging.file.syslog post.file.sshkey archive.path.archivebase archive.path.archivedir path.rundir path.cycledir path.scenariodir monitoring.logging.file.cyclelog monitoring.logging.file.scenariolog asgs.path.advisdir asgs.path.stormdir path.advisdir...

@jasonfleming and @carolakaiser - can you both look at the above list of `run.properties` values, and tell me if redacting them (e.g., sanitizing `$USER` and email addresses) would break anything...

I agree, maybe we can slate this for post-season?

I think the best result out of this issue is to: 1. have a set of best practices for minimizing personal information on public files/locations 2. some standard developer practices...

Yeah, this is a very hard to define target. I think doing it by file (like `run.properties`) and just making it a best effort is all we can do.

I added `run.properties` as the target for this, maybe once this is done we can identify another file to clean up.

~~@jasonfleming - let's talk, what about an approach like this - [f976675](https://github.com/StormSurgeLive/asgs/commit/f976675072161bdb1c6427e0bcb9c2788dff42d9), where we just expose the settings in the `mesh_defaults.sh`?~~ disregard

> Ok I think this is working except for defining the ADCIRC version support for various features. Let's discuss next time we meet. @jasonfleming remind me, was there anything actionable...