I'm looking for a part-time remote job.

Hire me


I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).


Follow me:

Feature #605

SVN monkey

Added by Andriy Lesyuk over 9 years ago. Updated over 8 years ago.

Status:
Open
Priority:
Minor
Assignee:
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%


Description

Orangutan can be very helpful for employees which use SVN...

What is required for a user to track time? A user must specify work hours, project and maybe issue and a short description...

What does developer which uses SVN do? Runs “update” when comes to the office and runs “commit” when leaves... If we assume that a user always specifies a description when committing (-m) we have a start time, end time and a description! All that we need is project/issue - project can be guessed (or determined if SVN was registered in Redmine) and issue can be extracted from -m message...

That is:
  • When user does “update” Orangutan starts “tracking”;
  • When user goes away and returns Orangutan tracks breaks and saves them somewhere;
  • When user commits...
  • Orangutan tries to determine the project (if failed the monkey can ask for project later);
  • Orangutan tries to determine the issue;
  • Orangutan suggests a user to save tasks...

The last is done when there are no conflicts - that is a user did not save any entries for the time a user is believed to work.

That is a user will only be required to answer “yes” per commit (besides the cases when the project is not known)...


Related issues

Related to Orangutan - Enhancement #158: Extend architecture to support external notifiers Closed 18 Jun 2010 20 Jun 2010

History

#1 Updated by Andriy Lesyuk over 9 years ago

The algorithm above was described very shortly. Of course, in reality it will be much more complicated. For example:
  • It will ignore updates between the first update and commit (because it is recommended to always update before commit);
  • The first update will be usually a morning update;
  • The algorithm can be also changed to treat commit as a start of the task if it (commit) was done at the middle of a working day;
  • etc.

#2 Updated by Andriy Lesyuk about 9 years ago

  • Status changed from Open to Incomplete

Not sure if anyone needs this...

#3 Updated by Andriy Lesyuk over 8 years ago

  • Status changed from Incomplete to Open

Also available in: Atom PDF

Terms of use | Privacy policy