This ticket is to allocate sprint points of completing the Qt Beer demo project

Describe the bug
sdk_refactoring_demo app is not in working condition. We need to upgrade dependencies and issues need to be resolved.

To Reproduce
Steps to reproduce the behavior:

1. Upgrade to the latest dependencies and run the app.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

Were you using an @‎application when the bug was found?

• [e.g. @‎ https://github.com/atsign-foundation/at_demos/tree/sdk_refactoring_demo]

Additional context
Add any other context about the problem here.

Describe the bug

Analyzing at_data_share...             2.6s

warning • lib/src/util/command_line_parser.dart:11:21 • The operand can't be null, so the condition is always
          'true'. Remove the condition. • unnecessary_null_comparison

Steps to reproduce

1. First I cd at_data_share
2. Then I dart pub get
3. And then dart analyze

Expected behavior

No warnings

Write demos to help aid the doc site with examples.

• 1-authentication
• 2a-create-public-atkey
• 2b-create-self-atkey
• 2c-create-shared-atkey
• 2d-create-atkey-with-metadata
• 3a-put-public-key
• 3b-put-self-atkey
• 3c-put-shared-atkey
• 3d-get-public-atkey
• 3e-get-self-atkey
• 3f-get-shared-atkey
• 4a-monitor
• 4b-notify
• 5a-hooks

Describe the bug
Share recipe and remove recipe is not working as expected in the at_cookbook demo app

To Reproduce
Steps to reproduce the behavior:

1. First I Installed the at_cookbook demo and paired it with an atsign
2. Then I Added a dish by clicking the + icon
3. a. And then selected the newly added dish from my dishes screen and selected the remove option
   b. From the selected dish, select the share option
   c. Enter the atsign to share and click on the Share cuisine.

Expected behavior
If we click on the remove button, The selected dish needs to be removed
If we click on the shared cuisine, The cuisine should be shared with the entered atsign

Screenshots

Smartphone (please complete the following information):

• Device: [e.g. iPhone11]
• OS: [e.g. iOS14.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 59]

Were you using an @‎ application when the bug was found?

• [e.g. at_cookbook demo app]

Additional context
Add any other context about the problem here.

A status badge shows whether a workflow is currently failing or passing. In addition to this, it is important to show our Github BSD 3-clause License badge on all public repositories.

A common place to add the status and license badge is in the README.md at the top alongside the GitHub License.

+ ![example workflow](https://github.com/<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg)
+ [![GitHub License](https://img.shields.io/badge/license-BSD3-blue.svg)](./LICENSE)

Is your feature request related to a problem? Please describe.

N/A

Describe the solution you'd like

Remove at_cookbook, at_hello_world

@gkc should we remove at_demo_data?

Describe alternatives you've considered

No response

Additional context

No response

Unlist the following packages on Pub.dev ~ @nickelskevin to provide further details

• at_demo_data

Is your feature request related to a problem? Please describe.

I'd like to start work on the at_cookbook sample app in at_app.
In order to do that, I'd like to first convert it to use the at_app base template.
This will make it easier to follow, since we will be using the same boilerplate code for all sample apps.

Describe the solution you'd like
Redo the at_cookbook sample app using the at_app template.

Describe alternatives you've considered
N/A

Additional context
N/A

Update Github documentation for to be unlisted pub.dev package at_demo_data.

Review at_demo_data readme.md, changelog.md and look for standard archetype template updates to make current. Repo will remain active even though it will be unlisted on Pub.dev.

• Review for current logo
• Add badging
• Does text body map to current standard archetype for consistency (dependency on archetype update)
• Update readme.md
• Update changelog.md

The PulseOximeter demo is going to be used for IoT Expo and needs updating!

• Speed - Needs to be migrated to using 'forText' notifications
• Needs to be running on latest secondary build (no memory leaks)
• Apps in store need to be updated (HRO2 app) - Android/IoS/Windows
• App needs to allow device owner to send results to more than one atSign and with option send all data or some
• Stretch goal have app add atSigns that people get at the show to see their results on their phone
• Stretch Goal to update to new onboarding widget (v5.0.0.1)
• Get hardware working and reliably!
• Get SIM in place and working - stretch goal with IoTSafe

Enhancements

• History of readings over time
• Change Recipients and Data that is Shared

More details here:-
https://docs.google.com/document/d/1YIb1gd89Ka169lAOTNnr4YeXWbGPZIcdA5rz4pKYXFk/edit#heading=h.a4jfrgebwgg5

Engineering buffer card for Qt / Atsign Plant Demo

Related to #153

Review at_demo_data readme package version (example the package version is 2.0.3, but the readme description says - dependencies: at_lookup: ^1.0.0)

• Action: remove this section from README and maybe add any other relevant information. We can remove the entire Installation section from README.
• Missing @ sign logo @cpswan

• Started a PR to normalize all of the emojis in demo data #191
• Want to be careful about getting this change implemented as I don't want to break any tests which might depend on the ve.

Is your feature request related to a problem? Please describe.
Currently keys in at_demo_data are unencrypted which is different from the format in .atKeys file(encrypted using self encryption key)

Describe the solution you'd like

• create json data for demo data keys similar to .atKeys format
• create.atKeys file for demo data users so apps testing using demo atsigns can use the .atKeys file

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Create demos with espressif and at_c

Describe the bug
Messages were being delivered as expected for a while. But after some time the messages were not being delivered to the receiver atsign. Once I restart the app, All the previous messages were delivered again

To Reproduce
Steps to reproduce the behavior:

1. First I installed the at_chat demo app in as atsign A and atsign B in 2 devices
2. Then send message from atsign A to atsign B
3. And then checked the chat history in the atsign B

Expected behavior
All the chats should be displayed

Screenshots

If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

• Device: [e.g. iPhone11]
• OS: [e.g. iOS14.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 59]

Were you using an @‎application when the bug was found?

• [e.g. @‎ chat]

Additional context
Attaching the app logs
chatDemoApp_logs.docx

This issue was automatically created by Allstar.

Security Policy Violation
Project is out of compliance with Binary Artifacts policy: binaries present in source code

Rule Description
Binary Artifacts are an increased security risk in your repository. Binary artifacts cannot be reviewed, allowing the introduction of possibly obsolete or maliciously subverted executables. For more information see the Security Scorecards Documentation for Binary Artifacts.

Remediation Steps
To remediate, remove the generated executable artifacts from the repository.

Artifacts Found

• at_chats/android/gradle/wrapper/gradle-wrapper.jar

Additional Information
This policy is drawn from Security Scorecards, which is a tool that scores a project's adherence to security best practices. You may wish to run a Scorecards scan directly on this repository for more details.

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

@cconstab to provide details

Scores tab in pub.dev missing documentation for:

• follow dart file conventions
• provide documentation
• pass static analysis
• support sound null safety

Description

There's a typo in the description

System.out.println("Hello World!\n");

Expected Behaviour

Should not be typo! :)

Is your feature request related to a problem? Please describe.

N/A

Describe the solution you'd like

• Create a packages folder
• Move at_lorawan into the folder
• Move at_talk into the folder

Describe alternatives you've considered

No response

Additional context

@JeremyTubongbanua I know you are doing some work in this repo, so keep in mind that we will introduce a packages/ folder...

Although should we call it packages?
One one hand it doesn't really make sense... they aren't going to be published packages.
On the other, we should be consistent with the other repos.
@gkc @cpswan thoughts?

The docker demo has open port 22 when you do service start ssh

Can close by adding the following lines to the Dockerfile base image

# "PasswordAuthentication no" in /etc/ssh/sshd_config
RUN sed -E -i 's|^#?(PasswordAuthentication)\s.*|\1 no|' /etc/ssh/sshd_config

# "ListenAddress 127.0.0.1" in /etc/ssh/sshd_config
RUN sed -i 's/#ListenAddress 0.0.0.0/ListenAddress 127.0.0.1/g' /etc/ssh/sshd_config

• Right nav under documentation API reference requires review to make sure content is complete and up to date (samples and examples)
• Documentation link page not found error

Please look at libraries too (current, samples and examples)
LIBRARIES

• at_demo_data

The demo will actually have 3 docker containers:

1. sshnp
2. sshnpd
3. sshrvd

Demo will involve running the 3 docker containers then sshnp will ssh into sshnpd

We should create a demos folder to nest demos under, it's getting quite messy as we keep adding things.

Is your feature request related to a problem? Please describe.

Ssh into a raspberry pi without that device having any open ports

Describe the solution you'd like

A step-by-step tutorial/demo

Describe alternatives you've considered

No response

Additional context

No response

Is your feature request related to a problem? Please describe.

• Create demo where sender encrypts and uploads file to Storj and receiver downloads the file from StorJ and decrypt

Describe the solution you'd like

• Generate a symmetric key and encrypt the file using at_client SDK
• Use uplink tool from StorJ to upload and get shareable file link
• Share the file link, file encryption key, IV through notification
• Receiver receives the notification, downloads the file using shared link , decrypt the file using file encryption key and IV

Describe alternatives you've considered

No response

Additional context

No response