App breakage should be a factor in removal.

[addyosmani]

Maybe we should include some verbiage in our acceptance rules to cover long term breakage of an implementation. This is a particularly poor experience for users and doesnt look good for authors either.

Like, if an app has been broken for N releases without update it gets removed until fixed.

This has the potential to encourage more authors to actively check in.

[arthurvr]

Yes, I can only agree with that. 👍

[sindresorhus]

👍

[passy]

👍

[arthurvr]

@tastejs/todomvc I think we all agree on this, so do we want to document this somewhere, or can we close the issue?

[samccone]

I think we can close this since we all agree, just good to have documented in the issue right?¿

[addyosmani]

Agreed. We should prob document somewhere though. Wiki?
On 24 Mar 2015 3:02 am, "Sam Saccone" notifications@github.com wrote:

I think we can close this since we all agree, just good to have documented
in the issue right?¿

—
Reply to this email directly or view it on GitHub
#1203 (comment).

[arthurvr]

Seems fine. Will take care of that this weekend.

[arthurvr]

Anyone an idea where we should have this documented? Maybe we should have a whole paragraph in the contributing.md about being around to help us maintain your app after submitting it?

[arthurvr]

I would honestly love it if we could say something like

Please think about the fact that contributing a new app means more than just
a one-off pull request submitting the app. When the app gets included on the site,
you will need to help use maintaining the app and help us to solve issues with the
implementation. If the app breaks for a decent amount of time, we will (temporary)
remove it from the site, until somebody opens a PR to fix the raised issues.

but guess it's a little too much?