Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: update intel text in providers list (meta: negotiating wording for donor descriptions & contributions) #912

Merged
merged 1 commit into from
Nov 8, 2017

Conversation

rvagg
Copy link
Member

@rvagg rvagg commented Oct 11, 2017

@nodejs/build we've been having private discussions with Intel about their hardware contributions and how best to acknowledge it—they have donated two physical boxes now hosted at nearForm, for benchmarking/perf work, which we are immensely thankful for of course. It raises some interesting questions about how far we go with putting marketing content into our README that I think we should discuss together. @mhdawson and I have been doing so privately in the context of this, and he has taken the lead primarily on updating this list and the associated graphic as well as our promotion of our providers across our various channels (this repo, twitter and in conference talks).

Keeping in mind that we entirely use donated resources and provide (soft) commitments to co-promote with our donors to make it worth their while being involved. This has been very helpful in attracting and retaining donors, most recently MacStadium signed up with some amazing resources and they don't have a direct connection to Node.js like a lot of our other providers do so the benefits to them are almost entirely marketing-related.

In this PR is the latest iteration of some wording we've been discussing with Intel, slightly modified by me (I've put their tag-line in quotes). If you look over our existing list you'll see a mix of simple "they've donated X" and "they are a Y company and have donated X" (see ARM just above this one for the most obvious comparison to Intel).

So my proposal (consider it a strawman for discussion) is that we allow donors to provide tag-lines like this but we keep them in quotes. Also, the text about their contribution should fit into a single, non-awkward sentence. Aside from that I don't have any suggestions for rules when negotiating wording here other than on a case-by-case basis to keep it reasonable.

@gibfahn
Copy link
Member

gibfahn commented Oct 11, 2017

Definitely +1 on quotes, otherwise it looks like it's missing a citation needed tag.

I'm fine with having a single line about what each company represents, but if we're doing this we should make sure we go back to our existing donors and ask what they'd like to see (so it doesn't look like we're favouring one company).

@mhdawson
Copy link
Member

If it just said "a world leader" instead of "the", I'd be ok without the quotes and happier overall. My preference is that we include whatever link that the provider wants, and in the page for that link they can sing their own praises, but that the text on our page is relatively neutral. The hard case would be if we have two contributors both claiming to be "the world leaders".

@joaocgreis
Copy link
Member

I believe a link would allow for companies to provide more information, without creating an opportunity for conflicting descriptions in this page. But if the general feeling is that the tag-lines provide better marketing value here, I'm also ok with that.

@refack
Copy link
Contributor

refack commented Oct 16, 2017

LGTM

@menepiet
Copy link

Was this one settled? Having a link to provide more information would help indeed.

@gibfahn
Copy link
Member

gibfahn commented Oct 23, 2017

Was this one settled? Having a link to provide more information would help indeed.

Nope, it'll be settled when this Pull Request is landed (closed).

@rvagg rvagg merged commit 11c3e3c into master Nov 8, 2017
@rvagg rvagg deleted the intel-text branch November 8, 2017 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants