https://github.com/chobbes/icfp-captioning

https://github.com/chobbes/icfp-captioning

Science Score: 10.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
    2 of 7 committers (28.6%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (10.3%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

Basic Info
  • Host: GitHub
  • Owner: Chobbes
  • Default Branch: main
  • Size: 3.22 MB
Statistics
  • Stars: 0
  • Watchers: 4
  • Forks: 5
  • Open Issues: 0
  • Releases: 0
Created almost 4 years ago · Last pushed over 3 years ago
Metadata Files
Readme

README.org

* TL;DR?

Make sure you get accurate captions for your talk by following these instructions!

1. Find your directory, if your directory is missing feel free to create one by copying another.
2. Inside your directory is a ~caption_wordlist.csv~ file.
3. Edit ~caption_wordlist.csv~ with terms and their pronunciation, as well as any extra details that might help the captioners.
   - You can use libreoffice to edit this.
   - Include words that the average person wouldn't know. Anything spell-check wouldn't understand by default is a good idea.
     + Names of author's and anybody who will be cited
     + Names of tools
     + Names of programming languages
     + Technical terminology
4. Feel free to add your slides or paper, we can pass these off to the captioner as well
5. Submit a pull request to this repository with your updated CSV file
   - If you don't know how to submit a PR, feel free to make an issue on github

More detailed notes below :).

* Instructions

Real-time captioning for ICFP will be provided by human captioners. To
ensure that your talk is captioned correctly it is important to
provide a list of any uncommon words and technical terms that will be
used in your talk ahead of time, as well as the pronunciation of these
terms --- this will allow the captioners to prepare ahead of time and
add the terms to their personal dictionary, ensuring that they can
quickly and accurately caption your talk.

** What words should we include?

A good rule of thumb would be anything that the average person
wouldn't know about and anything that spell-check wouldn't know by default:

- Names of author's and anybody who will be cited
- Names of tools
- Names of programming languages
- Technical terminology

The captioners are skilled professionals, but may not be aware of
terms in our field, and may mishear them unless given context ahead of
time.

** How do we contribute?

Each talk should have a directory, and within that directory there is
a CSV file. The *most* important fields in this CSV file are the term
and pronunciation columns, please fill these in and submit a *pull
request* to the repository.

The CSV file has the following format:

|------------------+-----------------------------+----------------------------------------------------------------------------------------------------------------------------------+-------+-----------------------------------------|
| Term             | Pronunciation               | Context / Example Usage                                                                                                          | Notes | Tags                                    |
|------------------+-----------------------------+----------------------------------------------------------------------------------------------------------------------------------+-------+-----------------------------------------|
| itree            | eye-tree                    | shorthand for "interaction tree"                                                                                                 |       | semantics                               |
| interaction tree | interaction tree            |                                                                                                                                  |       | semantics                               |
| semantics        |                             |                                                                                                                                  |       | semantics, theory                       |
| compiler         | com-pile-er                 | A program which translates code in one programming language into another, often performing optimizations to make the code faster |       | compilers                               |
| frontend         | front end                   |                                                                                                                                  |       | compilers                               |
| backend          | back end                    |                                                                                                                                  |       | compilers                               |
| vellvm           | vel-um                      | Name of the project, it's a formal semantics of LLVM IR                                                                          |       | compilers, semantics, projects          |
| IR               | I.R.                        | Shorthand for "intermediate representation", a programming language                                                              |       | compilers                               |
| LLVM             | L.L.V.M.                    | A compiler infrastructure project that provides                                                                                  |       | compilers                               |
| LLVM IR          | L.L.V.M. I.R.               |                                                                                                                                  |       | compilers                               |
| clang            | clang, sometimes "see-lang" |                                                                                                                                  |       | compilers, projects                     |
| Coq              | Like in peacock             | Coq is a proof assistant / programming language that is used to implement vellvm, "we have implemented and proved this in Coq"   |       | proof assistants, programming languages |
| monad            | moe-nad                     | "because itrees are a monad..."                                                                                                  |       | theory                                  |
| monadic          | moe-nad-ick                 | "we have a monadic interface..."                                                                                                 |       | theory                                  |
| lambda           | lam-duh                     | Used to refer to anonymous functions "we have a lambda function here"                                                            |       | theory                                  |
| lambda calculus  | lam-duh calculus            |                                                                                                                                  |       | theory                                  |
|------------------+-----------------------------+----------------------------------------------------------------------------------------------------------------------------------+-------+-----------------------------------------|

The *most* important fields are the term and pronunciation columns, please fill these in!

In addition, it may be helpful to provide some example uses and
context can also be helpful for understanding how the term might be
used, and you can leave any other notes you have about the term in the
notes column.

For pronunciation feel free to use IPA, or whatever works for you for
conveying pronunciation.

The tags column is also optional, but adding some tags about the usage
of the term can help us organize a larger glossary to provide to
captioners for future conferences.

** What else can I do?

Uploading your slides / paper into your directory can also be
helpful. This will give captioners access to your talk and they can
have a backup copy to follow along to, and we may skim through the
talks ahead of time for any extra keywords that might be worth adding.

Owner

  • Name: Calvin Beck
  • Login: Chobbes
  • Kind: user
  • Location: Philadelphia

GitHub Events

Total
Last Year

Committers

Last synced: 12 months ago

All Time
  • Total Commits: 113
  • Total Committers: 7
  • Avg Commits per committer: 16.143
  • Development Distribution Score (DDS): 0.637
Past Year
  • Commits: 0
  • Committers: 0
  • Avg Commits per committer: 0.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Calvin Beck h****s@u****a 41
KatStark K****k@h****k 38
Vadim Zaliva l****d@c****g 24
Apoorv Ingle 1****m 4
Kenji Maillard k****i@m****e 2
Arnaud Spiwack a****k@t****o 2
Tomasz Drab t****r@c****l 2
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 12 months ago

All Time
  • Total issues: 0
  • Total pull requests: 5
  • Average time to close issues: N/A
  • Average time to close pull requests: about 4 hours
  • Total issue authors: 0
  • Total pull request authors: 3
  • Average comments per issue: 0
  • Average comments per pull request: 0.6
  • Merged pull requests: 5
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
  • kyoDralliam (2)
  • tomaszdrab (2)
  • aspiwack (1)
Top Labels
Issue Labels
Pull Request Labels