search

associazione-rousseau / camelot-flutter

Cross platform Flutter application to subscribe and vote on Rousseau.
GNU General Public License v3.0
15 stars 11 forks source link

Autofill SMS backend #105

Open emanuelconunaemme opened 4 years ago

emanuelconunaemme commented 4 years ago

We need to send the 2FA with a certain format to be ready by Android. To do that the client has to tell the server that it's Android

bhack commented 4 years ago

Is this a dup of https://github.com/associazione-rousseau/camelot-flutter/issues/96?

emanuelconunaemme commented 4 years ago

@bhack this is the backend task for me. it involves some verification with Apple and Google. I already implemented, but it's not working. I need to debug it. Not sure it's a client or server error.

bhack commented 4 years ago

In this case I can't help you since we are in the close source lands

bhack commented 4 years ago

I suggest you to add a backend label for this type of tickets so It is more clear that the community can not contributed with code on these type of tickets.

But in general I suggest you to add labels to other tickets like contribution welcome or e.g. a specific label for ticket that are selected from the feedback form in the app. Just to have a little bit of transparency on what It Is related to the closed-source backend, what issues are made public coming from the beta-tester internal app feedback form as these kind of "issues" or "feature requests" are not instant public but they require Associazione Rosseau's intermediaton/gatekeeping on what It could be public on github and what not.

It could be nice to upvote feedbacks after your clustering/reducing activity on duplicates to have public evidence of priorities on the roadmap expecially for features requests but there Is not a so strong github user community to upvote here.

emanuelconunaemme commented 4 years ago

+1

emanuelconunaemme commented 4 years ago

Done @bhack. I reviewed all the open issues and added "backend" and "good first task". All the non-backend tasks are implicitly assignable.

bhack commented 4 years ago

Ok thanks. What do you want to do with issues and feature requests coming from the app feedback form? There are (still) not so much active github users around the project. Is not better to create a discourse.org free space? It would be easier and low barrier for no-coders to discuss about features there.

emanuelconunaemme commented 4 years ago

For the bugs, we can create an issue based on the description. Although it's more work, we need to go through the feedbacks anyway to aggregate them and sort them by count. Same for the most requested features. For the actual product discussion, you brought up a good point. One of the idea we had was to use the already tested format: "Level UP". Although, it's a good idea to have something async.

bhack commented 4 years ago

For the bugs, we can create an issue based on the description. Although it's more work, we need to go through the feedbacks anyway to aggregate them and sort them by count. Same for the most requested features

I suppose It will be quite time consuming on your side if you will start to do It formally.

If we don't have still enought github users around the project we could try to build up at least a prosumers community around the project. I think that entry level users probably will still use the feedback form.

Do you think It is hard to set-up a discourse instance and configure it with Rosseau auth?