Mockup Interface discussion

In this issue, let's make the exercise of imagining "the perfect" terminal interface to be used with lore. To kick off the discussion, I created the first set of mockups as described below:

First time opening the interface

If the user opens the interface for the first time, it should not have any pre-setup; for this reason, we need to guide users throughout the basic configuration. When this configuration is done, we must save the user options in a config file. Maybe we can have something like this:

User select the target mailing list:

Bookmark main page (main page)

After the setup, the user must be sent to the bookmark page. If the user has already set up everything, this must be the first page opened. This page has two types of bookmark sections:

1. Patches: All patches that the developer bookmarked.
2. Mailing list: All mailing lists that the user registered.

See the interface:

Accessing mailing list

Let's say that the user clicked on the mailing list item. They must see something like this:

The user can select any list they want.

Showing recent patches

After users click on the target mailing list, they can see X new patches (we need to define a magic number for this). Something like this:

Select a target patch

After seeing the new set of patches, the developer can open a specific one that will look like this:

References

This is the link reference for the above images:

https://mydraft.cc/c7qm8fvmalqt53upd6gg

And this is Greg workflow which we can use to get some inspiration:

http://www.kroah.com/log/blog/2019/08/14/patch-workflow-with-mutt-2019/

Acceptance Criteria:

• Define the interface sequence
• Agree with the interface