Module is implemented and available ink halcyon-cn1 library

@sevan.evans Tags here are what we call Pins in the client app code. Pins are currently implemented as a mockup and hardcoded. With the server side support and library support we can now have proper and full implementation in the client.

For more details, please refer to ticket kangaroo-76 where we discussed all the details. It is very lengthy discussion I would suggest to start reading it from the end.

Some additional information can also be found in the document here: https://github.com/tigase/kangaroo-tigase-extensions/blob/master/docs/tagging-jids.md

Got it, I'm on it.

Sevan

{cut >>>}On Fri, Mar 26, 2021, at 3:41 PM, Artur Hefczyc wrote:

Feature was updated by Artur Hefczyc in project Halcyon at 26 Mar 2021 15:39.

issue #54 https://projects.tigase.net/oauth?state=%2Fissue%2FHALCYON-54 Implement tags for users and channels https://projects.tigase.net/oauth?state=%2Fissue%2FHALCYON-54 Created by Bartosz Małkowski Artur Hefczyc

@Sevan Evans Tags here are what we call Pins in the client app code. Pins are currently implemented as a mockup and hardcoded. With the server side support and library support we can now have proper and full implementation in the client.

For more details, please refer to ticket kangaroo-76 https://projects.tigase.net/issue/kangaroo-76 where we discussed all the details. It is very lengthy discussion I would suggest to start reading it from the end.

Some additional information can also be found in the document here: https://github.com/tigase/kangaroo-tigase-extensions/blob/master/docs/tagging-jids.md

View https://projects.tigase.net/oauth?state=%2Fissue%2FHALCYON-54%23focus%3DComments-4-29275.0-0 Reply https://projects.tigase.net/oauth?state=%2Fissue%2FHALCYON-54%3FreplyTo%3D4-29275 You (sevan.evans) received this message because you subscribe to @mentions in issue descriptions and comments and notification events for the Assigned to me saved search. To unsubscribe, you can mute notifications for this issue https://projects.tigase.net/api/unsubscribe?token=MTYxOTMwODgwMDAwMHwxLTQ4NHwyLTEyNDA1fDZSblg5UnA3c3JKOGxZZXNwaEE4X092eEtrYXk4%0D%0Ac1Q5dE5sRDZOdXRrLXMNCg%0D%0A or edit your notification preferences https://projects.tigase.net/oauth?state=%2Fusers%2Faab3bed5-4e46-4ead-a4c8-d6c07198a021%3Ftab%3Dnotifications. YouTrack 2020.3.5333 {cut}

Documentation moved; now found at https://github.com/tigase/kangaroo-tigase-extensions/tree/master/src/main/docs

@wojtek @andrzej.wojcik @bmalkow At the moment we have 2 repos with documentation:

1. https://github.com/tigase/kangaroo-tigase-extensions
2. https://github.com/tigase/kangaroo

Maybe we could have just one repo with docs?

Sorry about that @sevan.evans , I was moving things around to make the structure more logical.

@kobit Actually we currently have 3 repositories - there is additional https://github.com/tigase/kangaroo-tigase-extensions-systems/ with extensions for the actual deployed systems (I would like to rename kangaroo-tigase-extensions to kangaroo-tigase-extensions-hub for clarity). As for the documentation -- we can move everything over to the main kangaroo repo and just link from the extension repos - should I proceed?

Hm, I am thinking and I am not sure. More logical is to keep documentation close to the source code, so everything is in one place. It does not make much sense to combine all these repos into one either.

Let's have the main/master/generic documentation in the kangaroo repo and the code specific documentation in the same repo where the source code is. However, we need somehow to have one place with links and some basic info about each part.

@wojtek Could you please update README.md file in the Kangaroo repo with information about all other kanagroo repos with links to them and basic (1-2 sentences) description what these other repos have?

I think the approach with having documentation in 3 places makes sense - extensions may evolve quicker / have versions and having relevant documentation there (tied to the particular sources version) makes the most sense (we use same approach in our other repositories).

@kobit I updated repository readme as per instruction.

thank you.