menu

ZEIT

Our mission is to make cloud computing as easy and accessible as mobile computing. You can find our Next.js community here.

Channels
Team

Refining Our Feedback Flow

August 19, 2019 at 12:04pm

Refining Our Feedback Flow

August 19, 2019 at 12:04pm

Hello there!

I'm Leo. My job is taking care of ZEIT's product range.

Today, I'd like to talk about an exciting new idea that the product team has been working on:

Current Feedback Flow

We have noticed that most of you are very engaged in helping us improve our product - either via bug reports or feature suggestions. These reports happen via our various communication channels (Spectrum, E-Mail, Twitter, etc).

However, we've noticed that – by far – most of you tend to report issues our GitHub repositories.

At ZEIT, we're very grateful for this, as we've been able to fix various bugs and add highly requested features through this. However, we've noticed that there's a way to make it even more convenient for you to file these kinds of reports:

Refined Feedback Flow

Currently, issues are reported on various of our repositories:

However, all of these codebases are really just one product: ZEIT Now. This leads to platform bugs, platform feature requests and reports for other codebases all ending up on a single repository: now-cli.

In turn, we decided that it would be best if we merged those three repository into a single one: zeit/now.

This will be especially useful because now-cli depends on both now-builders AND now-client – so a monorepo really is the best choice going forward.

Most importantly, however, you'd be able to just create issues on a single repository.

What Do You Think?

Do you agree with what I said above? Would you like us to move towards this direction? Do you have any objections?

I'd love to hear what you think!


August 19, 2019 at 6:12pm

I like the idea because I think it can helps integration tests. As I said in a PR for now-static-build, I don't know how to run now-dev tests to check if my change in the builder works correctly(might be not related thought). So if you can go to monorepo, this would simplify and secure development making now tools more reliable because everything will be tested together before merging.

like-fill
2
  • reply
  • like

I like it! It was sort of confusing to guess which repo I should look for issues - as youve said they often overlap. When I think of Now I think of the whole product range, not a single set of them.

like-fill
2
  • reply
  • like

August 20, 2019 at 1:42pm

How will you use Github Releases and changelogs then ?

  • reply
  • like

August 21, 2019 at 11:14am

Like we do on zeit/now-builders. In addition, those releases would have changelogs.

https://github.com/zeit/now-builders/releases

Edited
like-fill
1
  • reply
  • like

September 6, 2019 at 3:42pm

As long as you can do your best to make clear at the old repo URLs where to find the corresponding content in the new repos so that years of linking in chats, issues, and documentation aren't dead, I'm totally in.

  • reply
  • like