Everyone who posted in previous weeks is welcome back this week, as always.
OK! So, as usual:
My static blog generator: blogcpp.org (Mercurial repository). I have updated it yesterday, a new release is scheduled for September or so, depending on how much I want to work on it. I would love to have a search functionality in it...
My bookmarks synchronization service: ymarks.org (Mercurial repositories). Currently, it has 43 users on Chrome and 67 on Firefox (yes, the one review was a bug... that happens when nobody helps me). This is your chance to participate in an upcoming cross-browser project. If you feel like it: I planned an Android client months ago as well, but I won't manage to do that in 2018 anymore.
My Twitter client: ZenTweet.net (Mercurial repository). If you have ever wondered how Twitter's API works, this is for you. You might see that the repository and the code are German-only ... this could be an easy first task? ;-)
Mercurial is common enough (used by Mozilla and similar projects) to be an interesting VCS for projects which could need contributors (I have others on Darcs and SVN), it has a good, mature and very alive ecosystem (unlike Bazaar), it has a lot of useful plug-ins (e.g. for history rewriting) and not a totally broken branching/merging mechanism (like Git).
Edit: at least I have managed to fsck up a Git repository twice while merging two incompatible branches. Never happened with Mercurial.
OK! So, as usual:
Might I ask why you use Mecurial for your projects?
Mercurial is common enough (used by Mozilla and similar projects) to be an interesting VCS for projects which could need contributors (I have others on Darcs and SVN), it has a good, mature and very alive ecosystem (unlike Bazaar), it has a lot of useful plug-ins (e.g. for history rewriting) and not a totally broken branching/merging mechanism (like Git).
Edit: at least I have managed to fsck up a Git repository twice while merging two incompatible branches. Never happened with Mercurial.
Ahh I see.