Greetings and Salutations, since I haven't heard of Ken for a while (he currently is rather busy as far as I remember), I decided to take MWS in my hands as long as he can't spare the time. I cannot promise you to give you a real weekly MWS, but I will do my best. Oh, and please forgive my English, it isn't as good as Ken's.
------------------------------------------------------------------------ Table of Contents ------------------------------------------------------------------------ - Editors Notes - CVS Status and Development Strategy - Midgard 1.4.4 and 1.5.0 Roadmap Proposal - Asgard 1.4.3 released, Roadmap to Asgard 1.4.4 - Midgard Paths - Beta Release ------------------------------------------------------------------------ Editors Notes From: Torben Nehmer <[EMAIL PROTECTED]> ------------------------------------------------------------------------ I have some ideas how we could support a real weekly column about Midgard. I want everybody out there to send me material that you want to have published here -- both Midgard developers and Midgard users. This includes almost everything that could be interesting for the Community. If you speak about longer articles, provide me with a summary and a link to an online version of it. I'd gladly provide Webspace on my Midgard Knowledgebase[1] if somebody would need it for Midgard. If you authors have no objections (I can decide this on a case-by-case-basis) I will look over your contributions before I include them here to get a unified look-and-feel. [1] http://www.nathan-syntronics.de/midgard ------------------------------------------------------------------------ CVS Status and Development Strategy From: Torben Nehmer <[EMAIL PROTECTED]> ------------------------------------------------------------------------ Finally the new CVS is online, complete with a restructuralization done. The current tree looks like this: /admin/ => Administration Interfaces, one Directory for each /ancient/ => Ancient stuff, sort of an Archive. /contrib/ => User Contributed stuff to Midgard /dev/ => Midgard Core Development Area (MMP for example) /documentation/ => Guess what ;-) /Midgard/ => Stable Midgard Core Area /misc/ => Miscellaneous stuff fitting nowhere else /proposals/ => Proposals on what to do further on with Midgard The CVS can be accessed in several ways: 1. Anonymous CVS Access: Anonymous (=read only) access is only available through pserver. The CVSROOT for this is [2], the password is empty. 2. Read/Write access through SSH: Read/Write access is only available through SSH tunnels or via local access. If you want an account for CVS, please send a mail to [EMAIL PROTECTED] [3] (not to me personally please). You will then receive a local system account on Nathan, where the CVS is hosted, complete with full local system access including an E-Mail account and a personal Webspace. Midgard compiles perfectly on Nathan, all development packages are there. Feel free to use this account as you like. Access to the Repository with CVS Root [4]. Don't forget to set "CVS_RSH=ssh", since rsh connects are not allowed on Nathan. If you miss any packages/programs on Nathan, feel free to drop me a mail and I will see what I can do. Anybody with Read/Write Access to the CVS Repository should be subscribed to both [EMAIL PROTECTED] and [EMAIL PROTECTED] Use [5] to subscribe to dev, and [6] to subscribe to cvs. The [EMAIL PROTECTED] list will show you any commits made to the repository so that you stay up to speed. 3. CVSweb CVSweb is also back online and can be accessed through [7]. Development Strategy: In order to allow us to separate beta-testing and bugfixing I suggest that we maintain two development branches: The "main" branch, accessible by the regular HEAD revision which represents the current development status with everything that will go into the next major release (currently 1.5.0). You can add new features and such things there, as long (and this is really important) as you do _not_ endanger backwards-compatibility. Any API change should be done in a separate development branch and discussed on the lists before they get introduced into mainstream CVS. The current major version (1.4.x in our case) will be worked on in a separate branch. This branch is currently named release-1_4_3-branch. All important bugfixes should be done there as well as in mainstream CVS. This should ensure that we can fire out bugfix releases fast while continuing development. I would suggest that all bugfixing is done in the release branch and that they will be backported into mainstream CVS en block. I could do that on a regular basis if you like it. Please send any comments and feature wishes about the CVS to the Development List [8] to discuss it there, I'm open to almost anything. [2] :pserver:[EMAIL PROTECTED]:/home/cvsmgd [3] [EMAIL PROTECTED] [4] :ext:[EMAIL PROTECTED]:/home/cvsmgd [5] [EMAIL PROTECTED] [6] [EMAIL PROTECTED] [7] http://cvs.midgard-project.org/ [8] [EMAIL PROTECTED] ------------------------------------------------------------------------ Midgard 1.4.4 and 1.5.0 Roadmap Proposal From: Torben Nehmer <[EMAIL PROTECTED]> ------------------------------------------------------------------------ I've spent some thoughts about how we should continue with Midgard Development. Here is my proposal: The short run: Midgard 1.4.4 1.4.4 will be mainly a bugfix release which will be developed based on the 1.4.3 Release in a saperate branch in CVS. What already went into mainstream CVS will be backported into the 1.4.3 branch. Only very important new features will be backported to this release and only if they do not break backwards compatibiltiy in any way. Since 1.4 is currently Mainstream Midgard we should try to keep it stable. In my Eyes the priorities for this release are the following bugs, if you feel, that I missed some important bug, please tell me: - Article update problem - Replication of deleted objects (there is a patch available AFAIR) - Asgard (Asgard 1.4.3 should be bundeled with Midgard 1.4.4) - Attachment Serving HTTP Headers I will do a freeze with a single RC after those bugs are fixed. Included in this release for purley testing purposes will be a current version of MMP - for those who like to live on the cutting edge. I hope to be able to fire out the RC during the next three weeks somewhere around September the 15th with the final release abaout a week later. The long run: Midgard 1.5.0 Midgard 1.5.0 development can start just now, it will happen in the main CVS trunk. A couple of new features and changes will be introduced here, so it won't be 100% backwards compatible to the 1.4. tree. New features will include about this: - The introduction of MMP as default Apache Midgard Module - Deprecation of the midgard-data package (it will be split up between midgard-lib and separate packages for the different administration interfaces) - Change of the parameters to longtext fields - Introduction of the API changes requested in the different feature requests - I will implement some MidCOM specific stuff into Midgards Style Engine to allow dynamic switching to different Styles on runtime. - Anything that other contributers get up and running to the time of the first RC. - Compatibility to PHP 4.3 There is no timetable yet for this release, but a rough guess would lead me to the expect it in December, depending on how much time (especially) Emiliano will have. ------------------------------------------------------------------------ Asgard 1.4.3 released, Roadmap for Asgard 1.4.4 From: Matthias Englert <[EMAIL PROTECTED]> Editor: Torben Nehmer <[EMAIL PROTECTED]> ------------------------------------------------------------------------ Asgard 1.4.3 has finally been released. You can download Asgard 1.4.3 from the Asgard website [9]. This is mainly a bugfix release but also the start of independence for Asgard, Please report any bugs to the Midgard Project's Bugtracker [10]. Fixes and improvements since 1.4.2: - separate Asgard from Old Admin and VMUC - fixed and much improved element referencing - fixed move/copy functions - introduced a list of predefined mime-types for attachments - fixed unnecessary escape sequences on editing - fixed incorrect location string for pages and page-elements - show id of objects with empty names in tree-view - fixed wrong children displays on object creation - fixed open nested groups in group-tree-view - fixed open nested articles in topic-article-tree - show location-bar for parameters - show version information in footer - fixed help links on start page - more verbose displaying of id for empty names like suggested by Philipp Rotmann Known bugs and limitations: - copy/move in object view does nothing - location bar is empty for some object types - event module missing - some translations missing Currently planed for Asgard 1.4.4: - more universal location bar - improvement in element referencing for very special situations - Add some meaningful HTML Title - better move and copy support - integrate event module - search volunteers for translations - some cosmetic changes [9]: http://asgard.midgard-project.org [10]: http://bugs.midgard-project.org ------------------------------------------------------------------------ Midgard Paths - Beta Release From: David Schmitter <[EMAIL PROTECTED]> Editor: Torben Nehmer <[EMAIL PROTECTED]> ------------------------------------------------------------------------ David Schmitter has released the first beta version of Midgard Paths. It is intended to be a simple way to reference objects by their name and tree location. Midgard Paths will probably move to the Midgard CVS soon, and it might be integrated in Midgard's C-Core somewhere in Midgard 1.5 or 1.6. The current PHP-coded release can be found at [11], the documentation at [12] and the Repligard File at [13]. Midgard Paths allows you to do <?php $article = mgd_get_object_by_path('/to:myTopic/ar:myArticle/myReply'); ?> instead of <?php $topic = mgd_get_topic_by_name('myTopic'); $article = mgd_get_article_by_name($topic->id, 'myArticle'); $article = mgd_get_reply_by_name($article->id, 'myReply'); ?> or <? $article = mgd_get_object_by_guid('6e068094d8f2eeb420d78711ca1c5b30'); <? [11]: http://midgard.dataflow.ch/ [12]: http://midgard.dataflow.ch/pathdoc.html [13]: http://midgard.dataflow.ch/midgard-paths.xml.gz ------------------------------------------------------------------------ Want to continue reading MWS? Please help us create this newsletter. Currently, it's mostly a one-man show, which is anticipated to fail in the long term. We urgently need volunteer writers who prepare items. Please see the contributing page to find out how to help. We're looking forward to receiving your mail at [14]. Midgard is an Open Source Content Management System, visit our Homepage [15] for further Information. [14]: [EMAIL PROTECTED] [15]: http://www.midgard-project.org Live long and prosper! Torben Nehmer -- Torben Nehmer, Munich, Germany http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED] PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
