Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event log #15

Open
przemoc opened this issue Sep 6, 2016 · 0 comments
Open

Event log #15

przemoc opened this issue Sep 6, 2016 · 0 comments

Comments

@przemoc
Copy link

przemoc commented Sep 6, 2016

Keeping log of all events could be quite useful for users and for debug purposes.

I think following 5 fields would be enough.

Mandatory fields:

  • Timestamp (in ISO8601, obviously)
  • Who triggered it - User, Auto
  • Action - e.g. ReaPack install, Repository import, Repository refresh, ReaPack upgrade
  • Result: OK, ERR

Optional fields:

  • Details: depends on the action, e.g.:
    • For ReaPack install:

      Name: <ReaPack name>
      
    • For repository import:

      URL: <Repository index URL>
      
    • For repository refresh:

      New packages (1):
      - Some new package name (v0.3)
      Obsoleted packages (1):
      - Some obsoleted package name (v0.6)
      New versions (2):
      - Some other package name (v0.9)
      - Some another package name (v0.7)
      Removed versions (1):
      - Some another package name (v0.6)
      
    • For errors:

      Error: Error description
      
    • For ReaPack upgrade:

      Name: <ReaPack name> (v<old version> -> v<new version)
      

Such log should receive its own window, which could be viewed by user when needed.

(If such log would be introduced before releasing new stable version, then event like enabling all repositories could be easily recorded, but I also think that such action shouldn't be performed fully automatically and there should be message box asking for user consent and explaining that enabling != installing, etc.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants