matthias/mayan-edms
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Files
059dff02f3fa8635d0e9d90b43b27fd0c045f444
mayan-edms/news.html

293 lines
27 KiB
HTML
Raw Blame History

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Mayan EDMS :: Latest news</title>
<meta name="description" content="Latest development, support news for Mayan EDMS" />
<meta name="keywords" content="open source, django, dms, edms, cms, electronic document, news" />
<link href="css/main.css" rel="stylesheet" type="text/css" />
<link rel="icon" type="image/png" href="images/bullet.png" title="Mayan" />
<!-- Add jQuery library -->
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.7/jquery.min.js"></script>
<!-- Add mousewheel plugin (this is optional) -->
<!-- <script type="text/javascript" src="/fancybox/lib/jquery.mousewheel-3.0.6.pack.js"></script> -->
<!-- Add fancyBox -->
<link rel="stylesheet" href="packages/fancybox/source/jquery.fancybox.css?v=2.0.4" type="text/css" media="screen" />
<script type="text/javascript" src="packages/fancybox/source/jquery.fancybox.pack.js?v=2.0.4"></script>
<!-- Optionaly add button and/or thumbnail helpers -->
<link rel="stylesheet" href="packages/fancybox/source/helpers/jquery.fancybox-buttons.css?v=2.0.4" type="text/css" media="screen" />
<script type="text/javascript" src="packages/fancybox/source/helpers/jquery.fancybox-buttons.js?v=2.0.4"></script>
<link rel="stylesheet" href="packages/fancybox/source/helpers/jquery.fancybox-thumbs.css?v=2.0.4" type="text/css" media="screen" />
<script type="text/javascript" src="packages/fancybox/source/helpers/jquery.fancybox-thumbs.js?v=2.0.4"></script>
<script type="text/javascript">
$(document).ready(function() {
$(".fancybox").fancybox({
prevEffect : 'fade',
nextEffect : 'fade',
closeBtn : false,
helpers : {
buttons : {},
overlay : {
opacity : 0.8,
css : {
'background-color' : '#000'
}
},
thumbs : {
width : 50,
height : 50
}
}
});
});
</script>
<script type="text/javascript">
(function() {
var po = document.createElement('script'); po.type = 'text/javascript'; po.async = true;
po.src = 'https://apis.google.com/js/plusone.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s);
})();
</script>
</head>
<body>
<div id="header">
<h1><a href="#">News</a></h1>
<ul id="menu">
<li><a href="index.html">about</a></li>
<li class="active"><a href="news.html">news</a></li>
<li><a href="screenshots.html">screenshots</a></li>
<li><a href="download.html">download</a></li>
<li><a href="support.html">support</a></li>
<li><a href="others.html">on the web</a></li>
<li><a href="gpl.html">GPL violations</a></li>
</ul>
</div>
<div id="teaser">
<div class="wrap">
<div id="image"></div>
<div class="box">
<h2>Welcome to <em title="Electronic Document Management System">Mayan EDMS</em><span class='gplus'><g:plusone size="medium"></g:plusone></span></h2>
<p>
Open source, Django based document manager with custom meta-data indexing, file serving integration, document tagging and OCR capabilities.
</p>
<a href="https://dashboard.appsembler.com/appstore/app/48/mayan/"><img style="width: 40%;" src="images/appsembler_button.png" /></a>
</div>
</div>
</div>
<div id="bar">
<div class="wrap">
<span class="step"><a>1</a> Capture</span>
<span class="step"><a>2</a> Organize</span>
<span class="step"><a>3</a> Store</span>
</div>
</div>
<div class="wrap">
<ul class="piramid_bullets news">
<li>
<a href="#20120828"><h3><span class="red">August 28, 2012</span></h3></a>
<h4>GPL violations, second (and hopefully final) update</h4>
<p>The <strong>DMS</strong> market is a very big revenue market, there are just few but big players, now do the math. <strong>Mayan EDMS</strong> was never very well received into this market, from it's <strong>Wikipedia</strong> article being erased to its entries being removed from <strong>open source DMS software directories</strong> and press releases being sometimes ignored, I'm used to this kind of situation, such is life, this is not a tantrum.</p>
<p>I have a full time day job and <strong>Mayan EDMS</strong> provides some side income by means of my own startup (<a href="http://documen.to">Documen.to</a>), I'm have been well aware that from the beginning people would make money from it, a lot more than me too. Even the stand alone consultants are probably doing more money than me and the corporations are most certainly doing a lot more, so, as I said that doesn't bother me in fact it is something that has been promoted from day one. Some people are doing consulting (<a href="http://quintagroup.com/">Quinta Group</a>), others are doing service level agreements, others are doing cloud deployments (<a href="http://appsembler.com">Appsembler</a>), others selling turn-key solutions integrating <strong>Mayan EDMS</strong> with scanning and printing equipment, others want to sell repackaged versions of <strong>Mayan EDMS</strong> (<a href="http://www.jtpnet.com/">JTP</a>) others are selling document appliances (<a href="http://www.rtm-it.com">RTM-IT</a>). All that doesn't bothers me in fact I feel proud my software and the choice of license I use is creating commercial opportunities for so many.</p>
<p>This is also not an issue of the <strong>GPL</strong> being defective, or about me not reading or applying the <strong>GPL</strong> incorrectly, and certainly not about <strong>GPL</strong> vs. <strong>BSD</strong> vs. <strong>MIT</strong> vs. <strong>Apache</strong>, etc. While I do appreciate the suggestions about the license change, I will stick with the <strong>GPL</strong>. The <strong>GPL</strong> is not complicated, its basic premise is actually simple: you get software with certain freedoms, you can do whatever you want with it as long as those freedoms remain unchanged.</p>
<p>If you look at the changelog, there have been <strong>20</strong> releases so far in about a year and a half, please point out where in my past communications I have said I intend to change the licenses of all those previous releases or the license of the current release. The <strong>GPL</strong> actually doesn't allows that, it protects the code itself from everybody including from myself. If I were to stop working on <strong>Mayan EDMS</strong>, anyone can continue working and releasing new versions, and that is the beauty of it. That is something that doesn't happens with commercial software, in the commercial setting when the company decides the product is dead, it is dead and there is nothing the end users can do about it.</p>
<p>Some action is better than no action, restricting access to the development branch has been criticized, but it is managing to weed out non compliance and sending a message of the seriousness with which the <strong>GPL</strong>, the copyright issues and the contributions of the community are being taken. The community has been supportive of this decision as they understand what is at stake and the reasons behind it.</p>
<p>If the development were to continue behind doors, that is not a <strong>GPL</strong> violation, the <strong>GPL</strong> doesn't dictate development procedure, so development can be done with limited access and when ready, released and it will still be valid <strong>Free</strong> and <strong>Open Source software</strong>.</p>
<p>I don't mind people charging for their services in relation to <strong>Mayan EDMS</strong> or for <strong>Mayan EDMS</strong> itself, within the terms of the <strong>GPL</strong> it can be resold for a reasonable fee, in the same way I can download <strong>Ubuntu</strong>, burn a CD and charge a percent over the costs of the CD and the cost of the download, that same situation is allowed for <strong>Mayan EDMS</strong>. Reasonable is open to interpretation but $999.00 per seat license is not a reasonable fee if your are also changing copyrights, not releasing the source code and marketing it as an original product. That is callous, it is a copyright infringement and a <strong>GPL</strong> infringement.</p>
<p>Given the amount of flame I've gotten in my inbox for this I'm reassured that not releasing the information of the non compliant products was the best course of action and a decision that eventually led to the resolution of this issue. I cannot however, guarantee that will be the case in the future.</p>
<p>Finally, I am very happy to inform that 2 of the original non compliant products as well as many other individuals have come forward with the intent to comply with the <strong>GPL</strong> or reach some kind of licensing agreement.</p>
</li>
<li>
<a href="#20120828"><h3><span class="red">August 28, 2012</span></h3></a>
<h4>GPL violations, update</h4>
<p>To all the people telling me to f****** learn to read and to RTFM the <strong>GPL</strong>: I have read the <strong>GPL</strong>, this is not my first project being released as <strong>Free software</strong>, as <strong>Open Source software</strong> or under the <strong>GPL</strong> (<a href="http://code.google.com/p/descartes-bi/">Descartes BI</a>, <a href="https://github.com/rosarior/django-replication">Django-replication</a>, <a href="https://github.com/rosarior/pdf-form-fill">pdf-form-fill</a>). It is also not the first project to enjoy widespread use and to be released as a commercial product by other people (<a href="https://github.com/rosarior/django-inventory">Django-inventory</a>), however in those instances the people doing the forks have complied with the <strong>GPL</strong> admirably providing source code for their changes, retaining all copyrights, notices and original license even when being released under a different name. That however is not the situation that is happening now. This is not "whinnying over some little program" (as it is being described commonly in the feedback I'm getting via email), the <strong>GPL</strong> is no less legal than a commercial license and must be followed and enforced equally, <strong>Mayan EDMS</strong> is not some "little program" currently sporting 26,000 lines of code. And just because a program is being released as <strong>Free Open Source</strong> software doesn't make it any less valuable than a commercial counterpart. Finally the entire source was not removed, only the development branch and the hotfix branch for the next version. Let me repeat that again, the entire source code was <strong>NOT</strong> removed only the <strong>TWO (2)</strong> latest <strong>unreleased</strong> branches. Lastly about the commercial competition issue: If I have no problems with people or business making money off <strong>Mayan EDMS</strong>, in fact I proud myself in creating commercial opportunities to others by advertising them, right here, in this very website, on the top menu, three tabs to the right. I hope this clarifies and overturns some of the misinformation being circulated, thank you.<p/>
</li>
<li>
<a href="#20120827"><h3><span class="red">August 27, 2012</span></h3></a>
<h4>GPL violations</h4>
<p>I choose to release <strong>Mayan EDMS</strong> under the <strong>GPL</strong> which means you get the source code of the software plus the freedom to use it, modify it and pass it on forward to other people. I share the fruits of my labor and all that you are asked to do is share what you build on top of <strong>Mayan EDMS</strong> too. If being given the software with all these liberties and that simple requirement wasn't enough, <strong>Mayan EDMS</strong> is also provided free of charge, it cost you $0.00 to download, install or use, there is no registration required, there are no limitation of the amount of user, roles, group, folders, documents, indexes or features, unlike most other open source document management software in the market. However that doesn't mean <strong>Mayan EDMS</strong> is public domain and that it belongs to everybody, that's the only thing I'm keeping for myself, it is my property but I'm choosing to share it with you. If you fork <strong>Mayan EDMS</strong> into a closed or private respository, stop and think about what you are doing because you going about it the wrong way. Likewise if you fork <strong>Mayan EDMS</strong> and the first patch you commit is to change the name, stop. It has come to my attention that there are a number of unauthorized forks of <strong>Mayan EDMS</strong> being offered for download as if the original version was being abandoned and at least one fork is being sold with a comercial license to add insult to injury. These violators have been listed in a new page called <a href="gpl.html">GPL violations</a>.</p>
<p>How will this affect the future of <strong>Mayan EDMS</strong>? It is too early to tell, what is certain is that the latest technologies being added to <strong>Mayan EDMS</strong> must be protected until they are ready to be released. Taking this into account and effective inmediately the development branch has been removed from the public repository until I figure out what to do or that it is finished and ready for public release as the next version of <strong>Mayan EDMS</strong>.</p>
</li>
<li>
<a href="#20120807"><h3><span class="red">August 07, 2012</span></h3></a>
<h4>Mayan development work in progress</h4>
<p>This has been a very exciting development cycle, many new additions are making their way into the code as well as third party project support.</p>
<p>A huge thanks go to <a href="http://www.rtm-it.com/">RTM-IT corp.</a> for their donation of <em><strong>Citadel</strong></em>, their commercial clustering product for <strong>Mayan EDMS</strong>. <em><strong>Citadel</strong></em> is now part of the <strong>Free Open Source</strong> version of <strong>Mayan EDMS</strong> and available for everyone to use and enjoy! We hope that along with <a href="http://www.rtm-it.com/">RTM-IT Corp.</a> and <a href="http://www.seeopen.it/">SeeOpen S.r.l.</a> other commercial organizations step up and contribute to the core of what <strong>Mayan EDMS</strong> is. If you make money somehow from <strong>Mayan EDMS</strong> please consider giving something back to the community, whether it is monetary donations, patches, testing and now that clustering is an integral part of <strong>Mayan EDMS</strong>, hardware for a server farm for testing will be needed, so every bit helps.</p>
<p>Another great news is that the first mobile app specifically designed for <strong>Mayan EDMS</strong> is in the works by <strong>Pablo Juan Rivera (orangethirty)</strong>.</p>
<p><img class="screenshot center" src="images/news/mayan_android_promo.png" /></p>
<p>Along with a major refactoring of every internal code from navigation to tool registration some frequently requested additions have been implemented and added like: a complete move to <strong>Django 1.4</strong>, a bootstrap app to create metadata, indexes and document types to help user get up and running faster when installing <strong>Mayan EDMS</strong> for the first time. Several more translations have made their way: <strong>Dutch</strong> (<strong>Lucas Weel</strong>), <strong>Bulgarian</strong> (<strong>Iliya Georgiev</strong> and <strong>Koldo</strong>) and <strong>French</strong> (<strong>Pierre Lhoste</strong>). Full migration to <strong>South</strong>, this will make upgrade from this next version onwards much easier. Trash can support, a <strong>Pygments</strong> renderer to support colorized display of code files, initial implementation of retention policies and many more fixes and small updates everywhere.</p>
<p><img class="screenshot center" src="images/news/mayan-news-jobprocessor.png" /><img class="screenshot center" src="images/news/mayan-news-pygments.png" /><img class="screenshot center" src="images/news/mayan-news-nodes.png" /></p>
</li>
<li>
<a href="#20120630"><h3><span class="red">June 30, 2012</span></h3></a>
<h4>Mayan 0.12.2 released</h4>
<p>This is the second maintenance release of the 0.12 series. Issues covered in this version: more secure auto admin creation, new logo in place, installation environment report app for remote debugging, anonymous statistics gathering, German translation by Tetja Rediske and Tilmann Sittig and a fix for the duplicated extension bug when uploading a new document version. One new feature of importance is the ability to check out documents effectively blocking new versions of the document while the original user that checked out the document updates it. For more information read the full <a href="http://mayan.readthedocs.org/en/latest/releases/0.12.1.html">release notes</a>.</p>
</li>
<li>
<a href="#20120614"><h3><span class="red">June 16, 2012</span></h3></a>
<h4>Free trial of Mayan EDMS on the cloud</h4>
<p><a href="http://appsembler.com">Appsembler.com</a> has graciously offered to provide a free 30 day trial of Mayan EDMS on their breakthrough SaaS platform for completing this <a href="http://bit.ly/mayan-survey">survey</a>!
</li>
<li>
<a href="#20120604"><h3><span class="red">June 04, 2012</span></h3></a>
<h4>Mayan 0.12.1 released</h4>
<p>Mostly a bug fix release, but three very important improvements made into this version. The document text parsing subsystem has been re-factored to allow several parsers per file type, a new PDF parser based on poppler-utils's pdftotext utility submited by Brian E. was also added. This is now the default method Mayan EDMS will execute to try to extract text from a PDF file and failing that will fallback to the previous method. Be sure to install the poppler-utils OS package to take advantage of this new parser. Also added is an improved office document conversion method that doesn't rely on unoconv to work, aside from this mayor improvements other changes made it into this release: complete Italian translation, an automated install method using a Fabric file (fabfile) that supports single, multiple and heterogeneous deployments, the installation documentation was also updated. The OCR queue is now active by default when first created during the syncdb phase and the OCR_AUTOMATIC_OCR option now defaults to True. These two changes are made to reduce the steps required for new users to start enjoying the benefits of automatic text extraction from uploaded documents without having to read the documentation and have a more functional default install. As always full documentation as well a release notes can be found at <a href="http://mayan.readthedocs.org/en/latest/releases/0.12.1.html">readthedocs.com</a></p>
</li>
<li>
<a href="#20120524"><h3><span class="red">May 24, 2012</span></h3></a>
<h4>Statistics gathering</h4>
<p>With the recent removal of Mayan EDMS's article from Wikipedia, because of a lack of notability according to the editors that tagged it, a renewed effort to gather statistics in underway. If you are using, planning to use or just interested in Mayan EDMS please take a moment to fill out this simple <a href="https://docs.google.com/spreadsheet/viewform?formkey=dHVSTld2M2tkR3BfUFFfWm1PM1hQaXc6MQ">survey</a>.</p>
</li>
<li>
<a href="#20120429"><h3><span class="red">April 29, 2012</span></h3></a>
<h4><strong>Interesting video</strong>, Mayan EDMS case study by SaaS provider <a href="http://appsembler.com">Appsembler</a>.</h4><br />
<iframe class="screenshot center" width="420" height="315" src="http://www.youtube.com/embed/ioUJEBA5c1c?rel=0" frameborder="0" allowfullscreen></iframe>
</li>
<li>
<h3><span class="red">March 13, 2012</span></h3>
<h4>Mayan EDMS <strong>Google Plus Hangout</strong>.</h4><br />
<p>I will be doing a <strong>Google plus</strong> hangout to answer questions about <strong>Mayan EDMS</strong> and <strong>document management</strong> for those using it or planning to use it. So if you have a <strong>Google Plus</strong> account drop by Wednesday March 14, 2012 at about 7:00pm AST for the first ever <strong>Mayan EDMS Hangout!</strong></p>
</li>
<li>
<a href="#20120313"><h3><span class="red">March 13, 2012</span></h3></a>
<h4>Version 0.13 development cycle started.</h4><br />
<img class="screenshot center" src="images/news/395266_prisoners_of_rust_1.jpg" />
<p>Two very much requested features have landed in the development version of <strong>Mayan EDMS</strong>: The ability to send documents or document links via email and to be able to receive document as attachments via email and process them automatically.</p>
<a class="fancybox" rel="news" href="images/news/mayan-pop3.png" title="POP3 email support"><img class="screenshot center" src="images/news/mayan-pop3.png" width="640px"/></a>
<p>So head over to <strong>Github</strong> and <a href="https://github.com/rosarior/mayan/tree/development">clone the latest development branch</a> to start using and testing these new features.</p>
</li>
<li>
<a href="#20120227"><h3><span class="red">February 27, 2012</span></h3></a>
<h4>Mayan EDMS version 0.12 released!</h4><br />
<img class="screenshot center" src="images/news/548599_68236939.jpg" />
<p>Almost 3 months in the making and <a href="https://github.com/rosarior/mayan/commit/2b1e1be680eda385491a148cbca018061ea9c96d">1 year after it was initially started</a>, version 0.12 of <strong>Mayan EDMS</strong> is now available. Thanks to everybody that <a href="http://readthedocs.org/docs/mayan/en/latest/credits/contributors.html">contributed</a> in one way or another to make this possible! Highlights for this new version include:</p>
<ul>
<li>ACL support, per document, folder or tag access control</li>
<li>Anonymous user support, allow non authenticated user access to the web interface</li>
<li>Updated Russian translation as well as new Italian and partial Polish translations</li>
<li>Widgets usability improvements</li>
<li>Ability to download multiple documents as a single zip file</li>
<li>Customizable <strong>GPG</strong> home directory, for distributions that do not provide a sensible default</li>
<li>Command line utilities for the bulk upload of documents and user accounts</li>
<li>Refactored document indexing, multiple automatic indexes can now created</li>
<li>Improved code quality and <a href="http://readthedocs.org/docs/mayan/en/latest/index.html">documentation</a></li>
</ul>
<br />
<p>For a more complete list of the new features, changes and removed items read the <a href="http://readthedocs.org/docs/mayan/en/latest/releases/0.12.html">Version 0.12 release notes</a>.</p>
</li>
<li>
<h3><span class="red">January 12, 2012</span></h3>
<h4>New Google group</h4><br />
<p>To increase communication between users of <strong>Mayan EDMS</strong>, a <strong>Google group</strong> has been created, it is low volume and everything related to <strong>Mayan EDMS</strong> will be discussed there.</p>
<table border=0 style="background-color: #fff; padding: 5px;" cellspacing=0>
<tr><td>
<img src="http://groups.google.com/intl/en/images/logos/groups_logo_sm.gif"
height=30 width=140 alt="Google Groups">
</td></tr>
<tr><td style="padding-left: 5px">
<b>Subscribe to Mayan EDMS</b>
</td></tr>
<form action="http://groups.google.com/group/mayan-edms/boxsubscribe">
<input type=hidden name="hl" value="en">
<tr><td style="padding-left: 5px;">
Email: <input type=text name=email>
<input type=submit name="sub" value="Subscribe">
</td></tr>
</form>
<tr><td align=right>
<a href="http://groups.google.com/group/mayan-edms?hl=en">Visit this group</a>
</td></tr>
</table>
</li>
<li>
<h3><span class="red">December 19, 2011</span></h3>
<h4>Document level access support</h4><br />
<p>Still many things left to do, but after much work the <strong>ACL subsystem</strong> is in a usable state. Document level access is already supported with folder and tag level access following suit.</p>
<a class="fancybox" rel="news" href="images/news/acl_support.png" title="Document level access support"><img class="screenshot center" src="images/news/acl_support.png" width="640px"/></a>
</li>
<li>
<h3><span class="red">December 13, 2011</span></h3>
<p>The Italian translation for <strong>Mayan EDMS</strong> has been completed, merged in the development branch and will be included in the upcoming version 0.12. Many thanks to <a href="http://www.seeopen.it">SeeOpen.IT</a> for this contribution.</p>
</li>
<li>
<h3><span class="red">December 7, 2011</span></h3>
<h4>Bugfix version v0.11.1</h4><br />
<p>This is the first bugfix release of the .11 series, and includes the following:</p>
<ul>
<li>A documents deletion regression fix</li>
<li>Improves error detection when importing keys from a keyserver</li>
<li>Fixes a wrong method call when verifying signatures for the first time upon document uploading</li>
<li>django-compress is now disabled by default to avoid problems when deploying with DjangoZoom</li>
</ul>
</li>
<li>
<h3><span class="red">December 6, 2011</span></h3>
<h4>Mayan v0.11 released!</h4>
<h5>Highlights</h5>
<p>Two of the most asked features have been included:</p>
<ul>
<li>Document signature verification support (both: embedded and detached)</li>
<li>Document versioning support</li>
</ul>
<p>The full changelog can be found here: <a href="http://readthedocs.org/docs/mayan/en/development/updates.html#version-0-11">http://readthedocs.org/docs/mayan</a></p>
</li>
<li>
<h3><span class="red">December 4, 2011</span></h3>
<h4>Document versioning</h4>
<p>Multiple document versions is almost ready and will be included in the next version (v0.11), the REST API has also been updated to expose this new functionality.</p>
<a class="fancybox" rel="news" href="images/mayan-multi-ver.png" title="Document versioning"><img class="screenshot center" src="images/mayan-multi-ver.png" width="640px"/></a>
</li>
<li>
<h3><span class="red">December 3, 2011</span></h3>
<h4>Digital signature verification</h4>
<p>Digital signature verification has seen many updates but it is still uncertain if it will be complete enough to be included in the next version.</p>
<a class="fancybox" rel="news" href="images/mayan-signature.png" title="Signature verification"><img class="screenshot center" src="images/mayan-signature.png" width="640px"/></a>
</li>
</ul>
</div>
<div id="footer">
<p class="right">Design: Luka Cvrk, <a title="Awsome Web Templates" href="http://www.solucija.com/">Solucija</a></p>
<p>&copy; Copyright 2011, 2012 <a href="mailto:roberto.rosario@mayan-edms.com">Roberto Rosario</a> &middot; All Rights Reserved</p>
</div>
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-22801354-1");
pageTracker._trackPageview();
} catch(err) {}</script>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink