You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2021. It is now read-only.
Right now, when you upload an extension, you get a warning that you have not chosen any Inform builds, and people will not be able to access your extension from within the Inform IDE. I suggest listing the criteria for figuring out whether the extension should be marked with an Inform build or not. Does marking an Inform build imply that the extension follows the guidelines for extensions in the public library? That it's been tested? That the author plans to maintain and support it? That the author believes it is ready for public use? etc. It would also be helpful to have that sort of explanation available to the general public, even if they never upload any extensions to the site, so that they know why some extensions are marked with a build, and some are not.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, when you upload an extension, you get a warning that you have not chosen any Inform builds, and people will not be able to access your extension from within the Inform IDE. I suggest listing the criteria for figuring out whether the extension should be marked with an Inform build or not. Does marking an Inform build imply that the extension follows the guidelines for extensions in the public library? That it's been tested? That the author plans to maintain and support it? That the author believes it is ready for public use? etc. It would also be helpful to have that sort of explanation available to the general public, even if they never upload any extensions to the site, so that they know why some extensions are marked with a build, and some are not.
The text was updated successfully, but these errors were encountered: