[Pidgin] #15513: Add OTR (Off The Record plugin) to release

[Pidgin]

#15513: Add OTR (Off The Record plugin) to release
--------------------------+-----------------------
 Reporter:  ioerror       |       Owner:  datallah
     Type:  enhancement   |      Status:  new
Milestone:                |   Component:  privacy
  Version:  2.10.6        |  Resolution:
 Keywords:  security otr  |
--------------------------+-----------------------

Comment (by MarkDoliner):

 Responding to an email from the devel at pidgin.im mailing list:

 On Tue, Feb 12, 2013 at 3:05 PM, Ethan Blanton <elb at pidgin.im> wrote:
 > I am not interested in including a third-party binary plugin in our
 > Windows build only; I would be more inclined to bring the Pidgin
 > OTR plugin (or a version thereof) into the Pidgin sources, and
 > release it on all platforms where the dependencies are met.  (I see
 > that you propose this on your bug.)

 Yeah, I would prefer not to bundle a binary with our Windows installer.  I
 have a hunch that it would be as easy to bundle the source and build for
 all platforms.  I think more people would benefit from this, and I think
 it would be easier to manage.  Do you have any crazy dependencies?  I
 guess we would need to add libotr to our Windows installer.

 I'm not sure what that would mean for your release cycle.  How often do
 you release?  At our most frequent we maybe only release every other
 month.  Recently it's been less frequent.  Would that be a problem?  I
 think you would still be able to do your own standalone releases more
 frequently (I can't think of any problems that would cause.  I guess maybe
 some users might end up with 2 versions of the plugin if they installed it
 themselves locally).  And it would be up to you whether you want to
 completely move your development to our source repo, or continue
 maintaining your code in your own source repo and periodically sync into
 our repo.

 I'd also prefer for this to go in the default branch (eventually 3.0.0)
 and not the release-2.x.y branch.  Which would mean your plugin wouldn't
 ship with Pidgin until we're actually ready to release 3.0.0, which is
 still months away (no planned release date).

 So I don't know, if there are no major objections over the next day or
 three then we can maybe just give you write access to our Mercurial repo?

 > So ... the net wrapup of all of that is that I'm left feeling a little
 > bit nervous about how smoothly this will go for Pidgin in the long
 > run, but I think it's a positive general step if you are willing to
 > step up for long-term maintenance, and I support it.

 I agree with all this.

-- 
Ticket URL: <https://developer.pidgin.im/ticket/15513#comment:30>
Pidgin <http://pidgin.im>
Pidgin