Project Qualification Guidance about foundation HOT 4 OPEN

The main issue with impact or community acceptance is that it hinders incubation of new projects (as they are starting from a point of zero). The way some other foundations get around this is to have a formal incubation process which new projects would have to graduate through - however so far we've been keeping the .NET Foundation a more lightweight foundation.

It also depends on how the advisory council, technical steering group and the board of directors decide to interpret 'general use to the .NET community' which may evolve over time just as the guidelines for acceptance have evolved on a case by case basis so far. Ultimately that last point is a judgement call.

I would like to see more transparency in the process for joining the foundation and getting accepted - but baby steps...

from foundation.

Makes sense 👍

from foundation.

What about the "impact" or "community acceptance" or is this not important at all and even the most smallest project can be part of the .NET Foundation?

from foundation.

Presumably there is always a subjective judgement as pointed out in the last point "The project should be of general use to the .NET community. The Advisory Council and Technical Steering Group help the Board of Directors in determining this.". I don't think adding additional terms which are vague and subjective themselves would be helpful.

from foundation.