Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New examples guidelines #1910

Merged
merged 4 commits into from
Jul 14, 2018

Conversation

FadySamirSadek
Copy link
Collaborator

solves #1886

contributing.md Outdated
- [x] The framework/stack you are using is at least 1 year old.
- [x] The framework you are using should have at least 5k stars if it is hosted on Github or equivalent on other platforms.
- [x] Your app should be able to work on recent versions of all major browsers.
- [x] Your app should bring something truly new to the table, but minor variations of existing frameworks , languages or existing TodoMVC apps.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that's a typo? "but not minor variations..."?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will fix it, thanks 👍

@rickhallett
Copy link

I think this is good - the requirements need to be fairly strict as otherwise there will be a continual need to evaluate small company or individual frameworks. This just wouldn't be possible.

I think it is worth clarifying what is meant by 'brings something truly new to the table'. We could start with a summarised list of the features that the current repositories have.

@FadySamirSadek
Copy link
Collaborator Author

@WhiteFire0 I do not think an exhaustive list of features is the solution I think the first four guidelines are yes-no questions which is what we need but the last one just means your example has to be different because people can always use the same stack in different ways. I think we will always have to discuss and think if an app is a good addition or not but the first 4 guidelines are going to help us a lot in the decision making process

@FadySamirSadek
Copy link
Collaborator Author

@ahmed-90 Fixed the typo and rephrased the statement.
can you please have a look? Thanks 🙂

@dtheb
Copy link

dtheb commented Jul 14, 2018

@FadySamirSadek Looks good to me. 👍
BTW I still think that this list should be enhanced with a technical (lighthouse like) checklist to ensure standardization.

@FadySamirSadek
Copy link
Collaborator Author

@ahmed-90 I think this should be added incrementally. I think we should add lighthouse to our CI system but this can be added in an hour in the future. Will open an issue for it and feel free to submit a PR.

@FadySamirSadek FadySamirSadek merged commit 51f65fa into tastejs:master Jul 14, 2018
@FadySamirSadek FadySamirSadek deleted the new-example-guideline branch July 14, 2018 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants