I would like to propose myself @sicoyle as a Maintainer of the dapr/docs repository.
I am a maintainer of dapr/components-contrib, dapr/dapr-agents, and dapr/python-sdk and have been a consistent contributor to dapr/docs alongside my work. Recent contributions include:
Ensuring that every component upon official Dapr Release is covered by the docs and registered properly within runtime and have created a ton of issues in the docs in support of this effort, as well as from the Dapr Agents community: https://github.com/dapr/docs/issues?q=is%3Aissue%20state%3Aopen%20author%3Asicoyle
dapr/docs#5216: Conversation API updates following a Discord user feedback
dapr/docs#5160: MCPServer resource type docs
dapr/docs#5120: Dapr Agents v1.0 release announcements/docs updates
dapr/docs#5034: Updates to Dapr Agents API
dapr/docs#4794: Correcting component docs after cross checking runtime registration for my endgame task for the official Dapr release
Various PR reviews:
dapr/docs#5159: New component for v1.19
dapr/docs#5108: Dapr Agents new LLM client
dapr/docs#4311: AWS IAM docs
I also regularly get tagged on AWS doc updates relating to the authentication profiles by Mark :)
PRs: https://github.com/dapr/docs/pulls?q=is%3Apr+author%3Asicoyle+is%3Aclosed
Issues: https://github.com/dapr/docs/issues?q=is%3Aissue%20state%3Aopen%20author%3Asicoyle
My feature work across the repos I maintain frequently ships with paired documentation updates, and I have demonstrated the technical judgment and consistent contribution pattern expected of a dapr/docs maintainer.
Requesting nominating/approving votes from: @msfussell, @yaron2, @marcduiker.
I would like to propose myself @sicoyle as a Maintainer of the dapr/docs repository.
I am a maintainer of dapr/components-contrib, dapr/dapr-agents, and dapr/python-sdk and have been a consistent contributor to dapr/docs alongside my work. Recent contributions include:
Ensuring that every component upon official Dapr Release is covered by the docs and registered properly within runtime and have created a ton of issues in the docs in support of this effort, as well as from the Dapr Agents community: https://github.com/dapr/docs/issues?q=is%3Aissue%20state%3Aopen%20author%3Asicoyle
dapr/docs#5216: Conversation API updates following a Discord user feedback
dapr/docs#5160: MCPServer resource type docs
dapr/docs#5120: Dapr Agents v1.0 release announcements/docs updates
dapr/docs#5034: Updates to Dapr Agents API
dapr/docs#4794: Correcting component docs after cross checking runtime registration for my endgame task for the official Dapr release
Various PR reviews:
dapr/docs#5159: New component for v1.19
dapr/docs#5108: Dapr Agents new LLM client
dapr/docs#4311: AWS IAM docs
I also regularly get tagged on AWS doc updates relating to the authentication profiles by Mark :)
PRs: https://github.com/dapr/docs/pulls?q=is%3Apr+author%3Asicoyle+is%3Aclosed
Issues: https://github.com/dapr/docs/issues?q=is%3Aissue%20state%3Aopen%20author%3Asicoyle
My feature work across the repos I maintain frequently ships with paired documentation updates, and I have demonstrated the technical judgment and consistent contribution pattern expected of a dapr/docs maintainer.
Requesting nominating/approving votes from: @msfussell, @yaron2, @marcduiker.