All posts by Bradley M. Kuhn

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

If You’ve Got a Problem With Me, Please Contact Me!

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/29/untrustworthiness.html

[ I usually write blog posts about high-minded software freedom
concepts. This post isn’t one of those; it’s much more typical personal
blog-fare, so please stop reading here if you’re looking for a good
software freedom essay; just move on to another one of my blog posts if
that’s what you want. ]

I heard something really odd today. I was told that a relatively large
group of people find me untrustworthy and refuse to work or collaborate
with me because of it. I heard this second-hand, and I asked for more
details, and the person who told me really doesn’t want to be involved
any further (and I don’t blame that person, because the whole thing is
admittedly rather silly, and I’d walk away too if it wasn’t personally
about me).

There are people in the world I don’t trust too, of course. I always
tell them so to their face. I just operate my life in a really
transparent way, so if I believe someone is my political opponent, I
tell them so. I’ve written emails to people that say things
like: Now that you work for Company Blah, I have to assume you’re
working against Free Software, because Company Blah has a history of
doing so.
If someone says something offensive to me, I tell them
they’ve offended me. Sometimes, I clearly say that I am explicitly not
forgiving the person, which thus makes it clear that there is a standing
issue between us indefinitely. I do occasionally hold a grudge.
(Frankly, I doubt people who claim they never hold a grudge, because
everyone I’ve ever met seems to have a grudge against somebody for
something.)

I’ve been told that I’m not tactful. I always respond
with: Of course, I’m not a tactful person. I’ve made a conscious
choice not to change that behavior because, IMO, the other
option is to leave people guessing about how you feel about their
actions. If I think someone’s action is wrong, I tell them I think it’s
wrong and why. If I think someone’s action is good, I thank them for it
and ask if I can help in the future. That’s not a tactful way to live,
I admit, but I believe it’s nevertheless an honorable way to live. I’m
grateful for the tactful people I know, because I realize they can
accomplish things that I can’t, but I also point out that there are
things that the untactful can accomplish that the tactful can’t. For
example, only the tactless can point out emperors who wear no
clothes.

Meanwhile, the kinds of backroom (and seemingly tactful) politics that
we sometimes see in Free Software have a way of descending into high
school drama. I heard from Foo who heard from Bar that you won’t
be elected class president because nobody likes you
. No, I
can’t say who Bar heard it from. No, I can’t tell you exactly
why.
This immature behavior is, IMO, much worse than being
tactless.

I frankly think those who operate this way should be ashamed of
themselves. I’m therefore putting out a public call (which is just a
repeat of what I’ve said privately to people for years): if you have
some problem with something I’ve done, or find my actions at any time
untrustworthy, or wrong, or anything else negative, you’re welcome to
contact me. I get emails almost weekly anyway of people who have issues
with something I’ve said on the Free as
in Freedom
audcast
or somewhere else. I take the time to
answer almost everyone who writes to me. I also always tell people that
you can keep pinging me until I answer and I won’t be offended if you
do. Sometimes, I might just write back with the reasons why I decided
not to answer you. But, I’ll always at least tell you my opinions on
what you’ve said, even if it’s just a tactless: I don’t think what
you’re writing about is a major priority and I can’t schedule the time
to think about it further right now
. I challenge others in the
Free Software community to also rise up to more transparency in their
actions and statements.

I want to be clear, BTW, there’s a difference between being tactless
and mean. I work really hard not to be mean; I sometimes fail, and I
also work very hard to examine my actions to see if I’ve crossed the
line. I send apologies to people when it becomes apparent that I’ve
been not just tactless but also mean. I have to admit, though, there
are plenty of mean people kicking around the Free Software world who owe
a bunch of apologies (including some to me), but if you
think I owe you an apology, I encourage you to write to me and ask for
one. In my tactless style, I’ll either give you an apology or tell you
why I disagree about why you deserve one. 🙂

Finally, I thought hard about whether to “name names”
herein. It’s surely obvious that a specific situation has inspired my
words above, and those who know what this situation is will realize
immediately; those that don’t will sadly be left wondering what the hell
is going on. Still, as disgusted as I am about the backroom politics
I’m dealing with at the moment, I think public admonishment of the
perpetrators here would cross the line from tactless to mean, so I
decided not to cross the line.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.

Left Wondering Why VideoLan Relicensed Some Code to LGPL

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/11/22/vlc-lgpl.html

I first met the original group of VLC developers at
the Solutions GNU/Linux
conference in 2001. I had been an employee of FSF for about a year at
the time, and I recall they were excited to tell the FSF about the
project, and very proud that they’d used FSF’s premier and preferred
license (at the time): GPLv2-or-later.

What a difference a decade makes. I’m admittedly sad
that VLC
has (mostly) finished its process of relicensing some of its code under
LGPLv2.1-or-later
. While I have
occasionally supported
relicensing from GPL to LGPL
, every situation is different and I
think it should be analyzed carefully. In this case, I don’t support
VideoLan’s decision to relicense the libVLC code.

The main reason to use the LGPL,
as RMS put
eloquently long ago
, is for situations where there are many
competitors and developers would face serious difficulty gaining
adoption of a strong-copylefted solution. Another more recent reason
that I’ve discovered to move to weaker licenses (and this was the case
with Qt) is to normalize away some of
the problems
of proprietary relicensing
. However, neither reason applies to
libVLC.

VLC is the most popular media player for desktop computers. I know
many proprietary operating system users who love VLC and it’s the first
application they download to a new computer. It is the standard for
desktop video viewing, and does a wonderful job advocating the value of
software freedom to people who live in a primarily proprietary software
world.

Meanwhile, the VideoLan Organization’s press statements have
been quite vague on
their reasons for changing, saying only that this change was
motivated to match the evolution of the video industry and to spread the
VLC engine as a multi-platform open-source multimedia engine and
library
. The only argument that I’ve seen discussed heavily in
public for relicensing is ostensibly to address the widely publicized
incompatibility of copyleft licensing with various App Store agreements.
Yet, those incompatibilities still exist with the LGPL
or, indeed, any true copyleft license. The incompatibilities of Apple’s
terms are so strict that they make it absolutely impossible to comply
simultaneously with any copyleft and Apple’s terms at the same time.
Other similar terms aren’t much better, even with Google’s Play Store
(— its terms are incompatible with any copyleft license if the
project has many copyright holders)0.

So, I’m left baffled: does the VLC community actually believes the LGPL
would solve that problem? (To be clear, I haven’t seen any official
statement where the VideoLAN Organization claims that relicensing will
solve that issue, but others speculate that it’s the reason.) Regardless,
I don’t think it’s a problem worth solving. The specters of
“Application Store” terms and conditions are something to
fight against wholly in an uncompromising way. The copyleft licensing
incompatibilities with such terms are actually a signaling mechanism to
show us that these stores are working against software freedom
actively. I hope developers will reject deployment to these application
stores entirely.

Therefore, I’m left wondering what VLC seeks to do here. Do they want
proprietary application interfaces that use their core libraries? If
so, I’m left wondering why: VLC is already so popular that they could
pull adopters toward software freedom by using the strong copyleft of
GPL on libVLC. It seems to me they’re making a bad trade-off to get only
marginally more popular by allowing some proprietary derivatives. OTOH,
I guess I should cut my losses on this point and be glad they stuck with
any copyleft at all and didn’t go all the way to a permissive
license.

Finally, I do think there’s one valuable outcome shown
by this
relicensing effort
(which
Gerv pointed out first
): it is possible to
relicense a multi-copyright-held code based. It’s a lot of work, but it
can be done. It appears to me that VLC did
a responsible and reasonable
job on that part, even if I disagree strongly with the need for such a
job here in the first place.

Update (2012-11-30): It’s been pointed out to me that
VLC has relegated certain code from VLC into a library called libVLC,
and that’s the code that’s been relicensed. I’ve made today changes to
the post above to clarify that issue.


0 If you want to hear more
about my views and analysis of application store terms and conditions,
please listen to the
Application Stores Panel

that I
was on

at FOSDEM
2012
, which was broadcast on the audcast,
Free as in Freedom.