Re: [VOTE] Release Apache Superset (incubating) 0.37.0 based on Superset 0.37.0rc2

[Erik Ritter]

+1 binding

Erik

On Thu, Jul 16, 2020 at 3:02 AM Ville Brofeldt 
wrote:

> Hello Superset Community,
>
> This is a call for the vote to release Apache Superset
> (incubating) version 0.37.0.
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.0rc2/
>
> Git tag for the release:
> https://github.com/apache/incubator-superset/tree/0.37.0rc2
>
> The Change Log for the release:
> https://github.com/apache/incubator-superset/blob/0.37.0rc2/CHANGELOG.md
>
> The Updating instructions for the release:
> https://github.com/apache/incubator-superset/blob/0.37.0rc2/UPDATING.md
>
> public keys are available at:
>
> https://www.apache.org/dist/incubator/superset/KEYS
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Superset (Incubating) Team

Re: [CANCELLED] [VOTE] Release Apache Superset (incubating) 0.37.0 based on Superset 0.37.0rc1

[Erik Ritter]

FYI, Airbnb does Superset deploys on Wednesdays, so we should have a
superset (pun intended) of 0.37 changes tested and deployed by EOD
Wednesday.

Erik

On Mon, Jul 13, 2020 at 4:59 PM Maxime Beauchemin  wrote:

> Please link to the issue if it's out already.
>
> Also everyone(!), please keep poking holes at 0.37.0rc1 and testing it as
> much as you can. We want for as many issues as possible to be discovered
> prior to going through the trouble of assembling RC2
>
> Thanks,
>
> Max
>
> On Mon, Jul 13, 2020 at 9:51 AM Ville Brofeldt  >
> wrote:
>
> > Dear Superset Community,
> >
> > a critical regression was identified during testing of 0.37.0rc1 (thanks
> > for reporting this @bryanck!). We are therefore cancelling the vote on
> this
> > release candidate. A new vote will be started shortly after all fixes for
> > known issues on the first release candidate are finalized.
> >
> > Thanks,
> > The Apache Superset (Incubating) Team
> >
> >
> > > On 11. Jul 2020, at 11.53, Ville Brofeldt 
> > wrote:
> > >
> > > Hello Superset Community,
> > >
> > > This is a call for the vote to release Apache Superset
> > > (incubating) version 0.37.0.
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.0rc1/
> > >
> > > Git tag for the release:
> > > https://github.com/apache/incubator-superset/tree/0.37.0rc1
> > >
> > > The Change Log for the release:
> > >
> https://github.com/apache/incubator-superset/blob/0.37.0rc1/CHANGELOG.md
> > >
> > > public keys are available at:
> > >
> > > https://www.apache.org/dist/incubator/superset/KEYS
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> > > of votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thanks,
> > > The Apache Superset (Incubating) Team
> >
> >
>

Re: [VOTE] [SIP-47] modernize/facelift superset.apache.org

[Erik Ritter]

+1 (binding)

Erik

On Mon, Jun 29, 2020 at 3:34 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> I'm kicking off the vote for SIP-47
> , see the
> [DISCUSS] thread-equivalent in the GitHub issue comment.
> 
>
> As the author of the SIP, consider this a +1 from me!
>
> Max
>
> On Tue, Jun 23, 2020 at 10:08 AM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > FYI - there's a conversation considering Docusaurus as an alternative to
> > Gatsby/DocZ for superset.apache.org please chime in in the SIP issue on
> > GitHub if you have an opinion on the matter!
> >
> > I'm looking to kick off a vote as comments/input settles.
> >
> > Max
> >
> > On Wed, Jun 17, 2020 at 10:20 PM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> >> Please read and chime in here:
> >> https://github.com/apache/incubator-superset/issues/10088
> >>
> >
>

Re: FYI - Forked NVD3

[Erik Ritter]

I'm curious why we decided to fork to preset-io/nvd3 vs.
apache-superset/nvd3, but otherwise I think it makes sense. Maybe you can
add the nvd3-fork package inside the superset-ui organization (
https://www.npmjs.com/settings/superset-ui/members) so that all the
publishing permissions work automatically?

Erik

On Thu, Jun 18, 2020 at 10:23 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Just an FYI that I forked NVD3 last night.
> https://github.com/apache-superset/superset-ui/pull/615
>
> I reached out to the maintainers more than a week ago to offer help but
> they're not responsive.
> https://github.com/novus/nvd3/issues/
>
> Happy to grant access to the npm package to committers/PMC, do we have a
> publish list of all of the committers/PMC npm usernames somewhere?
>
> The primary/trunk branch had fixes we've been needing for years that never
> got released, and it's likely that we need to patch/tweak the lib in the
> future.
>
> The goal is really just to be able to patch things, clearly we're not
> investing further in NVD3, the plan being to move towards some other
> library, echarts  being a top
> contender.
>
> Max
>

Re: Newcomers and Google Season of Docs

[Erik Ritter]

Hi Gaurav,

Thanks for the thorough email with the great ideas for improving Superset!
To address your two main points:

The Google Season of Docs seems like a very worthwhile initiative to
participate in, but I wonder if we can support it sufficiently within the
Superset organization. I see that we require 2 organization administrators
and at least 2 open source mentors for the documentation writers to
participate in the program. While I suspect many people would be interested
in helping out as mentors, it's unclear what the workload required is for
the organization administrator role within the program.

Additionally, since the deadline for registration is May 4th, it might not
be possible to put together an application within this time frame. While
I'm not counting out the ability for us to participate, I'd expect that
we'd need at least 2 Commiters/PPMC members willing to own this project. I
would be happy to be one of them in a supporting role, but I think we need
someone else willing to step up and drive the application process as I'm
quite busy already this quarter. If anyone else wanted to volunteer then we
could continue this conversation in a Slack channel to try and nail down
details if we think it's worthwhile to apply.

As for improving the curve for newcomers/students, I'm all in favor for the
standard of tagging beginner issues as "good first issue". I believe we
have a bot that we can use so that anyone can add tags to issues if they
feel they're good first issues (is this correct Max?), and I'd also like to
autogenerate some issues for TypeScript conversion that would be good first
issues as well. In general, providing a good entry point for new
contributors is important to maintaining and growing the Superset
community, and I think most of us would be in favor of making it easier for
new contributors to participate.

Thanks again for your email and your ideas!
Erik Ritter

On Sat, Apr 18, 2020 at 10:07 AM Gaurav Agrawal 
wrote:

> Hi Everyone,
>
> I am Gaurav Agrawal, a student who often likes to work on superset and
> engage with the community.
>
> I am aware that superset has recently been appreciated for improving the
> docs, but I feel for further improvements and project's outreach with
> students around the world it could be really nice for it to participate in
> Google Season of Docs.
>
> It's deadline for Organizations is very near, around 4th May is the last
> date.
>
>
> As It comes under Apache so I am not completely sure about project's
> policies and procedures for the same.
>
>
> The second thing is about improving the curve for newcomers and students,
> one such great trick for doing such thing is Newcomer issues, this is a
> very popular and established way which many open source projects adopt.
> They leave many issues explicitly which are not so urgent and are newcomer
> friendly for students and newcomers by labelling them as "newcomers" or
> "good first issue" .
>
> In some cases developers even leave comments that can make solving the
> issue really easy.
>
>
> If this is a feasible option for Superset I would really like to see this
> happening so that we can have more and more people getting comfortable and
> started with it. I feel that for any open source project newcomers are a
> great and for students/newcomers themselves Open source is  a great way to
> learning a lot of things like coding, community engagement, distributed
> development workflow etc.
>
>
> Thanks for your time and consideration, hope that these ideas will be
> considered.
>
>
> Best Regards,
> Gaurav
>

Re: [VOTE] [SIP-38] Visualization plugin refactoring

[Erik Ritter]

+1 binding

Erik Ritter

On Thu, Mar 26, 2020 at 10:52 PM Grace Guo 
wrote:

> +1 binding
>
>
> Grace
>
> > On Mar 26, 2020, at 11:24 AM, Evan Rusackas  wrote:
> >
> > Superset Community,
> >
> > This is a call to vote for SIP-38: Visualization plugin refactoring
> >
> > Further details here:
> > https://github.com/apache/incubator-superset/issues/9187
> >
> > The vote will be open for at least 1 Week or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thank you!
> >
> > Evan Rusackas
> > Preset, Inc.
>
>

Re: [VOTE] [SIP-37] Proposal to implement CSS-in-JS using Emotion

[Erik Ritter]

+1 (non-binding)

Erik

On Tue, Feb 25, 2020 at 2:24 PM William Barrett  wrote:

> +1 (non-binding)
>
> Will Barrett
> Staff Software Engineer
> Preset, Inc. | https://preset.io
> On Feb 25, 2020, 2:12 PM -0800, Rob DiCiuccio , wrote:
> > +1 (non-binding)
> >
> > On Tue, Feb 25, 2020 at 10:00 AM Evan Rusackas  wrote:
> >
> > > Hello Superset Community,
> > >
> > > This is a call to vote for SIP-37 Proposal to implement CSS-in-JS using
> > > Emotion.
> > >
> > > Further details here:
> > > https://github.com/apache/incubator-superset/issues/9123
> > >
> > > The vote will be open for at least 1 Week or until the necessary number
> > > of votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thanks,
> > >
> > > Evan Rusackas
> > > Preset, Inc.
> > >
> >
> >
> > --
> >
> > *Rob DiCiuccio*
> > Director of Engineering
> > Preset | https://preset.io
>

Re: [VOTE] [SIP-39] Global Async Query Support

[Erik Ritter]

+1 (non-binding)

Erik

On Tue, Mar 10, 2020 at 3:49 PM Craig Rueda  wrote:

> +1 binding
>
> -Craig
> 
> From: Evan Rusackas 
> Sent: Tuesday, March 10, 2020 3:44 PM
> To: d...@superset.apache.org 
> Subject: [VOTE] [SIP-39] Global Async Query Support
>
> Superset Community,
>
> This is a call to vote for SIP-39: Global Async Query Support
>
> Further details here:
> https://github.com/apache/incubator-superset/issues/9190
>
> The vote will be open for at least 1 Week or until the necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thank you!
>
> Evan Rusackas
> Preset, Inc.
>

[RESULT] [VOTE] [SIP-40] Proposal for Custom Error Messages

[Erik Ritter]

Thanks to all participants, the vote for SIP-40 is now closed.

The vote PASSED with 8 +1 and 0 -1 votes:

Binding votes:
- Craig
- Ville
- Max
- Grace
- Krist

Thanks,
Erik

[VOTE] [SIP-40] Proposal for Custom Error Messages

[Erik Ritter]

Superset Community,

This is a call to vote for SIP-40: Proposal for Custom Error Messages.

Further details here:
https://github.com/apache/incubator-superset/issues/9194

The vote will be open for at least 1 Week or until the necessary number of
votes are reached.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks!
Erik

[DISCUSS] [SIP-40] Proposal for Custom Error Messages

[Erik Ritter]

Please discuss and subscribe here:
https://github.com/apache/incubator-superset/issues/9194

Thanks,
Erik

Re: Re: [VOTE] [SIP-26] Proposal for Implementing Connection Pooling for Analytics Database Connections

[Erik Ritter]

I think discussion occurring in the Github issue is ideal. However, as I
(and many others) don't often view notifications from issues being created,
we depend on the [DISCUSS] email to alert us to a new SIP being created.

Erik

On Tue, Feb 18, 2020 at 1:57 PM Brannon, Terrence
 wrote:

> It seems that discussion also occurs in the github issue itself:
> https://github.com/apache/incubator-superset/issues/8574
>
> Do you desire a single place of discussion? Or is it OK for discussion to
> occur in the github ticket as well the dev-list?
>
> -Original Message-
> From: Erik Ritter 
> Sent: Tuesday, February 18, 2020 11:23 AM
> To: dev@superset.incubator.apache.org
> Cc: d...@superset.apache.org
> Subject: [EXTERNAL] Re: [VOTE] [SIP-26] Proposal for Implementing
> Connection Pooling for Analytics Database Connections
>
> -1 (non binding)
>
> It appears that this SIP did not have a [DISCUSS] email sent to the dev
> list (see mailing list history here:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.apache.org_list.html-3Fdev-40superset.apache.org-3Alte-3D1y-3ASIP-2D26=DwIFaQ=1hIq-C3ayh4zm6RZ7m4R2A=YFv754w0-1hOQn5jCB3GpLIc7nupwqAk7x9jHnHpUVw=E8BZqaFzEwFAZ1PA2nZUTav7ln9yEwst8LDPhLoYO8M=Yxfh76rdED68gjVEHvvclUe0AEa7-Mlsq5d_DkAwpYM=
> ), so I'm concerned that everyone who wanted to provide feedback didn't get
> a chance. Could we make this the [DISCUSS] thread then revote a week from
> now?
>
> Thanks,
> Erik
>
> On Tue, Feb 18, 2020 at 7:22 AM Craig Rueda  wrote:
>
> > +1 binding
> >
> > - Craig
> >
> > > On Feb 17, 2020, at 9:46 PM, Grace Guo
> > > 
> > wrote:
> > >
> > > +1 binding
> > >
> > > - Grace
> > >
> > >> On Feb 14, 2020, at 2:41 PM, Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> > >>
> > >> Superset Community,
> > >>
> > >> This is a call to vote for SIP-26 Proposal for Implementing
> > >> Connection Pooling for Analytics Database Connections
> > >>
> > >> Further details here:
> > >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apa
> > >> che_incubator-2Dsuperset_issues_8574=DwIFaQ=1hIq-C3ayh4zm6RZ7m4
> > >> R2A=YFv754w0-1hOQn5jCB3GpLIc7nupwqAk7x9jHnHpUVw=E8BZqaFzEwFAZ1P
> > >> A2nZUTav7ln9yEwst8LDPhLoYO8M=USx_1rKoin5B7pP1oQ3gJxRAj3D7fowah4AT
> > >> veNYt1s=
> > >>
> > >> The vote will be open for at least 1 Week or until the necessary
> > >> number
> > of
> > >> votes are reached.
> > >>
> > >> Please vote accordingly:
> > >>
> > >> [ ] +1 approve
> > >> [ ] +0 no opinion
> > >> [ ] -1 disapprove with the reason
> > >>
> > >> Thanks!
> > >>
> > >> Max
> > >
> >
>
>
> U.S. BANCORP made the following annotations
> -
> Electronic Privacy Notice. This e-mail, and any attachments, contains
> information that is, or may be, covered by electronic communications
> privacy laws, and is also confidential and proprietary in nature. If you
> are not the intended recipient, please be advised that you are legally
> prohibited from retaining, using, copying, distributing, or otherwise
> disclosing this information in any manner. Instead, please reply to the
> sender that you have received this communication in error, and then
> immediately delete it. Thank you in advance for your cooperation.
>
> -
>

Re: [VOTE] [SIP-26] Proposal for Implementing Connection Pooling for Analytics Database Connections

[Erik Ritter]

-1 (non binding)

It appears that this SIP did not have a [DISCUSS] email sent to the dev
list (see mailing list history here:
https://lists.apache.org/list.html?d...@superset.apache.org:lte=1y:SIP-26),
so I'm concerned that everyone who wanted to provide feedback didn't get a
chance. Could we make this the [DISCUSS] thread then revote a week from now?

Thanks,
Erik

On Tue, Feb 18, 2020 at 7:22 AM Craig Rueda  wrote:

> +1 binding
>
> - Craig
>
> > On Feb 17, 2020, at 9:46 PM, Grace Guo 
> wrote:
> >
> > +1 binding
> >
> > - Grace
> >
> >> On Feb 14, 2020, at 2:41 PM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
> >>
> >> Superset Community,
> >>
> >> This is a call to vote for SIP-26 Proposal for Implementing Connection
> >> Pooling for Analytics Database Connections
> >>
> >> Further details here:
> >> https://github.com/apache/incubator-superset/issues/8574
> >>
> >> The vote will be open for at least 1 Week or until the necessary number
> of
> >> votes are reached.
> >>
> >> Please vote accordingly:
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove with the reason
> >>
> >> Thanks!
> >>
> >> Max
> >
>

[RESULT] [VOTE] [SIP-36] Proposal for standardizing use of TypeScript

[Erik Ritter]

Thanks to all participants, the vote for SIP-36 is now closed.

The vote PASSED with 6 +1 and 0 -1 votes:

Binding votes:
- Krist
- Craig
- Grace
- Ville
- Chris
- Max

Thanks,
Erik

[VOTE] [SIP-36] Proposal for standardizing use of TypeScript

[Erik Ritter]

Superset Community,

This is a call to vote for SIP-36: Proposal for standardizing use of
TypeScript.

Further details here:
https://github.com/apache/incubator-superset/issues/9101

The vote will be open for at least 1 Week or until the necessary number of
votes are reached.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks!
Erik

[DISCUSS] SIP-36 Proposal for standardizing use of TypeScript

[Erik Ritter]

Please discuss here:
https://github.com/apache/incubator-superset/issues/9101

Thanks!
Erik Ritter

Re: [VOTE] SIP-34 Proposal to establish a new design direction, system, and process for Superset

[Erik Ritter]

+1 (non-binding)

Excited to see this new step forward in the user experience!
Erik

On Sun, Feb 2, 2020 at 10:00 PM Ville Brofeldt 
wrote:

> +1 (binding)
>
> Ville
>
> On Mon, Feb 3, 2020 at 7:56 AM Maxime Beauchemin <
> maximebeauche...@gmail.com>
> wrote:
>
> > Superset Community,
> >
> > This is a call to vote for SIP-34: Proposal to establish a new design
> > direction, system, and process for Superset
> >
> > Further details here:
> > https://github.com/apache/incubator-superset/issues/8976
> >
> > The vote will be open for at least 1 Week or until the necessary number
> of
> > votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Best,
> >
> > Max
> >
>

Re: Proposed Meetup One-off Schedule Change

[Erik Ritter]

Looks like folks are in favor of this, so we're moving forward with holding
the next Superset Meetup at 9AM PT on Thursday, September 19th.

Thanks!
Erik

On Sun, Sep 8, 2019 at 9:10 AM Maxime Beauchemin 
wrote:

> +1
>
> On Sat, Sep 7, 2019 at 7:11 PM Daniel Gaspar  wrote:
>
> >
> >
> > On 2019/09/06 21:06:11, Erik Ritter  wrote:
> > > Hi All,
> > >
> > > As discussed in today's Superset Meetup, the current time we have
> > scheduled
> > > for meetups (every other Friday at 12PM PT) isn't very friendly to our
> > > contributors in other parts of the world. As there are a few folks from
> > > Europe that we already know of actively contributing to Superset, I'd
> > like
> > > to propose moving the next Superset Meetup to Thursday, September 19th
> at
> > > 9AM PT. This should correspond to Thursday afternoon for our European
> > > contributors and be much easier to attend than Friday nights.
> > >
> > > I'm proposing this as a one-off change to gauge interest, but we may
> want
> > > to incorporate a rotating time for meetups into the official schedule
> in
> > > the future as the community continues to grow. If consensus is positive
> > > regarding the proposed time change, then I'll follow up confirming the
> > > change.
> > >
> > > Thanks!
> > > Erik
> > >
> >
> > +1 Thanks
> >
>

Proposed Meetup One-off Schedule Change

[Erik Ritter]

Hi All,

As discussed in today's Superset Meetup, the current time we have scheduled
for meetups (every other Friday at 12PM PT) isn't very friendly to our
contributors in other parts of the world. As there are a few folks from
Europe that we already know of actively contributing to Superset, I'd like
to propose moving the next Superset Meetup to Thursday, September 19th at
9AM PT. This should correspond to Thursday afternoon for our European
contributors and be much easier to attend than Friday nights.

I'm proposing this as a one-off change to gauge interest, but we may want
to incorporate a rotating time for meetups into the official schedule in
the future as the community continues to grow. If consensus is positive
regarding the proposed time change, then I'll follow up confirming the
change.

Thanks!
Erik

Re: [ANNOUNCE] Please welcome new Superset committer Erik Ritter

[Erik Ritter]

Hi All,

I'm excited to continue contributing to the Superset project in the role of
committer! I've enjoyed working with all of you on the project thus far and
look forward to writing (and reviewing!) many more PRs.

Thanks,
Erik

On Thu, Aug 29, 2019 at 9:49 AM Grace Guo 
wrote:

> Hi folks!
>I'm very pleased to announce that the Superset PMC has voted Erik
> Ritter to be a committer. Since late May this year, he has closed a few
> pull requests (
> https://github.com/apache/incubator-superset/pulls?q=is%3Apr+author%3Aetr2460+is%3Aclosed
> <
> https://github.com/apache/incubator-superset/pulls?q=is:pr+author:etr2460+is:closed>),
> covering bug fixes, chores, new features. Erik has done incredible work in
> improving Superset’s documentation, issues and community involvement.
>
> Please join me in welcoming Erik Ritter!
>
> Thanks,
>
> Grace
> on behalf of the Superset PMC
>
>

Re: [VOTE] PR #4725 - Publishing Dashboards

[Erik Ritter]

+1 from me!

I think some of the delay for LGTM-ing this PR came from ensuring the db
migration would let us launch the feature without any change to the current
user experience. Also, the cognitive overhead from catching up on >50
comments for context. Regardless, I think that it's an awesome feature, and
I'm really grateful for the unit tests too!

Erik

On Mon, Jul 8, 2019 at 10:13 AM Tresdon Jones 
wrote:

> Very glad to see such outstanding support for this feature!
>
> I must say I'm a bit confused as to what and where the grievances /
> blockers are because I'm not seeing them on the PR or on this thread. Are
> they happening on some synchronous communication channel that I'm not
> looped in on? I would like to address these issues and make this work for
> as many folks as possible but that is hard when I do not see the objections
> raised. Some clarification / ideas about next steps would be very much
> appreciated.
>
> Best always,
> Tresdon
>
>
> On Mon, Jul 8, 2019 at 1:32 AM Matthew Mutee  wrote:
>
> > +1. Would be useful to us.
> >
> > Regards,
> > Matthew M. Mutiso
> >
> >
> >
> > On Tue, 2 Jul 2019 at 20:32, Tresdon Jones 
> > wrote:
> >
> > > Hello all,
> > >
> > > I want to gather some sentiment around this PR which allows users to
> > > communicate whether their dashboards are for general consumption or for
> > > their own purposes (work to be done before general consumption,
> esoteric
> > > dashboards / charts, or "this is a test" type dashboards). It aims to
> > > declutter the main area for listing dashboards by filtering on this
> > status.
> > >
> > > https://github.com/apache/incubator-superset/pull/4725
> > >
> > >
> > > This PR will introduce a few changes to different parts of the
> > application:
> > >
> > > DB changes:
> > >
> > >1. A DB migration will add the boolean field "published" to the
> > >dashboards table in superset.db. It will set all dashboards to
> > > published on
> > >migration so that all dashboards remain visible.
> > >
> > > UI changes:
> > >
> > >1. On listing dashboards through the "dashboards" link at the top of
> > the
> > >application there will be a new sortable column called "published".
> > >2. Dashboards will have a badge at the top of them next to the
> favstar
> > >communicating the status of it (Draft or Published) *unless* the
> > >dashboard is already published and the viewing user has no
> permissions
> > > to
> > >change it.
> > >3. The aforementioned badge can be clicked to toggle the status of
> the
> > >dashboard or it can be edited through the dashboard CRUD view.
> > >
> > >
> > >
> > > I would very much appreciate a response of +1 if this would be a useful
> > and
> > > welcome feature in your environment and a -1 with grievances if there
> are
> > > objections regarding – this would provide exigency for putting a
> feature
> > > flag in front of this functionality. Many thanks in advance for your
> > > participation!
> > >
> > > Best always,
> > > Tresdon
> > >
> >
>