Thank you both -- yes, I see the problem.  It was tricky to get the 
questions right to apply across ecosystems with different infrastructure 
and terminology; but we're particularly interested in comparing ecosystems 
like Go and (much of) Swift that don't have central repositories with ones 
like R/CRAN that do.  So we're definitely interested in your insights even 
if the wording feels strange in places.

Anyway, I've tweaked things where I can without throwing off the survey's 
comparability with already-collected answers, and I think most of the 
questions appear more sensible for Go, if not perfect.

For those of you in the future who take the survey -- if there's anything 
left that doesn't make sense, just answer literally if you can, and/or skip 
questions that don't apply.  But we definitely will take into account Go's 
lack of a repository when interpreting the answers.

Ingo Oeser wrote:
| There is no central repository of Go code.

Volker Dobler wrote:
>
> I tried to fill out the survey but I got lost as I'm unsure what
> "go (community packages)" really means. 
>

 

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to