Skip to content

Create an issue / PR template #3

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.

Sign up for GitHub

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

Jump to bottom
Closed
japaric opened this issue Nov 21, 2018 · 1 comment · Fixed by #6
Closed

Create an issue / PR template #3

japaric opened this issue Nov 21, 2018 · 1 comment · Fixed by #6

Comments

@japaric
Copy link
Member

japaric commented Nov 21, 2018

To be used as the submission template.

More info at https://help.github.com/articles/about-issue-and-pull-request-templates
@japaric
Copy link
Member Author

japaric commented Nov 21, 2018

Things that must be included in the submission:

  • Author name, or GH / twitter / IRC username if preferred.
  • Link to the author website, or GH / twitter profile page
  • Link to the project website, or repository where the code is hosted if the project doesn't have a website
  • Short project description. 1 paragraph, max 280 characters.
  • 1 picture or video of the project. Aspect ration must be 4:3. Width should not be larger than 900px.

japaric added a commit that referenced this issue Jan 10, 2019
@japaric
Add evaluation guidelines and instructions on how to submit a project
5ee9452 
closes #3
closes #4
@japaric japaric mentioned this issue Jan 10, 2019
Merged
japaric added a commit that referenced this issue Jan 12, 2019
@japaric
Add evaluation guidelines and instructions on how to submit a project
4ac4ff5 
closes #3
closes #4
bors bot added a commit that referenced this issue Feb 20, 2019
@bors @japaric
Merge #6
688292c 
6: Add evaluation guidelines and instructions on how to submit a project r=adamgreig a=japaric

The guidelines include all I can think of at the moment. We'll probably come up
with more of them once start reviewing user submissions. And, maybe, in the
future these guidelines could become a document on "good practices for
structuring embedded applications".

Q: Is there any additional information we'll like to request from the submitter,
apart from the information in `data.yml` (see #5)? This information would be
provided in the description of the pull request. If not then we don't need a
pull request template as I suggested in #3.

r? @rust-embedded/resources

closes #3
closes #4

Co-authored-by: Jorge Aparicio <[email protected]>
@bors bors bot closed this as completed in #6 Feb 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add evaluation guidelines and instructions on how to submit a project rust-embedded/showcase
1 participant
@japaric