Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Onboarding Tracker] Traffic Influence #176

Open
6 of 11 tasks
jgarciahospital opened this issue Feb 14, 2025 · 3 comments
Open
6 of 11 tasks

[Onboarding Tracker] Traffic Influence #176

jgarciahospital opened this issue Feb 14, 2025 · 3 comments

Comments

@jgarciahospital
Copy link
Collaborator

jgarciahospital commented Feb 14, 2025

API information

Action List

  • Create repository
  • Update of APIBacklog.md with new status
  • Get nominations of initial code owner(s) (one mandatory) (API owner)
  • Update CODEOWNERS file with PR (@FabrizioMoggio as initial codeowner)
  • 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

@jgarciahospital
Copy link
Collaborator Author

@FabrizioMoggio I have included provisionally the email list of Edge, do you also want to maintain that subproject? (independant repo but same subproject, meetings, mailist...)

@hdamker
Copy link
Collaborator

hdamker commented Feb 14, 2025

@FabrizioMoggio I have included provisionally the email list of Edge, do you also want to maintain that subproject? (independant repo but same subproject, meetings, mailist...)

Repository created, including an issue with first tasks: camaraproject/TrafficInfluence#1 for @FabrizioMoggio

@FabrizioMoggio
Copy link
Collaborator

@FabrizioMoggio I have included provisionally the email list of Edge, do you also want to maintain that subproject? (independant repo but same subproject, meetings, mailist...)

Yes, the TI API is still included in the Edge Cloud WG. In my understanding everything should proceed as before, in terms of collaboration with the Edge cloud WG and contributors, it is just a different Repo.

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

No branches or pull requests

3 participants