This is an option. I have a few concerns about it:
- There will be a lot of repos and it will be messy to manage and it might
be harder for users to find it. I am expecting at least more than ten
(different services times different languages).
- There will be some duplicated code such as
Hi, all:
Can it also be one of the options to even have separate repo for each type
of spouts? The reasons it is worth considering are:
1. Allow each spout to evolve and release in different pace because each is
technically driven by external source software. For example, the community
may need
+Siming
On Tue, Jan 15, 2019 at 11:35 PM Ning Wang wrote:
> Hi, all,
>
> A few of us (Spencer, Saikat, Siming, Karthik, Josh, Sree) discussed today
> in our general slack channel that we should have spouts code somewhere so
> that people can reuse them (spouts are highly reusable in general)
