I would vote for something like Niclas proposed. Much clearer than having yet another product / component name...
For instance, PLC4X DSP, PLC4X Signal Processor, or something what clearly describes in one or two words / shortcuts what the component does. See Kafka and its ecosystem: Kafka Connect, Kafka Streams, Confluent Schema Registry, Confluent Rest Proxy, Confluent Control Center, etc... Kai On Sun, Sep 15, 2019 at 9:05 AM Julian Feinauer < j.feina...@pragmaticminds.de> wrote: > Hi, > > I was thinking about naming and came up with ideas like... > > - trace4j > - dsp4j (digital signal processing, that is) > - pluse (as we detect pulses and stuff) > - oscilloscope <-- I quite like that, it fits quite well as we really look > into signals > > What are thoughts on those? > > J > > Am 08.09.19, 22:38 schrieb "Niclas Hedhman" <nic...@hedhman.org>: > > peanut gallery; I would recommend a descriptive name, in format of > "PLC4X > Abc", rather than a stand-alone name. Somewhere in the future, you may > have > a dozen of these and one wouldn't know where to start looking. > > Cheers > Niclas > > On Mon, Sep 9, 2019 at 4:51 AM Julian Feinauer < > j.feina...@pragmaticminds.de> > wrote: > > > Hi all, > > > > I just discussed (off-list) with Justin the next steps needed. > > They are > > > > * fill out software grant (pm) > > * Start IP clearance vote on incubator list (JF) > > * Gather ICLA from all contributors of CRUNCH > > > > Parallel I’d like to start a discuss on how we should call it as > PLC4X > > subproject. > > > > Any ideas or suggestions? > > > > Julian > > > > > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > > >
