Ruby API for accessing/updating Google Groups - based on Mechanize
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib
test
.document
.gitignore
Gemfile
Gemfile.lock
LICENSE.txt
README.rdoc
Rakefile
VERSION
rgroups.gemspec

README.rdoc

rgroups

Ruby API for accessing/updating Google Groups - based on Mechanize. This essentially just screen-scrapes Google Groups and automates clicking on things. It's not entirely efficient, but it sure beats having to script it yourself.

Note: As of 2013-11-09, I've found that large portions of the gem no longer work. I do not have any particular reason to continue maintaining it (and ew, screen scraping really is horrible). If anyone wishes to contribute, that's fine.

Usage

Setup is easy!

require 'rgroups'
rg = RGroup.new
rg.login('username', 'password')

Or, if you're using Google Apps for your Domain (GAFYD):

rg = RGroup.new('mydomain.com')
rg.login('username', 'password')

Adding a user to a group:

rg.add_user('address@domain.com', 'group', :message => 'message to send to invitees')

Adding a user directly (only for GAFYD accounts):

rg.add_user('address@mydomain.com', 'group', :mode => 'direct', :notify => true, :message => 'message to send to people', :delivery => 'digest')

Modifying a user's delivery options:

rg.update_user('address@domain.com', 'group', 'set_delivery', :value => 'summary')

Modifying a user's membership type:

rg.update_user('address@domain.com', 'group', 'set_member', :value => 'manager')

Notes

This relies on the 'old style' Google Groups. Please ensure that your group is using the old style before reporting a bug. Support for the new style should come soon…

Contributing to rgroups

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.

  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.

  • Fork the project.

  • Start a feature/bugfix branch.

  • Commit and push until you are happy with your contribution.

  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright

Copyright © 2012 Andrew Hayworth. See LICENSE.txt for further details.