But we may already be a Beta Tester

[jidanni]

In Settings > Feedback section:
Become a Beta Tester...
But we may already be a Beta Tester.
So the wording should say:
Become a Beta Tester (if not one already)....
Or else more fancy detection should be enabled.

[nicolas-raoul]

I actually don't see this in the dev branch I use... maybe the UI has changed and this is not needed anymore?

This is actually a good first task for anyone who wants to take it: check whether the UI includes that string or not, in both master and the maintenance branch. Thanks!

[jidanni]

Maybe also related to #3976.

[Mugurell]

A potential issue with the above string recommendation - Become a Beta Tester (if not one already) is that on some devices it could not entirely fit on one row.
Maybe this important note could be added to the description? (Opt-in to..)

[jidanni]

OH, AND... do mention "alpha tester" too!
Because currently beta=non-beta!!
And it will take the user a long time to figure out

1. beta=non-beta, and even longer, if ever, to stumble upon the fact that:
2. There is also a little mentioned alpha.

[gouri-panda]

I want to work on this issue.

[gouri-panda]

@nicolas-raoul Should I start working on this issue? and also I need descriptions.

[misaochan]

I don't think there's any need to mention alpha in the app, as it's not possible to opt in to alpha solely within the app (it requires signing up to our google group). Alpha is generally for users who are already very familiar with our project and have looked us up on GitHub. It can be unstable and primarily exists as a shortcut to allow contributors to test master without having to do an AS build, so I don't feel comfortable recommending users to be alpha testers in-app.

Because currently beta=non-beta!! And it will take the user a long time to figure out beta=non-beta

IMO the description text already says "Opt in to our beta channel to get early access to new features etc". If there are currently no new releases available, then there is nothing to get "early access" to.

@gouri-panda It seems like there is a PR up at #3984 ? @madisoncfallin are you interested in making the requested changes to your PR?

@gouri-panda If you still are looking for an issue to work on, anything with the "bug" label can easily be assigned to you too. :)

[jidanni]

I would say do like
https://www.chromium.org/getting-involved/dev-channel
Full disclosure of all four channels to the testing community, right from the start.

[misaochan]

We have a wiki for the same purpose: https://github.com/commons-app/commons-app-documentation/blob/master/android/Volunteers-welcome!.md

[jidanni]

OK, but

1. Starting as a user looking at the wording on Fixes #3968 But we may already be a Beta Tester #3984
2. There is no path for them to ever reach that wiki page.

[AdityaArunSharma]

Hey! @misaochan @jidanni @nicolas-raoul
I am a begineer in open source but have little experience in andriod development.
Can I work in this good first issue? I am very eager to start with open source.

[nicolas-raoul]

@AdityaArunSharma The "good first issue" was about searching strings and it is done already, I just forgot to remove the tag, sorry for the confusion! Anyway welcome to the team, glad to have you on board ! :-) Would you mind finding another issue at https://github.com/commons-app/apps-android-commons/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+no%3Aassignee+-label%3Aassigned+-label%3Adebated+label%3Abug ? Thanks!

[Rishavgupta12345]

@nicolas-raoul can you please tell me what actually we have to do in this issue? is this issue even relevant to be open?

[nicolas-raoul]

Beta versioning is not used as much as it used to be in the past, so no need to spend time on this now.