Skip to content

Access: accept the team invitation (write) and the editor agreement #41

Description

@mmcky

Problem. #3 said that write access came through the French translation team, but the repository gave read access only until 2026-09-23, which is why the reviews up to then came from a fork (#19/#23 and #24/#25 in round 1, then #77, #78 and #80 in round 2).

State (2026-09-23). Write access is in place, through a direct invitation to this repository.

The editor agreement. Superseded by the translation manual: How your review is used (nothing to sign).

Done when

  • repos/…/collaborators/Honaminto/permission returns write (invitation accepted)

Activity

  1. added
    maintenanceMaintenance tasks on the repository
    auditWhole-lecture human audit artefact
    on Aug 21, 2026
  2. mmcky commented on Sep 23, 2026

    @mmcky
    ContributorAuthor

    Update 2026-09-23. Both organisation invitations expired unaccepted — sent 2026-07-15 (expired 2026-07-23) and sent 2026-08-21 with the translation-team-french membership (expired 2026-08-29) — so @Honaminto still had read, and his three round-2 PRs (#77, #78, #80) again came from his fork. A direct repository invitation with write permission was sent today (expires 2026-09-30) and flagged on #80, where he is active, since the email route has not reached him. This issue can close once repos/QuantEcon/lecture-python-programming.fr/collaborators/Honaminto/permission reports write.

  3. mmcky commented on Oct 6, 2026

    @mmcky
    ContributorAuthor

    Write access has been in place since 2026-09-23, through a direct invitation to this repository, which is what the check above asks for. The editor agreement is no longer needed: the translation manual's How your review is used says there is nothing to sign. This issue is complete.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    auditWhole-lecture human audit artefactmaintenanceMaintenance tasks on the repository

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions