### WordPress - Web publishing software
Copyright 2011-2019 by the contributors
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
This program incorporates work covered by the following copyright and
permission notices:
b2 is (c) 2001, 2002 Michel Valdrighi - m@tidakada.com -
http://tidakada.com
Wherever third party code has been used, credit has been given in the code's
comments.
b2 is released under the GPL
and
WordPress - Web publishing software
Copyright 2003-2010 by the contributors
WordPress is released under the GPL
---
### GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
### Preamble
The licenses for most software are designed to take away your freedom
to share and change it. By contrast, the GNU General Public License is
intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if
you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on,
we want its recipients to know that what they have is not the
original, so that any problems introduced by others will not reflect
on the original authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at
all.
The precise terms and conditions for copying, distribution and
modification follow.
### TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
**0.** This License applies to any program or other work which
contains a notice placed by the copyright holder saying it may be
distributed under the terms of this General Public License. The
"Program", below, refers to any such program or work, and a "work
based on the Program" means either the Program or any derivative work
under copyright law: that is to say, a work containing the Program or
a portion of it, either verbatim or with modifications and/or
translated into another language. (Hereinafter, translation is
included without limitation in the term "modification".) Each licensee
is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the Program
(independent of having been made by running the Program). Whether that
is true depends on what the Program does.
**1.** You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a
fee.
**2.** You may modify your copy or copies of the Program or any
portion of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
**a)** You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
**b)** You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any part
thereof, to be licensed as a whole at no charge to all third parties
under the terms of this License.
**c)** If the modified program normally reads commands interactively
when run, you must cause it, when started running for such interactive
use in the most ordinary way, to print or display an announcement
including an appropriate copyright notice and a notice that there is
no warranty (or else, saying that you provide a warranty) and that
users may redistribute the program under these conditions, and telling
the user how to view a copy of this License. (Exception: if the
Program itself is interactive but does not normally print such an
announcement, your work based on the Program is not required to print
an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
**3.** You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
**a)** Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections 1
and 2 above on a medium customarily used for software interchange; or,
**b)** Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your cost of
physically performing source distribution, a complete machine-readable
copy of the corresponding source code, to be distributed under the
terms of Sections 1 and 2 above on a medium customarily used for
software interchange; or,
**c)** Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is allowed
only for noncommercial distribution and only if you received the
program in object code or executable form with such an offer, in
accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
**4.** You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt otherwise
to copy, modify, sublicense or distribute the Program is void, and
will automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this
License will not have their licenses terminated so long as such
parties remain in full compliance.
**5.** You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
**6.** Each time you redistribute the Program (or any work based on
the Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
**7.** If, as a consequence of a court judgment or allegation of
patent infringement or for any other reason (not limited to patent
issues), conditions are imposed on you (whether by court order,
agreement or otherwise) that contradict the conditions of this
License, they do not excuse you from the conditions of this License.
If you cannot distribute so as to satisfy simultaneously your
obligations under this License and any other pertinent obligations,
then as a consequence you may not distribute the Program at all. For
example, if a patent license would not permit royalty-free
redistribution of the Program by all those who receive copies directly
or indirectly through you, then the only way you could satisfy both it
and this License would be to refrain entirely from distribution of the
Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
**8.** If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
**9.** The Free Software Foundation may publish revised and/or new
versions of the General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Program does not specify a
version number of this License, you may choose any version ever
published by the Free Software Foundation.
**10.** If you wish to incorporate parts of the Program into other
free programs whose distribution conditions are different, write to
the author to ask for permission. For software which is copyrighted by
the Free Software Foundation, write to the Free Software Foundation;
we sometimes make exceptions for this. Our decision will be guided by
the two goals of preserving the free status of all derivatives of our
free software and of promoting the sharing and reuse of software
generally.
**NO WARRANTY**
**11.** BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
**12.** IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
### END OF TERMS AND CONDITIONS
### How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
one line to give the program's name and an idea of what it does.
Copyright (C) yyyy name of author
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
Also add information on how to contact you by electronic and paper
mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
type `show w'. This is free software, and you are welcome
to redistribute it under certain conditions; type `show c'
for details.
The hypothetical commands \`show w' and \`show c' should show the
appropriate parts of the General Public License. Of course, the
commands you use may be called something other than \`show w' and
\`show c'; they could even be mouse-clicks or menu items--whatever
suits your program.
You should also get your employer (if you work as a programmer) or
your school, if any, to sign a "copyright disclaimer" for the program,
if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright
interest in the program `Gnomovision'
(which makes passes at compilers) written
by James Hacker.
signature of Ty Coon, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library,
you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the
[GNU Lesser General Public
License](http://www.gnu.org/licenses/lgpl.html) instead of this
License.
Real World Examples of Circumstances That May Taint a Deal Process - sinth.info
Four recent cases illustrate circumstances that may expose a deal to challenge because of a conflict of interest, and the ways a board or special committee may help insulate a deal process from someone with a potential conflict.
There are no hard and fast rules to apply where there is a potential conflict because the factual backgrounds and relationships in strategic corporate transactions are always highly complex, and there is no “perfect” deal process ordained by the courts.
Sometimes when a board is considering a strategic transaction, it may find that a key figure who can influence the deal process — for example, a founder, controller or CEO-negotiator — has a potential conflict of interest. They may be on both sides of the deal, or they may simply have personal motivations and interests that are not shared by all stockholders. Such conflicts can arise on either the buy- or sell-side.
In this situation, it will fall to the board or a special committee to find the best way to address any conflict. Each situation comes with its own set of facts, so there are no all-purpose rules that apply in every case. But four recent Delaware decisions scrutinized deal processes that were challenged by stockholders because influential figures, negotiators or other fiduciaries involved in the process had conflicts. These rulings offer examples both of behavior that could be cast in an unfavorable light if a deal is challenged, and approaches boards have taken that courts found were helpful to insulate the conflicted person and preserve the integrity of the deal process.
A deal process need not be “pitch perfect,” the Delaware Supreme Court stressed in one of the cases. Examining the facts of the four cases suggests what actions courts may find in-tune or off-key.
Factors the Courts Viewed Disfavorably
CEO Directing the Sale Process Was Set on One Buyer
When the take-private of Mindbody was challenged by stockholders, the court described how a private equity firm groomed the seller’s CEO to favor a deal with it. For example, the buyer invited the CEO to a conference it sponsored to prospect for acquisition targets where it emphasized how officers of companies it acquired could become very wealthy post-acquisition. Enamored with the prospective buyer, the CEO told it that he was looking for a “good home” for his company and its management team.
The court highlighted that the CEO rejected bidders that he disliked for personal reasons and signaled a lack of interest in competing offers by going on vacation during the go-shop process, telling management to decline presentations in his absence unless they were “urgent.” He also adjusted his company’s revenue guidance downward to depress the stock price and make a deal more attractive for his preferred buyer.
The court took issue with the CEO’s outsized role throughout the deal process and noted that the seller should have taken time to develop alternatives to promote competition and ensure a value-maximizing process.
Negotiator’s Experience Level and Personality
When TransCanada purchased Columbia Pipeline and the target’s stockholders challenged the deal, the court noted that both Columbia’s CEO and CFO hoped to retire early and, from the outset, sought to arrange a sale that would trigger change-of-control benefits for themselves.
The court also detailed the missteps of the CFO, who was appointed to lead the sale process despite the fact that he had never had a major role in an M&A negotiation. During one early meeting with the eventual buyer, the CFO handed over his talking points about the deal price and timing. He also arranged one-on-one meetings with Columbia directors, which he used to manipulate the flow of information and steer the directors individually toward his desired result.
The court said that qualities that may be laudable in other contexts can be undesirable during the deal process. For example, in Columbia Pipeline’s case, the “trusting, team-oriented, and transparent” CFO who lacked “guile” and a “poker face” created vulnerabilities and undercut his company’s negotiating leverage.
By contrast, in the Tesla-Solar City decision discussed below, the court praised the board for vesting negotiating power in an indisputably independent director who exercised mastery over the negotiations.
Interactions With Counterparties
In both the Mindbody and Columbia Pipeline cases, the court reprimanded the negotiators for ignoring communication guidelines set by their boards. For example, the negotiators privately tipped their preferred counterparties (directly and through their bankers) about their companies’ target price and their personal motivations for a sale.
The Mindbody court also criticized the CEO for permitting the company’s banker to facilitate a connection for him with the potential private equity buyer before the formal sale process had begun and without board authorization.
Counterparty’s Role Aiding and Abetting Conflicts
While the conflicts in the Mindbody and Columbia deals arose on the target side, in both cases the courts found the buyers — the counterparties — liable for damages as well because they took advantage of those conflicts.
The Columbia Pipeline and Mindbody decisions chastised the buyers for inducing the sellers’ conflicted negotiators to act against the interests of their stockholders by, for example, revealing inside information, including before due diligence, so that the buyers could move more quickly than other potential bidders.
The Columbia court further admonished the executive who led negotiations for TransCanada for persistently violating Columbia’s process boundaries, including standstill agreements, no-teaming agreements and prohibitions on unsupervised contacts with management.
The court also criticized him for exploiting the conflicts of interest on the seller’s side by reneging on an agreement in principle and then “ambushing” the seller with a lower bid, coupled with a coercive and false threat to publicly disclose that negotiations had ended, knowing the seller was by then wedded to making a deal happen.
The court also held that TransCanada’s lead negotiator manipulated his relationship with Columbia’s lead negotiator by drawing on their past professional friendship and creating the impression that they were working together as partners behind the scenes.
In the Mindbody and Columbia Pipeline cases, the courts also faulted the buyers for failing to correct misstatements or omissions in the sellers’ proxy statements. In both cases, the buyers were contractually obligated to do so.
Factors the Courts Viewed Favorably
An Independent Board or Special Committee Making Its Own Decisions in the Best Interests of the Company
When Tesla considered buying Solar City, Tesla’s founder, who was presumed to control the company, also held a stake in Solar City and was therefore on both sides of the transaction. The court questioned the founder’s involvement, which included making overtures to Tesla’s board about the transaction, directing management to prepare presentations about the transaction, and participating in board meetings about the transaction.
Notwithstanding those facts, the court found that the Tesla board was not coerced on the timing or terms of an offer, or how long to spend on due diligence. The board proved itself willing to vigorously debate assumptions and oppose the conflicted director’s wishes.
Similarly, when Oracle purchased a company co-founded by Oracle’s founder, former CEO and largest shareholder, and on whose board he served, the court rejected a challenge to the deal. There the special committee implemented “rules of recusal” that prohibited the founder from discussing the transaction with anyone but the special committee, required employees who were involved in assessing the transaction to be informed of the recusal, and forbade officers and other employees from participating in the negotiation process absent the special committee’s direction.
In contrast to the Mindbody situation, the court in Oracle praised the special committee’s willingness to let the deal die if it was not in the company’s best interests.
Helpful Independent Financial Advisors
The courts in the Tesla, Oracle and Columbia Pipeline cases praised the boards or special committees for selecting top-tier financial advisors without longstanding relationships or conflicts with their companies or counterparties.
In the Tesla case, the court positively noted that, during due diligence, the company’s banker investigated the seller’s financial state, had discussions with the seller’s financial advisor, adjusted the focus of its work as concerns arose, reran analyses as needed, and kept the board apprised of new developments. The court also noted that, in response to information discovered during due diligence, the board lowered the offer price.
In the Mindbody decision, the court applauded the company’s banker for sharing its knowledge about the buyer, including its modus operandi and associated risks, but said that the company’s CEO ignored that information.
In Sum
In sum, Delaware courts have long held that a deal process does not have to be perfect and there is no one-size-fits-all blueprint. The facts and circumstances of each deal process will be considered and any one of the potentially problematic issues described above alone may not be enough to doom the process. But these cases should help directors understand what circumstances may taint a deal process and, on the other hand, what guardrails they may want to consider to protect the integrity of a deal process.
Endnotes
1Skadden advised Oracle’s special committee.(go back)