Github user chrismattmann commented on the pull request:
https://github.com/apache/climate/pull/154#issuecomment-78403668
@MJJoyce your statement about "endorsed" by the project has to do with
endorsement by the PMC. The PMC doesn't endorse anything here at the ASF. They
do "sign" releases, and vet them, but it's very much driven by someone who
makes release as the RM, and then a VOTE of the PMC in which there are more +1s
than -1s, etc.
People scratch their itches in open source code all the time. @MBoustani is
a PMC member of the project here, and he has scratched an itch by developing
this CLI which to date, besides the UI, is the only example that we really have
of not having to know Python or to be a Python programmer to take advantage of
the stuff provided by OCW.
Your comment about not calling this RCMES, b/c this project is called
Apache OCW, is a fine one to make, but not considering the fact that in the
*Apache OCW* proposal it is clear that the code was seeded by RCMES as a
project and there is provenance there. We don't want to cause confusion and if
this were a consumer or business/industry market, then we might about naming
and branding from a product perspective. But we're talking about code and a
name from the progenitors of the project which involves not really competition,
but people that are also working on the code at JPL too.
If @MBoustani thinks RCMES is a good name to call this, and he has
developed a neat app that illustrates OCW, and we have right now RCMES as
pretty much the flagship application that uses OCW why wouldn't we want to show
an affinity and affiliation here between the names?
I think technically the way to get it done (so that other institutions can
use OCW and call it UCLA Climate Power Tool; or IITM's Super Climate
Diagnoster, etc.) is to make those two parameters in the CLI, institution and
project name, configurable as env vars. The default values for those can be set
to OCW and Apache; then downstream, we can easily have a quick .properties or
Python .ini file that sets this to NASA JPL and RCMES in that case. I think
that would satisfy everything.
---
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.
---
