if specific to jupyterlab, then [3] makes sense. Am wondering whether that gets confusing, if it will also be used in datalab, and/or other (similar/same underlying tech but going by different names)?
On Thu, Jul 16, 2020 at 12:35 PM Pablo Estrada <[email protected]> wrote: > +1 for 3. Thanks Ning. > > On Thu, Jul 16, 2020 at 10:54 AM Kenneth Knowles <[email protected]> wrote: > >> +1 for [3] >> >> On Wed, Jul 15, 2020 at 5:47 PM Robert Bradshaw <[email protected]> >> wrote: >> >>> +1 for [3] as well. >>> >>> On Wed, Jul 15, 2020 at 5:40 PM Ahmet Altay <[email protected]> wrote: >>> > >>> > I agree with Kyle. [3] sounds more accurate. >>> > >>> > On Wed, Jul 15, 2020 at 3:00 PM Kyle Weaver <[email protected]> >>> wrote: >>> >> >>> >> I prefer [3]. >>> >> >>> >> On Tue, Jul 14, 2020 at 10:53 AM Ning Kang <[email protected]> wrote: >>> >>> >>> >>> Hi everyone, >>> >>> >>> >>> Last week, I sent a design doc and proposals in this email thread >>> about creating a JupyterLab extension for Interactive Beam. If you haven't >>> had a chance to look at it and you're interested in Interactive Beam, >>> please feel free to leave comments. >>> >>> >>> >>> Let's start a vote for the name of this extension to be used when >>> published to NPM. >>> >>> Here are some of the candidate names: >>> >>> [1] apache-beam-sidepanel >>> >>> [2] apache-beam-interactive-sidepanel >>> >>> [3] apache-beam-jupyterlab-sidepanel >>> >>> [4] <I don't like [1][2][3], my proposal is ${XXX}> >>> >>> >>> >>> >>> >>> The vote will be open for at least 72 hours. It is adopted by >>> majority approval, with at least 3 PMC affirmative votes. >>> >>> >>> >>> Thanks! >>> >>> >>> >>> Ning. >>> >>
