<p>Kaaryasthan is a <a href="https://www.gnu.org/philosophy/free-sw.en.html">free</a> task management software for small teams. Kaaryasthan helps you to manage private projects. You can add tasks & issues (items) in to your project. An item has title, description, discussions, creator, assignees, and labels. Project milestones can be created with due date and items with priority order.</p>
<p>The source of Kaaryasthan is hosted at GitHub: <a href="https://github.com/kaaryasthan/kaaryasthan">https://github.com/kaaryasthan/kaaryasthan</a>
The repo has source code for both user interface and server. The user interface of Kaaryasthan is written in Angular, server in Go, and PostgreSQL
is used for the database. <a href="http://www.blevesearch.com">Bleve</a> is is used for full-text search and indexing. The license is AGPL-3.0. The project is in Alpha stage now. Let me know, if you have any questions.</p>
<p>Disclaimer: As of now, this is just a side project for me. I have a full-time job, so I work only on my free time.</p>
<hr/>**评论：**<br/><br/>PaluMacil: <pre><p>Personally, I don't contribute to, recommend, or use AGPL software because it feels very restrictive to me. I prefer to provide software as MIT or BSD (I like Apache more in theory but prefer simplicity) and happily use / support LGPL and GPL plus a linking exception, but something with AGPL would prevent me from integrating its UI with other projects. I understand that some project might make sense as GPL (and certainly respect an author to make that choice), but I believe they are few (things like servers, art programs, and office software have been good GPL examples), and AGPL to me is never okay. My server is my personal business, and defining usage over a network as "distribution", requiring me to divulge modifications feels amazingly invasive of my personal space. I still emphasize that an author can make one's own choice, but this is the one license that I'll actively advise people to avoid in usage or in project contribution.</p></pre>baijum: <pre><p>Thanks for sharing your thought about AGPL!</p>
<p>I understand the AGPL-3.0 license will not be attractive for certain
contributors.</p>
<p>Despite these negatives, I think I have made up my mind.</p>
<p>Those who are not familiar with AGPL-3.0 license, I would suggest to
read this article: <a href="https://www.gnu.org/licenses/why-affero-gpl.en.html" rel="nofollow">https://www.gnu.org/licenses/why-affero-gpl.en.html</a></p>
<p>A quote from the above article:</p>
<blockquote>
<p>The GNU Affero General Public License is a modified version of the
ordinary GNU GPL version 3. It has one added requirement: if you
run a modified program on a server and let other users communicate
with it there, your server must also allow them to download the
source code corresponding to the modified version running there.</p>
</blockquote></pre>baijum: <pre><p>Here is one case study about AGPL-3.0: <a href="https://www.youtube.com/watch?v=116nfodTVOY" rel="nofollow">https://www.youtube.com/watch?v=116nfodTVOY</a></p></pre>
