Does anyone want to take over PaperTrail?

[airblade]

I can't seem to find enough time these days to give PaperTrail the attention it deserves. Does anyone want to take it over?

Here's what you'd be signing up for:

• The domain model has stood the test of time pretty well, but I think it could be a little more intuitive (Make domain model more intuitive #115, My two cents on what widget.versions.last.next_version should return. #124).
• The code is clean and well commented.
• The test code is harder to read than it should be. It uses an old version of Shoulda and has lots of nested contexts.
• There are one or two edge cases to fix (version_at may incorrectly return nothing #131, Version#changeset raises a ArgumentError #88).
• The big, unsolved problem is handling associations (Tracking many_to_many relationships #12, Added transaction support for restoring associations #44, Restore has_many through association when undoing a destroy #121, How to implement paper_trail on has_many associations #148).
• The code is tied to Rails 3. It would be nice to generalise it to support, say, Sinatra (Make PaperTrail work with Sinatra / Padrino / Rack #119).

[bhushangahire]

I am gonna work using this gem for Rails 3 version. I can continue working on it. Let me know.

[airblade]

@bhushangahire Thanks for the offer. Ideally I'd like someone who's already worked with PaperTrail a bit, and maybe even contributed code to it, but of course I don't want to rule anyone out.

[bhushangahire]

Sure no issues.

[m4tm4t]

I think (or not) I have a "way" for associations.

I have an Article model. It has many Page (polymorphic).

Basically, we can use the meta option

class Article
  has_paper_trail :on => [:update, :destroy], meta: {pages: Proc.new {|article| article.pages } }
  has_many :pages, as: :pageable, dependent: :delete_all
end

class Page
  belongs_to :pageable, :polymorphic => true, touch: true
end

the article is touched, but paper_trail don't care about updated_at column

[batter]

@airblade - I would be willing to at least take a crack at merging the existing pull requests and seeing if I have time to continue working on it going forward if you're still looking for someone. Let me know.

[airblade]

@batter Thank you! Try as I might I still haven't managed to find time for PaperTrail despite all the great pull requests piling up.

I've added you as a collaborator to the repo. Let me know if you have any queries and I'll do my best to get back to you quickly.

[stevenbristol]

@batter Thank you for taking this over!

Any idea of when handling has manys might be added?

[batter]

@stevenbristol - There were a few smaller features / issues I was going to address, for a 2.7.0 release. Hoping to address them and make a release before the holidays. I was planning on trying to tackle the has_many's and some other more complex tasks for a 3.0 release, but I wouldn't expect that to be ready until some time around February, as I will be travelling a lot in late December and January and won't have access to my computer for much of it.

If you or anyone else wants to take a crack at implementing, I'm open to looking at pull requests. #44 seems the most promising implementation attempt to date, but I haven't had the time to fully investigate and explore it. We want to make sure this is done properly, I'd like to avoid a shoddy implementation that is not sustainable for the long term.

See the Milestones Page for a tentative plan on release cycles.

[airblade]

I'm closing this now: @batter is doing a superb job :)