3 ms·

The UI seems very usable. I wonder how the performance stacks up against something like gogs. One of the main things I don't like is the email focus. I think o

The UI seems very usable. I wonder how the performance stacks up against something like gogs. One of the main things I don't like is the email focus. I think one of the best things the modern git websites have done is replace email with merge requests which are just so much easier to use, tag, and search. I get that this is a tool made for those old devs who still want to do everything from mutt though.

Aeolun 8y ago
Balls, I thought this was really nice until I read your comment. That patch page is pretty indecipherable.
chrismorgan 8y ago
I shall claim that difficulty in using email for these things is mostly because of unfamiliarity. Keeping patches and discussion together can work really well. It tends to do better for record-keeping, especially. It may take a bit of getting used to, but when you are used to it, it’s a sane and reasonable approach in most cases. (Not all, but most.)
chriswarbo 8y ago
The nice thing about email is that you're free to render and interact with it in any way you like. Yes, you could use mutt; or you could use Webmail if you prefer; or you could run them through some automation scripts; or through some custom CLI/GUI/mobile app/Web service/etc.
- baroffoos 8y ago
  GitLab and GitHub also send you emails but they provide a sane UI to use as well. The only benefit I see to email is it serves as a central notification location so I dont have to check every website to see what is new.
  - chriswarbo 8y ago
    > The only benefit I see to email is it serves as a central notification location so I dont have to check every website to see what is new. I agree that email is good for notifications. Surely "checking Web sites to see what's new" was solved with RSS/ATOM? (Again, once the data's out there, the UI is your choice; e.g. I convert RSS/ATOM to maildir so I can use my preferred email client for everything; I put HackerNews (HNRSS and HNNotify), subreddits, youtube channels, etc. into the same folder as my mailing lists)

Aeolun 8y ago

Balls, I thought this was really nice until I read your comment. That patch page is pretty indecipherable.

chrismorgan 8y ago

I shall claim that difficulty in using email for these things is mostly because of unfamiliarity. Keeping patches and discussion together can work really well. It tends to do better for record-keeping, especially. It may take a bit of getting used to, but when you are used to it, it’s a sane and reasonable approach in most cases. (Not all, but most.)

chriswarbo 8y ago

The nice thing about email is that you're free to render and interact with it in any way you like. Yes, you could use mutt; or you could use Webmail if you prefer; or you could run them through some automation scripts; or through some custom CLI/GUI/mobile app/Web service/etc.

baroffoos 8y ago
GitLab and GitHub also send you emails but they provide a sane UI to use as well. The only benefit I see to email is it serves as a central notification location so I dont have to check every website to see what is new.
- chriswarbo 8y ago
  > The only benefit I see to email is it serves as a central notification location so I dont have to check every website to see what is new. I agree that email is good for notifications. Surely "checking Web sites to see what's new" was solved with RSS/ATOM? (Again, once the data's out there, the UI is your choice; e.g. I convert RSS/ATOM to maildir so I can use my preferred email client for everything; I put HackerNews (HNRSS and HNNotify), subreddits, youtube channels, etc. into the same folder as my mailing lists)