baby-bro 0.0.2 → 0.0.3

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. data/README.rdoc +2 -6
  2. data/VERSION +1 -1
  3. data/baby-bro.gemspec +1 -1
  4. metadata +3 -3
data/README.rdoc CHANGED
@@ -4,17 +4,13 @@
4
4
 
5
5
  == DESCRIPTION:
6
6
 
7
- Baby Bro monitors timestamp changes in configured project directories and automatically tracks active development time for those projects. The name is a play on "Big Brother", which came up in a conversation with a colleague when discussing the idea for this utility. As in, if your employer were running this utility on your workstation with you knowing it, "Big Brother" would be watching you.
7
+ Baby Bro monitors timestamp changes in configured project directories and automatically tracks active development time for those projects. The name is a play on "Big Brother", which came up in a conversation with a colleague when discussing the idea for this utility. As in, if your employer were running this utility on your workstation without you knowing it, "Big Brother" would be watching you.
8
8
 
9
9
  Baby Bro isn't meant to be used like that, however. It's meant to be used by anyone who wants to automatically keep track of the amount of time they spend actively working on files in a particular project's directory.
10
10
 
11
11
  == SYNOPSIS:
12
12
 
13
- When working on source code, a developer is typically modifying files in a particular directory and saving them periodically. By monitoring the timestamps of files in a project directory and detecting when a file has been updated, one could theoretically measure a developer's time spent changing code by logging timestamp changes and grouping them in to sessions of continuous activity. This is how Baby Bro works.
14
-
15
- == REQUIREMENTS:
16
-
17
-
13
+ When working on source code, a developer is typically modifying files in a particular directory and saving them periodically. By monitoring the timestamps of files in a project directory and detecting when a file has been updated, one could theoretically measure a developer's time spent changing code by logging timestamp changes and grouping them into sessions of continuous activity. This is how Baby Bro works.
18
14
 
19
15
  == INSTALL:
20
16
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.0.2
1
+ 0.0.3
data/baby-bro.gemspec CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  Gem::Specification.new do |s|
7
7
  s.name = %q{baby-bro}
8
- s.version = "0.0.2"
8
+ s.version = "0.0.3"
9
9
 
10
10
  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
11
11
  s.authors = ["Bill Doughty"]
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: baby-bro
3
3
  version: !ruby/object:Gem::Version
4
- hash: 27
4
+ hash: 25
5
5
  prerelease: false
6
6
  segments:
7
7
  - 0
8
8
  - 0
9
- - 2
10
- version: 0.0.2
9
+ - 3
10
+ version: 0.0.3
11
11
  platform: ruby
12
12
  authors:
13
13
  - Bill Doughty