mikemcquaid / hookhand

:arrow_right_hook: Runs scripts from webhooks.

Some things you should know about life:

• all open source maintainers (including me!) owe you nothing
• emailing open source maintainers (including me!) directly instead of opening issues on their project is a rude thing to do
• there's some things that good engineers do
• drive-by negativity is literally killing open source
• you should stop mentoring first-time contributors to open source projects
• if you can't say something nice: maybe you shouldn't say anything at all
• if you're automating things remember that robots are better at pedantry and humans at empathy
• dogs love you in a way that your cat never will
• you should have a system to get things done (or you can copy mine)
• Babylon 5 is the best sci-fi TV program ever made
• you should contribute to open source every friday (or, even better, every weekday)

hookhand's Issues

bi-directional synchronization

Moved here from git-multimail/git-multimail#109

I don't know if the final result will be a code change to HookHand, some additional docs, a separate project, or simply a conclusion that it is a bad idea.

For context, the Apache Software Foundation has a bunch of git repositories: https://git-wip-us.apache.org/repos/asf; many are mirrored here: https://github.com/apache/.

Mirroring in this case means that pushes to the asf repository cause the content to appear on github.

I'd like to make that bidirectional. By that I mean that in addition to the above, pushes that happen to github (either explicitly or implicitly by merging pull requests) cause content to appear in the asf repository.

On a project that only sees dozens of pushes per day, where most users primarily use the same copy, where much work occurs on discrete branches, where both machines are generally up, and where synchronization is a matter of seconds; problems with be rare. Rare, but not nonexistent. It is important, therefore, for things to be set up to ensure that when problems occur that the appropriate people are notified so that the problems can be addressed.

If needed, I can go into more details as to why the ASF feels it needs a live copy. I doubt I need to explain why people find the GitHub user interface attractive :-). But I recommend that we simply take that as a given for now, and focus on what the technical challenges would be to address this.