Is this jus about issue trackers.

Date: 2014-05-20 01:37 am (UTC)
From: (Anonymous)
I'm probably over-simplifying, but it seems that the big problem is the issue tracker.
Email is a standard (lots of standards) with standard tools.
git is a near-standard which could use better support, but works well.
Issue trackers are .... a mess.

That sample work-flow shouldn't require a switch to a web browser. The dev should be able to reply to the email and the reply should be fully authenticated and allow 'mark as duplicate' etc. All relevant info should be in the local email archive and the local git archive, both of which should be linked from the email in an 'obvious' way.

Once we had a sensible distributed federated issue tracker, the rest would just follow naturally, wouldn't it?

- NeilBrown
From:
Anonymous
OpenID
Identity URL: 
User
Account name:
Password:
If you don't have an account you can create one now.
Subject:
HTML doesn't work in the subject.

Message:

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org


 
Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.

Profile

Matthew Garrett

About Matthew

Power management, mobile and firmware developer on Linux. Security developer at Google. Ex-biologist. @mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer.

Expand Cut Tags

No cut tags