otrv4 / otrv4

Off-the-Record Messaging Protocol version 4. -This is a draft- This repository is a mirror of http://bugs.otr.im/otrv4/otrv4

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Recover rights of github.com/off-the-record and update

Neustradamus opened this issue · comments

Recover rights :

Update old projects on it (libotr and otrbot)

Move all projects on only one github, old address will be not lost, there will be a redirection.

OTR.im website is missing on Github.

Update this page: http://otr.im/clients.html
-> Psi is missing
-> CoyIM is missing

Recover rights :
https://github.com/off-the-record

That seems to be a mirror, so no need to recover and idk why the need to recover.

Move all projects on only one github, old address will be not lost, there will be a redirection.
OTR.im website is missing on Github.
Update this page: http://otr.im/clients.html
-> Psi is missing
-> CoyIM is missing

This is unrelated to this repo. This repo is about the specification. The OTRv3 and OTRv2 code is located here: https://bugs.otr.im/ and any issue regarding the website otr.im should be placed there, where the website resides. Eventually, we will move everything to one website and one repo, but this is not the place for those issues.

Thanks,

Yes, there is not the otr.im website project here, it is for this, I have done this ticket here... you can create website project and move this ticket to the new project :)

The other organization on github is managed by some people from team, better to recover and have only one space with the last code from old libotr (4.1.1) in more that libotr-ng.
And otrbot is not here.

It is better, for have all in off-the-record organization (old and new), the main project is Off-the-Record Messaging (OTR).

Like I have said, move will be easy and not link lost.
Example: otrv4/otrv4 moves off-the-record/otrv4, there will be a redirection (no link losts).

  • website (missing)
  • pidgin-otr (missing)
  • libotr (not up-to-date)
  • otrbot (I am not sure)
  • otrv4
  • libotr-ng
  • pidgin-otrng
  • ed448
  • otrng-prekey-server
  • OTRv4-properties
  • libgoldilocks
  • otr4
  • OTRv4-over-XMPP
  • otrv4-client-imp-recommendations
  • pidgin-otrng-testing
  • otrv4-prekey-server
  • prekey-server-docker-compose
  • prekey-server-xmpp
  • libotr-ng-toolkit
  • little-ed448-Goldilocks
  • otrv4_reference_design

Hey,

The other organization on github is managed by some people from team, better to recover and have only one space with the last code from old libotr (4.1.1) in more that libotr-ng.
And otrbot is not here.

The repositories here are related to OTR version 4, hence the name 'OTRv4'. We don't have a place for all the OTR code from previous versions.

The other organization on github is managed by some people from team, better to recover and have only one space with the last code from old libotr (4.1.1) in more that libotr-ng.
And otrbot is not here.

The otrbot is related to OTRv3 and OTRv2, not to OTRv4, which is what this organization is about.

It is better, for have all in off-the-record organization (old and new), the main project is Off-the-Record Messaging (OTR).

As stated, the organization here is OTRv4, hence the name 'OTRv4'. In the future, we might have a global place for all OTR; but it is not here.

Example: otrv4/otrv4 moves off-the-record/otrv4, there will be a redirection (no link losts).

As @DrWhax have said, it seems like off-the-record is an out-dated mirror and nobody really needs access to it. The OTRv4 organization (which is only for code and specs related to OTRv4) will remain here until we have a global place for OTR, which will not be off-the-record repo.

Thanks,

Bwt @Neustradamus , you can report issues for the website here: https://bugs.otr.im/infra/otr-im-website

Hope that helps :)

@Neustradamus I added Psi: http://otr.im/clients.html

Do you think Psi+ is needed there as well?

@claucece, thanks and yes :)
Note that normally the OTR plugin is integrated in Psi and Psi+, except if it is not compiled by maintainer.