Acknowledgement for core feature supporters

Hello Team,

@gina and I discussed the sponsoring attribution and came up with the following suggestion. Please vote!

##Event Organization

Event Organizers get a recognition for their monetary and non-monetary efforts to organize an endorsed Neos event. For example

  • a Neos conference
  • a Meet Neos event
  • a Neos DevCamp
  • a Neos Bar Camp
  • a Neos Sprint

Types of recognition

  • physical badge: as a frame that can be hung on a wall or stand on a shelf
  • digital badge: a graphic to put on the website
  • mentioning in news/newsletters/official communication on

Badges contain the [opt: international] [event name] and [date] and the organizer logo.

There are no different levels for an event sponsoring, as the event itself produces marketing output/publicity corresponding to its size.


  • Yes! Fully agree to the suggestion
  • Yes, but read my improvement suggestion in the comments
  • No!

0 voters

Core Feature Sponsoring

A company or person is eligible for a core feature sponsoring recognition once the money spent on a core feature exceeds the minimum threshold of 4.000 € of effort (approx. 40h of work).

Types of recognition

  • Gold - 20.000€ (approx. 200h)
  • physical badge (smaller than event sponsor) to stand on a desk
  • digital badge to put on website
  • news mention on with option to add a section about the company
  • Silver - 8.000 € (approx. 80h)
  • digital badge to put on website
  • news mention on
  • Bronze - 4.000 € (approx. 40h)
  • digital badge to put on website

Badges contain “Core Feature Sponsor [level]: [feature name]” and the company logo


Companies, where active core team members work on core features are not eligible for the core features sponsoring. The reasons being that we want to recognize the actual spending of money on Neos and we believe that the “Active Core Team Member” Sponsoring is much stronger in its marketing effect.
There is an edge case, where another employee (not a core team member) of a company develops a core team feature. However, we agreed to not flesh this case out until it actually materializes.


  • Yes! Fully agree to the suggestion
  • Yes, but read my improvement suggestion in the comments
  • No!

0 voters

Active Core Team Member Sponsoring

Companies that employ and support one or more active core team members are rewarded for their investment in Neos (assumed they support the core team member spending company time for their Neos work).

Type of recognition

  • digital badge which shows the [current number] of active core team members and the company logo. The badge is hosted by the Neos team in the cloud and updated when the number of core team members at the company changes.
  • when a new team member is added, there is a news on and the new team member is added to the teams page


  • Yes! Fully agree to the suggestion
  • Yes, but read my improvement suggestion in the comments
  • No!

0 voters

As a connected question: should we add a company attribute/field to the team member profile that is shown on the “teams” page?

  • Yes, let’s add the company field to the team member profile
  • No!

0 voters

Next steps

If the vote passes, we will look into the design of badges and technical solutions where necessary.


Gina and Tobi

Hey, what would be the minimum amount of time the company has to sponsor?

E.g. in some periods of time I’m allowed to work 20hrs/month on new UI during work time (depends on general workload), I generally get to fix bugs we hit during our projects and so on. Also I join codesprints on company time. But as well as that, I spend a lot of my personal time on Neos, so it’s more like 50%/50%.

Regarding the profile field, I think that should be up to a contributor to decide. E.g. I’d definitly love our company to be listed next to my name.

1 Like

At first I thought: “I am fine with a physical badge, but not sure how much effort and costs that would bring with delivery and stuff. I can imagine to leave the choice to the supporter if it’s appreciated to have one.”. But thinking about it for a bit longer it should be pretty easy as chances are high that there’re team members on the event, and there we can reach out the badge ‘on stage’ of course, and there it will always be cool to the company.

Regarding the team member sponsoring: here we should not forget the companies that have been supporting the current (in)active members. We’ve for example supported the decix sprint last year by attending with 3 people and pay for travel / hotel ourselves. I think that by doing so the sprint last year cost us a considerable amount (around 1500 for travel / food / accommodation only, not speaking about wages / lost revenue). And that’s just one sprint example, and there’re more companies that supported Neos bigtime by ‘team member capacity’.

Not sure if this is off topic, but thinking about the costs of joining a sprint I’d also like to vote for a sprint supporter badge for companies that support by paying for expenses like traveltime / accommodations as that’s basically equal to sponsoring the event and doing a reimbursement from the sprint budget.

1 Like

As we target for something like 4/hrs per week or 20hr/month in terms of time to contribute to the project this should be some kind of an upper limit?! So if you do get that much time i think it should be at least good to get the badge.

Talking about sponsoring a team member or just anyone who will join the sprint?

I wouldn’t make a differentiation between the two in this case. Paying for traveltime / accommodation should be seen as direct sponsoring if you ask me. Of course a company can market “we send people to sprints” themselves, so I’m not talking about the time. Just the concrete travelcosts / accommodation.

regarding the activity discussion (@dimaip) I would generally refer to our discussion in Frankfurt: Activity discussion – Neos Sprint 2015 – Frankfurt

Of course, we need to flesh this out more and actually apply it in action :wink:

@radmiraal: the sponsoring for people to come to sprints is a valid and also delicate topic. We need to discuss this in more detail, as we probably don’t want to give out acknowledgements in an inflationary manner but on the other hand of course we want to recognize time and money spent for the project. I need to think about this…

First: In my opinion the company has an advantage when they send their developer.
From my experience (also in my company) it is a great opportunity for the developer to learn from (like minded) experienced people. Also it boosts their spirit. In addition the company gets direct connection to the core team.

Second: We talk about accomodation and travel costs (since upper mentioned it is not about the time they put in). So to put a number on I would say this is in average round about 500.- Euro.

So as a company you get

  • free highend know-how transfer
  • direct, personal connection to the core team

That’s like a workshop at a conference but without paying for the workshop. Even better you get direct connection to the core developers. In return the open source project gets help.

So I would say: no badge for paying for the accomodation and travel costs because that’s round about 500.- Euro and we voted further up by 51% for a minimum amount of 4000.- euro (33% voted for even more: 8000.-)

So I suggest we could vote on that…

1 Like

hi all,

i’working this out now and will come step by step back with:

  1. a matrix of badge designs (physical and digital) (they will be available on github later on)
  2. a short how-to to produce the physical badge
  3. an idea and draft where to put the general info about the acknowledgements
  4. an idea and draft where and what to announce, when we’re done
  • an draft on the news per supporter
  • an how-to here in discourse where and how to handle the incoming applications for badges

i will ask jens at sitegeist to draft the badge design based on the brand guide.

cheers gina


Hey @gina, I don’t really follow your argumentation to be honest. If I understand you correctly you say:

  • a company already has advantage because they can use it as marketing
  • as a core member you have advantages like knowledge / access to the team

Those might both be true, but that’s no guarantee at all and completely unrelated. First of all a company only has an advantage if they do market it. Bigger companies might do that, but I was for example always putting all the effort in Neos itself, and not in marketing things… having a badge would’ve been an easy marketing way, but furthermore I don’t see the relation and having a company I don’t see the value of “being a team member” over “contributor to open source”.

The second one is also not the full truth… The knowledge transfer and access to the teams is already true when people join slack, leach channels or just send pm’s.

But even if those would be real advantages which are equal to everybody (companies, freelancers, hobby-people): how should it make me feel that I spent hundreds (even thousands) of euros over the last years on travel / accommodation costs while I could’ve reimbursed? If that is not acknowledged it will lead to a simple thing… People will reimburse, and might use that money to buy a badge. What is the gain? Extra costs and probably less money to spend…

Honestly I’d be fine with whatever the outcome would be, but I see some flaws in the reasoning. If the whole badges system would’ve been in place before the 1.0 of Neos at least I would’ve reimbursed everything and sponsored back because that would’ve given me an advantage I could really use.

hey rens, good to hear from you.

you say a person who is not necessarily a team member but attends a code sprint once (not reimbursing the travel and accommodation costs) should get a badge for the support (of not reimbursing).

i can follow all you arguments but i have no idea how to proceed but to take a voting seriously that we acknowledge from a minimum amount of 4000.- on, which is independent of the type of support.

you say this minmum amount for a badge would lead to everybody reimbursing travel costs. that would be very sad.

since the voting here seems to be clear we can’t ignore it. what we can do it get the things done which we voted on and discuss and vote later about an extension of the concept.

so this is what i suggest to do, to address both needs of taking team decisions seriously but also be open to changes, new input, suggestions and extensions.

Hey @gina, nope, I’m not saying everybody should get a badge. I just feel like it would be fair for people that spend quite an amount of money on travel costs or accommodation costs and never get any public exposure for doing so. That’s why I started this discussion multiple times already, and still the outcome is disappointing at least.

I don’t think its sad when people reimburse, that’s turning the whole thing around which is unfair. It’s nice when people do not reimburse, and for that it would be nice if there’s some acknowledgement. To me it’s so fairly simple… I can decide not to reimburse as sponsoring. If I would be allowed to reimburse, but I don’t… then this is clear sponsoring. If that is not acknowledged, why would I then not reimburse and keep the money and sponsor it in some other way (maybe buy a badge).

Regarding the voting: I wasn’t aware of some decision, probably missed it… The voting above in the polls left it open as it asked for “yes, with my comments below” and my comments are below :wink:

And really, I’m not saying we should throw around badges or so. But to me personally I feel like it would’ve been nice to get a badge which I could’ve put on my website, and I can imagine other freelancers that spent hours and hours on the project could benefit from it too. Those people can only contribute if they have enough work, and if such a badge can support those contributors in some way, than it’s a small gesture which IMHO isn’t even worth long discussions… still it goes on for about 1,5 years now…

1 Like

hi rens,

sure, this i why i suggested a way forward.
if you don’t think that’s an solution what other solution do you suggest?

i’m a bit helpless here since i have a clear decision on the one hand and valid input on the other. so my idea is to work at least on the clear points (which the designer already does) and extend it then with other valid inputs later on. else we do not even move forward on the decided points which would be a pitty.

don’t you like that suggestion and if not do you have an idea how to solve that otherwise?

Hey @gina, argh, missed the “vote on an extension later”, yes, that would be good to keep progress. But then it is important that the extension really follows, even if that still means there won’t be badges. But this part needs to be sorted out at some point.

1 Like

Here are the new badges -> Supporter and Sponsoring Badges

I was just reviewing @gina’s draft article for the announcement of the new badges on (not published yet), when I stumbled over the levels for longtime supporters.

I have the following outcome from our discussions in Hamburg (Nov 2016):

The Designers have created Bronze to Diamond, the “Individual” one is not designed (yet). I thought I remembered a comment, who would deliver the 40h of support for the Diamond level. (imho this is solveable, if our foundation pays a fair hourly rate for the team member who works these hours - if we ever get a diamond sponsor :wink: ).

@lisa_sitegeist do you see big trouble with the free/discounted conference tickets?

@gina where did you take the amounts for Platinum and Diamond in your draft article from? Any concerns to using the amounts above (higher than in your draft article)?


hi tobias,

which numbers do u mean? i only see one typo: from 50 € to 1000 € per month. 1000 is wrong for sure. the rest seems to be right. and i do not really care if we go for annual or monthly numbers…
but maybe i oversee things, since it is morning ;-).
i totally agree on the numbers in the upper table.

regarding the hours i do not recall the discussion, i think i did not attend that part…


One little remark: I fear the 40 hours free support for diamond are hard to track and verify.

Hi @tobias

I don’t see a general problem with the free tickets, but I am not sure how it’s going to work with the “any other event”. Because I don’t know if someone already used their ticket for a Meet Neos or other.
There must be a list of Supporters (probably a google-drive doc) with an overview. And if someone wants a ticket for another event they have to give us an info so we can write it down?! Something like that.


I also don’t recall having heard about the “x hours of support” before. I’m not sure how this should work out in practice, since I assume that this will require quite some organization: the Neos Foundation will legally commit to provide that service when someone buys the Diamond plan - what if we don’t find anyone who has time / wants to provide support, even if its paid?

From our experience here at Flownative, there are a couple of other questions to be answered:

  • what’s the reaction time? hours, days, weeks, months?
  • will supporters be liable for any errors / mistakes? Or the Foundation? Up to which degree?
  • what topics are covered by the support?
  • how are the support tickets coordinated? Do we need a help desk for that and team members take turns to answer questions?

I think we’d be better off to either put something else into the package or include a voucher for support which can be redeemed at one of the Neos agencies, so they are responsible for all the above.


I’m all in for the voucher idea!