Update libcifpp fork's ownership

[martin-s-a]

It will be more stable if this dependency was owned by I2PC instead of me, as I recently thought of changing username and that would break all existing installations.

This change would still require everyone to pull the latest devel version to work, but it would be the last time that is ever required (unless I2PC changes name, which I think is unlikely).

I can wait for the next release to merge this so it is bundled into it and affects the minimum amount of users possible.

Note: The GitHub Actions pipeline will obviously fail until the name change is actually made, which I haven't done yet.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[albertmena]

But have we to create the I2PC/libcifpp repository? as a fork?

[martin-s-a]

But have we to create the I2PC/libcifpp repository? as a fork?

No, from my fork, in repository settings, I can choose to transfer the ownership of the repo to I2PC. An email will reach the associated account for confirmation, and, if you accept it, the switch is made.

[oierlauzi]

I have forked libcifcpp inside I2PC to enable this change

[oierlauzi]

But have we to create the I2PC/libcifpp repository? as a fork?

No, from my fork, in repository settings, I can choose to transfer the ownership of the repo to I2PC. An email will reach the associated account for confirmation, and, if you accept it, the switch is made.

Ups, did not see this. Deleting the fork then

[oierlauzi]

Do not merge before the ownership is transferred

[oierlauzi]

Updated v3.24.12.0-Poseidon tag