Hi all, this is the location of the proposed MERCs: https://gitlab.com/Michael.Price/mayan-edms/tree/master/docs/mercs At the moment we have the following proposals:
* merc-process, MERC-0001 = Process MERC to propose the creation of the MERC documents. * test-writing, MERC-draft = Process MERC to document and standardize the way tests are written in Mayan EDMS. * mergin-roles-and-groups, MERC-draft = Feature MERC that proposes the elimination of the Role models and transfer their functionality to the Group model. * support-forum, MERC-draft = Process MERC that proposes the creation of a support forum for the Mayan EDMS community using a self hosted and proper forum software instead of Google Group, a mailing list platform configured as a forum. We also created an addendum to the development chapter of the documentation with things that need worked on or fixed. These are things we found during the work done to release version 2.8 of Mayan EDMS NG. The chapter file is here: https://gitlab.com/Michael.Price/mayan-edms/blob/master/docs/topics/development.rst We believe this proposal procedure and a better documentation process is all that Mayan EDMS needs to continue being a disruptive product in the document management industry. Copy of the Pending tasks addendum: -------------- *Pending tasks* These are task that need to be completed but are missing a dependency or a design decision. As more information is added to each, they should be converted into a MERC. *API* * User API edit view: Should not be able to add of remove groups without corresponding group access. * User group list API get & post views: Should adding a group to an user via the API return 201 or 200. Currently returns 201. * Consistent API return code for delete views without access. Some views return 403 other return 404. *Caching* * Size limited caching. A new model in the common app will keep track of all cache files. A manager method will be provided that will return the cache files in other of age to be deleted. *Forms processing* * Remove usage of self.cleaned_data. Use self.clean_data instead. *Metadata* * Metadata lookup memory. Add a select2 style widget that will query a new metadata API endpoint that will return all used values so far. *Notifications* * Fix notification duplication of global & per document subscription notifications. (This was fixed prior to the release) *Other* * Python based Javascript package manager. Each app specifies what library and version needs. The common app (or a new app) will add all the JS loading lines automatically so that compress can detect them. * When moving documents to the trash update the message to "submitted" and not "moved" or "deleted" since this is handled by a task queue and is not immediate and doesn't delete the document. * When emptying the trash update the message to "submitted" since this is handled by a task queue and is not immediate. * New app that allows creating user document filters. Will provide the same service as the document filters class. Interface can be made using the template language or the same UI as the smart links. * Allow add queue metadata that can be exported via a management command. This will allow creating supervisor templates without all the worker entries being hardcoded. * Delete .gitignore files from copied packages. Include .gitignore files keep compiled or distributable files from being included in the main repository. Temporary measure until a Javascript library manager is added. * Automatically capture license information from installed Javascript libraries. * Automatically capture license information from installed Python packages. *Permissions* * Permission should be reciprocal. Example: To be able to add a tag to a document, the user must hold the tag add permission for the document and for the tag to be added. To be able to enable a metadata type to a document type, the user must hold the metadata add permissions for the metadata type and for the document type. * Edit type permissions should only grant the ability to edit the properties of an object. To modify its relationship with other objects a reciprocal permission check should be instead. *Sources* * Add ACLs support to sources. * Provide error message/feedback when scanning from a remote scanner fails. * Redirect to the same source when scanning from a remote scanner finishes. *Testing* * Add document test mixin that creates documents types and documents (to be used in dynamic_search.test_api). *UI* * Shift click to select multiple documents. * During the document upload wizard and the option to double click to select document type and submit the form. The purpose is to speed up the step with less mouse travel since this is a common screen. * Add metadata to the Menu class to allow UI code to decide where and how to display each menu. *Workflows* * Workflow trigger filters. Example: {{ document.document_type.name = 'invoice' }} or same UI as the smart links app. Will allow restricting the firing of workflow actions by a user defined filter criteria. * Require a permission for document types to avoid a user that has the workflow creation permission to attach a workflow to a document type they don't control. * Research making APIWorkflowDocumentTypeList a subclass of documents.api_views.APIDocumentTypeList * A POST request to APIWorkflowDocumentTypeList should require some permission on the document type part to avoid adding non controlled document types to a new workflow. * To transition a workflow, the transition permission is only needed for the workflow. Make it necessary to have the same permission for the document of document type. * To view the transition log, the workflow view permission is only needed for the document. Make it necessary to have the same permission for the workflow or for the transition and the states. -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
