Details

      Description

      Apache has published a new set of project branding requirements. This is in
      addition to the Incubator's requirements for Podling branding, websites, etc.

      The primary materials to review are the website and the project documentation.

        Activity

        Hide
        Chris A. Mattmann added a comment -
        • schedule
        Show
        Chris A. Mattmann added a comment - schedule
        Hide
        Marvin Humphrey added a comment -

        The first item on the branding checklist is OK:

        All of our resources are served from apache.org servers. There's no
        lucy.apache.org top level domain yet, but we'll be ready when there is.

        Show
        Marvin Humphrey added a comment - The first item on the branding checklist is OK: Project Website Basics homepage is project.apache.org http://www.apache.org/foundation/marks/pmcs.html#websites All of our resources are served from apache.org servers. There's no lucy.apache.org top level domain yet, but we'll be ready when there is.
        Hide
        Marvin Humphrey added a comment -

        The second item on the branding checklist is done:

        All the documents listed at http://s.apache.org/ipp have been reviewed and
        modified as necessary, as has the website.

           perl/README
           perl/buildlib/Lucy/Build.pm
           perl/Build.PL
           perl/lib/Lucy.pod
           perl/lib/Lucy/Docs/Cookbook.pod
           perl/lib/Lucy/Docs/Tutorial.pod
           clownfish/lib/Clownfish.pod
           charmonizer/README
        
        Basically, we should review all of the following:
        
          * Any introductory documentation. 
          * Any README or INSTALL document.
          * Any project description metadata.
          * Any build file that generates project description metadata.
        

        We now observe the following:

        • Refer to "Apache Lucy" rather than just "Lucy" at our publicly exposed
          edges.
        • Differentiate between Apache Lucy as project and product. The main web
          page uses a proper software product description: "Apache Lucy is full-text
          search engine library written in C and targeted at dynamic languages."
        Show
        Marvin Humphrey added a comment - The second item on the branding checklist is done: Project Naming And Descriptions: use proper Apache forms, describe product, etc. http://www.apache.org/foundation/marks/pmcs.html#naming All the documents listed at http://s.apache.org/ipp have been reviewed and modified as necessary, as has the website. perl/README perl/buildlib/Lucy/Build.pm perl/Build.PL perl/lib/Lucy.pod perl/lib/Lucy/Docs/Cookbook.pod perl/lib/Lucy/Docs/Tutorial.pod clownfish/lib/Clownfish.pod charmonizer/README Basically, we should review all of the following: * Any introductory documentation. * Any README or INSTALL document. * Any project description metadata. * Any build file that generates project description metadata. We now observe the following: Refer to "Apache Lucy" rather than just "Lucy" at our publicly exposed edges. Differentiate between Apache Lucy as project and product. The main web page uses a proper software product description: "Apache Lucy is full-text search engine library written in C and targeted at dynamic languages."
        Hide
        Marvin Humphrey added a comment -

        Items 3-5 on the branding checklist all relate to the website.

        This was done when the CMS site went live late yesterday. The nav links are
        embedded in our basic.html template, so they will end up on future pages as
        well.

        The footer in basic.html contains all the required language.

        The exported Lucy logo png used on the website has a TM, as it's embedded in
        the source SVG file.

        Show
        Marvin Humphrey added a comment - Items 3-5 on the branding checklist all relate to the website. Website Navigation Links: navbar links included, link to www.apache.org included. http://www.apache.org/foundation/marks/pmcs.html#navigation This was done when the CMS site went live late yesterday. The nav links are embedded in our basic.html template, so they will end up on future pages as well. Trademark Attributions: attribution for all ASF marks included in footers, etc. http://www.apache.org/foundation/marks/pmcs.html#attributions The footer in basic.html contains all the required language. Logos and Graphics: include TM, use consistent product logo on your site. http://www.apache.org/foundation/marks/pmcs.html#graphics The exported Lucy logo png used on the website has a TM, as it's embedded in the source SVG file.
        Hide
        Marvin Humphrey added a comment -

        The last branding checklist item is our DOAP file:

        I created an up-to-date DOAP file for Lucy moments ago; registration is
        pending, as I've sent an email to site-dev@a.o per the instructions.

        http://incubator.apache.org/lucy/doap.rdf

        Show
        Marvin Humphrey added a comment - The last branding checklist item is our DOAP file: Project Metadata: DOAP file checked in and up to date http://www.apache.org/foundation/marks/pmcs.html#metadata I created an up-to-date DOAP file for Lucy moments ago; registration is pending, as I've sent an email to site-dev@a.o per the instructions. http://incubator.apache.org/lucy/doap.rdf
        Hide
        Marvin Humphrey added a comment -

        All branding checklist items have been completed, so I'm
        resolving this issue.

        Show
        Marvin Humphrey added a comment - All branding checklist items have been completed, so I'm resolving this issue.

          People

          • Assignee:
            Marvin Humphrey
            Reporter:
            Marvin Humphrey
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development