Hi Omkar,
1. Create a Jira for each. 2. Check in the code on a per Jira basis. (Makes it easier to review each change.) 3. Go through the normal review process. 4. Commit the changes. As a friendly reminder, please develop future code in the source tree instead of outside of it. :) Thanks, Gunnar From: Omkar Prabhu [mailto:[email protected]] Sent: Wednesday, March 22, 2017 11:27 AM To: [email protected] Subject: Re: 0.1 Release Readiness Hi all, I am a committer for Apache IOTA. I have the following performers that i would like to contribute: 1. Kafka 0.8 and Kafka 0.10 Subscribers 2. MQTT Publisher, Subscriber Let me know how to proceed. Thanks, Omkar On Wed, Mar 22, 2017 at 9:02 AM, Tony Faustini <[email protected] <mailto:[email protected]> > wrote: Hi Gunnar, thanks for helping on this. I wanted to encourage everyone to re-engage so we can get the release back on track. I know that some of the committers have developed performers as part of their work at Litbit. They have permission from Litbit to contribute these performers which are both useful and exemplary examples of how to write more complex performers. If you are a committer that can make such a contribution can you let the dev list know what those performers are? I assume since Litbit has an agreement with Apache and that individual committers have ICLAs in place they could contribute these performers to help others see how to write more complex performers. Let me know if my understanding is correct. Thoughts? -Tony On Feb 18, 2017, at 11:23 PM, Gunnar Tapper <[email protected] <mailto:[email protected]> > wrote: Hi, Please merge in the IOTA-38 pull request, which addresses all license issues reported by rat. >From what I see, these fixes plus Barbara's build instructions takes us 2/3rds >from the first release. Once the jar files are changed to source with build, >we should be ready to start the steps needed for the first iota release! -- Thanks, Gunnar If you think you can you can, if you think you can't you're right.
