README file: Add Glossary

[niinat]

Issue: Glossary is missing from Rultor product specification, it needs to be added at the end.
https://github.com/niinat/rultor/blob/master/README.md

[yegor256]

@alex-palevsky role is SA here

[yegor256]

@alex-palevsky and it's a bug

[alex-palevsky]

@alex-palevsky and it's a bug

@yegor256 I tagged this as "bug"

[alex-palevsky]

@niinat attached this issue to milestone "2.0" (let me know if this is wrong)

[alex-palevsky]

@alex-palevsky role is SA here

@yegor256 thanks, the role is SA here

[alex-palevsky]

@niinat thanks a lot for reporting, 15 mins added to your acc, pmt ID AP-656649754B348300W

[yegor256]

@alex-palevsky roles is SA here

[alex-palevsky]

@alex-palevsky roles is SA here

@yegor256 OK, it is SA here

[alex-palevsky]

@gumbelmj This task is yours, please go ahead keeping in mind this. If any questions, don't hesitate to ask right here

The budget of this task is 30 mins. This is exactly how much time will be compensated, when the task is completed. Read about our Definition of Done

[gumbelmj]

@alex-palevsky having read many of @yegor256's blog entries, if I understand the process correctly, this task should just be to add a "Glossary" section to the Readme.md with a TBD. Since I don't actually know what terms belong in the glossary or the definition of those terms, as I supposed to then create a puzzle to populate the glossary?

[alex-palevsky]

@alex-palevsky having read many of @yegor256's blog entries, if I understand the process correctly, this task should just be to add a "Glossary" section to the Readme.md with a TBD. Since I don't actually know what terms belong in the glossary or the definition of those terms, as I supposed to then create a puzzle to populate the glossary?

@gumbelmj @yegor256 please help us here

[yegor256]

@alex-palevsky this one should be postponed

[alex-palevsky]

@alex-palevsky this one should be postponed

@yegor256 OK, I put "postponed" label here

[alex-palevsky]

@alex-palevsky this one should be postponed

@yegor256 all right, we'll find someone else for this task