cotto - using email to parrot.org to open an issue on the parrot repo

gistfile1.txt

cotto:

I want to, tentatively,[1] retract my suggestion of using a proxy repo in
favor of what, I think, is a more robust approach, that is, moritz'.[2]

Here, in-the-main, is moritz' idea:

    1. Create a bug@parrot.org email address, if there isn't one already;
    2. Have a cron job fetch any new emails delivered to this address; and
    3. If it looks like a bug report, the cron job launches a script to open
    an issue. 

This approach, largely, obviates the credentials concern and has the advantage
of keeping us in control of the process. It also has the added advantage of
not requiring us to rely upon github "magic" to make everything go.[3] 

Please let me know what you think.

Thank you.

---------------
[1] My tentative retraction is contingent upon 

(1) whether or not we can set up an email account on parrot.org; 
(2) whether or not we can execute cron jobs on Drupal's servers; and 
(3) whether or not we want to use parrot.org for something like this.  

Depending on your answers to (1), (2), and (3), we may or may not be back to
the proxy repo option.

[2] Fwiw, initially, I thought of doing something very similar to what moritz
proposed earlier this morning in #parrot. Wwhich, btw, is why I contacted the
github folks to ask them if there was a way for us to obtain a project email
account.  Unfortunately, at this time, this is not possible.

What I did NOT think of was using a parrot.org email account.

Unfortunately (or, fortunately, depending on your view), most of my tenure
with parrot has been during the post-parrot.org, github era of parrot's
development, so I simply don't often think of parrot.org.

[3] This is probably a'bit unfair.  I'm reasonably certain the hooks api will
work as advertised.