Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

requesting kFramework 11 for the Everybot #7708

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

yapplejack
Copy link

I understand that it may be a bit late to request usage tracking for the Everybot but was wondering if it was still possible. If this is not the proper way to request this I would appreciate being pointed in the correct direction if this is possible.

I assume we would be able to call this in Robot.java just like the KitBot does.

@yapplejack yapplejack requested a review from a team as a code owner January 18, 2025 18:18
@github-actions github-actions bot added the component: hal Hardware Abstraction Layer label Jan 18, 2025
@sciencewhiz sciencewhiz added attn: NI component: usage reporting Analytics for library usage sent to FIRST on competition fields. labels Jan 18, 2025
@sciencewhiz
Copy link
Contributor

Kitbot used both 9 & 10

@yapplejack
Copy link
Author

yapplejack commented Jan 18, 2025

@sciencewhiz Is there an open number we could use? We would always be happy to take 118 😊.

@Kevin-OConnor
Copy link
Contributor

As Joe said Kitbot used 9 & 10 for the different frameworks to collect info to see if we should simplify in the future. Using 11 for the Everybot works for me.

Both the KitBot one and this one are certainly not the "right way" to do it because in the current model NI is really the keeper of the keys, but this data would be very helpful to have.

@yapplejack
Copy link
Author

yapplejack commented Jan 18, 2025

Awesome! Switched it to 11, and will use the same code the kitbot uses to track this (with the number 11 and a correct comment).

image

@yapplejack yapplejack reopened this Jan 19, 2025
@yapplejack yapplejack changed the title requesting kFramework 10 for the Everybot requesting kFramework 11 for the Everybot Jan 19, 2025
@yapplejack
Copy link
Author

Would it be fine for me to release the code with this?

image

I would like to get the Everybot code out ASAP, lmk if I can include this.

@PeterJohnson
Copy link
Member

That's fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attn: NI component: hal Hardware Abstraction Layer component: usage reporting Analytics for library usage sent to FIRST on competition fields.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants