Version 2 (modified by Jens Maus, 8 years ago) (diff)

more edits

YAM Developer Summit 2012 (Wohlenberg, Germany)

On the evening of June 1st 2012 and June 2nd 2012 the two leading YAM developers Thore Böckelmann and Jens Langner met in the nice little city of Wohlenberg, Germany. One of the goals of this meeting was to discuss and decide on the 2012/2013 development roadmap of YAM. Besides general discussions on the current development situation of YAM the development roadmap for the YAM 2.8 and versions beyond were discussed throughoutly. This page should summarize information on the general consensus of this meeting so that users and interested developers can get an impression which road the future development of YAM will take.

General consensus/descisions

  • The development of YAM 2.8 is progressing nicely and there are chances that it might already be released before its planned release date (christmas 2012).
  • Major changes in YAM 2.8 will be the recently implemented multi-identity/multi-smtp server as well as unlimited signature support which will greatly support the introduction of the IMAP protocol in future versions of YAM.
  • Before releasing a final YAM 3.0 version with full IMAP support a 2.9 version will be released in the course of 2013 with some intermediate (limited) IMAP support already.
  • Future versions of YAM will continue to be released for AmigaOS4/PPC, MorphOS/PPC, AmigaOS3/m68k, AROS/x86, AROS/PPC and AROS/x86_64.
  • While all AmigaOS-derived platforms will be supported, maintainers (developers) for MorphOS/PPC and all AROS-based platforms are missing and should be encouraged to join the YAM project.
  • Contributing translators are updating their catalogs on a regular basis which supports the initial decision to open catalog translation for every interested translator rather than solely relying on the nowadays vanishing Amiga Translators' Organization (ATO).
  • More translators are required and should be encourage to join the project so that we can support a larger amount of different languages.
  • Consolidation regarding moving our different online support systems (FAQ, Forum, Documentation) to solely using 'trac' will continue with eventually porting important topics from the formerly phpBB-based forum to the trac-based forum plugin.

YAM 2.8 roadmap decisions

  • #57: The upcoming threaded mail view will not use NListtree because of performance considerations. It will be implemented by using simple text indentation in the current mail listview. Internal changes are still required to link the "References:" header field entries to an internal mail hierarchy.
  • #74: Full Content-Type 'format=flowed' support requires substantial changes to TextEditor.mcc so that quoting characters (>) are replaced by vertical bars.
  • #124: The current mailing-list support (in each folder config) will be abadoned and replaced by an own YAM configuration page which will allow to configure an unlimited amount of mailing-list addresses for which e.g. Mail-Reply-To: and Mail-Followup-To: will be applied.
  • #127: xadmaster.library support will be integrated mostly for allowing to unarchive all supported xad client formats.
  • #128: The SPAM filter routines will be synced again to the latest Thunderbird sources and support for external SPAM systems (e.g. spamassassin) added similar to how this is handled in Thunderbird.
  • #131: Full SSL certificate authentication support is needed but requires substantial changes to allow the user to add own root certificates, etc. A simple notification of a potentially invalid certificate is nevertheless highly required and will be implemented first.
  • #132: The current way of storing passwords in the .config file is insecure. A complete encryption of the .config file is, however, not desirable. A master password mechanism will therefore be implemented which will store the master password in the .users file and then encrypt all passwords in the .config file with that master password. If no password is set the user should be warned/reminded that a master password is required.
  • #135: The current error/event console is far from being perfect. It will be changed to carry several groups of events (warnings, errors, information) and will be changed to be a vertical list rather than having to switch horizontally between items.
  • #222: Previous versions of YAM were creating folders in the PROGDIR: of YAM. With 2.8 a PROGDIR:folders directory will exist were folders will be stored per default.
  • #284: Currently the YAM window have to be explicitly snapshotted to save the column and folder list sorting in the global config. With 2.8 YAM will automatically save its state to disk upon exit of the application. This will improve usability of the main window.
  • #306: Amigaguide-based documentation lacks maintainers and will be converted into wiki pages to which YAM will directly link when using the HELP key.
  • #309: The 'Status Update' option will be removed from the config GUI and moved to the hidden option. In addition it will be changed to only change the 'new' mail status to 'unread' upon restarting YAM and not after each mail download.
  • #310: The GUI elements for manually changing the attachment encoding (quoted-printable vs. base64) will be removed from the write window as the automatic works perfectly.
  • #311: The write window will get an AttachmentImage/Group similar to what the read window has since YAM 2.6. As soon as an attachment is added it will be displayed on the first page of the write window so that it is more easily clear that the mail being composed contains an attachment.
  • #313: The Daylight Saving Time switching notification will be removed for platforms directly supporting DST switching (e.g. AmigaOS4).
  • #314: Default folders will be placed at the right position when they are recreated (currently they are always added at the bottom).
  • #315: The "New Mail" config page will be removed and options moved to the identities config page instead.
  • #317: An attachment reminder will be added to the write window. As soon as user-definable keywords are entered (e.g. 'attachment') the write window will show a reminder that an attachment might be missing.
  • #320: The possibility to move folders to different root directory or partitions/volumes will be removed as this constantly leads to misconfigurations by users (folder should always be in the same directory tree).
  • #321: The recently added cycle gadget to choose the identity in the write window will be modified to be more easily usable via keyboard.

YAM 2.9+ roadmap decisions