Joe, Thanks for the comments!
Slightly deviating from code consistency discussion but I think you raised some important points. I may on the glass half empty side, but being a user who witnessed many time how modularity played on other communities i am not particular excited about the prospect. I agree with Olegz comments about the benefits of the registry to code that due to licensing issues would not be able to merged into NiFi, I am excited about faster builds and selective packaging but past IMNHSO things get ugly very quickly. To be 100% transparent it is probably because I personally benefited from having my code reviewed and subjected to the always helpful input of people like yourself, Aldrin, BBende, JPercivall, Matt B, Oleg, Pierre, and the rest of the wider community. I think of how ListenSMTP evolved in two days more than I would be able to improve it in a lifetime, all thanks to a very strong core of contributors around this community. Perhaps it is because as a volunteer I have had to manage some sites build around WordPress and noticed that quite frequently a WordPress site is a see of plugin modules that as time progresses start getting outdated, turning the long term maintenance of the platform an absolute pain. And to be honest it has a healthy ecosystem around it: free modules, commercial modules, independent registries, product reviews and support forums. At this stage I would like to point out: Support forums - we need to start thinking about how we plan to manage third party plugins as shared mailing lists are woefully inadequate to do so. Even Elastic seems to have ended up using both its support forums and GH's issue pages to provide support to users. In any case, back to the original issue: I think I will second Adam's comments around not assuming the registry will help around the original issue highlighted: Consistency, Code repetition and long term support. Cheers On Thu, Feb 23, 2017 at 6:25 AM, Joe Witt <[email protected]> wrote: > more good points... > > We will need to think through/document the benefits that this > extension bazar would provide and explain the risks it also brings to > users. We should document for developers best practices in building > new components or extending existing ones and we should allow users to > socialize their findings for processors. If someone sees a processor > with 'one star' from a few users versus '4.5' from a thousand they > would get a different level of confidence. We should in general think > about how to 'mature' components in these registries and such. > > That said, I think some of the problems we're talking about we'd be > very honored and fortunate to be solving. Right now we're making it > hard to build and develop releases and slowing our agility as a > community. > > Good problems to have though! > > joe > >
