Github user chrismattmann commented on the pull request:
https://github.com/apache/climate/pull/154#issuecomment-78315995
Why this this just be an "app" that runs on top of OCW. We have examples of
this all the time. For example, in Apache OODT, we have apps that reference
config that were developed in projects at NASA JPL (for example PGE config
originally developed on the JPL Airborne Snow Observatory project; workflow
policy originally developed on NPP, etc.)
These example apps and config are simply that - example apps and config. It
seems the core of the debate here is whether or not the command line interface
here is an "app" that runs on top of OCW; or whether it's a core part of OCW.
I really have no preference here per se, but can see both sides of the
coin. I don't think this is a blocker issue. One way could simply be to make
those two properties at the end (organization and title) configurable? If they
were configurable (e.g., set by an environment variable and property file, with
sensible defaults set, even to JPL and RCMES in question), then I think it's
fine.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
