If I submit a component, I want to know who downloads it so I can reach out on community and ask if they like it, do they have feedback, do they need help, etc.  If I turn this on, maybe on download they can "opt out", but ultimately I would like a list so I can reach out.

I really don't want to opt out on every forge component I download in each development environment I work on.

We are already having features available to rate and review a component, if we like too. If I don't like to review or rate a component then I would not want to be bothered with additional questions.

Hi Daniel, I think the problem is if someone downloads a component and they have issues, they just ignore it and move on.  Also, many devs contribute because they run consulting companies, they want to elevate their skills and expand their network, and this could be a way to do it.

Although i sometimes wish to reach out to people who downloaded my components i think that developers will always opt-out. I would rephrase this idea to: A forge contributor should have to the possibilty to reach out to all "Followers" of a component. That should be in a way that the contributor never sees the actual account data.

Hi Jennifer,,

You know why people move away from a Forge component, look at the unanswered Forum questions.

99% are psoted on a Forge component. So they to ask for help, but for, reasons that might be very valid, as everybody is working hard, the component creates don;t reply and help to overcome the problem one has trying to use the component.

Regards,

Daniel

Stefan I think you're proposing a great compromise.  I had experience with this, I uploaded a component but accidentally uploaded a module vs. an app and missed a dependency, and my component shows 10 downloads and only one person bothered to ask about it.  This is one of the scenarios where I think the reach out is important, after 10 downloads and no ratings/questions, I would wonder what was going on.  I can rephrase it.

Hi, Jennifer! Thank you so much for your idea. 

Is this idea about how to help producers receive more feedback about their Forge components? 

If yes - we agree we need to work on it and have that opportunity under our radar, indeed! 

We'll be researching the best approach to this problem, but disclosing who downloaded the component isn't in the list of possible solutions.