chore: AFP info for general public

[sofianguy]

Description of Change

Migrating App Feedback Program info from the maintainers repo. This will be linked in the upcoming 3.0.0 blog post.

cc @ckerr

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• relevant documentation is changed or added
• PR title follows semantic commit guidelines

Release Notes

Notes: no-notes

[MarshallOfSound]

@sofianguy If we put this at the top level it won't end up on the website, where-as if we put it in tutorials or something it will auto-deploy to the site afaik.

https://github.com/electron/electron/tree/master/docs/tutorial

Maybe that would be a better home if we want this on the website?

[sofianguy]

@MarshallOfSound I do want to put it on the website at some point. I spoke to Zeke briefly about where to put it on the website. For now that's undecided, so I think it's okay to leave it here for public linking purposes.

[MarshallOfSound]

Sounds good.

If the plan is to link to it and move it later we should ensure the link points to the exact commit it lands on, not just master. Otherwise we'll move it and all the links will break

[sofianguy]

@MarshallOfSound good point!

@codebytere -- link to exact commit for blog post

[ckerr]

Sam's got a good point -- even if this is an interim spot, we should put it someplace where at least we can put a redirect in the future.

For that reason, 👍 for moving this into docs/tutorials instead of the top-level

[groundwater]

A few quick thoughts

1. people don’t know about slack
2. we won't necessarily admit everyone who applies
3. we can prob skip the technical details e.g. 10k UH

I think we should just say we have a program, we use it to help prioritize work and get applications upgraded to the next stable as soon as possible. There’s an expectation of attending weekly status meetings, and people can inquire at info@electronjs.org

The details of our next cycle may change based on feedback from the last run, so I think we can just discuss the problem the AFP is trying to solve, and the approximate commitment required by the apps in the program.

I think on big change will be that for 4.0 we will be prioritizing apps who are closer to the next big hurdle, likely decided by user-count. That is, an app close to shipping to their next 1M users will be prioritized vs. an app far from shipping.

[sofianguy]

@groundwater Ok. The details will remain in the maintainers repo.

@ckerr can you copy-edit my new changes please?

[ckerr]

Short, friendly, and to the point. ❤️

Minor:

• I'd make explicit that we'd like the reported issues to be on betas. Possible rewording: "for large-scale Electron apps to test our beta releases and report..."

• s/app-specific blockers/app-specific issues/

• s/weekly check-in meetings/short, online weekly check-ins/

[ckerr]

3.0.0 is blocked on this, and it's a docs-only PR.

• electron-lint failure appears to be unrelated; mentioned to @jkleinsc in #ci channel

• electron-osx-testing is queued behind 11 tasks. Since this PR only adds a new .md file, I'm going to bypass that.

[release-clerk]

No Release Notes

[trop]

We have automatically backported this PR to "3-0-x", please check out #14673