Skip to content

Add Appsilon attribution across teal packages #1754

Closed

Description

@donyunardi

Apply consistent Appsilon attribution and collaboration updates across all eight teal packages in pharmaverse: teal, teal.code, teal.data, teal.logger, teal.reporter, teal.slice, teal.widgets, and teal.picks.

Use the relevant package name and repository URL in the wording below. Track each package's pull request in the separate tracking comment on this issue.

DESCRIPTION

  • Add Appsilon to the existing Authors@R list:

    person(
      "Appsilon Sp. z o.o.",
      email = "teal@appsilon.com",
      role = c("cph", "fnd")
    )
  • Where these contributors are already listed, update their email addresses:

    • Andre Verissimo: andre.verissimo@appsilon.com
    • Vedha Viyash: vedha@appsilon.com
    • Oriol Senan: his confirmed Appsilon email address (confirm the address before updating).
  • Preserve their existing roles and other metadata.

  • Preserve Roche's attribution and all existing individual contributor credits.

README.md

Add this collaboration statement below the introduction, before installation instructions:

teal is developed by Roche, Appsilon, and the wider open-source community. Roche and Appsilon are copyright holders of the project, which is hosted in the pharmaverse GitHub organisation.

Link Roche, Appsilon, and pharmaverse to their respective websites.

Update the Acknowledgment section with the following wording. If the section is missing, add it.

teal was created at Roche and is developed together with Appsilon and the wider open-source community. Thank you to everyone who has contributed code, reported an issue, improved the documentation, or built a module. To get involved, explore the open issues or join the #teal channel in the pharmaverse Slack.

  • Link "open issues" to the package's issue tracker and "pharmaverse Slack" to the Slack community.
  • Substitute the relevant package name for teal, keeping the remaining wording consistent. Keep the Slack channel as #teal for every package.

NEWS.md

Add these two entries under the development version:

- teal has moved to the pharmaverse GitHub organisation: https://github.com/pharmaverse/teal.
- Appsilon becomes a core contributor and joins F. Hoffmann-La Roche AG as a copyright holder of teal, working alongside the wider contributor community.
  • Substitute the relevant package name and repository URL.
  • If the migration entry was already added by a migration PR, retain it without duplicating it.

LICENSE

  • Add and Appsilon Sp. z o.o. to the existing copyright line, following the admiral format.

  • Preserve the existing copyright year:

    Copyright <existing year> F. Hoffmann-La Roche AG and Appsilon Sp. z o.o.
    

Generated documentation

  • Rebuild and review each package's documentation.
  • Verify that company attribution, contributor emails, the collaboration statement, acknowledgments, and license information appear correctly.

Activity

  1. donyunardi commented on Oct 23, 2026

    @donyunardi
    CollaboratorAuthor

    Add each package's pull request link to this table when the PR is created.

    Package Pull request
    teal #1755
    teal.code pharmaverse/teal.code#301
    teal.data pharmaverse/teal.data#396
    teal.logger pharmaverse/teal.logger#131
    teal.reporter pharmaverse/teal.reporter#472
    teal.slice pharmaverse/teal.slice#699
    teal.widgets pharmaverse/teal.widgets#370
    teal.picks pharmaverse/teal.picks#143
    teal.transform pharmaverse/teal.transform#295
  2. changed the title [-][Epic] Update Appsilon attribution across teal packages[/-] [+]Add Appsilon attribution across teal packages[/+] on Oct 23, 2026
  3. self-assigned this
    on Oct 26, 2026
  4. llrs-roche commented on Oct 28, 2026

    @llrs-roche
    Member

    FYI: Only teal.picks PR is not merged, pending an update of the @osenan email.

  5. llrs-roche commented on Oct 28, 2026

    @llrs-roche
    Member

    All PR merged now: They include also removing the CLA so it is easy for other people to contribute.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions