Hi Felix and JB,

Sounds good. We'll cancel this vote and prepare a new WIP release that
addresses the feedback mentioned in this thread.

Best,
Hezheng

On Fri, Jun 24, 2022 at 10:24 PM Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> Hi,
>
> I would recommend to cancel this vote and prepare a new release including:
> - cleanup on the icon and png file about license
> - flag DISCLAIMER on WIP
> - improve NOTICE file
>
> Regards
> JB
>
> On Fri, Jun 24, 2022 at 9:27 PM Hezheng Yin <yinhezheng1...@gmail.com>
> wrote:
> >
> > Hi Felix, thanks for the suggestion. If we were able to resolve the
> > licensing issues Justin raised, would you still recommend us switching to
> > WIP DISCLAIMER?
> >
> > Hi Justin, thanks for the clarification. We have gone through all the
> > image files in the release:
> >
> > 1. All flaticon icons [1] are replaced with blueprintjs icons [2] that
> have
> > Apache 2.0 license.
> > 2. For images created by ourselves, do we need to formally license them?
> If
> > so, is there a guideline that we can follow?
> > 3. In DevLake UI, we also make use of GitHub/GitLab/Jenkins/Jira logos on
> > the integration page. We found their logo usage guidelines [3][4][5][6]
> > online but couldn't find a formal license for these logos. For example,
> the
> > GitHub Logos and Usage page [3] states it's ok to "Use the Octocat or
> > GitHub logo to advertise that your product has built-in GitHub
> > integration". Is it compliant with Apache policy to include such logos in
> > the release?
> >
> > We'll restart the voting process on the DevLake mailing list once we
> > address the issues above.
> >
> > [1] https://www.flaticon.com/pricing
> > [2] https://blueprintjs.com/
> > [3] https://github.com/logos
> > [4]
> >
> https://about.gitlab.com/handbook/marketing/corporate-marketing/brand-activation/trademark-guidelines/
> > [5] https://www.jenkins.io/press/
> > [6] https://www.atlassian.com/company/news/press-kit
> >
> > Best,
> > Hezheng
> >
> >
> >
> > On Wed, Jun 22, 2022 at 8:52 PM Justin Mclean <jus...@classsoftware.com>
> > wrote:
> >
> > > Hi,
> > >
> > > > And to be sure, we should go through the community vote step again
> before
> > > > making another voting thread in general@incubator.apache.org. Is
> this
> > > > correct? Thanks in advance!
> > >
> > > Yes your PPMC will ned to vote on the new release candidate before
> > > bringing it for a vote by the incubator PMC.
> > >
> > > Kind Regards,
> > > Justin
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Reply via email to