[anti-censorship-team] goptlib's git repository, and its (recent) source code

[David Fifield]

I maintain the git.tpo repo, but I do not have anything to do with any
of the others. I believe that at some point ahf's copy was planned to be
a "goptlibext" fork to include convenience features that I thought did
not belong in the base library.
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac/-/issues/28940#note_2604850

In my opinion, there is little harm in using an outdated version of
goptlib. The last important bugfix I am aware of is in version 0.7, from
2017. The example programs were improved in v1.0.0 (2019), but they do
not affect the library itself. If you are using Go modules you should
use v1.0.0 or later. If you need the LOG feature, v1.1.0 or later.

I don't have a problem with there being mirrors of the main repository.
I could make a tarball if that makes your packaging easier, but I don't
have the ability to place downloads at dist.tpo.

On Sun, Sep 27, 2020 at 12:49:09PM +0000, Vinicius Zavam wrote:
> olá Anti-censorship Team,
> 
> I write to you to share the current status of "goptlib" and its git
> repositories, plus mirrors (and the source code).
> 
> As maintainer of "a few" packages depending on goptlib, I missed an
> updated version of its main git repo
> (git.tpo/pluggable-transports/goptlib) into the actual GitHub Orga. of
> the Tor Project (@torproject), or any official mirror like the ones
> hosted at the new GitLab server - AFAIK, most people relied on @ahf's
> GitHub sync in the past (also not up to date).
> 
>   - FYI: packages depending on goptlib which were recently ported into
> *BSD include the OONI Probe CLI
> 
> So, I took the chance of getting a synced copy into the TorBSD's goptlib
> repo (github.com/torbsd/goptlib) - which was sadly also with an outdated
> version of the source code.
> 
>   - I took the already existing repo, and just synced it; did not create
> or change anything.
> 
> This move is based on the lack of support of the ports frameworks we
> currently use on OpenBSD/FreeBSD/NetBSD; they work nicely with GitHub's
> or GitLab's API, but not with cgit(web). another solution for that would
> be serving a tarball via https://dist.tpo (but I did not find any).
> 
> I would be pretty much happy to help and would volunteer myself to keep
> it always on track, should any extra hands are needed here; but I have a
> couple questions:
> 
>   - should my GH account be linked to tpo's (@torproject)?
> 
>   - would you like us (TorBSD/tdp) to sign any additional sync or commit?
> 
>   - how oft should we sync (or/and sign)?
> 
>   - is it fine to keep the current updated repo, or would you like us to
> "deprecate" it?
> 
>   - any other suggestions, ideas or objections?
> 
> You can reach out to me via email or on IRC (my key+info are on
> https://tpo/about/people page)
> 
> That's it... and TYVM for the hard work! Muito obrigado :)