Things have been progressing very rapidly and many of the foundation changes to the code have been made allowing for other high level changes to finally be implemented:
- The move to Celery is almost complete - The REST API has received a lot of attention in terms of quality and quantity, there are 79 API endpoints so far exposing about 75% of Mayan's total functionality, making integration work very easy. - Sending and receiving document via email is complete as well as having watched folders that upload documents at intervals. - The move to Django 1.7 won't be possible for this next release but the work to do so is well underway, it will be a high priority item for the next version. - Search results are now secured with required permissions and exposed as an API service. - Another big change is the metadata validation work by Gary Walborn that solves the problem of not only checking user input but also formatting it if needed. - Mathias Behrle's help is too big to list individually, his input, testing and help managing the project deserve much mention. - Work on the settings files started by Paul Whipp continued with some improvements what will allow Mayan to be deployed to production much easier. - Thanks to Mathias's initiative, text message across the entire code have been removed and simplified to increase make it easy to translate Mayan into more languages. In this same topic Ford Guo has submitted a complete translation to Simplified Chinese making Mayan more accessible to millions of new users. - Devin Ceartas, Mathias, Jens Kadenbach and Timothy Duffy have been incredibly helpful and patient helping solve some very obscure bugs relating to PDF handling and sub-process calling which prompted the eventual move to Celery. - Support for Python 2.6 has been deprecated and work on supporting Python 3 has started. - While still early for inclusion, Emlyn Clay's work on a new bootstrap based template system is nothing short of amazing. - Finally the code footprint has also been reduce drastically with the removal of many superfluous code. - Subscription and activity on the Google Group, Github's page, Google Plus page, Transifex project page, Website and Twitter account have increased, thanks to every subscriber, member, poster and reader! - Last but not least, thanks to Cryptico Corporation and S.A., LLC for sponsoring work on Mayan EDMS. I've tagged some more issues with the label 'easy pickings' to allow for people wanting to contribute to tackle tickets that do not require complete immersion on the code. Now that the templates have been simplified I've also added a label called 'frontend / GUI' for those wanting to take on the appearance and layout of the project. Finally here is a list of the issues that are blocking the next release: https://github.com/mayan-edms/mayan-edms/milestones/1.1, the completion counter says 33% complete but a good part of the tagged issues are almost ready to be closed or are not as difficult to complete now that most of the architecture code changes have been completed. As always thanks to everybody for your work in helping move the project forwards it would not be hard to name this next version Mayan 2.0 based on the amount of code and changes that have taken place, thanks! -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
