On Thu, 25 Apr 2024 at 15:18, tison <wander4...@gmail.com> wrote:
>
> > The array is a list of pages in which the disclaimer could not be found.
>
> I do a quick check for the podlings I'm familiar with:
>
> For StreamPark, it reports:
>    "disclaimers": [
>       14,
>       [
>         "https://streampark.incubator.apache.org/team";,
>         "https://streampark.incubator.apache.org/user";
>       ]
>     ]
> But both pages should have the disclaimer at the footer.

The checker does not currently support pages generated by Javascript.

Those pages display as completely empty if Javascript is not enabled;
that is not very friendly.

>
> For Fury, Answer, and HoraeDB, the result seems correct. It reports that
> HoraeDB doesn't have the DISCLAIMER on all of its pages; this is the
> case. I'll reach out to them to resolve this.
>
> I mentor a new podling GraphAr, which seems missing in the report.
>
> Best,
> tison.
>
>
> sebb <seb...@gmail.com> 于2024年4月25日周四 22:11写道:
>
> > On Wed, 24 Apr 2024 at 13:05, tison <wander4...@gmail.com> wrote:
> > >
> > > Hi Sebb,
> > >
> > > > quite a few podlings where the text is only present on some of the web
> > > pages
> > >
> > > [1] you refers writes:
> > >
> > > >> Podling web sites MUST include a clear disclaimer on their website
> > >
> > > So, IMO it's clear that every page should contain such info (typically as
> > > part of the footer). If you find any podling violates this policy, you
> > can
> > > name them and I'd like to give a look.
> >
> > I updated the Whimsy site scanner to report on top-level links to
> > podling pages which don't appear to have the disclaimer.
> > This does not yet appear in the Whimsy podlings report, but the raw
> > data is in the JSON file at
> >
> > https://whimsy.apache.org/public/pods-scan.json
> >
> > Search for "disclaimers", e.g.
> >
> > "disclaimers": [
> >       1,
> >       [
> >         "https://hugegraph.incubator.apache.org/docs/";,
> >         "https://hugegraph.incubator.apache.org/docs/download/download/";,
> >         "https://hugegraph.incubator.apache.org/community/";
> >       ]
> >
> > The initial number (1 above) is the count of references that do appear
> > to have the disclaimer.
> > The array is a list of pages in which the disclaimer could not be found.
> >
> > In the above case, I think they all need the disclaimer, but there may
> > be some cases where it is not appropriate.
> >
> > > For the podlings I participate in, I spread the docu template [2] to
> > ensure
> > > that this policy is followed.
> > >
> > > [2]
> > >
> > https://github.com/apache/apache-website-template/blob/f8129ca66fdff1c97e0749eb2ed319f1739f6f34/docusaurus.config.ts#L137
> > >
> > > > and in announcement emails
> > >
> > > This sounds like a new sentence to me. Have we ever had a consensus
> > before?
> > > I agree that such a policy can help convey the project's status more
> > > clearly, and it won't be difficult to add such a section in the
> > > announcement email. Most of the podlings may be unaware of this point,
> > and
> > > I didn't hear about this before.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > sebb <seb...@gmail.com> 于2024年4月24日周三 15:58写道:
> > >
> > > > My understanding is that the Incubator disclaimer text [1] should be
> > > > present on all website pages and in announcement emails, so consumers
> > > > are clear about the status of the software.
> > > >
> > > > However there are quite a few podlings where the text is only present
> > > > on some of the web pages, and most announce emails don't include the
> > > > disclaimer.
> > > >
> > > > Note that unlike licensing issues, which can be sorted out during
> > > > incubation, this is something that must be addressed from the very
> > > > beginning.
> > > >
> > > > Sebb
> > > > [1] https://incubator.apache.org/guides/branding.html#disclaimers
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to