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/T2PHC2CQ2KWTU2NWH434GY44G6EQ62Y4/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "T2PHC2CQ2KWTU2NWH434GY44G6EQ62Y4",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/XEUYQPGBZYK3A6UP7RKKMNOYOOELQBIT/?format=api",
    "sender": {
        "address": "w5did (a) amsat.org",
        "mailman_id": "8da25cae70294f3687f590ebe6fded03",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/8da25cae70294f3687f590ebe6fded03/emails/?format=api"
    },
    "sender_name": "Louis McFadin",
    "subject": "[eagle] Re: [Fwd: Re: EaglePedia Upgrades/Enhancements]",
    "date": "2006-11-03T04:29:18Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/XEUYQPGBZYK3A6UP7RKKMNOYOOELQBIT/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "I recommend postponing it a day or week.\nElection day is a very big thing here at least for me.\nWe also have a BOD telecon that evening which I also hope to get  \npostponed.\n\nOn Nov 2, 2006, at 8:20 PM, Jim Sanford wrote:\n\n> Team:\n> What are your choices regarding the TeamSpeak conference for Tuesday?\n>\n>\n> All:\n> Thanks to Emily for all this work.  I'm still digesting the note.\n>\n> I wish to add a note regarding Dave Hartzell:  Some of you remember me\n> asking for help because I was spending too much time editing in\n> EaglePedia.  Dave stepped up to the plate and has been taking my\n> delusions (\"I want . . ..\") and turning them into reality.  This is\n> incredibly valuable, and I am very grateful to Dave.\n>\n> Finally, regarding the TeamSpeak conference for 7 November:  I will  \n> not\n> be able to make it.  Tuesday is election day here in PA, and I also  \n> have\n> a Township Planning Commission meeting that night -- which I have to\n> run, since the Chairman is out of town.  Monday is also out for me,\n> since I need to attend the Board of Supervisors' meeting.\n>\n> So, options as I see it:\n>\n> 1.  Cancel the meeeting for this month.\n> 2.  Hold it Tuesday without me.  I'll still put together an agenda (I\n> have no inputs so far.)\n> 3.  Reschedule to another evening Wed - Friday.\n>\n> I'd prefer option 3, but will live with your consensus.\n>\n> What say the team?\n>\n> Thanks & 73,\n> Jim\n> [email protected]\n>\n>\n> Emily Clarke wrote:\n>\n>>\n>> I wanted to update you on EaglePedia, specifically about upgrades to\n>> the base MediaWiki software and about personnel.  This is a rather\n>> long email to explain what changes will take place - I encourage all\n>> of you to read it and provide any feedback.\n>>\n>> First of all I'd like you all to welcome Dave Hartzell N0GTD who is\n>> joining the team as co-sysop of EaglePedia.  Most of you have had a\n>> chance to meet Dave at the Symposium - Dave, along with Eric, served\n>> to introduce speakers during presentations.  Dave is on the IT staff\n>> at NASA Ames and is not a programmer,  but Dave will take\n>> responsibility for the EaglePedia system administration which will\n>> free me up to concentrate on software development.\n>>\n>> The EaglePedia core software desperately needs an upgrade.  The\n>> current version is 1.5.0 and we are plagued by compatibility issues.\n>> I propose that the upgrade take place beginning on the day following\n>> the next Teamspeak conference (which I think will be the 7th of\n>> November - if not, let me know).  We will have to shut down  \n>> EaglePedia\n>> during the upgrade period.  The details follow.\n>>\n>> Over the past few days I have upgraded the staging server from 1.5.0\n>> to 1.8.2 (current version) however it was not trivial.  I basically\n>> had to upgrade to 1.5.7, then to 1.6.0 (which is very unstable but\n>> included database changes), then to 1.8.2 (which seems very stable  \n>> but\n>> also introduced database changes.)  At the 1.6.0 level the current\n>> configuration documents become unusable and it took almost a full day\n>> to resolve. To resolve it the Wiki had to be initialized from  \n>> scratch,\n>> which creates new (blank) configuration settings.  These were then\n>> changed to fit our configuration.  From there upgrading to 1.8.2 had\n>> no issues.  Since I now have a 1.8.2 set of configuration settings it\n>> is may be possible to upgrade from 1.5.7 to 1.8.2 directly - I will\n>> probably roll back the staging server and test this before upgrading.\n>> It will save several hours if we can.\n>>\n>> There are a number of other changes that were required.\n>>\n>> 1) In 1.8.2 the core Monobook Skin was re-written.  Our version of\n>> Monobook skin was highly customized and had to be re-written. This  \n>> was\n>> primarily to support the hierarchical menu structure in the left side\n>> menu.\n>>\n>> 2) Version 1.8.2 gives programmers access to a global user object\n>> (1.5.0 kept the user object as a protected subclass of the global  \n>> wiki\n>> object) so this now allows me to authenticate users.  This is a much\n>> better solution - in the past I had to rely on a custom skin\n>> (MonoNoTabs) to be the default skin and have all registered users set\n>> their skin to Monobook.  Now Monobook can be the default skin since I\n>> can turn off the tabs, search field and toolbox based on user\n>> authentication.  We will no longer need to support the MonoNoTabs  \n>> skin.\n>>\n>> 3) Unfortunately the additional buttons on the Edit Toolbar still\n>> require modification of the EditPage code.  There is a proposal to\n>> move this to the Monobook javascript code, but no work has been done\n>> for this and I don't agree with this implementation.  My proposal to\n>> the MediaWiki community is to change this to a separate include file\n>> that will be easier to maintain, and this is what I have done for\n>> 1.8.2.  I've submitted the proposed solution to MediaWiki.\n>>\n>> 4) Extensions were broken in 1.5.0.  In 1.8.2 they work, and as a\n>> result I have created one (and will create others) to do some of the\n>> security tasks for us.  By moving this code into extensions we  \n>> will be\n>> able to upgrade in the future without making changes to the base code\n>> (other than the Monobook and toolbar modifications.)  The first\n>> extension I wrote will necessitate a change in protected pages, but\n>> adds functionality.  The old function was:\n>>\n>>           {{NoPublish}}\n>>\n>> This used a template, and about three other files (Monobook,\n>> SkinTemplate and Skin) had to be extensively modified to detect and\n>> modify the existing page data.  The new function is in one extension\n>> and uses the syntax:\n>>\n>>           <restrict [group = somegroupname]>Restricted text ...\n>> </restrict>\n>>\n>> There are two advantages to this\n>>\n>>     * it can restrict all or part of a page depending on where the\n>>       <restrict></restrict> tags are placed and\n>>     * the restriction can be lifted for an individual group.\n>>\n>> Up to this point we haven't used groups, but we can.  So for example,\n>> if you wanted something to be seen by Rick, Jim and Bob only Dave can\n>> create a group called \"executive\" and using <restrict\n>> group=executive>Some text...</restrict> only the executive team could\n>> see the restricted text - everyone else only sees a comment that  \n>> there\n>> is a group restriction.\n>>\n>> 5) Additional extensions have been installed and tested.  These  \n>> include:\n>>\n>>     * Citations - you can put in <ref>Some reference</ref> and  \n>> then at\n>>       the bottom of the page use <references/> to list the citations.\n>>     * Inputbox - this will allow us to create a dedicated \"Create New\n>>       Article\" page.  Although not entirely needed, this will\n>>       eliminate the confusion of searching for a page name and  \n>> getting\n>>       a \"not found - click here to create\".\n>>     * CategoryTree - this dynamically produces a browse-able tree of\n>>       categories down to individual articles.  This eliminates the\n>>       need to manually create the Eagle Project Categories tree page.\n>>     * RequireCategory - this requires someone to enter a category  \n>> name\n>>       for a new article before it is saved. This way all articles\n>>       ultimately are browse-able using the CategoryTree tool\n>>\n>>    Other extensions can be installed if needed.  See\n>> http://meta.wikimedia.org/wiki/Extensions for a comprehensive list of\n>> additional extensions.\n>>\n>> 6) Non-native characters can be added - I've added an extension and\n>> modified the edit page template to display groups of non-native\n>> characters that people may wish to insert.  These are grouped as\n>> Latin-1, Greek, Math Symbols, Currency Symbols, Misc. Symbols and\n>> Geometric Shapes.  Below the edit box the list will appear - if a  \n>> user\n>> needs a Symbol, they merely click on it.\n>>\n>> 7) No integrated WYSIWYG Editor yet - unfortunately there is still no\n>> viable WYSIWYG solution for generating Wiki markup that is reliable\n>> and supported.  The WINOR project was abandoned and as near as I can\n>> tell there is only debate, but no real progress.  Most disheartening,\n>> FCK still carries the warning that it may corrupt the document\n>> database (which would be fatal).\n>>\n>>     One solution I am considering is to provide FCK in a popup\n>> window.  The editor will operate in a separate window and when saved\n>> it will pipe input through some HTML to Wiki conversion utility to\n>> convert the HTML to Wiki markup and insert it into the editor window.\n>> At first glance CPAN has HTML::WikiConverter that could be used, but\n>> it would be better to have something written in PHP so that the\n>> process could use a memory pipe rather than having to write the HTML\n>> to a temp file, convert the file, and read it back in again.  This is\n>> not trivial, and I'm not sure how much of a priority I should put  \n>> on this.\n>>\n>>\n>> 73,\n>>\n>> Emily\n>>\n>>\n>> ---------------------------------\n>> N1DID formerly W0EEC - CM87tm\n>>\n>> Support Project OSCAR - http://www.projectoscar.net\n>> <http://www.projectoscar.net%A0%A0%A0/>\n>>\n> _______________________________________________\n> Via the Eagle mailing list courtesy of AMSAT-NA\n> [email protected]\n> http://amsat.org/mailman/listinfo/eagle\n\n",
    "attachments": []
}