RaphaelAdewale commented on issue #10753: URL: https://github.com/apache/seatunnel/issues/10753#issuecomment-4676714556
> Thanks [@SaiPande](https://github.com/SaiPande) and [@RaphaelAdewale](https://github.com/RaphaelAdewale) — both are still open areas, but they should be tracked a little differently. > > * [@SaiPande](https://github.com/SaiPande): for **Syslog**, please continue the claim in [[Feature][syslog-connector] can seatunnel support a syslog-connector #2649](https://github.com/apache/seatunnel/issues/2649) as well, since this umbrella tracker already points to that dedicated issue for the actual connector work. That will keep the implementation discussion in one place. > * [@RaphaelAdewale](https://github.com/RaphaelAdewale): for **Splunk**, this umbrella issue is the right coordination entry, and the connector is still open for a PR. > > For the smoothest first contribution, please keep the first PR as one small and reviewable slice on the `dev` branch: > > 1. make it explicit whether you are doing **Source** first, **Sink** first, or a very small shared base plus one side > 2. include the minimal docs / example config needed for that first slice > 3. link the PR back to this tracker (and for Syslog, also back to [[Feature][syslog-connector] can seatunnel support a syslog-connector #2649](https://github.com/apache/seatunnel/issues/2649)) > > For first-time contributors, a narrow vertical slice is usually the fastest way through review. If you want, you can leave one short follow-up comment with the exact V1 scope before opening the PR. That is dully noted @DanielLeens. I will keep you updated. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
