Misc updates

_bookdown.yml

@@ -44,5 +44,6 @@ rmd_files: ["index.Rmd",
            "c-and-fortran.Rmd",
            "mavericks.Rmd",
            "debug-rd-links.Rmd",
-           "news-for-bookdown.Rmd"]
+           "news-for-bookdown.Rmd",
+           "references.Rmd"]
 clean: [packages.bib]

debug-rd-links.Rmd

@@ -27,7 +27,7 @@ W  checking Rd cross-references (<...>ms)
 ## What worked
 
 First, the `SummarizedExperiment` package was added to the `Depends:` section
-of the DESCRIPTION file.
+of the `DESCRIPTION` file.
 
 ```
 Depends:

description-file.Rmd

@@ -192,7 +192,7 @@ package type (i.e., `Software`, `AnnotationData`, `ExperimentData`, or
 `Workflow`). `biocViews` terms are case-sensitive.
 
 The field name "biocViews" is case-sensitive and must begin with a lower-case
-'b'. Please use a single line with biocViews seperated by commas
+'b'. Please use a single line with `biocViews` separated by commas
 
 (i.e,`biocViews: GeneTarget, SingleCell`).
 

general-package-development.Rmd

@@ -42,8 +42,12 @@ Do not use filenames that differ only in case, as not all file systems are case-
 
 ### Package size {#package-size}
 
-The source package resulting from running `R CMD build` should occupy less than 5 MB on disk.
-If your package includes (e.g. in the vignettes) some screenshots, this limit can be reached quite quickly. Their size can be reduced (often as much as 70%) in a lossy but quality-preserving manner by using tools such as [pngquant](https://pngquant.org/) (available as a command line utility and as a GUI on most systems).
+The source package resulting from running `R CMD build` should occupy less than
+5 MB on disk. If your package includes some screenshots (e.g., in the
+vignettes), this limit can be reached quite quickly. Their size can be reduced
+(often as much as 70%) with lossy compression using tools such as
+[pngquant](https://pngquant.org/) (available as a command line utility and as a
+GUI on most systems).
 
 ### Check duration {#check-duration}
 

git-version-control.Rmd

@@ -79,19 +79,20 @@ Builds occur once per day, and take approximately 24 hours. See the
 
 Traditional Annotation packages are not stored in GIT due to the size of
 annotation files. To update an existing Annotation package please send an email
-to maintainer@bioconductor.org. A member of the Bioconductor team will be in
+to <maintainer@bioconductor.org>. A member of the Bioconductor team will be in
 contact to receive the updated package.
 
 Newer annotation packages can be stored in GIT as it is a requirement to use the
 `r BiocStyle::Biocpkg("AnnotationHub")` server hosted data. The larger sized
 files are not included directly in the package. To contribute a new Annotation
-package please contact hubs@bioconductor.org for guidance and read the
+package please contact <hubs@bioconductor.org> for guidance and read the
 documentation on [Create A Hub Package][].
 
 Currently direct updates to annotation packages, even those stored on git, are
 not supported. If you wish to updated an annotation package, make required
 changes and push to git.bioconductor.org. Then send an email to
-hubs@bioconductor.org or maintainer@bioconductor.org requesting the package be propagated.
+<hubs@bioconductor.org> or <maintainer@bioconductor.org> requesting the package
+be propagated.
 
 ## Subversion to Git Transition
 
@@ -704,7 +705,7 @@ _Bioconductor_ repositories.
 
 __Goal:__ You want to start fresh after failing to resolve conflicts
 or some other issue. If you intend to go nuclear, please contact the
-bioc-devel@bioconductor.org mailing list.
+<bioc-devel@bioconductor.org> mailing list.
 
 #### Force _Bioconductor_ `devel` to GitHub `devel`
 
@@ -1058,9 +1059,9 @@ maintain the package and avoid deprecation and removal.
    package be updated.  Include the package name and the contact information for
    the new maintainer.
 
-3. Update Package DESCRIPTION file
+3. Update Package `DESCRIPTION` file
 
-   The DESCRIPTION file of the package should be updated to the new maintainer
+   The `DESCRIPTION` file of the package should be updated to the new maintainer
    information and pushed to the Bioconductor git.bioconductor.org repository.
 
 ### Remove Large Data Files and Clean Git Tree
@@ -1435,7 +1436,7 @@ repository.
 #### More questions?
 
 If you have additional questions which are not answered here already,
-please send an email to bioc-devel@bioconductor.org.
+please send an email to <bioc-devel@bioconductor.org>.
 
 ### Helpful resources:
 

important-bioc-features.Rmd

@@ -3,10 +3,10 @@
 ## biocViews {#biocviews}
 
 Packages added to the _Bioconductor_ Project require a `biocViews:`
-field in their DESCRIPTION file.  The field name "biocViews" is
+field in their `DESCRIPTION` file.  The field name "biocViews" is
 case-sensitive and must begin with a lower-case 'b'.
 
-biocViews terms are "keywords" used to describe a given package. They
+`biocViews` terms are "keywords" used to describe a given package. They
 are broadly divided into four categories, representing the type of
 packages present in the _Bioconductor_ Project 
 
@@ -15,29 +15,29 @@ packages present in the _Bioconductor_ Project
 3. Experiment Data
 4. Workflow
 
-biocViews are available for the [release][release-biocviews] and [devel][biocViews] branches of
-_Bioconductor_. The devel branch has a check box under the tree
-structure which, when checked, displays biocViews that are defined but
-not used by any package, in addition to biocViews that are in use. See also
-[description section](#description-biocviews)
+`biocViews` are available for the [release][release-biocviews] and
+[devel][biocViews] branches of _Bioconductor_. The devel branch has a check box
+under the tree structure which, when checked, displays `biocViews` that are
+defined but not used by any package, in addition to `biocViews` that are in use.
+See also [description section](#description-biocviews)
 
 ### Motivation {#biocviews-motivation}
 
-One can use biocViews for two broad purposes.
+One can use `biocViews` for two broad purposes.
 
 1. A researcher might want to identify all packages in the
    _Bioconductor_ Project which are related to a specific purpose.
    For example, one may want to look for all packages related to "Copy
    Number Variants".
 
 2. During development, a package contributor can "tag" their package
-   with biocViews so that when someone looking for packages (like in
+   with `biocViews` so that when someone looking for packages (like in
    scenario 1) can easily find their package.
 
 ### biocViews during new package development {#biocviews-pkg-devel}
 
 Visit the ['devel' biocViews][biocViews] when you are in the process of
-adding biocViews to your new package. Identify as many terms as
+adding `biocViews` to your new package. Identify as many terms as
 appropriate from the hierarchy. Prefer 'leaf' terms at the end of the
 hierarchy, over more inclusive terms. Remember to check the box
 displaying all available terms.
@@ -46,30 +46,30 @@ Please Note:
 
 1. Your package will belong to only one part of _Bioconductor_ Project
    (Software, Annotation Data, Experiment Data, Workflow), so choose only
-   biocViews from that category.
+   `biocViews` from that category.
 
-2. biocViews listed in your package must match exactly (e.g.,
-   spelling, capitalization) the terms in the biocViews hierarchy.
+2. `biocViews` listed in your package must match exactly (e.g.,
+   spelling, capitalization) the terms in the `biocViews` hierarchy.
 
 When you submit your new package for review , your package is checked
 and built by the _Bioconductor_ Project.  We check the following for
 biocViews:
 
-1. Package contributor has added biocViews.
+1. Package contributor has added `biocViews`.
 
-2. biocViews are valid.
+2. `biocViews` are valid.
 
-3. Package contributor has added biocViews from only one of the categories.
+3. Package contributor has added `biocViews` from only one of the categories.
 
-If you receive a "RECOMMENDED" direction for any of these biocViews
+If you receive a "RECOMMENDED" direction for any of these `biocViews`
 after you have submitted your package, you can try correcting them on
 your own following the directions given here or ask your package
 reviewer for more information.
 
-If a developer thinks a biocViews term should be added to the current acceptable
-list, please email bioc-devel@r-project.org requesting the new biocView, under
-which hierarchy the term should be placed, and the justification for the new
-term.
+If a developer thinks a `biocViews` term should be added to the current
+acceptable list, please email <bioc-devel@r-project.org> requesting the new
+`biocViews` term, under which hierarchy the term should be placed, and the
+justification for the new term.
 
 
 ## Common Bioconductor Methods and Classes {#reusebioc}

index.Rmd

@@ -5,6 +5,8 @@ author:
   - Daniela Cassol
   - Johannes Rainer
   - Lori Shepherd
+  - Marcel Ramos Pérez
+  - Martin Morgan
 date: "`r Sys.Date()`"
 site: bookdown::bookdown_site
 documentclass: book
@@ -17,7 +19,7 @@ description: "This is a minimal example of using the bookdown package to write a
 # Welcome {-}
 
 ```{r, fig.align='center', echo=FALSE, out.height="200px"}
-knitr::include_graphics("https://raw.githubusercontent.com/Bioconductor/BiocStickers/master/Bioconductor/Bioconductor.png")
+knitr::include_graphics("https://raw.githubusercontent.com/Bioconductor/BiocStickers/devel/Bioconductor/Bioconductor.png")
 ```
 
 ## Introduction {.unnumbered #intro}

install-file.Rmd

@@ -11,7 +11,7 @@ already there.
 
 Specifying this requirement does not guarantee that _Bioconductor_ will agree to
 install the external system requirement. It is encouraged to discuss any
-additional system requirements on the bioc-devel@r-project.org before
+additional system requirements on the <bioc-devel@r-project.org> before
 development.
 
 System requirements should never be exclusive to a particular

non-software-packages.Rmd

@@ -64,11 +64,11 @@ expected the majority of vignette code chunks are evaluated.
  ideally workflows make use of existing data in a Bioconductor repository or on
  the web; the workflow package itself should not contain large data files.
 
-* In the DESCRIPTION file, include the line "BiocType: Workflow". Please also
-  include a detailed Description field in the DESCRIPTION file. The DESCRIPTION
-  file should contain biocViews which should be from the [Workflow
-  branch][workflow-views]. If you think a new term is relevant please reach out to
-  <lori.shepherd@roswellpark.org>.
+* In the `DESCRIPTION` file, include the line "BiocType: Workflow". Please also
+  include a detailed Description field in the `DESCRIPTION` file. The
+  `DESCRIPTION` file should contain `biocViews` which should be from the [Workflow
+  branch][workflow-views]. If you think a new term is relevant please reach out
+  to <lori.shepherd@roswellpark.org>.
 
 * Submit the package to the [GitHub submission tracker][tracker] for a formal
   review. Please also indicate in the tracker issue that this package is a

package-end-of-life.Rmd

@@ -33,10 +33,10 @@ packages.
 
 2. Inactive maintainer
 
-   The maintainer listed in the DESCRIPTION file must be responsive to
+   The maintainer listed in the `DESCRIPTION` file must be responsive to
    questions on the support site, package-related email from users and
    Bioconductor team members, package-related errors in the build
-   system, and requests for bug fixes. The email in the DESCRIPTION must also
+   system, and requests for bug fixes. The email in the `DESCRIPTION` must also
    remain a valid, active email.
 
 
@@ -122,7 +122,7 @@ devel 3.3 would make the following transitions:
            .Deprecated(msg=paste(strwrap(msg, exdent=2), collapse="\n"))
        }
 
-3. Add the following annotation to the package DESCRIPTION file.
+3. Add the following annotation to the package `DESCRIPTION` file.
 
       PackageStatus: Deprecated
 
@@ -135,9 +135,9 @@ devel 3.3 would make the following transitions:
 
 A deprecated package can be un-deprecated and removed from the End of Life
 process if it is fixed before the next Bioconductor release. To have a
-package un-deprecated, please contact maintainer@bioconductor.org. If a package
-is already in the defunct stage; the package will mostly likely be requested to
-go through the new package submission process again.
+package un-deprecated, please contact <maintainer@bioconductor.org>. If a
+package is already in the defunct stage; the package will mostly likely be
+requested to go through the new package submission process again.
 
 ## 'Orphaned' packages
 
@@ -148,8 +148,8 @@ no response from a maintainer to the emails sent out from the core team, the
 package is considered 'orphaned'. Occasionally, members of the Bioconductor
 community reach out to take over maintenance of an 'orphaned' package. The
 interested replacement maintainer is asked to email the original maintainer and
-maintainer@bioconductor.org, to formally request permission to take over. Unless
-there is an explicit request for a package to be retired, Bioconductor will
-grant access to the interested replacement maintainer in accordance with open
-source software licenses that Bioconductor packages require and
+<maintainer@bioconductor.org>, to formally request permission to take over.
+Unless there is an explicit request for a package to be retired, Bioconductor
+will grant access to the interested replacement maintainer in accordance with
+open source software licenses that Bioconductor packages require and
 [package naming policy](#naming) that maintainers agree to upon submission.

package-name.Rmd

@@ -6,7 +6,7 @@ should not already exist as a current package (case-insensitive) in
 [_Bioconductor_][biocViews] nor [CRAN][CRAN pkgs]. Reusing
 archived or deprecated package names is also strongly discouraged and often will
 not be allowed. Before submission please inquire about using a legacy package
-name on the bioc-devel@r-project.org mailing list.
+name on the <bioc-devel@r-project.org> mailing list.
 
 An easy way to check whether your name is already in use is to check that the
 following command fails using the ['devel' version][] of Bioconductor: