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

Document consistency goods with files examples #129

Open
leobalter opened this issue Oct 28, 2015 · 5 comments
Open

Document consistency goods with files examples #129

leobalter opened this issue Oct 28, 2015 · 5 comments

Comments

@leobalter
Copy link
Member

After a discussion on qunitjs/api.qunitjs.com#114 (comment), it sounds we might use some examples of our kickstart configuration files we already use on most projects.

That might include, not exclusively:

  • .editorconfig
  • jshint and jscs configs
  • task runner configurations (currently grunt)
  • a whole CI configuration docs (this might become into another issue for individual tracking)

As the style guides, these might be strongly enforced, but breaking some rules - to explore to new standards - are welcome.

@jzaefferer
Copy link
Member

@arthurvr is this something you could help with?

A list of repos with config files in use, highlighting the (in)consistencies would be useful.

Some more files to add to the list: .csslintrc, .gitignore, .gitattributes, .travis.yml (sudo: false!)

On the dev leads meeting the idea was brought up to edit these files in one repo, then use bower/npmcopy to add/update them in individual repos. That would still require commits to each repo, but might still make it quite a bit easier to mange. Using bower/npmcopy, each repo can decide which files to actually include, so a project without CSS won't need to have a .csslintrc.

Regarding .editorconfig, we need to check if we need an exception to allow trailing whitespace in markdown files, since regular linebreaks are converted to spaces. Maybe we should use the trailing-backslash style instead, but that depends on our markdown converter actually support that.

@jzaefferer
Copy link
Member

Note from @arthurvr from on qunitjs/api.qunitjs.com#115: The package.json there uses 2 spaces for indent. That applies to other repos as well, since we use npm version which always reformats with 2 spaces. Doesn't look like that's ever going to change: npm/npm#3062

@jzaefferer
Copy link
Member

Regarding the centrally managed repo: If we have that, we could also include those files in this repo, to show the "current" config files on contribute.jquery.org, via @partial: https://github.com/jquery/grunt-jquery-content#partial

@scottgonzalez
Copy link
Member

There haven't been any objections, so I think we're good to move forward on this. Is anyone interested in leading this?

leobalter pushed a commit to qunitjs/api.qunitjs.com that referenced this issue Dec 9, 2015
@jzaefferer
Copy link
Member

I created a repo on the jquery-support org for this: https://github.com/jquery-support/dotfiles

Would be great if someone could do the initial collection of the various config files. I can help with getting them published and integrated elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants