I2P support forum

As we already know that monotone developers gone and no more help to do any further steps.

I know monotone is the favorite of the I2P developers but the real question is: Do you think any code contributer would download a dead project code and start helping I2P?

I see its faraway from happening.

Monotone signing keys as i read SHA-1 which is insecure.

so no further features , no issues going to be solved from upstream , project dead , insecure hashes ... does that sound attractive to any coder,company,industry,tester ...?

I hope to put this change on the road map.

Alternatives i dunno much (except git) , but i have found similar and active distributed software management:-

- Fossil
- Mercurial

To my knowledge the two strong points of Monotone are that

1) it supports resume
2) supports revocation of individual signing keys

I don't know anything about Mercurial, maybe you want to help us investigate if it supports both of those?

As far as Fossil, I used it in the lab and it's very nice. It sort of supports resume, but it doesn't support revocation of individual signing keys.

Hi

Also take into account: does I2P have (functional) issues with monotone which forces us to switch?
Currently none.
So far, we can search on for a good replacement which:
- supports resume
- key signed checkins
- revocation of keys/trust function implementation
- easy migration of mtn history into new system
- easy and fast works in I2P itself

Currently none has been found which support those all.
No need to switch to a worse functional system now. As been told for >6 years now.

echelon

Thats nice then , thx echelon and zlatinb i will try to communicate with these 2 projects and see if they provide these options and why they are not (if they dont).

Tickets Done:-

Fossil ticket:

https://fossil-scm.org/forum/forumpost/d5d763b70d

Mercurial mailing list:

https://www.mercurial-scm.org/pipermail ... 24194.html

more easy possible to do it through Fossil than Mercurial.