Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/WF2INRAM762H455K6UXJ6YBNS22EAFL2/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "WF2INRAM762H455K6UXJ6YBNS22EAFL2",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/WX35DGVLKZAELRHCD6MORVGXK5LAOWFM/?format=api",
    "sender": {
        "address": "greencl (a) mindspring.com",
        "mailman_id": "5421c5ff9a12494f8f7bd304db4ac696",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/5421c5ff9a12494f8f7bd304db4ac696/emails/?format=api"
    },
    "sender_name": "Chuck Green",
    "subject": "[eagle] Re: A wild thought",
    "date": "2007-01-02T17:07:22Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/WX35DGVLKZAELRHCD6MORVGXK5LAOWFM/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Jim,\n\nI don't see any down side to this.  And you have listed the up side(s).  \nI think you should do it (always easy to say someone else should do \nsomething - sorry).\n\nChuck\n\nJim Sanford wrote:\n> Team:\n> I've been thinking about this for a while.  Recent publicity for Eagle \n> in multiple publications has resurrected the thought, so I seek your \n> comments.\n>\n> I'm considering seeking, for each discrete peer review, an additional \n> review team member from AMSAT membership at large.\n>\n> Heretofore we've collected peer review teams from a subset of Eagle team \n> members with possibly a few known additions.  I'm considering seeking a \n> single at-large reivewer from within AMSAT MEMBERSHIP.  In my vision, \n> I'd go out to amsat-bb and ANS and solicit qualified volunteers.  Such \n> volunteers would have to be verifiable members of AMSAT-NA or another \n> AMSAT organization, and would be asked to send me a resume or c.v.  I \n> would use these to select the MOST qualified volunteer for a single \n> at-large position on the peer review team.  (I say that I would make the \n> selection, mostly to keep the additional admin burden off you; if any of \n> you want to help me choose, thanks!)  I would be responsible for \n> forwarding that individual all necessary materials to do the peer \n> review.  I would be responsible for coordinating with Bob and Eric that \n> that at-large member would have access to the AMSAT Engineering channel \n> on TeamSpeak for that particularl peer review (the password changes for \n> each discrete topic.)\n>\n> The advantages I see in this:\n>     -- furthers our \"openness\" with deeds not words\n>     -- gives motivated new talent an opportunity to share their \n> expertise with us\n>     -- gives us a chance to evaluate, select, and motivate new talent\n>     -- advances general membership \"buy-in\"\n>     -- gives us a better ultimate product\n>     --may lead us to new Eale team members!\n>\n> I see no down-side to this.  If you do, please advise ASAP.  If you \n> think this is a good idea, please let me know also.  If you have any \n> ideas on how to make the peer review process better, I'd like to hear \n> that as well.\n>\n> I'd like your responses by Friday 5 January.  If we decide to proceed, \n> I'd lke to include this in my next Journal article, which will be \n> written this weekend.\n>\n> Finally, I hope to convene a peer review of the UHF receiver ATP soon.  \n> For obvious reasons, I intend to use the same team which did the UHF \n> receiver design peer review, plus a couple of additions (w2gps and n4hy) \n> plus the at-large member, unless you convince me the latter is a bad idea.\n>\n> Thank you all, and very 73,\n> Jim\n> [email protected]\n>\n> _______________________________________________\n> Via the Eagle mailing list courtesy of AMSAT-NA\n> [email protected]\n> http://amsat.org/mailman/listinfo/eagle\n>\n>   \n",
    "attachments": []
}