Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Just to follow up, the author of that page/image has made some updates to remove confusion about ownership, clarify branding, and add appropriate linking. I’ve emailed trademarks@ + the private list, to confirm whether or not we can consider the matter resolved. Thanks, -e- Evan Rusackas ( he | him ) Frontend Lead Preset | preset.io On Oct 14, 2020, 11:49 PM -0700, Justin Mclean , wrote: > Hi, > > > I’ve stuck to the basic directions in [2] of sending a “friendly” email > > (AND Slack message, in our case), in private, to the community member. > > That is certainly the best first step with dealing with something like this. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, > I’ve stuck to the basic directions in [2] of sending a “friendly” email (AND > Slack message, in our case), in private, to the community member. That is certainly the best first step with dealing with something like this. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi Justin, As per the PPMC responsibilities for brand stewardship [1], I’ve reviewed the steps for reporting potential misuse of ASF marks [2]. This particular instance probably falls under the umbrella of “obvious problems”, or at least I’ll assume so, since it was brought up by a mentor. I’ve reached out directly to the person responsible for the DockerHub image(s). The guide for contacting third parties [3] seems to suggest a "Software Product Infringement” template be used, but I’m not seeing a link to that anywhere. Based on the other templates I DO see, which seem a little… legal… I’ve stuck to the basic directions in [2] of sending a “friendly” email (AND Slack message, in our case), in private, to the community member. This outreach only happened quite recently, so I’ll give them a little time to react before taking further steps involving trademarks@ and private@. TL;DR: I’ve reached out, and I’ll keep you posted! Thanks, -e- [1] https://www.apache.org/foundation/marks/responsibility#responsible [2] http://www.apache.org/foundation/marks/reporting.html#pmcs [3] https://www.apache.org/foundation/marks/templates/ Evan Rusackas ( he | him ) Frontend Lead Preset | preset.io On Oct 14, 2020, 9:34 PM -0700, general@incubator.apache.org, wrote: > > Those three seem fine. They are fine but there is still an issue with > branding/trademarks and some docker images. What is the PPMC doing about this?
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, > I hope that everyone is now subscribed after the last round of nagging, but I > still have no way to confirm who’s not on the list. Daniel Gaspar is still not subscribed, but all others have, I don’t see that as a blocker to graduation. > After taking this up with our mentors, we’ve seemingly landed on an agreed > plan to address this by making the following adjustments/commitments: > > • Announcing the meetings in advance (this just happened on the dev@ list, > actually) > • Rotating the time slot to be more accommodating to other regions > • Increasing grow community/public attendance > • Sharing out the notes to the list after each meeting > • Sharing out video of the meetings after they transpire, whenever available > • Committing to not making any community-wide decisions in these meetings That sounds like a better approach. I still think it is better to use asynchronous communication on the mailing and not have these sort of meetings. > Let me/us know if there are further actions needed on any of these three > points Those three seem fine. They are fine but there is still an issue with branding/trademarks and some docker images. What is the PPMC doing about this? Thanks, Justin
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi Justin, I wanted to follow up on those three concerns and how we’re addressing them, in hopes that we’re able to move forward with the graduation process. On Oct 9, 2020, 12:12 AM -0700, Justin Mclean , wrote: > > (1) PPMC members not subscribed to the private list. I hope that everyone is now subscribed after the last round of nagging, but I still have no way to confirm who’s not on the list. Some people were having some technical issue subscribing via email (it seems to silently fail for some reason), but for what it’s worth, the Whimsy Signup UI [1] worked for those who are aware they're having this issue. If being on the list is a dealbreaker, please send me/us a current list and we’ll either continue to work with them, or take them off the roster. > > (2) Synchronous Meetings > > The biggest issue I see is the this is not being announced or discussed on > the mailing list and what is discussed in those meetings is not brought back > to the list. Having these external discussions is a huge barrier to people > who want to contribute to the project but for one reason or another (e.g. > time zones or day job or other commitments) can’t attend that meeting. By > having these you are basically limiting people who can attend to full time > employees paid to work on the project in a similar time zone, that excludes a > lot of people.This was mentioned as an issue in a previous board report but > nothing seems to have been done about it. One of the core values of Apache > projects is that discussions need to be asynchronous and inclusive. It would > be helpful if your mentors added their thoughts about this. After taking this up with our mentors, we’ve seemingly landed on an agreed plan to address this by making the following adjustments/commitments: • Announcing the meetings in advance (this just happened on the dev@ list, actually) • Rotating the time slot to be more accommodating to other regions • Increasing grow community/public attendance • Sharing out the notes to the list after each meeting • Sharing out video of the meetings after they transpire, whenever available • Committing to not making any community-wide decisions in these meetings > > (3) Links to other companies This has been discussed on the private list with our mentors, and while the thread with tradema...@apache.org remains unanswered, we’ve gone ahead with your advice and removed the links from the logos on the website for now. [2] Let me/us know if there are further actions needed on any of these three points, but I’m hoping we’re closer to earning your +1 on the VOTE thread! Thanks again, [1] https://whimsy.apache.org/committers/subscribe [2] http://superset.incubator.apache.org/ Evan Rusackas ( he | him ) Frontend Lead Preset | preset.io
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, > (1) PPMC members not subscribed to the private list. > > I have no way to see who is or isn’t on the list Whimsey should show that to PMC member with a * next to their name. Currnly still not subscribed are: Aaron Suddjian Bogdan Kyryliuk Chris Williams Daniel Gaspar Serena Jiang There is also a ralme...@gmail.com subscribed who doesn’t seem to be on your PPMC, they probably should be removed. > (2) Synchronous Meetings The biggest issue I see is the this is not being announced or discussed on the mailing list and what is discussed in those meetings is not brought back to the list. Having these external discussions is a huge barrier to people who want to contribute to the project but for one reason or another (e.g. time zones or day job or other commitments) can’t attend that meeting. By having these you are basically limiting people who can attend to full time employees paid to work on the project in a similar time zone, that excludes a lot of people.This was mentioned as an issue in a previous board report but nothing seems to have been done about it. One of the core values of Apache projects is that discussions need to be asynchronous and inclusive. It would be helpful if your mentors added their thoughts about this. > (3) Links to other companies > > I’ve reached out to our mentors (via the private@ list, in case we can get > any other input as well) on the issue, and hope to hear back soon about how > other TLPs (e.g. Drill, Airflow, Beam, and surely more), have surmounted this > logo usage issue. I’ve seen this handled in a few ways, either it put on a page other than the main page or they don’t link to those companies. also be aware that some companies are more protective of their trademarks and you may even need to get permission to use their logos in this way. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, These change all look fine. So it seem the only outstanding things (unless any IPMC member brings up something else) are: - PPMC member not subscribe to the private list - How to deal with the synchronous meetings - Links to other companies on your front page. Have one of your mentors (or any ASF member in your project) take a look at this thread on the incubator private list [1]. Thanks, Justin 1. https://lists.apache.org/thread.html/r68df1ac8c2895071ca81e5183ad181891c98bbe1e379488653568327%40%3Cprivate.incubator.apache.org%3E - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi Justin, I’ve attempted to address your concerns about the website (https://superset.incubator.apache.org/), point by point, inline below. Much of this is addressed in new PRs merged in today. [I’m incrementing your annotation numbering for clarity]: Best part is, the Whimsy site check [8] no longer shows any red :) [5] https://github.com/apache/incubator-superset/pull/11133 [6] https://github.com/apache/incubator-superset/pull/11132 [7] https://github.com/apache/incubator-superset/pull/11140 [8] https://whimsy.apache.org/pods/project/superset Thanks, Evan Rusackas ( he | him ) Frontend Lead Preset | preset.io On Sep 30, 2020, 11:41 PM -0700, Justin Mclean , wrote: > Hi, > > I think there's a couple of minor thing that need some minor > fixes/clarification. > > I was looking at your website and can’t see where I can download the released > versions form the Apache mirrors [1]. (This relates to CD10 in the maturity > model and the distribution part.) This has be added in a new PR [5]. > I assume the main way people install Apache eSuperset is via PyPi [4]. It > would be good to update the logo and information on that page and make it > clearer that Superset is an Apache project. (This releases to LC50 in the > maturity model) PyPi is probably not be the primary way people install superset. It’s hard to say (we don’t have stats), but I would suspect GitHub is the main source. The logo has been updated via a new PR [6]. Should be all set now. > It looks like your web set is missing a few of the required links as well [2] > [3] These should also be addressed now via a newly merged pull request [5][7] > You might also want to check with trademarks about the links on the front > pages to other commercial products and companies as usually this is not > allowed. Some of these companies would also have conditions around how their > trademarks can be used. We’ve included a blanket statement about trademarks in the footer of the website (following the pattern of other Apache TLPs). We hope this is sufficient, but let us know if you feel that’s not the case. This is also in one of the new PRs [5]. > Thanks, > Justin > > 1. https://dist.apache.org/repos/dist/release/incubator/superset/ > 2. https://whimsy.apache.org/pods/project/superset > 3. https://incubator.apache.org/guides/sites.html > 4. https://pypi.org/project/apache-superset/ > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org Thank you!
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, > I’m not too surprised to hear that one or more people haven’t sent emails to > the list… most of the engagement happens on the GitHub repo and on Slack. > With help from our mentor, I’ve already reached out to folks who were > erroneously not on the private list (for varied reasons), and I believe most > have signed up already since then. Whimsy shows that 19 of 22 PPMC members > are on the list presently, but I have no way of seeing which three are not. Currently the following people are not subscribed: Aaron Suddjian Beto Dealmeida Bogdan Kyryliuk Chris Williams Daniel Gaspar Michelle Thomas Serena Jiang > All that having been said, we’ve reviewed the list and feel these PPMC > members are indeed active within the community and/or in good standing with > the community. That sounds fine to me. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, > Thanks for bringing up your concern here. The synchronous meeting you > describe does have an agenda with meeting minutes/notes [1], which are open > to the public, and was previously shared on the dev list [2] I note those in attendance are listed by company affiliation, contributors should act as individuals not what company they are affiliated with. The last time it was shared on the list was more than a year ago, this does't seem open and transparent communication that an ASF project needs to follow. These discussions need to be brought back to the mailing they need so they can involve the wider community especially those who can’t attend due to other commitments, including their day job or time zone issues. > From this point forward, we will make it clear that all are invited, and we > will share out the notes after each meeting. A better solution might be to not have them at all and have the discussion asynchronous on the mailing list. This this can be inconvenient it it give better value to the whole community not just those who know about and can attend those meetings. > Let us know if this assuages the concern, and if not, we’ll address further. It still a concern IMO, and I see it was noted as a concern in a board report, but doesn’t seem to have been addressed. I can see improvements in this project in a lot of other areas. It would be good to hear from other IPMC members and your mentors on this subject. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi Justin, We’re happy to move forward with all the people on the list (including our mentors, of course), and are under the assumption that they want to continue their involvement. If we need to explicitly contact them about moving from PPMC to PMC, we have not taken this action, and can do so. I’m not too surprised to hear that one or more people haven’t sent emails to the list… most of the engagement happens on the GitHub repo and on Slack. With help from our mentor, I’ve already reached out to folks who were erroneously not on the private list (for varied reasons), and I believe most have signed up already since then. Whimsy shows that 19 of 22 PPMC members are on the list presently, but I have no way of seeing which three are not. All that having been said, we’ve reviewed the list and feel these PPMC members are indeed active within the community and/or in good standing with the community. Thanks, -e- Evan Rusackas ( he | him ) Frontend Lead Preset | preset.io On Sep 30, 2020, 11:53 PM -0700, Justin Mclean , wrote: > Hi, > > With your proposed PMC list I can see a number of the people mentioned don’t > seem to be active and a number are not signed up to the project private > mailing list. A quick check found at least one who looks to have not sent a > single email to the mailing list during the entire incubation project. Has > the project asked if these people want to be on the new PMC? When a projects > graduates it sometimes a good idea to reduce the new PMC list to people who > are active in the project and prepared to take on responsibility of being PMC > members. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi Justin, Thanks for bringing up your concern here. The synchronous meeting you describe does have an agenda with meeting minutes/notes [1], which are open to the public, and was previously shared on the dev list [2] From this point forward, we will make it clear that all are invited, and we will share out the notes after each meeting. We can remind people in the community more periodically that these meetings take place and they are welcome to take part. That includes CCing the dev@ list on this email. It may also be worth noting that much of the community discussion stemming from any meeting most often takes place on GitHub (in SIPs and PRs/Issues) and on public channels in the Superset Slack [3]. Let us know if this assuages the concern, and if not, we’ll address further. [1] https://docs.google.com/document/d/1xRLqmUn-G7WiPe8qZnfuvbrYHZ1jmk9aSv9Bhjis2tg/edit [2] https://lists.apache.org/thread.html/65f3891f5fefa85e5ef4c8d23605c003accdc76a9b1bb023a5dd6595%40%3Cdev.superset.apache.org%3E [3] https://join.slack.com/t/apache-superset/shared_invite/zt-g8lpruog-HeqpgYrwdfrD5OYhlU7hPQ Thanks, Evan Rusackas ( he | him ) Frontend Lead Preset | preset.io On Oct 1, 2020, 12:02 AM -0700, Justin Mclean , wrote: > Hi, > > I know at one point this project was have bi-weekly synchronous meetings. Is > this still happened? My concern is that I don’t see any information of what > happens at these meetings being brought back to the mailing list. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, I know at one point this project was have bi-weekly synchronous meetings. Is this still happened? My concern is that I don’t see any information of what happens at these meetings being brought back to the mailing list. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, With your proposed PMC list I can see a number of the people mentioned don’t seem to be active and a number are not signed up to the project private mailing list. A quick check found at least one who looks to have not sent a single email to the mailing list during the entire incubation project. Has the project asked if these people want to be on the new PMC? When a projects graduates it sometimes a good idea to reduce the new PMC list to people who are active in the project and prepared to take on responsibility of being PMC members. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi, I think there's a couple of minor thing that need some minor fixes/clarification. I was looking at your website and can’t see where I can download the released versions form the Apache mirrors [1]. (This relates to CD10 in the maturity model and the distribution part.) I assume the main way people install Apache eSuperset is via PyPi [4]. It would be good to update the logo and information on that page and make it clearer that Superset is an Apache project. (This releases to LC50 in the maturity model) It looks like your web set is missing a few of the required links as well [2] [3] You might also want to check with trademarks about the links on the front pages to other commercial products and companies as usually this is not allowed. some of these companies would also have conditions around how their trademarks can be used. Thanks, Justin 1.https://dist.apache.org/repos/dist/release/incubator/superset/ 2. https://whimsy.apache.org/pods/project/superset 3. https://incubator.apache.org/guides/sites.html 4. https://pypi.org/project/apache-superset/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Graduate Apache Superset (incubating) as a TLP
Hi everyone, After discussion with the community[1], and a positive vote result[2], we believe we’re ready for graduation to a TLP, and we'd like to bring up in discussion with the IPMC. Please see the proposed board resolution below and let us know what you think. A few points to assist in the discussion: - Released 8 official Apache releases - Voted in 33 committers including 22 PPMC members - Achieved 30199 stars (and counting) on GitHub - Apache suitable name search has been approved [3] - Completed the Podling Maturity Assessment, all items are passed [4] - Our PPMC is diverse and consists of members from 4 organizations - There have been 489 contributors to the codebase - Closed 4661+ issues - Merged 4,833+ pull requests We've resolved all branding issues which include Logo, GitHub repo, documentation, website, and DockerHub. [1] https://lists.apache.org/thread.html/r0099bfda742dda24ade370b1c80ba6feeb5db525375a72c1e7142e39%40%3Cprivate.superset.apache.org%3E [2] https://lists.apache.org/list.html?d...@superset.apache.org:lte=1M:graduate%20Apache%20Superset [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-173, [4] https://github.com/apache/incubator-superset/wiki/Apache-Maturity-Model-Assessment --- Establish the Apache Superset Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to data exploration, analysis, visualization, and dashboarding. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Superset Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Superset Project be and hereby is responsible for the creation and maintenance of software related to data exploration, analysis, visualization, and dashboarding.; and be it further RESOLVED, that the office of "Vice President, Apache Superset" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Superset Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Superset Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Superset Project: * Aaron Suddjian * Beto Dealmeida * Bogdan Kyryliuk * Chris Williams * Craig Rueda * Daniel Gaspar * Erik Ritter * Evan Rusackas * Felix Cheung * Grace Guo * Jeff Feng * Jesse Yang * Jim Jagielski * John Bodley * Krist Wongsuphasawat * Maxime Beauchemin * Michelle Thomas * Nishant Bangarwa * Serena Jiang * Tai Dupree * Ville Brofeldt * Will Barrett NOW, THEREFORE, BE IT FURTHER RESOLVED, that Maxime Beauchemin be appointed to the office of Vice President, Apache Superset, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Superset Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Superset podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Superset podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- Thank you, Evan Rusackas ( he | him ) Frontend Lead Preset | preset.io
