DiSo Licensing & Copyright [WAS: Re: DiSo Action Streams ready for repository, naming schemes,]
Chris Messina
http://twitter.com/gstein/statuses/769974420
Thinking that that might be wise, but not sure about compatibility
with other licenses. I'll ask him.
Chris
On Tue, Mar 11, 2008 at 1:57 PM, Stephen Paul Weber
<singp...@gmail.com> wrote:
> I suppose. Gotta hate all this crap! I know rather large amounts of
> nothing in this area, so I'm open to whatever makes sense :)
>
>
>
> On Tue, Mar 11, 2008 at 2:53 PM, Chris Messina <chris....@gmail.com> wrote:
> >
> > Part of the issue of copyright assignment is to prepare for the
> > potential future success of this project (not counting any eggs yet,
> > just leveraging my experience from other OSS projects). If we end up
> > incorporating into some kind of foundation to manage IP or to hold
> > trademarks and things of that nature (ugh, I still hate the
> > "necessity" those things represent -- long live rationality!), having
> > the copyrights all "owned" by a single entity makes it easier to make
> > changes all at once, rather than having to go back and get sign off
> > from every contributor.
> >
> > Because of the open nature of this project, and the potential for
> > "drive by coding", it will be increasingly difficult to manage and
> > maintain a current list of contact information for prior contributors
> > should we need to make a licensing (or other) change which requires
> > each contributor's sign off. Without that sign off, we'll likely need
> > to either rewrite the code or strip it from our repository.
> >
> > Getting copyright assignment now prevents that from happening. This is
> > also a reason to restrict write-access to the repository.
> >
> > Regardless of the license of the code we use (which only really
> > governs reuse of the code), the issue of copyright affects us
> > internally in what we're able to do and how much flexibility we have
> > to make the best decisions for the health and continued wellfare of
> > the project.
> >
> > Chris
> >
> >
> >
> > On Tue, Mar 11, 2008 at 1:20 PM, Steve Ivy <stev...@gmail.com> wrote:
> > >
> > > Ok, pending Chris' investigations, +1 for MIT. Let's get a copy of the
> > > license into each component directory.
> > >
> > > Also, curious to see what Singpolyma "Going Evil" looks like. LOL! I
> > > think the copyright issue is more so that others annot *claim* the
> > > code as theirs, even though they are free to use and redistribute it.
> > > Chris?
> > >
> > > On Mar 11, 11:05 am, "Stephen Paul Weber" <singpol...@gmail.com>
> > > wrote:
> > >
> > > > After reading wikipedia, also leaning towards MIT.
> > > >
> > > > As for copyright - is that a big deal if we're under MIT? If I go
> > > > evil anyone can still use my MIT-licensed code, yes?
> > > >
> > >
> > >
> > > > On Tue, Mar 11, 2008 at 2:02 PM, Chris Messina <chris.mess...@gmail.com> wrote:
> > > >
> > > > > +1 to Steve Ivy's naming convention (wp-diso-* and wp-* for
> > > > > diso-specific and general plugins respectively).
> > > >
> > > > > Re: license, here's the MIT license:
> > > >
> > > > > Copyright (c) <year> <copyright holders>
> > > >
> > > > > Permission is hereby granted, free of charge, to any person
> > > > > obtaining a copy of this software and associated documentation
> > > > > files (the "Software"), to deal in the Software without
> > > > > restriction, including without limitation the rights to use,
> > > > > copy, modify, merge, publish, distribute, sublicense, and/or sell
> > > > > copies of the Software, and to permit persons to whom the
> > > > > Software is furnished to do so, subject to the following
> > > > > conditions:
> > > >
> > > > > The above copyright notice and this permission notice shall be
> > > > > included in all copies or substantial portions of the Software.
> > > >
> > > > > THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> > > > > EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
> > > > > OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
> > > > > NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
> > > > > HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
> > > > > WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> > > > > FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
> > > > > OTHER DEALINGS IN THE SOFTWARE.
> > > >
> > > > > here's BSD:
> > > >
> > > > > Copyright (c) <year>, <copyright holder>
> > > > > All rights reserved.
> > > >
> > > > > Redistribution and use in source and binary forms, with or without
> > > > > modification, are permitted provided that the following conditions are met:
> > > > > * Redistributions of source code must retain the above copyright
> > > > > notice, this list of conditions and the following disclaimer.
> > > > > * Redistributions in binary form must reproduce the above copyright
> > > > > notice, this list of conditions and the following disclaimer in the
> > > > > documentation and/or other materials provided with the distribution.
> > > > > * Neither the name of the <organization> nor the
> > > > > names of its contributors may be used to endorse or promote products
> > > > > derived from this software without specific prior written permission.
> > > >
> > > > > THIS SOFTWARE IS PROVIDED BY <copyright holder> ``AS IS'' AND ANY
> > > > > EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> > > > > WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> > > > > DISCLAIMED. IN NO EVENT SHALL <copyright holder> BE LIABLE FOR ANY
> > > > > DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> > > > > (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> > > > > LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
> > > > > ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> > > > > (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> > > > > SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> > > >
> > > > > Personally I'm leaning towards MIT. It seems simpler and more to the point.
> > > >
> > > > > One question: how do we deal with copyright? In most projects, the
> > > > > copyright is assigned to a master author/person/company. Since there
> > > > > is no "legal" DiSo entity, it seems that we should figure out this
> > > > > question. I'll ask my fellow open source foundation friends what they
> > > > > think.
> > > >
> > > > > Chris
> > > >
> > >
> > >
> > > > > On Tue, Mar 11, 2008 at 12:48 PM, Steve Ivy <steve...@gmail.com> wrote:
> > > >
> > > > > > On Mar 11, 9:06 am, "Stephen Paul Weber" <singpol...@gmail.com> wrote:
> > > > > > > The reason I didn't name it wp-diso-profile was that it is in a
> > > > > > > /wordpress directory already.
> > > >
> > > > > > Yeah, but that's not always going to be the case once we're packaging
> > > > > > these for individual download. Once it's on your HD you're going to
> > > > > > want that un-compressed folder to be recognizable. (IMHO)
> > > >
> > > > > > > Actionstream I dual MIT/BSD'ed for now - but you're right. Let's
> > > > > > > decide already.
> > > >
> > > > > > > I am ready to put the correct stuff in place to license all of my
> > > > > > > contributions to the DiSo code repository on Google Code under either
> > > > > > > an MIT, BSD, or compatible license, or to multi-license the code.
> > > >
> > > > > > What's the difference again between MIT and BSD? Any lawyer-ish types
> > > > > > hanging out here?
> > > >
> > > > > > > On Tue, Mar 11, 2008 at 12:01 PM, Steve Ivy <steve...@gmail.com> wrote:
> > > >
> > > > > > > > Stephen (and all),
> > > >
> > > > > > > > I think this is ready to go into the repo. What do you think? Would
> > > > > > > > you mind checking it in to /wordpress/wp-diso-actionstreams/trunk/ ?
> > > > > > > > You should have commit access.
> > > >
> > > > > > > > While you're in there, perhaps we could move diso-profile to wp-diso-
> > > > > > > > profile? I'd like to keep to the naming scheme wp-<plugin> in the case
> > > > > > > > of general technologies (oauth, openid) and wp-diso-<plugin> for more
> > > > > > > > social-specific code (actions streams, profiles, contacts, etc).
> > > >
> > > > > > > > Finally, if we are going to agree on a BSD or MIT license, let's
> > > > > > > > finally decide, and make sure that each component has the right
> > > > > > > > license file and source headers in place. I'm excited about where we
> > > > > > > > are right now!! Additionally, I have a partially done Movable Type
> > > > > > > > blogroll plugin I'm going to donate in the next week or so (assuming I
> > > > > > > > can get it to a usable level).
> > > >
> > > > > > > > --Steve
> > > >
> > > > > > > > What does the group think?
> > > >
> > > > > > > > On Mar 10, 9:13 pm, "Stephen Paul Weber" <singpol...@gmail.com> wrote:
> > > > > > > > > Tumblr support added (thanx Pras!) - polling bug fixed. I've uploaded
> > > > > > > > > 0.11 to the same URL as before. I should post about this on my blog,
> > > > > > > > > since so many others seem to be... heh
> > > >
> > > > > > > > > On Mon, Mar 10, 2008 at 1:12 PM, Stephen Paul Weber
> > > >
> > > > > > > > > <singpol...@gmail.com> wrote:
> > > > > > > > > > GUID done and done. the YAML has a field to specify 'identifier'
> > > > > > > > > > (usually url, id on atom, guid on rss2, depends on the service) - this
> > > > > > > > > > is hashed (sha1) and used as the database key. So if you bookmark the
> > > > > > > > > > same thing in delicious and magnolia (for example) they wouldn't both
> > > > > > > > > > show up.
> > > >
> > > > > > > > > > Twitter settings just now use the atom ID - which is not likely to be
> > > > > > > > > > the same as any id on tumblr or similar. That's where my pattern
> > > > > > > > > > matching thought came in. Thoughts?
> > > >
> > > > > > > > > > Pras has confirmed the polling bug. Fixed on my version, should be
> > > > > > > > > > posted this evening.
> > > >
> > > > > > > > > > A note about the YAML - if no URL is given in the action_streams
> > > > > > > > > > section, the URL from the profile_services section is used and we
> > > > > > > > > > autodetect RSS/ATOM with <link>s. My implementation supports rss2:
> > > > > > > > > > similar to the atom: from the original (which I also support).
> > > >
> > > > > > > > > > "What about editing that list of URLs? Where should one go to do that?" - Steve
> > > >
> > > > > > > > > > Which list? You mean to remove a service, what do you do? Right now
> > > > > > > > > > there is no way to do that (lazy me) - to change your username on a
> > > > > > > > > > service just 'add' it again and it will overwrite.
> > > >
> > > > > > > > > > List of available services? config.yaml
> > > >
> > > > > > > > > > Or something else?
> > > >
> > > > > > > > > > On Mon, Mar 10, 2008 at 12:53 PM, Pras Sarkar <pras.sar...@gmail.com> wrote:
> > > >
> > > > > > > > > > > I agree with Steve. It probably needs to start with some basic level
> > > > > > > > > > > of guid matching (where available), but in a lot of cases where guid
> > > > > > > > > > > is not available, or simply not preserved/changed, the deduping code
> > > > > > > > > > > needs some form of similarity matching. Using some basic distance
> > > > > > > > > > > calculation algos, deduping can be fairly accurate as the time-to-scan
> > > > > > > > > > > is short (most aggregators will have sourced and syndicated the
> > > > > > > > > > > content within hours of the original service).
> > > >
> > > > > > > > > > > -Pras
> > > >
> > > > > > > > > > > On Mar 10, 9:16 am, Steve Ivy <steve...@gmail.com> wrote:
> > > > > > > > > > > > I think de-duping will have to be more involved - prolly need to start
> > > > > > > > > > > > with the guid (in ATOM and some variants of RSS) as a basis, then
> > > > > > > > > > > > getting more esoteric from there.
> > > >
> > > > > > > > > > > > On Mar 10, 7:36 am, Singpolyma <singpol...@gmail.com> wrote:
> > > >
> > > > > > > > > > > > > Thoughts on more de-duping. Right now it just de-dupes /inside/ a
> > > > > > > > > > > > > service... but if someone adds their tumblr or something and has
> > > > > > > > > > > > > twitter in tumblr, etc, you don't want the same update displaying
> > > > > > > > > > > > > twice.
> > > >
> > > > > > > > > > > > > Can we safely just do something like:
> > > >
> > > > > > > > > > > > > $done = array();
> > > >
> > > > > > > > > > > > > foreach($items as $item)
> > > > > > > > > > > > > if(in_array($item, $done)) continue;
> > > >
> > > > > > > > > > > > > ? or do the other services often change it a fair bit? Should that
> > > > > > > > > > > > > be handled by cleanup inline (ie, facebook adds 'is twittering' - but
> > > > > > > > > > > > > twitter adds 'username: ' and that gets detected and removed, so the
> > > > > > > > > > > > > other could be as well...)
> > > >
> > > > > > > > > > > > > I think either way, detected dupes should be handled as current
> > > > > > > > > > > > > "dupes" are - output the node anyway, but hide it (for scrapers, they
> > > > > > > > > > > > > see the whole lifestream with all nodes)
> > > >
> > > > > > > > > > > > > On Mar 9, 10:38 pm, Pras Sarkar <pras.sar...@gmail.com> wrote:
> > > >
> > > > ...
> > > >
> > > > read more »
> > >
> > >
> > > >
> > >
> >
> >
> >
> > --
> >
>
> > Chris Messina
> > Citizen-Participant &
> > Open Source Advocate-at-Large
> > Work: http://citizenagency.com
> > Blog: http://factoryjoe.com/blog
> > Cell: 412.225.1051
> > IM: factoryjoe
> > This email is: [ ] bloggable [X] ask first [ ] private
> >
> > >
> >
>
>
>
>
> --
> - Stephen Paul Weber (Singpolyma)
>
> Web: http://singpolyma.net/
> Twitter: http://twitter.com/singpolyma
> IM: singp...@gmail.com
>
> >
>
--
Chris Messina
Citizen-Participant &
Open Source Advocate-at-Large
Work: http://citizenagency.com
Blog: http://factoryjoe.com/blog
Cell: 412.225.1051
IM: factoryjoe
This email is: [ ] bloggable [X] ask first [ ] private
Joseph Anthony Pasquale Holsten
works for X-windows, rails, etc. Closest enforceable license to PD.
Also a good choice for dual licensing.
http:// Joseph Holsten .com