|Version 5 (modified by 4 years ago) (diff),|
YAM Developer Summit 2013 (Wohlenberg, Germany)
On the evening of June 26th and June 27th 2013 the two leading YAM developers Thore Böckelmann and Jens Langner met again in Wohlenberg, Germany. Besides general discussions about Amiga development and YAM one of the major goals of the meeting had been the finalize of the 2013/2014 development roadmap for YAM. This page should summarize information on the general consensus of this meeting so that users and interested developers can get an impression which future road YAM development will take.
- The development on the YAM 2.8p1 update version had been finished and the final release is scheduled for calendar week 27.
- Development on YAM 2.9 had already partly begun and its final release will still be scheduled for christmas 2013.
- To improve handling of development priorities a new "YAM future releases" milestone will be used to put all tickets there which have the endorsement of the development team but where it isn't really clear in which major version these tickets will be implemented.
- In future, as soon as all assigned tickets of a milestone are closed the release will be immediately scheduled for ASAP.
- One major change in YAM 2.9 will be some intermediate (limited) IMAP support which will allow to download mails from IMAP servers quite similar to the POP3 protocol. However, as the IMAP protocol is quite complex and overwhelming full IMAP synchronization support is still expected to arrive with a final YAM 3.0 version hopefully in the course of 2014/2015.
- Future versions of YAM will continue to be released for AmigaOS4/PPC, MorphOS/PPC, AmigaOS3/m68k, AROS/x86, AROS/PPC and AROS/x86_64 with priority on AmigaOS4, MorphOS and AmigaOS3 as testing releases for AROS is hardly possibly and a clear maintainer for the AROS platform is still missing.
- There is still lack of maintainers (developers) for MorphOS/PPC and all AROS-based platforms are missing and the YAM team is highly interested in seeing maintainers joining for these platforms as that will greatly improve support for these.
- More translators are required and should be encourage to join the project.
- Consolidation to soley using the 'trac'-based development platform even for the FAQ, Forum and Documetation had been finised and greatly improved efficiency of the development.
YAM 2.9 roadmap decisions
- #6: UTF-8 encoding of all data in the index have to be used and the encoding/decoding routines used on runtime instead. This should greatly improve usability of YAM in environments of changing charset encodings.
- #7: If an UTF-8 editor is used it might be desirable to be able to directly export a mail from YAM to that editor. However, currently YAM does not convert the mail text to UTF-8 but instead always load the mail text in the local charset into an external editor. This can, however, be easily changed by adding an UTF8 export/import mechanism.
- #9: after analysis and dicussion, this issue seems to be quite straight forward to elimnate: we should always convert to the set charset encoding when writing the mail (even to disk).
- #10: some functionality had already been partly added to YAM to address this issue. The main problem is that YAM (and even the system) doesn't have a functionality yet to tell if a certain date is/was within or out of daylight saving time. This functionality will be added in 2.9 so that correct DST management should be possible.
- #12: the LISTFREEZE arexx command seems to be broken and will be fixed.
- #18: a possibility will be added to be able to put the quick-filter component of the main GUI at the bottom of the main window (as hidden option). To handle this and other cases more efficient a new "View" main menu item will be added so that functionality that changes the main GUI can be added here.
- #20: improving the documentation is always a desirable change.
- #35: a functionality will be added that will allow to ignore and encrypted mail during a manual search or automatic filter operations.
- #40: the functionality to automatically jump to the latest unread msg will be moved to a folder option rather than providing this option globally only.
- #45: the date field in a read window always shows the full date line of the mail header. This will be changed so that the read window will also always show the date/time converted in relation to the timezone of the user using YAM.
- #48: a problem will be fixed which didn't copy a filter setting if switch the rules.
- #55: functionality will be added to allow to show the progress of the external archive by popping up the shell output of it.
- #62: when displaying attachments of a mail through the read window the keys 0-9 will directly load/act on the attachments 0-9. This should improve efficency in handling mails mit attachments.
- #72: YAM will be changed to display URLs in a mail text using underlined font style to comply with common standards on other platforms.
- #76: when deleting a mail YAM will respect the sorting order of the mail list and will be changed to select the correct mail afterwards.
- #78: when using the 'more' button in the filter configuration YAM will automatically jump to the bottom entry.
- #79: functionality will be added to allow to delete a filter rule not only from the bottom of the filter list but also in between.
- #84: To make the mail transfer window somewhat more verbose YAM will be changed to allow to display the To: header line of mails as well. This should then help to better/easily identify potentially spammed emails.
- #100: Printing emails will be improved so that a brief list of attachments will be printed under all circumstances.
- #103: When dragging mail out of the spam folder YAM will take care to correctly 'unspam' a mail.
- #108: A NOICONS option will be added to the REQUESTFILE Arexx command to allow to omit display of icons in the ASL requester.
- #222: Mail folder directories will be moved to a subdir (MailDir:Folders) so that a proper order is maintained. In addition the functionality to set the path of a mail folder will be limited/removed and only a 'display name' and 'folder name' be mainted to identify the folder.
- #261: As soon as there is no active account the Get toolbar button will be disabled. In addition, if no outgoing mail is present the Sent Mail button will also be disabled.
- #284: YAM will be changed that it will automatically save the GUI layout upon exit. This also includes the column settings of the mail mail list and the folder list. Currently a user has to explicitly 'snapshot' the GUI layout via MUI's own functionality or via the folder list save mechanisms which is unintuitive. A new config page entry in the Start/Quit page will be added that will allow to disable this and revert to the old behaviour.
- #291: when a search window or filter list is opened it will never be notified of any folder change happening in parallel (delete/create/rename). Thus, the search window or on similar situation it might be out of sync and not display the current state of affairs. This will be fixed.
- #298: The addressbook main list will be reworked to be able to quickly resort it by clicking on column titles.
- #311: The write window will be changed to show a short attachment list in the top right corner of the window so that attachments can be quickly added/removed without having to move to the second tab of the write window.
- #317: YAM will get an attachment reminder functionality. That means while writing an email YAM will monitor the input and if special words out of a user-definable list are found YAM will remind the user that he might need to add attachments before sending a mail. That should prevent sending out emails with missing attachments.
- #389: A not quite straight forwarded bug will be fixed which is caused by a bug in the all kind of AmigaOS related incarnations of the datatypes.library in combination with the image cache of YAM. A workaround will be introduced which will disable the internal image cache of YAM when 8bit screens are used because otherwise crashes occurs due to performed palette remappings.
- #400,#230: YAM will get the functionality to define own standard folders (incoming, outgoing, etc.) based on the corresponding POP/IMAP account. This will allow to have different incoming folders and thus sort emails based on account.