[pkg-go] Minutes for the DebConf17 BoF
Michael Stapelberg
stapelberg at debian.org
Wed Oct 25 08:03:42 UTC 2017
Everyone, thanks for your updates, that helped clarify things!
I have updated the document to reflect the new positions. It seems
like we’re agreeing on having the upstream git history in the upstream
branch, and that also means importing new upstream versions no longer
needs special tooling.
Remaining undecided items are how we repackage non-DFSG free upstream,
how we manage patches, and whether/in which way we should support
dgit.
Please continue to add your comments/positions in the pad.
On Tue, Oct 24, 2017 at 10:05 PM, Martín Ferrari <tincho at tincho.org> wrote:
> On 21/10/17 17:10, Michael Stapelberg wrote:
>
>> Please give it a look at
>> https://oasis.sandstorm.io/shared/l4YsLYdwUgnhzzwmKS_TGwWyVQ9Ol8EKiMR8qhpHaS2
>> and add any remaining discussion points you would like to bring up
>> within the next 14 days, i.e. no later than 2017-11-04.
>
> I added my comments, and updated my preferences (mainly, that since
> albertito pointed me to gbp's ability to create reproducible tarballs, I
> have stopped using pristine-tar).
>
> What I feel is not too clear there is that many discussion points depend
> on others; the most important one being to follow upstream git history
> or not.
>
> In any case, it is important that other people check it out and comment.
> So far, I only see edits my Michael and me. Having a clear policy is
> very important to make the team more productive and easy to work with!
>
> --
> Martín Ferrari (Tincho)
>
> _______________________________________________
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
--
Best regards,
Michael
More information about the Pkg-go-maintainers
mailing list