Re: FreeBSD: GitLab

>> I mainly asked because GitLab seems to offer a richer toolset IMHO.
>
> The project is publishing many places, and will use features of the places
> it publishes as it refines the future workflow. The different
> mirroring/hosting services offer different features and it's not yet clear
> how we can best utilize them or if even one size fits all.

As with the move to git, readonly mirrors is fine thing.
Yet more general attempt to open up bug work issue trackers flow
read-write services etc for some things beyond say central freebsd.org,
can massively raise overhead, needlessly partition knowledge
base, raise peoples search and participation time by 2^n,
complexity alienate new dev and user influx, be harder for
donors to big picture, etc...

'A: hey here's my bug report on site H'
'L: H redundant, already filed over on service X'
'Z: but we're working it on J, see the mail list at U'
'W: well J blocks devs using tor with cloudflare so we can't read or
contribute there'
'X: did you see telegram message G you can add it to site R's wiki'
'Q: nope not bothering to set up yet another account for that'
'I: ddg search gave results to U, but V which was not indexed that I
found on F had my answer'
'E: i clicked your link but N already 404 expired sold out or shutdown'
'N: <crickets>, sorry for your loss'
'M: but the forum C said github clone A was it'
'O: they wanted my phone picture id and utility bill for an account, fuck that'
'B: i tried to integrate sites G and Y in my scripts to do miracle T
but they kept changing API's and it required plugins which were were
broken in pkg all month.'

Also consider before canonizing/depending elements to
third party services, especially ones without good export for
backup, mirror, and local use... people think corp services
will last forever, history shows they don't.