Try to import all issues and PRs from the old repository

[jaromil]

Take contact with @jedisct1 if possible and import the repository that was once, or decide to start from scratch. Anyone compelled to open his/her own issues and pull-reqs here please wait a few days for us to realise if we can port the old github repo or not.

You guys might already be considering this, but it would be nice if you could get the content from the wiki too, lots of documentation is currently missing. For now it is still accessible with Google cache e.g.:

• https://webcache.googleusercontent.com/search?q=cache:https://github.com/jedisct1/dnscrypt-proxy/wiki/Filtering
• https://webcache.googleusercontent.com/search?q=cache:https://github.com/jedisct1/dnscrypt-proxy/wiki/Blacklists
• etc.

[jaromil]

Today we finally noticed the archive uploaded on https://github.com/dnscrypt

It makes more sense to maintain dnscrypt there. If @jedisct1 agrees then please grant me administrator rights to the group and I'll keep working there.

[krattai]

NB: Just noted that fusl has now done some updates to the dnscrypt repo, so perhaps there needs to be some merge co-ordination. probably better to not have competing forks.

The repo on github/dnscrypt is from the opennic community. The Dyne and https://github.com/snorkasaurus/dnscrypt-proxy are the most up to date.

OpenNIC is still trying to decide what to do. If this repo becomes active, than I'm sure many of us would rather leave the active project under the capable hands of Dyne.

[jaromil]

I agree coordination is needed. To virtually handshake and align commitments we can use this mailinglist https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dnscrypt

[dartraiden]

Backup of DNSCrypt wiki - https://github.com/dartraiden/dnscrypt-wiki-backup
(taken from Google Cache)

[KrasnayaPloshchad]

Frank is prepared to receive issues and PRs now from the new repository.

[jaromil]

Frank's new work is indeed interesting. I wonder how long will take us to port plugins to it.
Meanwhile is a pity there is no answer from the opennic people.

[jedisct1]

Hi @jaromil

I was planning to add support for the old plugin API, mainly for you. But if you think your code could be rewritten in Go, that would make things easier :)

[reelsense]

This bot is the fastest way I can think of to move GH Issues.

https://github.com/dessant/move-issues

The one problem I see is the bot has to be authorized in the old repo.

[jaromil]

@jedisct1 many thanks of thinking of me / us :^) our fellow dev @parazyd is also proficient in go... nevertheless it would be really good if you can support C plugins.