| On 2018-05-08 10:10 AM, Richard
      Monson-Haefel wrote:
 
      
        One of the problems that I see with every
          project selecting their own logos is that there will be no
          consistency across the platform.  I think this is something
          that needs to be considered by the Marketing Committee in
          addition the individual projects.  Perception is as important
          as freedom and we want have a framework for creating new logos
          that complement rather than conflict with the Jakarta EE
          branding. I respectfully disagree. The projects should be able to have any
    logo they want. The Jakarta EE logo is the only logo that ties them
    all together into a platform.
 
 In particular any tying of the logos of the EE4J-hosted reference
    implementations to the Jakarta EE logo would give those
    implementations a special status over the independent
    implementations. I believe that would be unfair to TomEE, Wildfly,
    Websphere Liberty, WebLogic, etc.
 
 But please note that this thread has veered off from the original
    topic which is whether we want to create a Jakarta EE mascot
    distinct from Duke.
 
 
 
      
        
          
          Markus,If you are talking about
              replacing the
              JAX-RS Mascot and starting a design contest, then this is
              a decision left
              up to your community.  The PMC does not control the
              mascot/logos of
              an individual project.  This is very similar to
              MicroProfile.  We
              have our own brand/logo for MicroProfile, but we didn't
              require a blessing
              from the Technology PMC.  I would assume the same type of
              process
              would apply to all of the EE4J component projects.
 
 Were you told to ask the
              PMC for permission?
               Just curious if we're getting different instructions. 
              Thanks,
              Markus!
 
 ---------------------------------------------------
 Kevin Sutter
 STSM, MicroProfile and Java EE architect
 e-mail:  sutter@xxxxxxxxxx
                  Twitter:  @kwsutter
 phone: tl-553-3620 (office), 507-253-3620 (office)
 LinkedIn: https://www.linkedin.com/in/kevinwsutter
 
 
 
 From:      
               "Markus KARG"
              <markus@xxxxxxxxxxxxxxx>
 To:      
               <ee4j-pmc@xxxxxxxxxxx>
 Date:      
               05/07/2018 05:47
              PM
 Subject:  
               
                 [ee4j-pmc]
              Design
              Contest: Replacement for Duke Mascot
 Sent by:  
               
                 ee4j-pmc-bounces@xxxxxxxxxxx
 
 
 
 
 Dear PMC,
 
 recently I was told by the EF
              that I must
              not further use the Duke as a Mascot for any EE4J
              projects, as the EF wants
              to trademark all logos but the Duke is trademarked by
              Oralce.
 
 While I literally hate this
              decision, I
              have to respect it and find a solution. For marketing
              reasons, and just
              for fun, having a Mascot would be great.
 
 The only solution I do see is
              that we have
              to start a Mascot Design Contest. BTW, this time we should
              respect all
              the critics we earned with the Logo Design Contest: We
              need to have clearly
              described ALL criteria upfront, give enough time (six
              weeks at least),
              and publicly announce on the mailing list.
 
 What do you think?
 
 -Markus_______________________________________________
 ee4j-pmc mailing list
 ee4j-pmc@xxxxxxxxxxx
 To change your delivery options, retrieve your password,
                or unsubscribe
                from this list, visit
 https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_ee4j-2Dpmc&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=B13f4n_Vyp9UndxTLF25iLenLY_mzr9XfxJRj4V-vIA&s=QDkPvWjhXjwWsiUx2eFLyH1e2L8Z0DHGUCF-tile5jM&e=
 
 
 |