Hey Jim, it's a great suggestion and I'm glad you brought it up. That said for logistical reasons, it would be hard to implement. Also, it isn't the primary way of communication and develop.
Our aim is to provide more communications throughout the Superset community - thus we have setup a Slack channel as the primary way of general communications and GitHub as the primary way of discussing PRs. For those in the community who'd like to join, please click here to join. our Slack channel <https://join.slack.com/t/apache-superset/shared_invite/enQtMzI4MTQ4MjQ3MzE2LTk4MWI5MjNmYzI4YmU1ZmQ2ZGUyNTdhNThjMTQwOTQ0ZWJiZDY3YzUzOGM5NzM3M2NkMzhiNTVlYjVkMjQwNDE> . Also, our plan is to work on developing a shared roadmap for the Apache Superset community so that people have full visibility into where the project is going as well as open up channels for collaboration and input. Stay tuned for more here. On Mon, Mar 12, 2018 at 7:53 AM, Jim Jagielski <j...@jagunet.com> wrote: > Is it possible to have rotating meetings? Although such > meetings can be useful, they also have the disadvantage to > disenfranchise large segments of the current and potential > community, especially as the meetings become more popular > and seen as "the" way of communicating and development. > > It is great that the notes from the meetings are posted in public, > but we also want to ensure that anyone and everyone that wants > to participate, and achieve merit, have equal opportunities to > do so. > > > On Mar 12, 2018, at 9:54 AM, Stephanie Rivera <sriv...@spotx.tv> wrote: > > > > Hi Jeff et al, > > > > I am interested in joining. We have begun to use Superset here at SpotX > and > > my data engineering team is beginning to build out features for Superset. > > We do not have anything complete enough to commit yet. Mostly the team > has > > been learning the framework and models as to determine the best way to > > implement features instep with the current codebase. > > > > Cheers, > > > > Stephanie > > > > > > *Stephanie Rivera* |* Sr. Director of Data Intelligence* > > > > 8181 Arista Place | Suite 300 | Broomfield, CO 80021 | Westminster, CO > 80020 > > ph: 303.345.6650 | cell: 970.690.6904 | spotx.tv <http://www.spotx.tv/> > > <http://www.google.com/url?q=http%3A%2F%2Fwww.spotxchange. > com%2F&sa=D&sntz=1&usg=AFrqEzdlZjMtAvYRCQByfN6D_6PjZhSbSw> > > > > <https://www.google.com/url?q=https%3A%2F%2Fdl.dropbox.com% > 2Fs%2F5se5ucpqodjsq1h%2Flinkedin.png&sa=D&sntz=1&usg= > AFrqEzdTHQrlDWywpW7VZVpwGJJdOBY-Wg> > > > > > > > > On Mon, Mar 12, 2018 at 12:43 AM, Nishant Bangarwa < > > nbanga...@hortonworks.com> wrote: > > > >> He Jeff, > >> I work in IST timezone and would love to be part of these meetings. > >> Please add me. > >> > >> Also, is it possible to have the meeting little early as it will be too > >> late for me. > >> > >> -- > >> Nishant Bangarwa > >> Hortonworks > >> (M): +91-9729200044 > >> > >> > >> > >> > >> > >> > >> On 3/12/18, 10:31 AM, "Jeff Feng" <jeff.f...@airbnb.com.INVALID> wrote: > >> > >>> Apache Superset Community, > >>> > >>> The bulk of the committers on the Superset project from Airbnb & Lyft, > as > >>> well as a few active contributors from Twitter have been meeting every > 2 > >>> weeks on Friday from 12-1:30 pm PDT at Airbnb to discuss and advance > the > >>> project. > >>> > >>> In an effort to provide transparency, we are sharing the notes from the > >>> meeting: > >>> > >>> https://docs.google.com/document/d/1R8zKt8KCcOmKEdSHQshuj2DCChSyF > >> 41ehlqkRWOUDUA/edit?usp=sharing > >>> > >>> Additionally, if you would like to join the meetings via WebEx, please > let > >>> me know and I will add you to the invite. The next meeting will be > Friday > >>> 3/23 from 12-1:30 pm PDT. > >>> > >>> Cheers, > >>> Jeff > >> > > -- *Jeff Feng* Product Lead m: (949)-610-5108 twitter: @jtfeng
