WIP: Add first version of the CVPR rticle model

[DunLug]

Hi, I've began to create a template for the CVPR conference's stylesheet (see http://cvpr2020.thecvf.com/submission/main-conference/author-guidelines#submission-guidelines).
It's a work in progress, I created this pull request to ask questions if necessary and to avoid somebody to make this work twice.

TODO List:

• Harmonize the API to be similar to other papers
• Check that resulting documents are compliant with the rules
• Create a good example file
• Sign the contributor agreement
• Add the journalname_article() function to R/article.R if the output format is simple enough, otherwise create a separate R/journalname_article.R.
• Add the Pandoc LaTeX template inst/rmarkdown/templates/journalname_article/resources/template.tex.
• Add a skeleton article inst/rmarkdown/templates/journalname_article/skeleton/skeleton.Rmd.
• Add a description of the template inst/rmarkdown/templates/journalname_article/template.yaml.
• Please include the document class file (*.cls) if needed, but please do not include standard LaTeX packages (*.sty) that can be downloaded from CTAN. Please keep the number of new files absolutely minimal, and also make examples minimal (e.g., if you need a .bib example, try to only leave one or two bibliography entries in it, and don't include one hundred items in it without using all of them).
• Update Rd and namespace (could be done by devtools::document()).
• Update NEWS.
• Update README with a link to the newly supported journal.
• Add a test to tests/testit/test-formats.R.
• Add your name to the list of authors Authors@R in DESCRIPTION. You don't need to bump the package version in DESCRIPTION.

Issues

About the document usage, I don't understand how to tell knitr to search sty files inside the inst folder. I checked it in acm_article example but it doesn't seems to work either.

[cderv]

@DunLug where are you on this PR ?
I see that there is some unchecked boxes on your todolist. Do you plan on finishing it ?

In the meantime, if it is not yet ready for review, how about converting if to a draft PR ? You'll then change the status when ready to be reviewed so we know when to look

Thank you !

[DunLug]

Hi @cderv,
I'm really sorry I forgot about this pull request.
I'm currently finishing my thesis so I don't think I'll be able to work on it for now, so I convert it to a draft PR and update it after my PhD is done.
Thanks for your message

[cderv]

That is ok. Thank you !
We hope you'll find time to finish it. Cheers!

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ cderv
❌ DunLug
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cderv]

Hi,

I just have updated the branch with last change from our master. This will allow you to start on better basis for next time you'll find time to finish this contribution.

Thank you !

[cderv]

Suggested change

	- Added cvpr_article() document class
	- Added `cvpr_article()` output format for conference paper (thanks, @DunLug, #278).

[cderv]

👋 @DunLug - gettting back to you on this for a status update

I'm currently finishing my thesis so I don't think I'll be able to work on it for now, so I convert it to a draft PR and update it after my PhD is done.

Is this PR still a project you want to finish ? No pressure, just wants to known where we are at

[DunLug]

Hi, @cderv,
I kept this project in my list but found no time. Maybe this PR can be archived for now. I think it's better to create a new merge request when I'll have time to really update the code.

[cderv]

I passed it to draft. When you have time (or someone else), this one can be rebased, or closed and a new one started. Thanks for the reply