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

[FEATURE REQ] Standardize format of resources #13

Open
MadhavJivrajani opened this issue Jun 24, 2020 · 5 comments
Open

[FEATURE REQ] Standardize format of resources #13

MadhavJivrajani opened this issue Jun 24, 2020 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@MadhavJivrajani
Copy link
Member

Is your feature request related to a problem? Please describe.
Need to standardize the way resources are submitted, the resources available aren't uniform in terms of they way they are presented.

Describe the solution you'd like
Things like what the file should be named, what the title should be, should a link come first followed by a description or the other way round, a pre-requisite section is required or not need to be agreed upon.

Describe alternatives you've considered (if any)
None

Additional context
None

@MadhavJivrajani
Copy link
Member Author

MadhavJivrajani commented Jun 25, 2020

Here are a few things that we should maintain uniformly across resources:

  • The file name for the resource should be README.md and not anything else. Doing so would make more sense since when someone clicks on a folder for resources, a file named README.md is automatically displayed, this won't happen if the name is something else like in the QML folder.
  • Most online repositories (ex) dedicated for curating resources follow the pattern: Link to resource: Description of resource (description in the same line as the resource). The name that is given to the link is the title of the article/paper or the name of the video or if none of them apply, it should be a short name describing clearly what this resource entails and more description about the resource can be provided in the description of the resource.
  • We don't have a lot of resources per area as of now, but as and when we do, we can create sections for MOOCs, papers, websites, etc as done in the above-mentioned link.

After discussion, we can come up with a guideline for the same that should be followed. Let me know what your thoughts on this are.

@SashwatAnagolum
Copy link
Member

Sounds good. Will update the QML folder, as well as the tutorial guidelines file to reflect this.

@MadhavJivrajani
Copy link
Member Author

Let's create a file called CONTRIBUTING.md and put guidelines for tutorials and resources under separate sections in that?

@MadhavJivrajani
Copy link
Member Author

Due to inactivity, I'm assuming you agree with whatever is mentioned above.
@Sashe17 @SashwatAnagolum @mugdhapattnaik please change your resource files accordingly and send in a PR at the earliest.

@MadhavJivrajani
Copy link
Member Author

Any update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants