<commit_before># Frump

Distributed tasks management tool based on Git and Markdown.

## Why?

Many task and project management solutions have good integration with Git, 
but a problem is usually left unsolved: they keep all tasks and their flow
outside Git, so it is hard to have a full picture of project's status and past
development only by looking at Git log.  
The next unsolved problem is that while your code is in a distributed system,
your tasks are not, preventing a team form a truly distributed collaboration.  

This tool aims to solve these very problems: when you clone a repo that uses 
Frump then you get not only the code but also all current and past tasks 
with their full history. 

## How?

Frump aims to be simple and human readable, so Markdown is selected as the 
underlying file format, a file (usually `frump.md`) is used to keep the state 
of the current tasks and Git log is used as the database for past changes.

## Philosophy

The most important feature of Frump is that you can use it without any tool. 
Knowing Frump's conventions is the only requirement of effectively using it.  

This feature leads to the next one: Frump is as simple as possible, you can 
open `frump.md` and easily read and edit all tasks, and you can use git log 
to see all past changes and closed tasks (a task is considered closed when
is removed from `frump.md` file).  

And of course `git pull`, along with the new code, gets you new tasks and tasks 
changes and `git push` pushes your task changes in the same commit with your code.  <commit_msg>Add "why 'frump'" info to README.md<commit_after># Frump

Distributed tasks management tool based on Git and Markdown.

## Why?

Many task and project management solutions have good integration with Git, 
but a problem is usually left unsolved: they keep all tasks and their flow
outside Git, so it is hard to have a full picture of project's status and past
development only by looking at Git log.  
The next unsolved problem is that while your code is in a distributed system,
your tasks are not, preventing a team form a truly distributed collaboration.  

This tool aims to solve these very problems: when you clone a repo that uses 
Frump then you get not only the code but also all current and past tasks 
with their full history. 

## Why "frump"?

Because with git they make a lovely couple.

## How?

Frump aims to be simple and human readable, so Markdown is selected as the 
underlying file format, a file (usually `frump.md`) is used to keep the state 
of the current tasks and Git log is used as the database for past changes.

## Philosophy

The most important feature of Frump is that you can use it without any tool. 
Knowing Frump's conventions is the only requirement of effectively using it.  

This feature leads to the next one: Frump is as simple as possible, you can 
open `frump.md` and easily read and edit all tasks, and you can use git log 
to see all past changes and closed tasks (a task is considered closed when
is removed from `frump.md` file).  

And of course `git pull`, along with the new code, gets you new tasks and tasks 
changes and `git push` pushes your task changes in the same commit with your code.  
{'fraction_non_alphanumeric': 0.03649407361197754, 'fraction_numerical': 0.0, 'mean_word_length': 3.941448382126348, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '580759', 'n_tokens_mistral': 830, 'n_tokens_neox': 807, 'n_words': 555}