Replicant source code hosting and RMLL 2015

As mentioned a few months ago, Gitorious is closing down and even though the Replicant project page can still be reached there, cloning the repositories has been broken for some time. After thoroughly evaluating all the hosting possibilities for Replicant (thanks to the many suggestions from the community!), we have finally reached a decision. We didn’t want to be affiliated with a hosting provider that doesn’t match Replicant’s core values, that are all about software freedom. In addition, it seemed better not to be hosted by a third party, to ensure the security of the source code. These criteria left us with very little choice available, but thankfully, we were able to comply with them, as the Replicant source code is now hosted by the Free Software Foundaton, at!

We are very thankful to the FSF for providing us with that solution and the hardware required for our needs (the Replicant source code is very large). Eventually, we will move all the Replicant source there, as opposed to only the parts of CyanogenMod and AOSP that we modified, so that we don’t have to rely on any third party at all.

With all those discussions going on, I almost forgot to mention that I will be taking part in RMLL/LSM again this summer. The event takes place in Beauvais, France (near Paris) from July 6th to 10th (sorry for the short notice). I will be presenting two talks there, one about the overall state of the Replicant project, in French, and one about liberating mobile devices from the ground up, in English. In addition, I will be taking part in a workshop on free embedded devices in room 219, were I will show a few embedded devices running free software.

As usual, everyone is welcome to come, say hi and have a nice chat. It’s also possible to verify the Replicant release GPG key in person to trust the verification of our images releases. And of course, I’ll be available to help install Replicant on supported devices!

11 thoughts on “Replicant source code hosting and RMLL 2015

  1. Well, the certificate is the same that we use on other Replicant websites, it’s signed by CaCert by the way. I don’t see why the algorithm we use (TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, 128 bits, TLS 1.2) was disabled on your side. Is there any reason why we shouldn’t use it?

  2. PS. Is the FSF hosting using cgit? Or something else? Thanks!

    cgit seems like a great solution for self-hosting of Git repos in a publicly accessible form. I plan to set up my own personal cgit instance later this year.

  3. Do you have notes and/or video of your Liberating Mobile Devices From The Ground up presentation which you could share, please? I would love to see them. Thanks!

  4. Firefox doesn’t like the certificate on Can you contact FSF and see if that can be fixed? Thanks. uses an invalid security certificate.

    The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure.

    (Error code: sec_error_cert_signature_algorithm_disabled)

  5. Hi,

    I would like to know on which next recent models of phone are you working?

    Cause i wanted to buy a Samsung S3 but i find it only in used (i would like to buy a new S3, not already used by someone).

    Can you say to me the next recent models and when will there be a version of Replicant for these ones, cause i would like to buy a phone and install Replicant

    Thank you and congratulations for your work!

  6. I have a conflict of interest for the Replicant Wikipedia article, so I’d rather not update it myself. Also, I believe it is a bad idea to have supported devices status on the Wikipedia page, since this is likely to change and not be updated according to the Replicant wiki, in addition to duplicating the information. IMO, we should rather have information that is factual and isn’t likely to change, such as the various Replicant releases. It would make sense to say that release foo added support for device bar, etc.

  7. Thank you and the FSF very much for pushing that forward.
    In fact the situaton of source code hosting seems better than it was before.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.