Add DorotaC to the RISC-V team

[dcz-self]

I'm nominating myself to the RISC-V team.

The immediate reason is that I want to fix and release the gd32vf103xx-hal crate, rather than fork it and let changes fall into obscurity. The crate seems to be unmaintained for 2 years, with no release for 4 years. I was recommended to join the RISC-V team in order to get merge rights.

I'm also going to be completely satisfied if this application gets rejected in favor of adding me to the dead crate's maintainers directly. I intend to bring it to HAL v1.0 and stay on top of MRs.

Either way, the project I'm working on also requires fixes to the USB driver, so I'd use my team powers to take care of that too.

[dcz-self]

@Disasm @dkhayes117 @rmsyn I think this is relevant to you as those involved in the crate.

[jonathanpallant]

Generally, membership of Embedded Devices Working Group teams is on the basis of a history of good quality pull requests and review comments. As you're asking for permissions to modify a HAL, which fall outside the purview of the Embedded Devices Working Group, it's probably better to just ask for write permissions on the riscv-rust/gd32vf103xx-hal repo over in that org. I see that they claim that the EDWG's riscv-team maintains that repo, but I don't think that's true - or, if it was, it was an accidental overlap in team memberships rather than an explicit decision for an Embedded Devices Working Group team to start maintaining chip-specific HALs.

[romancardenas]

I agree. It appears that in the past, the same individuals from the RISC-V team maintained the HAL crates for RISC-V chips in a different organization. Now, it makes more sense to handle maintainer duties in the riscv-rust organization in an isolated manner. I will set up the environment of the riscv-rust organization for this.

EDIT: I opened a PR to clarify how that riscv-rust organization manages PAC and HAL crates: riscv-rust/teams#1