Re: [mantisbt-dev] MantisBT Logo

[Paul R. <pa...@ma...>]

One of the "issues" here is the loosely defined definition of
'team/mantisbt', and equally a lack of trademark over the word mantis

For an opensource project that has a corporate entity e.g. wordpress, or a
officially defined 'trust', it's easy - you state that any queries over
logo use needs to be licensed by said corporate entity.

So far, we've put a logo as a png in the repository (where we state the
repository is GPL licensed) and haven't done anything separate for the logo.

On the forum atrol's given the following advice previously:
http://mantisbt.org/forums/viewtopic.php?f=2&t=22230&p=54875&hilit=logo#p54875

Damien/Myself have previously said the following:  (and assumed the logo is
gpl)
http://article.gmane.org/gmane.comp.bug-tracking.mantis.general/3510/match=logo
http://article.gmane.org/gmane.comp.bug-tracking.mantis.general/3512/match=logo

and previously you've given users the ok to do colour modifications to the
logo:
http://article.gmane.org/gmane.comp.bug-tracking.mantis.general/839/match=logo

I will try and do some proper research when I'm not at work, however whilst
I think it's fairly obvious what we allow, equally where we are not an
officially registered group with an officially registered trademark, or
backed by a corporate entity etc etc, it probably actually makes it harder.

At the moment, we currently define everything back to "MantisBT Team", as
the overriding entity, which is a loosely defined term.

Paul


On Thu, Oct 2, 2014 at 7:43 AM, Victor Boctor <vb...@gm...> wrote:

> The vector graphics are available for use by the project, and I gave the
> logo to Damien before to set avatar on some site, but I just wasn’t sure
> about having in the mantisbt repository without having usage guidelines in
> place.
>
> We can go with any of the following options:
>
> 1. Share it in the mantibt-tools repository
> 2. Share it in a private git repository
> 3. Share it and distribute it with mantisbt
>
> We should publish the logo and usage guidelines for the logo at the same
> time.  For example, can other sites alter the logo, does it have to link
> back to our website, can it be printed on merchandise, etc.  I haven’t done
> the research to see what other projects are doing in this space.  But seems
> like Paul is motivated to do the research.
>
> Thoughts?
>
> On Oct 1, 2014, at 10:09 AM, P Richards <pa...@ma...> wrote:
>
> When we originally changed the logo for Mantis in 2012, my understanding
> was that we would be putting a copy of the logo in VECTOR format for people
> to use in the source repository.
>
> Following damien’s comment @
> https://github.com/mantisbt/mantisbt/pull/328#issuecomment-57475687 , I’m
> concerned whether as a team we now own and have royalty-free access to our
> current logo.
>
> As an open source project that can be developed by different people and
> other time the team has and I’m sure will continue to change, we should
> ensure that our logo is in the public domain.
>
> When we originally discussed the logo before @
> http://www.mantisbt.org/bugs/view.php?id=7994 – we had a number of offers
> from users to design for free a logo in the public domain and to give it to
> us in vector format.
>
> So given damien’s comment back to me, and roland’s request back in
> February 2012 below about having the logo available so we can freely modify
> it.
>
> I have a simple question:
>
> Is the current logo a free logo that can be made available in Vector
> format? If not, I suggest we reopen issue 7994 and look into designing a
> logo that is completely free for our use.
>
> I work in a school and have some students and work colleagues that would
> happily design a logo in vector format that would be royalty free and in
> the public domain for our use if for some reason the existing logo cannot
> be made available. In an ideal world, I’d hope that it is the case that the
> logo we picked in 2012 was indeed a publicly available logo that was free
> for our use for any purposes. At least, indeed this was what I was led to
> believe when Victor originally emailed about the new logo and stated: “In
> the issue you will find the old proposals, the new proposals, the
> guidelines that I wrote about what we want,” referring to the guidelines
> that stated:
>
> “- The logo should be available in image and vector formats (e.g. PNG,
> Adobe Photoshop and Adobe Illustrator)”
>
> Victor: could you send a copy of the logo in Vector Format to the mailing
> list, as per the original intention ?
>
> Thanks
> Paul
>
>
> *From:* Roland Becker [mailto:ro...@at... <ro...@at...>]
> *Sent:* 09 February 2012 09:32
> *To:* developer discussions
> *Subject:* Re: [mantisbt-dev] Misleading descriptions of MantisBT forks
> at github
>
> > 1. Logo in Vector Format - I'll have the logo in Adobe Illustrator
> format as well as PNG format.
>
> Please also SVG , so we could use open source solutions like Inkscape to
> modify whatever we want.
> At least it will show us whether Illustrator SVG export and Inkscape's PNG
> rendering will produce the same result.
> If the Inkscape output is different (I don't expect a 100% bit identical
> output), but what you can see is ok, we should use this one.
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk_______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>
>