New abbrs and last changes before dictionary

[T1xx1]

Add discussed abbrs

• [x] #31
• [x] #32
• [x] #33
• [x] #40 After this pull, I'm closing these issues.

Some suggestions before the dictionary.

1. Clear the issues. Close #14 as included in dictionary and acronym suggested by @oood. Close #17, #19, #20, #29.
2. I think we should open the GitHub projects by adding a list of issues in order of how we should resolve them however we will end up having thousands of issues without resolving them.
3. Add all the new dictionary commits in a new branch before creating the organization.

[kisvegabor]

I think it's not critical to fix pending abbreviations. We can continue their discussions when the we have the "raw database".

[oood]

Clear the issues. Close i, j and k / single letter abbrevs #14 as included in dictionary and acronym suggested by @oood. Close Add 'chr' to character #17, "function", "vertical" #19, Update README.md #20, pub, priv, lat and lng added or updated #29.

Considering that the project's positioning is to develop into a dictionary, then I support its inclusion.

Of course, we don't need to include all 26 letters, only those that are most commonly used.

I think we should open the GitHub projects by adding a list of issues in order of how we should resolve them however we will end up having thousands of issues without resolving them.

Agreed, it makes things easier, especially now that there are multiple to-dos and need a place to record the to-do list.

Would you like to help to see how to enable this? @kisvegabor

Add all the new dictionary commits in a new branch before creating the organization. I think it's not critical to fix pending abbreviations. We can continue their discussions when the we have the "raw database".

Sooner or later we all need to add them into the database.

[T1xx1]

Sooner or later we all need to add them into the database.

Yes, thought this before the org project.

[kisvegabor]

I think we should open the GitHub projects by adding a list of issues in order of how we should resolve them however we will end up having thousands of issues without resolving them.

What is the advantage of "Projects" compared to Issue labels?

[T1xx1]

I think we should open the GitHub projects by adding a list of issues in order of how we should resolve them however we will end up having thousands of issues without resolving them.

What is the advantage of "Projects" compared to Issue labels?

No just to list things in general. As I think you saw I opened #51 because I needed a place to list. Having labels it's not going to order how we are going to proceed with issues and prs.

[oood]

I think we should open the GitHub projects by adding a list of issues in order of how we should resolve them however we will end up having thousands of issues without resolving them.

What is the advantage of "Projects" compared to Issue labels?

No just to list things in general. As I think you saw I opened #51 because I needed a place to list. Having labels it's not going to order how we are going to proceed with issues and prs.

Yes, and members of this repository/org can edit it, but that todo list (#51) I cannot edit, because that is a personal issue (wait... "personal issue"? that sounds weird 🤦 I didn't mean it that anyway.... I just don't know how to describe it, sorry).

What is the advantage of "Projects" compared to Issue labels?

Not sure if you've used Trello for that (I used to work with a non-profit organization that used the platform to coordinate the daily work of volunteers from all over the world), it's similar to that. for team collaboration, sharing ideas, recording progress, setting to-dos, basically it's visual based and easy for people to see what to do next.

GitHub basically copied the functionality of Trello in my opinion. But their documentation is so terrible that most people don't understand what this feature does.

I'll show you a Trello self-introduction video so you know what it is. 👉 https://www.youtube.com/watch?v=AyfupeWS0yY

[oood]

GitHub basically copied the functionality of Trello in my opinion.

I need to correct that Trello is more mature and has more features than GitHub's Projects. But enough for a to-do list. It can't replace the collaboration and productivity of Trello, that's for sure.

[T1xx1]

Yes, and members of this repository/org can edit it, but that todo list (https://github.com/kisvegabor/abbreviations-in-code/issues/51) I cannot edit, because that is a personal issue (wait... "personal issue"? that sounds weird 🤦 I didn't mean it that anyway.... I just don't know how to describe it, sorry).

HAHAHAHAHAH

GitHub basically copied the functionality of Trello in my opinion.

I need to correct that Trello is more mature and has more features than GitHub's Projects. But enough for a to-do list. It can't replace the collaboration and productivity of Trello, that's for sure.

The only advantage GitHub has it being in the GitHub environment without going anywhere else.

[oood]

The only advantage GitHub has it being in the GitHub environment without going anywhere else.

Yes, in an organization, even a project can be applied to all repositories in the organization. This seamless integration and centralized management make things easier.