Skip to content

[Onboarding Tracker] Voice Verification Code #233

Closed

Description

@albertoramosmonagas

API information

Action List

  • Get nominations of initial code owner(s) (one mandatory) (API owner)
  • Create repository
  • Update of APIBacklog.md with new status
  • Update CODEOWNERS file with PR
  • Optional: get nominations of initial Maintainers (API owner)
  • Update Maintainers.md file with PR
  • Create wiki page
  • Create mailing list
  • Create README with links to wiki page and mailing list
  • Update README with API information (API owner)
  • Update of CAMARA presentation and website

CC: @camaraproject/admins @camaraproject/api-backlog_maintainers @camaraproject/marketing_maintainers

Sandbox repository to be part of “Number Insights” subproject.

Activity

  1. hdamker commented on Jun 9, 2025

    @hdamker
    Collaborator

    Added the mailing list of sp-number-insights@lists.camaraproject.org above, as the Sandbox will be part of the Sub Project.

  2. wrathwolf commented on Jun 10, 2025

    @wrathwolf
    Contributor
  3. hdamker commented on Jun 14, 2025

    @hdamker
    Collaborator

    Repository created. CODEOWNERS file is waiting for @niu-chinauicom to accept the invitation into the CAMARA organization as member.

  4. hdamker commented on Jun 22, 2025

    @hdamker
    Collaborator

    Invitation to @niu-chinauicom expired (after 7 days). The CODEOWNERS file is with that still invalid.

    Just now renewed the invitation. @jgarciahospital do you have an option to reach out to @niu-chinauicom?

  5. albertoramosmonagas commented on Aug 1, 2025

    @albertoramosmonagas
    ContributorAuthor

    Hello @camaraproject/voice-verification-code_codeowners and @niu-chinauicom,

    As part of our effort to keep the onboarding backlog up to date, we’re reviewing trackers that appear inactive but still show open items.

    This tracker currently has pending tasks. To move forward efficiently, could you please confirm:

    Whether these tasks are still in progress and expected to be completed soon, or

    • If the tracker is outdated and can be archived accordingly.
    • If there are any blockers or if support is needed to finalize the remaining steps, we’re happy to assist.

    Remaining items identified:

    • Optional: get nominations of initial Maintainers (API owner)
    • Update Maintainers.md file with PR
    • Update README with API information (API owner)

    We aim to finalize this cleanup during the current week. Your input would be appreciated to determine the next steps.

    Best regards,

  6. albertoramosmonagas commented on Sep 24, 2025

    @albertoramosmonagas
    ContributorAuthor

    Hi @camaraproject/voice-verification-code_codeowners, any updates?

  7. hdamker commented on Oct 6, 2025

    @hdamker
    Collaborator

    @albertoramosmonagas The team @camaraproject/voice-verification-code_codeowners is empty, as @niu-chinauicom has never accepted the invitation to the CAMARA GitHub organization.

    Can you reach out the proposal owner and see if there is another codeowner or we can merge this with #256?

  8. albertoramosmonagas commented on Oct 27, 2025

    @albertoramosmonagas
    ContributorAuthor

    Hi @niu-chinauicom,

    As part of the post-fall 25 meta-release clean-up review (camaraproject/Governance#199), this tracker has been identified as inactive since 1 August 2025. The initial onboarding steps are still pending, with no recent updates on the checklist or commits recorded.

    Response window: until 24 November 2025

    Next steps:

    • If progress is shared or the remaining onboarding actions are completed within this window, the tracker will remain active.
    • If no update is received by 24 November, the API Backlog Working Group will propose to close and archive this onboarding tracker in line with the unified Clean-up Process (Governance § “Lifecycle Clean-up Process”).
    • Ownership can be transferred to another CAMARA member before archival if there is continued interest.

    Please confirm whether the current codeowners plan to continue onboarding.

  9. albertoramosmonagas commented on Nov 24, 2025

    @albertoramosmonagas
    ContributorAuthor

    Hello again @niu-chinauicom,

    Following up on my previous message, today is the deadline for responding, and we expect the PR proposing these changes to be approved on Wednesday, November 26th. We are notifying you again before closing this issue permanently. We hope to receive some kind of confirmation from you before then.

  10. albertoramosmonagas commented on Dec 18, 2025

    @albertoramosmonagas
    ContributorAuthor

    Hi @niu-chinauicom @ChinaUnicomXiaoDongrui,

    The Number Insights group is holding regular meetings. As this API is part of the same group, you should participate in these meetings or have your participation reflected in the minutes. Here is the meeting schedule so you can sign up. Remember that the group's contact email address is sp-number-insights@lists.camaraproject.org for any questions you may have.

  11. ChinaUnicomXiaoDongrui commented on Dec 19, 2025

    @ChinaUnicomXiaoDongrui

    @albertoramosmonagas hello I'm very glad that we are in contact again. Regarding the Voice Verification Code, I understand that what we need to do at present is to confirm the codeowner (discussed in here). Only when we determine the codeowner can we update the content in the repository. My colleague @niu-chinauicom is handling this matter

  12. ChinaUnicomXiaoDongrui commented on Dec 19, 2025

    @ChinaUnicomXiaoDongrui

    @hdamker Congratulations, our CAMARA Technical Steering Committee Chair.

  13. niu-chinauicom commented on Dec 19, 2025

    @niu-chinauicom
    Contributor

    @hdamker Yes, the CODEOWNERs of the Voice verification have been confirmed. Additionally, the previous invitaion link of the the Voice verification to join the organization hasexpired- could you please resend the email? Thank you!

  14. hdamker commented on Dec 19, 2025

    @hdamker
    Collaborator

    @hdamker Yes, the CODEOWNERs of the Voice verification have been confirmed. Additionally, the previous invitaion link of the the Voice verification to join the organization hasexpired- could you please resend the email? Thank you!

    @niu-chinauicom glad to hear! I can't resend the mail directly, but I have renewed your invitation to the CAMARA Organization - it is valid for 7 days. Please let me know here when you have accepted it and I will take care of the @camaraproject/voice-verification-code_codeowners team then.

  15. hdamker commented on Dec 23, 2025

    @hdamker
    Collaborator

    @niu-chinauicom CODEOWNERS file finally valid - please continue with the tasks in camaraproject/VoiceVerificationCode#2

  16. ChinaUnicomXiaoDongrui commented on Dec 24, 2025

    @ChinaUnicomXiaoDongrui

    @hdamker thanks

  17. albertoramosmonagas commented on Feb 5, 2026

    @albertoramosmonagas
    ContributorAuthor

    Hi @ChinaUnicomXiaoDongrui and @niu-chinauicom, any updates or any progress in closing the onboarding tracker?

  18. ChinaUnicomXiaoDongrui commented on Feb 6, 2026

    @ChinaUnicomXiaoDongrui

    @albertoramosmonagas hello, I am pleasure to contact you again. After our discussion, We have been through this PR (camaraproject/VoiceVerificationCode#4) to update the Maintainers.md file and the README file
    including:
    1.The maintainer of this API has been supplemented in the Maintainer.md file
    2. The description of the API has been added to the README file

  19. albertoramosmonagas commented on Feb 6, 2026

    @albertoramosmonagas
    ContributorAuthor

    Hi @ChinaUnicomXiaoDongrui, thanks for the update. I have added a comment to the PR. Once it is merged, I believe there will be nothing left to do to close the onboarding tracker. Please notify us once it is merged.

  20. ChinaUnicomXiaoDongrui commented on Feb 9, 2026

    @ChinaUnicomXiaoDongrui

    @albertoramosmonagas thanks, I want to tell you that this issue is the same as the issue of Voice Notification. My colleagues @niu-chinauicom and I will update the Contributing section as soon as possible. At the same time, when the PR is merged, we will inform you and close this issue. Thank you for your support and assistance

  21. ChinaUnicomXiaoDongrui commented on Mar 2, 2026

    @ChinaUnicomXiaoDongrui

    @hdamker @albertoramosmonagas @niu-chinauicom hello everyone, I want to say that This API, like the Voice Notification API, we first updated the MAINTAIN.md file((camaraproject/VoiceVerificationCode#7)). After waiting for the community's review, we will update the README file, including the scope section (API description) and the contribution section (regular meetings, wiki pages, mail list, etc.)

  22. ChinaUnicomXiaoDongrui commented on Mar 2, 2026

    @ChinaUnicomXiaoDongrui

    We believe that after the README file is updated, this issue can be closed. Thank you for your continuous support and assistance. We will continue to contribute our content. If you have any questions, please feel free to contact us at any time @hdamker @albertoramosmonagas @niu-chinauicom

  23. albertoramosmonagas commented on Mar 12, 2026

    @albertoramosmonagas
    ContributorAuthor

    Hi @ChinaUnicomXiaoDongrui,

    I currently see the readme with fields with the placeholder yet, like:

    • Scope: The API(s) provide(s) the API consumer with the ability to:
      §Short API scope description§ !! ⚠️ Add here a scope description according to the API proposal
      Describe, develop, document, and test the API(s)

    • and Contributing
      Meetings are held virtually
      Schedule: !! tbd
      Registration / Join !! Update this link with your meeting registration/join link and delete the task
      Minutes: Access meeting minutes !! update this link to your minutes archive page using the "Share" link and delete the task

  24. ChinaUnicomXiaoDongrui commented on Mar 13, 2026

    @ChinaUnicomXiaoDongrui

    @albertoramosmonagas yes, I know, thanks for your reminding. I have submitted the updated PR(https://github.com/camaraproject/VoiceVerificationCode/pull/8). Once it is approved, I believe I can close this issue

  25. albertoramosmonagas commented on May 5, 2026

    @albertoramosmonagas
    ContributorAuthor

    All items have been completed.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions