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

find a way to give timeslices #2

Closed
rbouqueau opened this issue Jun 9, 2016 · 7 comments
Closed

find a way to give timeslices #2

rbouqueau opened this issue Jun 9, 2016 · 7 comments
Assignees

Comments

@rbouqueau
Copy link
Collaborator

for example, rbouqueau between 2009/05/25 and 2009/05/24 (inclusive) is handled differently

it is important for copyright purposes when contributors work for different employers (or for themselves)

how could we do that?

@RodolpheFouquet
Copy link
Owner

RodolpheFouquet commented Jun 9, 2016

Would you like to have, for example, 2 lines?

I could spend time to add a json config file to allow you to specify several timespans, and in the result you would have:

rbouqueau 2009-05-24 to 2009-05-25 | stats blablabla
rbouqueau (otherwise)              | stats blablabla

@RodolpheFouquet RodolpheFouquet self-assigned this Jun 9, 2016
@rbouqueau
Copy link
Collaborator Author

would be great, thanks :)

@RodolpheFouquet
Copy link
Owner

RodolpheFouquet commented Jun 9, 2016

{
  "periods": [
    { "user": "rbouqueau",
      "start": "2009-05-24",
      "end": "2009-05-25",
      "alias": "working at telecom"
    }
  ]
}

Would give:

rbouqueau (working at telecom)| stats blablabla
rbouqueau (otherwise)         | stats blablabla

Seems good for you?

And adding multiple periods could be

{
  "periods": [
    { "user": "rbouqueau",
      "start": "2009-05-24",
      "end": "2009-05-25",
      "alias": "working at telecom"
    },
   { "user": "rbouqueau",
      "start": "2009-05-26",
      "end": "2009-05-30",
      "alias": "working with unicorn superpowers, lasers and stuff"
    }
  ]
}

@rbouqueau
Copy link
Collaborator Author

Good. We need to allow end value in the future so that the same script can be used everytime e.g.

{
  "periods": [
    { "user": "rbouqueau",
      "start": "2000-01-01",
      "end": "2009-05-24",
      "alias": "working at telecom"
    },
   { "user": "rbouqueau",
      "start": "2009-05-26",
      "end": "2009-05-30",
      "alias": "working with unicorn superpowers, lasers and stuff"
    }
   { "user": "rbouqueau",
      "start": "2009-06-01",
      "end": "2079-05-30",
      "alias": "radio gaga"
    }
  ]
}

@RodolpheFouquet
Copy link
Owner

Why would you do that? Evey commit that wouldn't be in the specified timespan would be put in an "otherwise" section.

@RodolpheFouquet
Copy link
Owner

Though I might add support for timespans without start or end point.

Without start, it would be "everything before the end date", and without end point it would be "everything after the start date".

@rbouqueau
Copy link
Collaborator Author

Though I might add support for timespans without start or end point.

That was my point. But I also imagined that people could specify something wrong anyway (i.e. overlaps).

Any of these is fine for me :)

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

No branches or pull requests

2 participants