| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| hashtagvalues [2025/06/15 19:36] – admin | hashtagvalues [2025/06/15 19:43] (current) – admin |
|---|
| |
| **Flexible and //loosely-coupled//**\\ | **Flexible and //loosely-coupled//**\\ |
| This is extremely useful in small/medium size offices where people may be asked to do //different kinds// of work. One source of anguish that employees often have is that they don't get recognized (aka paid) for the hard-work they put in different types of work they did for the office. Such hashtag values can be inserted in appraisals between an employee and his/her manger or owner as comments into the Kanban system. | The concept of //hashtag values// is extremely useful in small/medium size offices where people may be asked to do //different kinds// of work. One source of anguish that employees often have is that they don't get recognized (aka paid) for the hard-work they put in different types of work they did for the office. Such hashtag values can be inserted in appraisals between an employee and his/her manger or owner as comments into the Kanban system. |
| |
| This is a //loosely-coupled// system. Which means, we do not insist that you //must// use this. Maybe you may use this with other variations. For e.g. instead of giving the values as number of hours spent, it could be percentages, reward points or actual money or some kind of //gamification// points... that's all up to that office which uses //Git Winch//. | This is a //loosely-coupled// system. Which means, we do not insist that you //must// use this. Maybe you may use this with other variations. For e.g. instead of giving the values as number of hours spent, it could be percentages, reward points or actual money or some kind of //gamification// points... that's all up to that office which uses //Git Winch//. |
| |
| |
| **Who can do this analysis**\\ | **Who can do this analysis?**\\ |
| Anyone can invoke the Hashtag analysis. Internally, //Git Winch// will assume that you are the owner of some //Kanban Group// in the web-app, and also owner of some repositories too. If you are not an owner of either, the generated CSV file will be empty. | Anyone can invoke the Hashtag analysis. However; internally, //Git Winch// will assume that you are the owner of some //Kanban Group// in the web-app, and also owner of some repositories too. If you are not an owner of either, the generated CSV file will be empty. //Git Winch// will only search in Kanban groups and repositories where you are the owner. |
| |
| Internally, //Git Winch// will check the backend coordination server's database and note down which all Kanban cards where you have commented, and all repository file-notes with your notes too. (Note: As stated above, only for the Kanban groups and Repositories that you had created). | Internally, //Git Winch// will check the backend coordination server's database and note down which all Kanban cards where you have commented, and all repository file-notes with your notes too. (Note: As stated above, I am repeating: only for the Kanban groups and Repositories that you had created). The first line of such comments and/or notes would be examined for comma-separated //hashtag values//. |
| |
| It will find out who else was the one who created the Kanban card. Or, in case of Repository file-notes; who else had written notes for that particular file. The first line of such comments and/or notes would be examined for comma-separated //hashtag values//. | It will find out the person who created the Kanban card. Or, in case of Repository file-notes; it will note down all members who had written notes for that particular file. |
| |
| For example; on one comment for a particular Kanban card you wrote the following comment | For example; on one comment for a particular Kanban card you may have written the following comment |
| |
| #admin:4.5 | #admin:4.5 |
| |
| In another file-note you had written the following | In another file-note you had written the following: |
| |
| #redlining:8;admin:9.5 | #redlining:8;admin:9.5 |
| |
| As you can see; you did not write just #admin or just #redlining. Instead you also gave a value for those hashtags. Again, I am reminding you: //For this action, Git Winch assumes you are the one doing the assessment and it would only check those Kanban groups and repositories, which you had created!// | As you can see; you did not write just #admin or just #redlining. Instead you also gave a value for those hashtags. |
| |
| Internally, //Git Winch// will place the values of 4.5 and 9.5 for //#admin//. And 8 would be the value for //#redlining//. Of course, the person to whom this value would be given would be based on whose Kanban card was being worked on. In case, of //file notes//, the values would be attributed to who else had put their own comments on that file. | This is quite similar to a teacher in a classroom giving marks for various subjects to students in the class. So the students (aka other members) themselves do not write their own hashtag values. But it is the teacher (i.e. the creator of the Kanban group or Repository) who wrote the hashtag value as a comment or file-note. |
| | |
| | Internally, //Git Winch// will place the values of 4.5 and 9.5 for //#admin//. And 8 would be the value for //#redlining//. Of course, the person to whom this value would be given would be based on whose Kanban card was being worked on. In case, of //file notes//, the values would be attributed to all those wh had put their own notes onthat file. |
| |
| After processing those hashtag values, the CSV file is generated. | After processing those hashtag values, the CSV file is generated. |