Provide instructions for getting funds for project logo design
Submitted by Wayne Beaton @wbeaton
Link to original bug (#509175)
Description
The Eclipse Foundation can provide funding for projects that want to create a logo. We need to describe that process. We should perhaps also include some discussion of this in the "Starting a Project" section.
Activity
(In reply to Wayne Beaton from comment 1)
Kat, what is the process that we've followed in the past for crowd-sourcing project logos creation?
Hi Wayne,
From my understanding the steps are as follows:
- The Eclipse Foundation will pay up to $500 for a project logo design;
- The project will be responsible for managing the design process;
- The project is responsible for providing feedback to the graphic designer;
- The project will need to pay for the design competition;
- Once the logo is created, an invoice must be submitted to Eclipse for reimbursement;
- Projects often use 99designs for their logo creation;
@Ian - Is there anything I missed?
(In reply to Katharine Hirsch from comment 2)
(In reply to Wayne Beaton from comment 1)
Kat, what is the process that we've followed in the past for crowd-sourcing project logos creation?
Hi Wayne,
From my understanding the steps are as follows:
- The Eclipse Foundation will pay up to $500 for a project logo design;
- The project will be responsible for managing the design process;
- The project is responsible for providing feedback to the graphic designer;
- The project will need to pay for the design competition;
- Once the logo is created, an invoice must be submitted to Eclipse for reimbursement;
- Projects often use 99designs for their logo creation;
@Ian - Is there anything I missed?
Yes these are the steps. Here is the text I would suggest we add to the project handbook.
<text>All Eclipse projects are encouraged to create a unique logo to identify their project. The Eclipse Foundation will help fund the creation of project logos. Projects can use a graphic design crowdsouring site, like 99designs, to create a logo. The project leader and committers are responsible for setting up the design process and providing the feedback to the different graphic designers. Based on past experience, the faster and more detailed feedback to the designers the better results.The project leader or committer will have to pay for the logo design in advanced. Once the logo is created, the project can then send the invoice to the Eclipse Foundation marketing team (Kat or Ian). The Foundation will reimburse up to US$600 for the logo design. Please also feel free to contact the Foundation marketing team with any questions about the logo design.
</text>@wbeatonsaid:(In reply to Ian Skerrett from comment 3)
...the project can then send the invoice to the Eclipse Foundation marketing team (Kat or Ian).
Send how?
If by email, then I'd prefer to give an alias.
Perhaps we can just link to the "contact us" page for a postal address?
I'd rather not put specific names of individuals in the handbook.
While I'd rather avoid making this any harder than it needs to be for project leads, endorsing a specific organization to provide the service is a violation of vendor neutrality. How do we be helpful without explicitly endorsing a (non-member) company?
(In reply to Wayne Beaton from comment 4)
(In reply to Ian Skerrett from comment 3)
...the project can then send the invoice to the Eclipse Foundation marketing team (Kat or Ian).
Send how?
email is the preferred method. I am not sure if I know how to do postal? :-)
If by email, then I'd prefer to give an alias.
Understood but this just generates more Spam for me. I was hoping that Kat and I are reasonable accessible in the community so people can find us?
Perhaps we can just link to the "contact us" page for a postal address?
I'd rather not put specific names of individuals in the handbook.
OK, how about 'marketing team'?
While I'd rather avoid making this any harder than it needs to be for project leads, endorsing a specific organization to provide the service is a violation of vendor neutrality. How do we be helpful without explicitly endorsing a (non-member) company?
99designs is just a suggestions not an endorsement.
(In reply to Ian Skerrett from comment 5)
(In reply to Wayne Beaton from comment 4)
(In reply to Ian Skerrett from comment 3)
...the project can then send the invoice to the Eclipse Foundation marketing team (Kat or Ian).
Send how?
email is the preferred method. I am not sure if I know how to do postal? :-)
If by email, then I'd prefer to give an alias.
Understood but this just generates more Spam for me. I was hoping that Kat and I are reasonable accessible in the community so people can find us?
If you think an alias is important, please us 'marketing@eclipse.org'
I'm looking into logos for a couple of projects for the Science Working Group so this is helpful.
One thing that would be really useful is a template/ example of the requirements that groups have used in the past, e.g. here's an example of the design spec used for the Eclipse Kapua project. If possible a link to the past 99designs contest (and maybe this is a way to suggest them without endorsing). Just thinking that in most cases the project leads are developers and for the ones who aren't too fussed about the specifics of logos (like me) could just adapt a previous example.
(In reply to Tracy Miranda from comment 7)
I'm looking into logos for a couple of projects for the Science Working Group so this is helpful.
One thing that would be really useful is a template/ example of the requirements that groups have used in the past, e.g. here's an example of the design spec used for the Eclipse Kapua project. If possible a link to the past 99designs contest (and maybe this is a way to suggest them without endorsing). Just thinking that in most cases the project leads are developers and for the ones who aren't too fussed about the specifics of logos (like me) could just adapt a previous example.
Unfortunately, I don
t have any old design specs and 99designs doesnt make old contests public. Each web site will have their own design spec process so I don`t think a template is feasible.FWIW, if a developer wants to spend the money on a logo design then they really need to be engaged and care about creating a new logo. A contest does take time and it does take someone to care. If you are not fussed about a logo, I would not use this process.
Hello,
Looks like the guidelines for project logo requests was never added to the Eclipse Project Handbook (or maybe I'm looking in the wrong place).
Could we get this updated?
Here are the instructions Ian proposed. Requests should be sent to Kat/Ian for actioning.
<text>All Eclipse projects are encouraged to create a unique logo to identify their project. The Eclipse Foundation will help fund the creation of project logos. Projects can use a graphic design crowdsourcing site, like 99designs, to create a logo. The project leader and committers are responsible for setting up the design process and providing the feedback to the different graphic designers. Based on past experience, the faster and more detailed feedback to the designers the better results.
The project leader or committer will have to pay for the logo design in advanced. Once the logo is created, the project can then send the invoice to the Eclipse Foundation marketing team (Kat or Ian). The Foundation will reimburse up to US$600 for the logo design. Please also feel free to contact the Foundation marketing team with any questions about the logo design.
</text>Thank you!
Kat
@wbeatonsaid:(In reply to Katharine Hirsch from comment 9)
Here are the instructions Ian proposed. Requests should be sent to Kat/Ian for actioning.
This text does not address the issues that I raised in Comment 4.
Further, I'd move "The Foundation will reimburse up to US$600 for the logo design." into the first paragraph. I think that it's the important bit.
Any thoughts regarding where in the document this belongs? Maybe under the Project Metadata section? [1]
(In reply to Wayne Beaton from comment 10)
(In reply to Katharine Hirsch from comment 9)
Here are the instructions Ian proposed. Requests should be sent to Kat/Ian for actioning.
This text does not address the issues that I raised in Comment 4.
My preference is to not include an email address or alias, as I mentioned in comment 5 & 6. If you think it is required then use marketing@eclipse.org.
Further, I'd move "The Foundation will reimburse up to US$600 for the logo design." into the first paragraph. I think that it's the important bit.
I actually disagree the important part is that projects are encourage to create logos. If you want to change the text, feel free.
Any thoughts regarding where in the document this belongs? Maybe under the Project Metadata section? [1]
Not sure why a logo creation would be metadata? I would suggest under Branding or the Project Checklist section. However, I trust you can put it where you think it makes the most sense in the handbook.
(In reply to Ian Skerrett from comment 11)
(In reply to Wayne Beaton from comment 10)
(In reply to Katharine Hirsch from comment 9)
Here are the instructions Ian proposed. Requests should be sent to Kat/Ian for actioning.
This text does not address the issues that I raised in Comment 4.
My preference is to not include an email address or alias, as I mentioned in comment 5 & 6. If you think it is required then use marketing@eclipse.org.
Further, I'd move "The Foundation will reimburse up to US$600 for the logo design." into the first paragraph. I think that it's the important bit.
I actually disagree the important part is that projects are encourage to create logos. If you want to change the text, feel free.
Any thoughts regarding where in the document this belongs? Maybe under the Project Metadata section? [1]
Not sure why a logo creation would be metadata? I would suggest under Branding or the Project Checklist section. However, I trust you can put it where you think it makes the most sense in the handbook.
My suggestion would be to place the project logo information in the most obvious place in the handbook: https://www.eclipse.org/projects/handbook/#logos-and-graphics.
I do think we need to include an email address in these instructions, because what happening right now is a broken telephone chain of requests, that after weeks, sometimes month of confusion, finally arrive to Ian or I with a frustrated project on the other end. Mike and Gael in recent weeks received questions from Projects about how to create a logo. They forwarded those requests to me. We (marketing/Ian/Kat) should be the obvious starting point for these projects, and we should make information easy to assess so that other parties don't need to get roped into the discussion.
@wbeatonsaid:(In reply to Ian Skerrett from comment 11)
My preference is to not include an email address or alias, as I mentioned in comment 5 & 6. If you think it is required then use marketing@eclipse.org.
We need to tell people how to engage. If not by email, then how? Bugzilla?
Further, I'd move "The Foundation will reimburse up to US$600 for the logo design." into the first paragraph. I think that it's the important bit.
I actually disagree the important part is that projects are encourage to create logos. If you want to change the text, feel free.
I can live with that.
Not sure why a logo creation would be metadata? I would suggest under Branding or the Project Checklist section. However, I trust you can put it where you think it makes the most sense in the handbook.
Just my first thought. Mostly because the PMI displays project logos based on content specified in project metadata.
(In reply to Katharine Hirsch from comment 12)
My suggestion would be to place the project logo information in the most obvious place in the handbook: https://www.eclipse.org/projects/handbook/#logos-and-graphics.
Good call. I'm glad that I asked.
I do think we need to include an email address in these instructions, because what happening right now is a broken telephone chain of requests, that after weeks, sometimes month of confusion, finally arrive to Ian or I with a frustrated project on the other end. Mike and Gael in recent weeks received questions from Projects about how to create a logo. They forwarded those requests to me. We (marketing/Ian/Kat) should be the obvious starting point for these projects, and we should make information easy to assess so that other parties don't need to get roped into the discussion.
+1
(In reply to Wayne Beaton from comment 13)
(In reply to Ian Skerrett from comment 11)
My preference is to not include an email address or alias, as I mentioned in comment 5 & 6. If you think it is required then use marketing@eclipse.org.
We need to tell people how to engage. If not by email, then how? Bugzilla?
I don't have a good answer so please just use the email alias.
Not sure why a logo creation would be metadata? I would suggest under Branding or the Project Checklist section. However, I trust you can put it where you think it makes the most sense in the handbook.
Just my first thought. Mostly because the PMI displays project logos based on content specified in project metadata.
OK, I will let you make the final decision. It would be nice to get this text added to the handbook so we can start referring to it.
@wbeatonsaid:I've taken the input from this thread and used it to modify the section titled "Logos and Graphics" under Branding.
https://www.eclipse.org/projects/handbook/#trademarks-project-logo
I think that I've got the wording right. Reopen if you feel some additional wordsmithing is required.
We added this some time ago.
https://www.eclipse.org/projects/handbook/#promoting-project-logo-design
