Hi Madhan,

It took some time but now we finished all of the required steps and you should 
see our contribution in Jira: https://issues.apache.org/jira/browse/ATLAS-4246
Can you confirm, that you can review this ticket and the available patch now?

Kind regards,
Aileen

-----Original Message-----
From: Madhan Neethiraj <mad...@apache.org> 
Sent: Dienstag, 9. März 2021 17:44
To: dev@atlas.apache.org
Cc: Jakob, Marcel (HPE DACH Data Practice) <marcel.ja...@hpe.com>; Geisse, 
Dennis <dennis.gei...@hpe.com>; Toleikis, Aileen <aileen.tolei...@hpe.com>
Subject: Re: Apache Atlas Commit Proposal

Hi Marcel Jakob, Dennis Geisse, Aileen Toleikis,

Thank you for reaching out on contributing to Apache Atlas.

Here are the steps to contribute to Apache Atlas:
  1. File a JIRA with details of the use case and issues faced (if relevant) at 
https://issues.apache.org/jira  (project = ATLAS)
  2. Create a review at https://reviews.apache.org/  (repository = atlas), with 
the patch containing the changes. Make sure to add 'atlas' group in the 
reviewers list.
  3. Update JIRA with the link to the review, and update status to 
PATCH_AVAILABLE

Apache Atlas developers will then be able to review the patch, and commit.

Hope this helps. Looking forward to your contributions.

Thanks,
Madhan

On 3/1/21, 11:50 PM, "Toleikis, Aileen" <aileen.tolei...@hpe.com> wrote:

    Hi Apache Atlas community,

    In a recent project we work with a Confluent Community Kafka cluster.
    We had to make some adjustments to Atlas to make it work with an
    "external" Kafka Cluster and an external Zookeeper.  Additionally we
    wanted to include the Confluent Community Schema Registry with its
    attributes into Atlas.

    Since the code is working for us, as a next step we wanted to
    contribute our developments to provide other users these capabilities.
    This is our first time contributing to Apache opensource we would love
    to get guidance on this!  Could you please assist in committing our
    code?  What would be prior steps? Do we need to run some special
    checks?

    Should we just file a JIRA with our problem statement and then produce
    a pull request?

    We are currently working to allow testing of this code without needing
    to do full integration testing.

    We are grateful for any advice or help!
    Thank you in Advance,

    Marcel Jakob, Dennis Geisse & Aileen Toleikis


Reply via email to