[2507 Grant Proposal] Rootstock QuestHub

[Tane]

Small, but “nivel” should be “level”?

@Tane

For those two missions, the descriptions seem to be unmatched. The first one is for “familiarizing the users” and the second one is for “training new developers” based on the other information.

Can you also make sure they are appropriate as well?

[Luis_VOTTUN]

These issues have been corrected. Please check if you wish. We would like to re-upload the final milestone proposal.

[Tane]

Found some missing and not-translated texts in the UI. They may not be blockers, but we would like you to diligently review all the UI components are properly provided.

[Luis_VOTTUN]

Thanks for the feedback. We will review these things again and we will correct them.

[Luis_VOTTUN]

We have fixed these issues. We are know still checking in the admin section but this should not be a blocker. Please do a final review if you wish and we will continue with the final proposal to put this in prod. Thanks for your support!

[Tane]

Thanks for fixing the issues! Tried to complete the very first task, but failed with the error below:

(The color of the error message isn’t ideal from the UX perspective either)

[Luis_VOTTUN]

We corrected this issue. Thanks for the feedback

[Tane]

Thanks for the fix. Confirmed it worked while the error message color is still broken.

We’d stop here as we are not to do all the QAs but the profile page in English doesn’t look complete at all.

[Luis_VOTTUN]

Thanks for all the checking. It´s not a simple application so it has multiple layers. As you could see, every time something was reported we are fixing it, and we will continue to do so with real user feedback too. At this point, we believe is the course to take. Finish the initial version so we can release it and get feedback from the community to fix othe minor bugs.

We are going to propose again the final milestone to finish this and launch the app. I hope we will get the community support to move this forward and keep building this application with RSK community.

Thanks again for your support

Vottun Team

[Luis_VOTTUN]

Hi fam,

We have some hipcups for sumitting the final proposal but finally is up and ready for voting. We will appreciate your support to launch this project for the community.

As alaways, we are here to address any community Qs.

Cheers!!
Vottun Team

[Curia]

We’ve decided to vote against this milestone. Our full reasoning is explained below.

@Curia

Proposal: [0907 Grant Proposal] Rootstock QuestHub - M4

Vote: Against

Rationale: Although the team has fixed several bugs, particularly around untranslated sections and some UX/UI issues, we still encounter parts of the website that remain untranslated. While this is not a blocker, it does affect the smoothness of the user experience. We suggest that the team carefully review all untranslated elements across the site, rather than relying on delegates to point them out individually. There is no urgency to approve Milestone 4, so we would like the team to thoroughly address all remaining untranslated items first.

[Kaf_Anode]

Hey @Luis_VOTTUN , thanks for the update.

As @Curia pointed out, there are still some issues that affect the user experience. When navigating the platform in English, some sections still appear in Spanish. And when switching to Spanish, some mission elements remain in English.

I would like to vote in favor of this proposal, do you think these issues could be resolved before the voting period ends? Happy to re-check once you push a new update.

[Tane]

We voted against as explained below, echoing @Curia 's points and our additional findings. We hope the team addresses most of the issues before submitting the final milestone.

Tané Delegate Thread

[0907 Grant Proposal] Rootstock QuestHub - M4 (Onchain) Vote: AGAINST Rationale: We keep finding minor untranslated texts and issues in the app even after pointing out a couple of them in the forum (while they have been addressed by the team.) There have been incomplete instructions in some tasks. In addition, there are too many tasks that require manual reviews, which isn’t scalable for many users.

[Luis_VOTTUN]

@Tane @Curia @Kaf_Anode We appreciate your feedback, but let´s put things in context.

We made the platform in 2 languages as an improvement, but it’sclear that this is finally going against us. We agreed that translations need to be clean. To catch this, we wrote a script that unfortunately didn’t catch it all. We will improve it, as we have been correcting all mistakes caught before the current submission.

So, with his context, being penalized for this improvement it doesn´t feel fair. Most of the time, these errors are considered minor and can be corrected more easily when the app is in prod and we get real feedback from real users at scale. Could you recognize the value of providing 2 languages instead of one (even though some words are still mixed)?

Finally, the last issue reported by @Curia who think that there are too many quests being reviewed manually. This is not part of the milestone. We will be operating the platform and especially for missions to value developers; these reviews are needed. We know how this works, and we will automate quests as needed, but we need to experience users before we do this properly. With this in mind, this last comment should not be an issue. Believe us we are the most interested part in advance and operate a succesful product.

Once again, we value all feedback, but please consider that you are delaying getting this application in prod for some minor issues (tolerable for most of the beta versions) that they will be fixed as we on-board users.

[Luis_VOTTUN]

Last update.

A new version of the script to catch translation issues has been deployed. Previously, it didn´t consider one kind pop-up that had the reported mistake.
We hope this fixes most of the issues now.
Thanks

[Tane]

@Luis_VOTTUN

Could you recognize the value of providing 2 languages instead of one (even though some words are still mixed)?

We sincerely disagree with this take. If you provide the product in multiple languages, they should be fairly complete. From our point of view as a product builder, there has still been so many parts that are undone. One of the critical examples is the email notifications that we started getting; they are suddenly started being sent and all in Spanish while we have been using the service in English.

[CodeKnight]

@Luis_VOTTUN

Could you recognize the value of providing 2 languages instead of one (even though some words are still mixed)?

I would consider it a distant second to having everything properly set up in one language, preferably English. The whole system should have been set up in English first to make sure it 100% worked, then other languages could be set up separately.

[ChronoTrigger]

Hi all,

Since the community seems to be divided, we wanted to leave our 2 cents here:
We decided to support Vottun’s proposal and here’s our rationale:

@ChronoTrigger

Sure there are a few kinks to polish in the website, but Vottun is an established crypto company.
Having their own brand to care for, we think it’s in their responsibility and best interest to keep polishing the product, and continuously improve the user experience.
If they clearly stated they prefer to launch soon and polish based on user feedback, this is a known and valid product management methodology, and I don’t think it’s our position to judge their methodology of choice.

As for the decision to release in two languages, either way if it was right or wrong, product management and prioritization are not trivial, and notably, it’s common to decide on premises and hypotheses which later on are not validated, and looking back it might feel obvious.

For full context, having started my carrer as an Engineer and later on migrated to be a Product Manager in Crypto, one of the hardest things to learn was to build continuously, get used to MVPs, hypotheses, validation, mistakes, and pivoting, open innovation, user-based feedback, etc. These are all qualities of modern Product Management, while in Engineering it is really only allowed for a product to be released 100% done, which absolutely cannot and will not ever fail.

All that said, I think we should give Vottun a credit as having chosen their methodology to accelerate improvement after onboarding users and based on user feedback. As an established crypto company, this might be how they like to do it and how they developed their other products.

[CodeKnight]

While I respect how hard the work can be, I would not pay a contractor for incomplete work with my own money and I treat DAO funds the same way.

It tends to be a lot harder to get things fixed after all payments have been made.

[Luis_VOTTUN]

Thanks @ChronoTrigger for your support. I think you summarized better than us our pointo fo view
We have the best interest in creating a successful product and prepare a polished product.
Regarding @CodeKnight comment, we are not a contractor, we are part of this proposal as an interested party. So our work will never finish as we will keep improving it. We have been fixing everything reported. We only ask to put this into prod to keep making more improvements.

The app is far more complex than initially was scoped and that´s a good tihng!! We want to launch it so we can make it even better.