Github user MJJoyce commented on the pull request:
https://github.com/apache/climate/pull/154#issuecomment-78415145
@chrismattmann thank you for that last paragraph. You've said exactly what
I've been trying to say without being nearly as confusing as I'm being =D
@MBoustani First off. This is great and thank you for putting it. My point
above regarding naming was that this is a great tool that I think other people
will want to use. It's a great way to get people to use OCW without needing to
write Python. While having this as a RCMES branded example of the toolkit is
great, I feel like it's far more powerful to have this be listed as a generic
OCW tool that is configurable for anyone to use. So we can host it at JPL and
call it the RCMES CLI and we can host it at UCLA JIFRESSE and call it the UCLA
CLI, etc. That was really what I was trying to get across with the naming
concerns. Let's not make this seem like JPL's tool that is an example of the
toolkit being used. Instead, let's make this the generic toolkit CLI that
anyone can use and that is can easily be configured for your organization to
use as well. Hopefully that clears up the point I was trying make (admittedly I
did a poor).
+1 to @chrismattmann's recommendation regarding making the settings
configurable. I think that's the perfect solution.
---
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.
---
