Le 2019-03-27 10:25, fgergo(a)gmail.com a écrit :
> On 3/27/19, 'Nicolas Mailhot' via golang-dev
> <golang-dev(a)googlegroups.com> wrote:
> ...
>>> Anyway here is the code, not finished, not feature-complete, very
>>> lightly tested, but already doing some useful things
>>>
https://pagure.io/modist/
> ...
>> And I should have added, the readme is sparse but the tool should be
>> self documenting, just build cmd/modist and run it, it will output
>> help
>> about available subcommands and their parameters
>
>
godoc.org/pagure.io/modist/ doesn't seem to work.
> As far as I can tell, most published go code works automagically with
>
godoc.org.
> If you plan to look into this,
godoc.org/github.com/golang/gddo can be
> one useful starting point.
Thanks for pointing out this. This is something that will probably need
looking at, if the code graduates from experiment, and is not deprecated
by improvements in upstream go tools.
Right now the priority was just publishing something that builds, to
have a concrete application example, and not just abstract exchanges on
the mailing list.
(This is still only about sharing go code.)
I wasn't sure if I should add or not, but since you reiterated that
you intend to make others check out the published code: you'll most
probably have a wider audience if or when the reason for the code is
in the documentation and it's available via a familiar mechanism.