Encourage experience reports

[mfisher87]

Experience reports are different than issue reports in that there isn't a presumption that something has gone wrong. I think often folks assume that mild annoyances or roadbumps are not worthy of rising to the level of an "issue report", so experience reports help both with identifying those things and with identifying areas where the user experience is already really good and needs to be protected.

Related to #281

[Sherwin-14]

@mfisher87 I can help with this. But I don't how we should proceed forward 😕. Is this something that we plan to emulate?

[mfisher87]

Awesome! Thanks for continuing to push us forward, Sherwin :)

I'm mostly inspired by this: https://github.com/FiloSottile/FiloSottile/blob/main/maintenance.md#experience-reports-are-gems

I just yesterday added experience reports to the JupyterGIS project here, and opened an issue for the same on the JupyterBook project here.

My two main thoughts are:

• Experience reports can be encouraged directly in the "open an issue" dialog box (.github/ISSUE_TEMPLATE/...)
• We can also push people to do this in our "marketing" materials. For example, in our docs' quickstart and README, where we have the attention of new users, we can add something like "We value your feedback! We want to hear all about your experience using earthaccess. Even if you're not noticing any issues or bugs, we want to know... what annoys you? What feels great? We'd love if you would share an experience report (link) with us!" We can do similar when we post on social media or write blog posts (or have blog posts written about us; ask those people to nudge readers towards opening experience reports).

Is this something that we plan to emulate?

I think yes, eventually. That's more of a synthesis / summary of experience reports categorized in to themes, and I think that's super valuable. Once we have the raw reports we can make an effort to build a page which categorizes the information in those reports.

[Sherwin-14]

We value your feedback! We want to hear all about your experience using earthaccess. Even if you're not noticing any issues or bugs, we want to know... what annoys you? What feels great? We'd love if you would share an experience report (link) with us!"

I will add this call into our docs quickstart and README. I also checked the PR that you linked and I feel that we can do the same for earthaccess as well as that looks pretty slick! What do you think about this?

[mfisher87]

I think that sounds great :) Would you like this issue assigned to you?

[Sherwin-14]

Yeah, that would be great! Do we have a label specifically for experience reports? If we don't have it then, should we create a specific label for this or are there existing labels that can be used for experience reports. What's your take?

[mfisher87]

Let's add a label for experience reports. type: experience report? Do you feel comfortable adding a new label?

[Sherwin-14]

Let's add a label for experience reports. type: experience report? Do you feel comfortable adding a new label?

Ah, I don't know honestly. I'll try adding a new label as part of this PR.

[mfisher87]

You can unfortunately only add new labels in the GUI. I really wish GitHub would let labels be configurable by a json file in .github/ or something.

In any case, I think you should have access! From the "Issues" page, at the top-right there's a "Labels" button. From there you can add new ones. Let me know if that works :)

[Sherwin-14]

It seems like I don't have access to adding labels.

[mfisher87]

Shoot, that's not what I expected :( New label created! type: experience report A report of the user's personal subjective experience using this software