*sigh* Time to knock off some of these items...

dual-licensing like that /is/ legal as long as you hold the copyright
for the software.
So it only works as long as every piece of code committed to the project
was written by them, the contributor released their personal copyright
to them, or signed a release that allowed them to release it under those
terms.

Personally I despise that practice, it's either open-source or not open
source... as far as I'm concerned that kind of practice is not
open-source. Namely because it inhibits the ability to collaborate
openly on something. If someone checks out the open-source code, makes a
pile of improvements to it... unless they decide to give up their rights
to that code to the company that originally created it, that code cannot
be incorporated back into the original without forking the project in a
way that said contribution is only available for people using the AGPL
version.
Though, I suppose that's the opinion of someone who releases his own
open-source code under the MIT license instead of the GPL.


Next... this fud about html5 going around is annoying...
html5 is touted by plenty of projects, pretty much whenever a project
switches to "<!DOCTYPE html>" they instantly claim html5 as bragging
rights, it doesn't really change much at all about the project. (besides
shrugging off xml hype that's really tag soup and ditching a lot of
unnecessary markup)
html5 is NOT in it's infancy. html5 is a large spec covering things that
are already speced, standardizing de facto features that browsers have
already implemented and are simply now being put into spec form, new
features that have already been adopted into implementation by browsers,
and new features that have not yet been implemented by browsers. On top
of that "html5" is used to describe things like WebSockets, WebWorkers,
etc... which aren't even part of the html5 spec.
"Using html5" can mean anything from using the doctype, to using already
existing de facto features that are simply being standardized, to using
new features like canvas which are already implemented enough they are
fairly reasonable to use if you have a reason to, to using newer
features like WebSockets which have an implementation but haven't made
their way to other browsers yet.
html5 may have a far away "completion" date, but thats the date for
absolutely everything... portions of the spec are already ready for, and
intended for use today.
Bragging about html5 or trying to dismiss something because they brag
about html5 means ABSOLUTELY NOTHING unless you are discussing precisely
which of the many things that are called "html5" is actually being used.
By the way, innerHTML and the api wysiwyg editors have to make use of to
provide wysiwyg ARE html5 specified.

Oh, for the record, MediaWiki has already gone "html5", it's already in
trunk and eventually it'll be turned on by default.


And finally... that editor is a html editor. Trying to make a html
wysiwyg editor work with WikiText is already enough of a mess, current
WYSIWYG still doesn't quite measure up, and the dynamic nature of that
editor is liable to make it even harder to integrate, bordering on the
impossible.

~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]

Alex Kozak wrote:
> IANAL, but I think a dual-licensing is fine as long as the AGPL is 
> compatible with MediaWiki (whatever that means).
>
> AK
>
> On Wed, Jul 21, 2010 at 9:05 AM, Laurent Alquier 
> <laurent-tknwmtfdyfhafugrpc6...@public.gmane.org 
> <mailto:laurent-tknwmtfdyfhafugrpc6...@public.gmane.org>> wrote:
>
>
>     (do over as a forward to the list and not a simple reply).
>
>     I agree on both accounts - the licensing seems problematic for
>     corporate use and HTML 5 is still very much in its infancy.
>
>     I can also add another comment :
>
>     - Rich text editors still need significant improvements to handle
>     MediaWiki tags (and semantic tags). Would such an editor be open
>     enough to plugins or extensions to support additional tags ?
>
>     - Laurent
>
>     On Wed, Jul 21, 2010 at 11:57 AM, Yaron Koren <yaro...@gmail.com
>     <mailto:yaron57-re5jqeeqqe8avxtiumw...@public.gmane.org>> wrote:
>
>         Hi,
>
>         This looks interesting. I have two main comments/questions
>         about it:
>
>         - I don't know if the license for Aloha Editor is compatible
>         with MediaWiki - it has a dual license, of AGPL for
>         open-source plus a commercial license:
>
>         http://www.aloha-editor.org/license.html
>
>         I'm far from a license expert - would that work, or not?
>
>         - It uses HTML5, i.e. everyone's favorite semi-nonexistent
>         technology. My understanding is that HTML5 is partly supported
>         by various browsers, though not IE. Is it too early to talk
>         about HTML5 in the context of MediaWiki?
>
>         -Yaron
>
>
>         On Wed, Jul 21, 2010 at 9:56 AM, Krabina Bernhard
>         <krabina-t2bvwtos7efeowh0uzb...@public.gmane.org
>         <mailto:krabina-t2bvwtos7efeowh0uzb...@public.gmane.org>> wrote:
>
>             Hi,
>
>             please have a look at this new editor:
>             http://www.aloha-editor.org/
>
>             Maybe this would be a nice feature for MediaWiki in
>             general and Semantic Forms in particular...
>
>             regards,
>             Bernhard
>
>
>
>
>         -- 
>         WikiWorks · MediaWiki Consulting · http://wikiworks.com
>
>         
> ------------------------------------------------------------------------------
>         This SF.net email is sponsored by Sprint
>         What will you do first with EVO, the first 4G phone?
>         Visit sprint.com/first <http://sprint.com/first> --
>         http://p.sf.net/sfu/sprint-com-first
>         _______________________________________________
>         Semediawiki-devel mailing list
>         semediawiki-devel-5nwgofrqmnerv+lv9mx5uipxlwaov...@public.gmane.org
>         
> <mailto:semediawiki-devel-5nwgofrqmnerv+lv9mx5uipxlwaov...@public.gmane.org>
>         https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>
>
>
>
>     -- 
>     - Laurent Alquier
>     http://www.linfa.net
>
>
>
>     -- 
>     - Laurent Alquier
>     http://www.linfa.net
>
>     
> ------------------------------------------------------------------------------
>     This SF.net email is sponsored by Sprint
>     What will you do first with EVO, the first 4G phone?
>     Visit sprint.com/first <http://sprint.com/first> --
>     http://p.sf.net/sfu/sprint-com-first
>     _______________________________________________
>     Semediawiki-devel mailing list
>     Semediawiki-devel@lists.sourceforge.net
>     
> <mailto:semediawiki-devel-5nwgofrqmnerv+lv9mx5uipxlwaov...@public.gmane.org>
>     https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>
>
>
>
> -- 
> Alex Kozak
> Program Assistant
> Creative Commons
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ------------------------------------------------------------------------
>
> _______________________________________________
> Semediawiki-devel mailing list
> semediawiki-devel-5nwgofrqmnerv+lv9mx5uipxlwaov...@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>   


-- 
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

Reply via email to