Please feel free to propose changes to the existing Apex contribution
guidelines, but prior to doing that I'd strongly recommend all community
members at least to review what already exists and to follow the
guidelines [1]. Additionally, it will be good that the community members
understand how Apache Apex contribution and release processes work, and
not simply engage in voting without engaging into discussion and
following existing guidelines. All this is an indication that except for
few individuals the community is not mature and independent.

Thank you,



"Before starting work, have a JIRA assigned to yourself. If you want to
work on a ticket that is assigned to someone else, send a courtesy
e-mail to the assignee to check if you can take it over. Confirm type,
priority and other JIRA fields (often default values are not the best fit)."

On 9/8/17 11:37, Sanjay Pujare wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB