State of Pidgin: Attracting and Maintaining New Contributors

[David Woodhouse]

On Thu, 2018-03-15 at 12:04 -0400, Ethan Blanton wrote:
> 
> So here's my call for contribution: can someone who has a good working
> understanding of both Git and Mercurial identify and document a simple
> workflow using a readily avialable git-to-hg connector to enable:
> 
> 1) Simple cloning of the upstream repo
> 2) Native creation of git feature branches for "git-like" PRs on the
>    git side
> 3) A single command push to BitBucket (perhaps using an alias)
>    producing a sequence of revisions that can be directly PR'd
> 
> If there is some reason that this *cannot* be done, I suspect it is a
> problem with the BitBucket interface for pull requests that we need to
> bring to Atlassian's attention.  (Of course, who knows how far that
> will go.)

I'll come up with a draft of that, as I *think* I have it kind of
working. I don't fully understand the branch vs. bookmark thing and why
I seem to need a separate cloned repo per PR, but I can at least fill
in the basic boilerplate of the procedures, for subsequent heckling.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5213 bytes
Desc: not available
URL: <https://pidgin.im/pipermail/devel/attachments/20180315/fb53d47d/attachment.bin>