Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update redsolution-jitsi-merge with recent changes #4

Open
cobratbq opened this issue Jun 28, 2020 · 2 comments
Open

Update redsolution-jitsi-merge with recent changes #4

cobratbq opened this issue Jun 28, 2020 · 2 comments

Comments

@cobratbq
Copy link
Contributor

See ibauersachs#33 (comment) for background.
@cobratbq cobratbq mentioned this issue Jul 6, 2020
Merged
@cobratbq
Copy link
Contributor Author

So about all the issues. @Neustradamus suggests moving stuff around etc. until we get everything in one repository. (IIUC)
Is this also what you guys want? Is there any point to doing this?

I am a bit at a loss why all of this is suddenly a big issue. I'm not sure how we'd want to proceed. It seems that jitsi/otr4j is now a stripped down repo (issues, releases, relationship with contributors) with up-to-date code-base (v0.23).

@cobratbq
Copy link
Contributor Author

I guess a question in a similar fashion. Would it work if I contribute the incomplete OTRv4 work to the repository such the work up to now is available in a separate branch? (There are plenty of things to fix apart from the OTRv4 implementation, such as maven configuration changes, licensing change, etc.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cobratbq