Giter Club home page Giter Club logo

iris-hep.github.io's Introduction

CI

Is this badge red? Click on it to find out what's wrong with the repository...

iris-hep.org Website

GitHub pages for IRIS-HEP project website.

Even if you have edit permissions, please make a pull request. The advantage of making a pull request instead of directly editing is that changes made via pull request will be tested to ensure that all is ok with your changes...

Testing locally quick instructions (see setup for full instructions):

gem install bundler
bundle install
bundle exec rake serve

Alternatively, you can test your changes out using the Jekyll docker image:

docker run --rm -it \
      --volume="$PWD:/srv/jekyll"  \
      -p 4000:4000 \
      jekyll/builder:stable jekyll serve --incremental

This will mount your checked out copy of this repo, then build and start the jekyll server mapping it to port 4000 on your computer. You can make changes locally and view them at http://localhost:4000

iris-hep.github.io's People

Contributors

alexander-held avatar bbockelm avatar brianhlin avatar carlosmalt avatar cranmer avatar davidlange6 avatar dcraik avatar ddavila0 avatar dependabot[bot] avatar djw8605 avatar fatala22 avatar gordonwatts avatar heather-gray avatar henryiii avatar ianna avatar jpivarski avatar masonproffitt avatar matthewfeickert avatar msneubauer avatar osg-cat avatar oshadura avatar pelmer avatar pre-commit-ci[bot] avatar rct225 avatar robrwg avatar rockybala avatar sebastianmacaluso avatar sfiligoi avatar shawnmckee avatar wguanicedew avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

iris-hep.github.io's Issues

Presentations filtered by person does not resolve shortname to name

sort team?

It would be nice to sort the team, maybe alphabetically by surname or first name.

add tag to hide a project

We have some projects that maybe don't need to be featured in the focus group.
Instead of deleting it, it would be nice if we could add a field in the project so that it is hidden on the focus group webpage.

Maybe the project webpage is still generated, just not linked off the focus group page.

Ideas for improvements

  • Maybe a discussions page would be better?
  • Empty or non-existing project or focus-area silences warning. Maybe special case some "non-project" focus areas (ssc) to avoid listing it? Maybe list non-existing projects / focus-areas? Should require (valid) focus-area, probably.
  • Should have a standard "Virtual" location suggestion.
  • Team group by area, maybe filters by affiliated or mainly supported, etc.
  • Document "core". Maybe error if any other focus area found? ✅
  • Can we remove the reliance on short names? Or automate them? They are a problem when the filename doesn't match the short name in some cases. (not removed, but forced to match)
    • short_title

Modified publication didn't update on webpage

Hi… something went funky here with PR #961

See
https://github.com/iris-hep/iris-hep.github.io-source/pull/961/files
you see the related-work: true was removed and the citation was changed. But the website didn’t update properly.

Current version of file:
https://github.com/iris-hep/iris-hep.github.io-source/blob/master/_data/publications/1864766.yml

But the publication still shows up in related work section with old citation information. Caching?

Update ServiceX Project Page

Please review the contents of the ServiceX project page here: https://iris-hep.org/projects/servicex.html

Try to have the following

  • Project description is up-to-date and reflects the current status of the project.
  • One or two figures explaining the architecture of the project and scale / performance results (such as screenshots from monitoring or a figure reproduced from a figure), as applicable.
  • Recent accomplishments (particularly if they are checking off an NSF milestone) and plans / research directions for the next year or so.
  • Team section has all the right people listed.
  • All relevant papers are listed under publications. Papers should acknowledge IRIS-HEP.
  • All relevant presentations are uploaded. Presentations should acknowledge IRIS-HEP.

fellow pages updates needed

hi @rct225 fyi - I was looking at fellow pages for a different reason
some potential inconsistencies (today is Nov 1)

Needs a fellow page Ajay,Rawat

Did a presentation but missing from the website
4eshanb.md -> presented Oct 25
FeistKyle.md -> presented today
HectorNoguez.md -> presented last week
SofiaGraziano.md --> presented today
decheine.md -> presented today
eric-moreno.md -> presented last week
AlanAneethJegaraj.md -> talked Oct 5
AneeshHeintz.md -> Oct 14 2020
AnishBiswas.md -> May 10 2021
Rahul-Agrawal.md -> Oct 25 2021
XiongfengSong.md -> Oct 14 2021

Clean-up collaborations page

The collaborations page (https://iris-hep.org/collaborations) looks a bit basic. At the minimum, each project should have a sentence or so on how they intersect with IRIS-HEP (not just NSF project numbers!).

Additionally, (at least) the following are missing:

  • SLATE
  • SOTERIA
  • New Awkward Array CSSI
  • EWMS
  • New DarkMatter / ServiceX CSSI
  • Any other HEP collaborations working with IRIS.

Create new Coffea-Casa Project Page

Please create a new Coffea Casa project page inside the DOMA area.

Try to have the following

  • Project description is up-to-date and reflects the current status of the project.
  • One or two figures explaining the architecture of the project and scale / performance results (such as screenshots from monitoring or a figure reproduced from a figure), as applicable.
  • Recent accomplishments (particularly if they are checking off an NSF milestone) and plans / research directions for the next year or so.
  • Team section has all the right people listed.
  • All relevant papers are listed under publications. Papers should acknowledge IRIS-HEP.
  • All relevant presentations are uploaded. Presentations should acknowledge IRIS-HEP.

Add check of personnel file match to institutional file

Description

As @henryiii pointed out, a test can be added (maybe even as a pre-commit hook?) to follow up his PR #83 to check that every person listed in an individual person YAML file also has their shortname listed in an institution personnel listing YAML file.

I don't know Ruby or I would add it myself right now, but if no one beats me to it I could take a stab at it when I've finished my thesis (in a few weeks).

Add a gallery of results to pyhf project page

Some helpful feedback received from @davidlange6 on how to improve the pyhf project page was

An example addition might be a gallery of results (basically graphics from the "use in publications" list).

There are already plenty of results that exist across the internet that can be shown, including results from SModelS, so this would be an easy addition.

A note to self: The pyhf page is already pretty list-y, so maybe try to "lead with awesome" and get some of the example plot up at the top.

Update SkyHook DM page

Please review the contents of the SkyHook DM project page here: https://iris-hep.org/projects/skyhookdm.html

Try to have the following

  • Project description is up-to-date and reflects the current status of the project.
  • One or two figures explaining the architecture of the project and scale / performance results (such as screenshots from monitoring or a figure reproduced from a figure), as applicable.
  • Recent accomplishments (particularly if they are checking off an NSF milestone) and plans / research directions for the next year or so.
  • Team section has all the right people listed.
  • All relevant papers are listed under publications. Papers should acknowledge IRIS-HEP.
  • All relevant presentations are uploaded. Presentations should acknowledge IRIS-HEP.

Collaborators

Add a collaborator "badge" for non-IRIS-HEP members in projects will have to be done manually Nevermind, may be automatic.

Automatically delete head branches

Can we please enable automatic deletion of PR head branches in the repo Settings, so that we don't have to manually delete them after each PR?

Should look like this (except that it is unchecked):
delete_head_branches

Focus area missing

The following people are not in a focus area:

floe
andrewchien
vgvassilev
klute
haxxardoux
rct225
b_cousins
m-carothers
meevans1
evanmassaro
o_gutsche
p_koppenburg
talvandaalen
yk_kim
ioifrim
a_digirolamo
tatiana-m
jeyserma
k_kvdam
mdhildreth
d_costanzo
dpiparo
g_raven
HedgeMage
danielsibemol
936-BCruz
s_campana
m_norman
t_boccali
alanjoshua
d_swanson
kherner
g_stewart
e_s-kennedy
GuillermoFidalgo
sthapa
p_couvares
d_brown

Use focus-area: core if general, or focus-area: if there's no specific focus area.

New news post page

Add a docs page describing how to write a news post, with special features.

Add higher quality image of IRIS-HEP logo with text

The current IRIS-HEP logo with the words "iris hep" (the Iris-hep-4-no-long-name series) is of decent quality for a small PNG when used on websites. However, when trying to use the image on other pages in a larger context the resolution isn't very good. Would it be possible to get a higher resolution image of it similar to the Iris-hep-5-just-graphic-large.png that exists?

I created one myself from the SVG that exists in GIMP, but it is several MB in size where the Iris-hep-5-just-graphic-large.png one is much smaller by comparison (~50 KB), so I'm not doing this in a smart manner.

Update XCache Project Page

Please review the contents of the XCache project page here: https://iris-hep.org/projects/caching.html

Try to have the following

  • Project description is up-to-date and reflects the current status of the project.
  • One or two figures explaining the architecture of the project and scale / performance results (such as screenshots from monitoring or a figure reproduced from a figure), as applicable.
  • Recent accomplishments (particularly if they are checking off an NSF milestone) and plans / research directions for the next year or so.
  • Team section has all the right people listed.
  • All relevant papers are listed under publications. Papers should acknowledge IRIS-HEP.
  • All relevant presentations are uploaded. Presentations should acknowledge IRIS-HEP.

Twitter

Would a twitter feed be an interesting addition to the website? I have it set up locally:


Screen Shot 2020-02-17 at 5 06 26 PM

Team page not being built on deploy

Description

Today @msneubauer added the YAML for a new entry to the team page (me) (c.f. abda6c8) which we can see from the commit history that GitHub pages successfully deployed. However, the Full Team page isn't updating.

I haven't attempted to build the page locally and see how it looks, and won't have time for the rest of the week, but if someone has thoughts on this it would be good to fix and then see if checks can be added in the future for page deployment. (@pelmer as it seems that you've done most dev work on the site maybe you have thoughts for things to poke here) Maybe something like Netlify as it seems to be nicer deployment testing then ReadTheDocs.

Update IDDS project page

Please review the contents of the IDDS project page here: https://iris-hep.org/projects/idds.html

Try to have the following

  • Project description is up-to-date and reflects the current status of the project.
  • One or two figures explaining the architecture of the project and scale / performance results (such as screenshots from monitoring or a figure reproduced from a figure), as applicable.
  • Recent accomplishments (particularly if they are checking off an NSF milestone) and plans / research directions for the next year or so.
  • Team section has all the right people listed.
  • All relevant papers are listed under publications. Papers should acknowledge IRIS-HEP.
  • All relevant presentations are uploaded. Presentations should acknowledge IRIS-HEP.

Line feed in project_goal for fellows page

A student submitted a pull request that initially seemed ok as far as format. It passed through the usual checks as well. However, the page never appeared on the site. After some investigation is seems that the extra line feeds in the project_goal caused an issue. It was not obvious at first when I looked at the file. The only clue I had that something was amiss was when I viewed the markdown file in the github repo, it did not appear "formatted" as the other fellows' markdown files.

You can see the changes I made here:
ae1b3d5

Update TPC Project Page

Please review the contents of the TPC project page here: https://iris-hep.org/projects/tpc.html

Try to have the following

  • Project description is up-to-date and reflects the current status of the project.
  • One or two figures explaining the architecture of the project and scale / performance results (such as screenshots from monitoring or a figure reproduced from a figure), as applicable.
  • Recent accomplishments (particularly if they are checking off an NSF milestone) and plans / research directions for the next year or so.
  • Team section has all the right people listed.
  • All relevant papers are listed under publications. Papers should acknowledge IRIS-HEP.
  • All relevant presentations are uploaded. Presentations should acknowledge IRIS-HEP.

Inactive people appearing on team lists

It appears that people who have been marked as inactive are still appearing on the team lists, at least the overall team list and the focus area ones. What is the point of marking someone as inactive if they still show up? Please remove inactive people from “active” team lists.

Issues with Copying Deployment

Hello, I am using your website to set up the DANCEOrg website, but I am running into some issues with deployment. (https://github.com/DANCEOrg/iris-hep.github.io-source)

Help would be thoroughly appreciated, and I would be glad to contribute if that would be useful.

The step that is failing is the "Check RuboCop" step. I checked the permissions for the get_indico.rb and it returned that it has rwx. Also, not sure why the Assignment Branch Condition size for inspire is too high for our code but was not for yours since our code is the same.

Offenses:

_plugins/getpub.rb:129:5: C: Metrics/AbcSize: Assignment Branch Condition size for inspire is too high. [<23, 49, 20> 57.71/55]
    def inspire(pub) ...
    ^^^^^^^^^^^^^^^^
_scripts/get_indico.rb:1:1: W: Lint/ScriptPermission: Script file get_indico.rb doesn't have execute permission.
#!/usr/bin/env ruby
^^^^^^^^^^^^^^^^^^^

citation for publication removes authors

We have several publications that are in INSPIRE, but INSPIRE doesn't know about what conference they were published in.
We've been adding that with the citation field, but that wipes out the author information.

Looking more closely, there seem to be several like this.
Examples:
1864766.yml
1858493.yml

It would be nice if there was a field that just added additional information (like note or additional_info that did not remove the author information pulled from INSPIRE.

Move to Travis

The plan is to move the source repository for the iris-hep website to a new name, iris-hep.github.io-source, on Wednesday some point after 15:00 EDT. There will be a small disruption in availability during the move. The website will become statically available again a few minutes later, and the Travis CI produced output will follow after that. This will enable publications to appear, as well as enabling PRs to be automatically checked for common issues.

Missing tags list

Here are the missing tags that need to be worked on. If there's really no project associated with a presentation, then project: (blank) can be added to silence the warning.

presentation #0 in _data/people/jlefevre.yml must contain location.
presentation #1 in _data/people/jlefevre.yml must contain location.
presentation #2 in _data/people/jlefevre.yml must contain location.
presentation #3 in _data/people/jlefevre.yml must contain location.
presentation #4 in _data/people/jlefevre.yml must contain location.
presentation #5 in _data/people/jlefevre.yml must contain location.
presentation #3 in _data/people/pelmer.yml must contain location.
presentation #4 in _data/people/pelmer.yml must contain location.
presentation #1 in _data/people/mweinberg2718.yml must contain project.
presentation #2 in _data/people/mweinberg2718.yml must contain project.
presentation #3 in _data/people/mweinberg2718.yml must contain location, project.
presentation #1 in _data/people/fatala22.yml must contain location.
presentation #2 in _data/people/fatala22.yml must contain location.
presentation #3 in _data/people/fatala22.yml must contain location.
presentation #5 in _data/people/fatala22.yml must contain location.
presentation #6 in _data/people/fatala22.yml must contain location.
presentation #7 in _data/people/fatala22.yml must contain location.
presentation #9 in _data/people/fatala22.yml must contain location.
presentation #10 in _data/people/fatala22.yml must contain location.
presentation #11 in _data/people/fatala22.yml must contain location.
presentation #0 in _data/people/wguan.yml must contain location.
presentation #1 in _data/people/wguan.yml must contain location.
presentation #2 in _data/people/wguan.yml must contain location.
presentation #3 in _data/people/wguan.yml must contain location.
presentation #4 in _data/people/wguan.yml must contain location.
presentation #5 in _data/people/wguan.yml must contain location.
presentation #6 in _data/people/wguan.yml must contain location.
presentation #7 in _data/people/wguan.yml must contain location.
presentation #8 in _data/people/wguan.yml must contain location.
presentation #9 in _data/people/wguan.yml must contain location.
presentation #10 in _data/people/wguan.yml must contain location.
presentation #11 in _data/people/wguan.yml must contain location.
presentation #1 in _data/people/drankincms.yml must contain location.
presentation #0 in _data/people/mmasciov.yml must contain location.
presentation #1 in _data/people/mmasciov.yml must contain location.
presentation #0 in _data/people/meevans1.yml must contain focus-area, project.
presentation #1 in _data/people/meevans1.yml must contain focus-area, project.
presentation #2 in _data/people/meevans1.yml must contain focus-area, project.
presentation #3 in _data/people/meevans1.yml must contain focus-area, project.
presentation #4 in _data/people/meevans1.yml must contain focus-area, project.
presentation #5 in _data/people/meevans1.yml must contain focus-area, project.
presentation #6 in _data/people/meevans1.yml must contain focus-area, project.
presentation #7 in _data/people/meevans1.yml must contain focus-area, project.
presentation #8 in _data/people/meevans1.yml must contain focus-area, project.
presentation #9 in _data/people/meevans1.yml must contain focus-area, project.
presentation #0 in _data/people/cranmer.yml must contain focus-area, project.
presentation #1 in _data/people/cranmer.yml must contain focus-area, project.
presentation #2 in _data/people/cranmer.yml must contain focus-area, project.
presentation #3 in _data/people/cranmer.yml must contain location, project.
presentation #4 in _data/people/cranmer.yml must contain focus-area, project.
presentation #5 in _data/people/cranmer.yml must contain focus-area, project.
presentation #6 in _data/people/cranmer.yml must contain focus-area, project.
presentation #7 in _data/people/cranmer.yml must contain project.
presentation #8 in _data/people/cranmer.yml must contain project.
presentation #9 in _data/people/cranmer.yml must contain project.
presentation #10 in _data/people/cranmer.yml must contain project.
presentation #11 in _data/people/cranmer.yml must contain project.
presentation #12 in _data/people/cranmer.yml must contain project.
presentation #13 in _data/people/cranmer.yml must contain project.
presentation #14 in _data/people/cranmer.yml must contain project.
presentation #15 in _data/people/cranmer.yml must contain project.
presentation #16 in _data/people/cranmer.yml must contain project.
presentation #17 in _data/people/cranmer.yml must contain project.
presentation #18 in _data/people/cranmer.yml must contain project.
presentation #19 in _data/people/cranmer.yml must contain project.
presentation #20 in _data/people/cranmer.yml must contain project.
presentation #21 in _data/people/cranmer.yml must contain project.
presentation #22 in _data/people/cranmer.yml must contain project.
presentation #23 in _data/people/cranmer.yml must contain project.
presentation #24 in _data/people/cranmer.yml must contain project.
presentation #25 in _data/people/cranmer.yml must contain project.
presentation #26 in _data/people/cranmer.yml must contain project.
presentation #27 in _data/people/cranmer.yml must contain project.
presentation #28 in _data/people/cranmer.yml must contain project.
presentation #29 in _data/people/cranmer.yml must contain project.
presentation #30 in _data/people/cranmer.yml must contain project.
presentation #31 in _data/people/cranmer.yml must contain project.
presentation #32 in _data/people/cranmer.yml must contain project.
presentation #33 in _data/people/cranmer.yml must contain project.
presentation #34 in _data/people/cranmer.yml must contain project.
presentation #35 in _data/people/cranmer.yml must contain project.
presentation #37 in _data/people/cranmer.yml must contain project.
presentation #38 in _data/people/cranmer.yml must contain project.
presentation #39 in _data/people/cranmer.yml must contain project.
presentation #40 in _data/people/cranmer.yml must contain project.
presentation #41 in _data/people/cranmer.yml must contain project.
presentation #42 in _data/people/cranmer.yml must contain project.
presentation #43 in _data/people/cranmer.yml must contain project.
presentation #44 in _data/people/cranmer.yml must contain project.
presentation #45 in _data/people/cranmer.yml must contain project.
presentation #46 in _data/people/cranmer.yml must contain project.
presentation #47 in _data/people/cranmer.yml must contain project.
presentation #48 in _data/people/cranmer.yml must contain project.
presentation #49 in _data/people/cranmer.yml must contain project.
presentation #50 in _data/people/cranmer.yml must contain project.
presentation #51 in _data/people/cranmer.yml must contain project.
presentation #52 in _data/people/cranmer.yml must contain project.
presentation #53 in _data/people/cranmer.yml must contain project.
presentation #54 in _data/people/cranmer.yml must contain project.
presentation #55 in _data/people/cranmer.yml must contain project.
presentation #56 in _data/people/cranmer.yml must contain project.
presentation #57 in _data/people/cranmer.yml must contain project.
presentation #58 in _data/people/cranmer.yml must contain project.
presentation #59 in _data/people/cranmer.yml must contain project.
presentation #60 in _data/people/cranmer.yml must contain project.
presentation #61 in _data/people/cranmer.yml must contain project.
presentation #0 in _data/people/savvy379.yml must contain meetingurl.
presentation #1 in _data/people/savvy379.yml must contain meetingurl.
presentation #2 in _data/people/savvy379.yml must contain meetingurl.
presentation #3 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #4 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #5 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #6 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #7 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #8 in _data/people/savvy379.yml must contain location.
presentation #0 in _data/people/evanmassaro.yml must contain focus-area, project.
presentation #0 in _data/people/davidlange6.yml must contain location.
presentation #1 in _data/people/davidlange6.yml must contain location.
presentation #2 in _data/people/davidlange6.yml must contain location.
presentation #3 in _data/people/davidlange6.yml must contain meetingurl, location.
presentation #4 in _data/people/davidlange6.yml must contain location.
presentation #5 in _data/people/davidlange6.yml must contain location.
presentation #1 in _data/people/gordonwatts.yml must contain location.
presentation #3 in _data/people/gordonwatts.yml must contain project.
presentation #4 in _data/people/gordonwatts.yml must contain location.
presentation #5 in _data/people/gordonwatts.yml must contain location.
presentation #6 in _data/people/gordonwatts.yml must contain location.
presentation #7 in _data/people/gordonwatts.yml must contain location, project.
presentation #8 in _data/people/gordonwatts.yml must contain location.
presentation #9 in _data/people/gordonwatts.yml must contain location.
presentation #10 in _data/people/gordonwatts.yml must contain location.
presentation #11 in _data/people/gordonwatts.yml must contain location.
presentation #12 in _data/people/gordonwatts.yml must contain location.
presentation #13 in _data/people/gordonwatts.yml must contain location, project.
presentation #14 in _data/people/gordonwatts.yml must contain location.
presentation #15 in _data/people/gordonwatts.yml must contain location, project.
presentation #16 in _data/people/gordonwatts.yml must contain location.
presentation #17 in _data/people/gordonwatts.yml must contain location, project.
presentation #19 in _data/people/gordonwatts.yml must contain project.
presentation #28 in _data/people/gordonwatts.yml must contain project.
presentation #31 in _data/people/gordonwatts.yml must contain project.
presentation #0 in _data/people/bbockelm.yml must contain location.
presentation #1 in _data/people/bbockelm.yml must contain location.
presentation #2 in _data/people/bbockelm.yml must contain location, project.
presentation #3 in _data/people/bbockelm.yml must contain meetingurl, location.
presentation #4 in _data/people/bbockelm.yml must contain meetingurl, location, project.
presentation #5 in _data/people/bbockelm.yml must contain meetingurl, location, project.
presentation #6 in _data/people/bbockelm.yml must contain meetingurl, location, project.
presentation #8 in _data/people/bbockelm.yml must contain location, project.
presentation #10 in _data/people/bbockelm.yml must contain focus-area, project.
presentation #11 in _data/people/bbockelm.yml must contain location, project.
presentation #12 in _data/people/bbockelm.yml must contain location.
presentation #13 in _data/people/bbockelm.yml must contain location.
presentation #14 in _data/people/bbockelm.yml must contain location.
presentation #15 in _data/people/bbockelm.yml must contain location, project.
presentation #16 in _data/people/bbockelm.yml must contain location, project.
presentation #17 in _data/people/bbockelm.yml must contain location.
presentation #18 in _data/people/bbockelm.yml must contain location.
presentation #19 in _data/people/bbockelm.yml must contain location.
presentation #20 in _data/people/bbockelm.yml must contain location, project.
presentation #21 in _data/people/bbockelm.yml must contain location, project.
presentation #3 in _data/people/carlosmalt.yml must contain location.
presentation #18 in _data/people/carlosmalt.yml must contain location.
presentation #0 in _data/people/etorro.yml must contain location, project.
presentation #0 in _data/people/BenGalewsky.yml must contain project.
presentation #1 in _data/people/BenGalewsky.yml must contain project.
presentation #4 in _data/people/BenGalewsky.yml must contain project.
presentation #1 in _data/people/SebastianMacaluso.yml must contain project.
presentation #0 in _data/people/ivotron.yml must contain focus-area, project.
presentation #1 in _data/people/ivotron.yml must contain focus-area, project.
presentation #0 in _data/people/robrwg.yml must contain location, focus-area, project.
presentation #1 in _data/people/robrwg.yml must contain location.
presentation #2 in _data/people/robrwg.yml must contain location.
presentation #3 in _data/people/robrwg.yml must contain location.
presentation #4 in _data/people/robrwg.yml must contain location.
presentation #0 in _data/people/tresreid.yml must contain location.
presentation #0 in _data/people/msneubauer.yml must contain project.
presentation #1 in _data/people/msneubauer.yml must contain project.
presentation #2 in _data/people/msneubauer.yml must contain project.
presentation #3 in _data/people/msneubauer.yml must contain project.
presentation #4 in _data/people/msneubauer.yml must contain project.
presentation #5 in _data/people/msneubauer.yml must contain project.
presentation #6 in _data/people/msneubauer.yml must contain project.
presentation #8 in _data/people/msneubauer.yml must contain project.
presentation #9 in _data/people/msneubauer.yml must contain project.
presentation #10 in _data/people/msneubauer.yml must contain project.
presentation #11 in _data/people/msneubauer.yml must contain project.
presentation #0 in _data/people/heather-gray.yml must contain location.
presentation #1 in _data/people/heather-gray.yml must contain location.
presentation #2 in _data/people/heather-gray.yml must contain location.
presentation #3 in _data/people/heather-gray.yml must contain location.
presentation #4 in _data/people/heather-gray.yml must contain location.
presentation #5 in _data/people/heather-gray.yml must contain location.
presentation #6 in _data/people/heather-gray.yml must contain location.
presentation #0 in _data/people/slava77.yml must contain focus-area.
presentation #0 in _data/people/sfiligoi.yml must contain meetingurl.
presentation #7 in _data/people/sfiligoi.yml must contain location.
presentation #0 in _data/people/marianstahl.yml must contain location.
presentation #1 in _data/people/marianstahl.yml must contain location.
presentation #0 in _data/people/irinaene.yml must contain location.
presentation #26 in _data/people/henryiii.yml must contain meetingurl.
presentation #0 in _data/people/irinaespejo.yml must contain project.
presentation #1 in _data/people/irinaespejo.yml must contain focus-area, project.
presentation #2 in _data/people/irinaespejo.yml must contain focus-area, project.
presentation #3 in _data/people/irinaespejo.yml must contain focus-area, project.
presentation #0 in _data/people/xiaocong-ai.yml must contain location.
presentation #1 in _data/people/xiaocong-ai.yml must contain location.
presentation #2 in _data/people/xiaocong-ai.yml must contain location.
presentation #3 in _data/people/xiaocong-ai.yml must contain location.
presentation #4 in _data/people/xiaocong-ai.yml must contain location.
presentation #5 in _data/people/xiaocong-ai.yml must contain location.
presentation #6 in _data/people/xiaocong-ai.yml must contain location.
presentation #7 in _data/people/xiaocong-ai.yml must contain location.
presentation #8 in _data/people/xiaocong-ai.yml must contain location.
presentation #0 in _data/people/cvarni.yml must contain focus-area.
presentation #0 in _data/people/xweichu.yml must contain location, project.
presentation #1 in _data/people/xweichu.yml must contain location, project.
presentation #0 in _data/people/nickcinko.yml must contain location.
presentation #1 in _data/people/nickcinko.yml must contain location.
presentation #2 in _data/people/dcraik.yml must contain location.
presentation #4 in _data/people/dcraik.yml must contain location.
presentation #0 in _data/people/fkw888.yml must contain location, project.
presentation #1 in _data/people/fkw888.yml must contain location, project.
presentation #2 in _data/people/fkw888.yml must contain location, project.
presentation #3 in _data/people/fkw888.yml must contain location, project.
presentation #4 in _data/people/fkw888.yml must contain location, project.
presentation #5 in _data/people/fkw888.yml must contain location, project.
presentation #6 in _data/people/fkw888.yml must contain location, project.
presentation #7 in _data/people/fkw888.yml must contain location, project.
presentation #8 in _data/people/fkw888.yml must contain location, project.
presentation #9 in _data/people/fkw888.yml must contain location, project.
presentation #10 in _data/people/fkw888.yml must contain location.
presentation #11 in _data/people/fkw888.yml must contain location, project.
presentation #12 in _data/people/fkw888.yml must contain project.
presentation #14 in _data/people/fkw888.yml must contain location, project.
presentation #15 in _data/people/fkw888.yml must contain location, project.
presentation #16 in _data/people/fkw888.yml must contain location, project.
presentation #17 in _data/people/fkw888.yml must contain location, project.
presentation #18 in _data/people/fkw888.yml must contain location, project.
presentation #19 in _data/people/fkw888.yml must contain location, project.
presentation #20 in _data/people/fkw888.yml must contain location, project.
presentation #21 in _data/people/fkw888.yml must contain location.
presentation #22 in _data/people/fkw888.yml must contain focus-area, project.
presentation #23 in _data/people/fkw888.yml must contain project.
presentation #24 in _data/people/fkw888.yml must contain project.
presentation #25 in _data/people/fkw888.yml must contain location, project.
presentation #26 in _data/people/fkw888.yml must contain location, project.
presentation #27 in _data/people/fkw888.yml must contain location, project.
presentation #28 in _data/people/fkw888.yml must contain location.
presentation #29 in _data/people/fkw888.yml must contain location, project.
presentation #30 in _data/people/fkw888.yml must contain location, project.
presentation #31 in _data/people/fkw888.yml must contain location, project.
presentation #32 in _data/people/fkw888.yml must contain meetingurl, location, focus-area.
presentation #33 in _data/people/fkw888.yml must contain meetingurl, location.
presentation #34 in _data/people/fkw888.yml must contain meetingurl, location, project.
presentation #35 in _data/people/fkw888.yml must contain meetingurl, project.
presentation #36 in _data/people/fkw888.yml must contain location, project.
presentation #37 in _data/people/fkw888.yml must contain location, project.
presentation #38 in _data/people/fkw888.yml must contain project.
presentation #39 in _data/people/fkw888.yml must contain meetingurl, location.
presentation #40 in _data/people/fkw888.yml must contain project.
presentation #41 in _data/people/fkw888.yml must contain project.
presentation #42 in _data/people/fkw888.yml must contain meetingurl, location, project.
presentation #43 in _data/people/fkw888.yml must contain meetingurl, project.
presentation #44 in _data/people/fkw888.yml must contain project.
presentation #46 in _data/people/fkw888.yml must contain project.
presentation #48 in _data/people/fkw888.yml must contain location, project.
presentation #0 in _data/people/matkinso.yml must contain project.
presentation #1 in _data/people/matkinso.yml must contain project.
presentation #2 in _data/people/matkinso.yml must contain project.
presentation #3 in _data/people/matkinso.yml must contain project.
presentation #4 in _data/people/matkinso.yml must contain project.
presentation #5 in _data/people/matkinso.yml must contain project.
presentation #6 in _data/people/matkinso.yml must contain project.
presentation #7 in _data/people/matkinso.yml must contain project.
presentation #0 in _data/people/heikomuller.yml must contain project.
presentation #1 in _data/people/heikomuller.yml must contain project.
presentation #2 in _data/people/heikomuller.yml must contain project.
presentation #0 in _data/people/LincolnBryant.yml must contain location.
presentation #1 in _data/people/LincolnBryant.yml must contain location.
presentation #2 in _data/people/LincolnBryant.yml must contain location.

Add CONTRIBUTING.md

Description

As I'm not very familiar with Ruby (though I know a lock file when I see one) it would be helpful if there was a CONTRIBUTING.md for the repo that outlined the expected development cycle and testing procedures for a PR before a core dev was flagged for review.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.