re version 2.8: do you plan to have a Docker container as well? (hint hint :-)
On Tue, Feb 27, 2018 at 5:40 AM, <[email protected]> wrote: > Hi all, > > We love Mayan EDMS and have come to depend on it for our daily work. Like > many of you we are worried about the effects hurricane Maria has had on the > development of the project. So we decided to do something about it. > > We gained good knowledge about the internals of Mayan EDMS from customizing > it for our own use. Looking at the code for the next version we could see > that much work had already been done. We were confident we could finish the > remainder tasks to be able to take the code to a point where a version 2.8 > would be possible. > > We contacted Roberto with our idea. While his communication options are > limited, he nonetheless provided us with some great guidelines. We don't > pretend our fork to replace Mayan EDMS so we are naming it Mayan EDMS NG > (Next generation). To make things easier we continued the version > numbering. > > So, we are proud to release our work as Mayan EDMS NG version 2.8. > > Our forks is just a continuation of the work already started by Roberto > for version 2.8. Therefore it is 100% compatible with any existing data. > > Our work focused on the following areas: > > * Finishing the API test refactor. The purpose of this refactor is to test > each API function for permission and access failure and success. The API > tests we also updated to conform with the new API Test class interface > which reduces a lot of boilerplate code. There are now a minimal of two > tests for each API function. > > * Some minor permission changes were made when obviously needed such as > the Workflow Create permission not having any effect. > > * Roberto had already backported the notifications feature to the "next" > branch and our work just focused on giving the final polish to this feature > by removing duplication. > > * Some user interface fixes and updated we added. These were inspired by > discussion on the mailing list and from looking at the Open Paperless fork > by Tina Zhou. > > * Introduction of the MERC (Mayan EDMS Request for Comment) as a means of > documenting the internals of the project, proposing features, changes to > the code as well as to the related process of the project. This type of > documentation mechanism has been very successful for other things like the > Internet (RFCs), Python (PEPs) and Django (DEPs) and we are sure it will > also help Mayan EDMS a lot. > > The repository for this fork is https://gitlab.com/Michael. > Price/mayan-edms. From there you can examine the changes that we made to > get the code to release level. Our work is available from PyPI as > mayan-edms-ng. > > We hope you enjoy it, thank you. > > Michael Price, internals and process > Eric Riggs, user interface > > -- > > --- > 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. > -- --- 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.
