From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, "Anselm R. Garbe" <garbeam@gmail.com>
Subject: Re: [9fans] wmii? 9p2000 compliant window manager.
Date: Sun, 20 Nov 2005 20:18:24 -0600 [thread overview]
Message-ID: <20051121021824.1862E2F6AF@dexter-peak.quanstro.net> (raw)
In-Reply-To: <20051120123039.GB20958@wmii.de>
i guess i'm guilty of not being clear too --- i was referring to the
copyright on 9base, not wmii, which appeared to me to be mit/x
on the web site.
thanks for clarifying things.
- erik
"Anselm R. Garbe" <garbeam@gmail.com> writes
|
| On Sat, Nov 19, 2005 at 10:35:21PM -0600, erik quanstrom wrote:
| > they only lists 19 applications. they seem to be playing fast-and-loose
| > with the copyright though. they only list the x/mit license and credit
| > only themselves.
|
| That is not true.
|
| I'm the maintainer of wmii, which does not contain any portions
| of plan9 code. It is developed from scratch und completely
| licensed under the terms of MIT license. Beginning with next
| version (wmii-3), which is planned for Xmas, all wmii-related
| servers (the core window manager, the shortcut manager, a
| keyboard driven menu and a pseudo-fs-router) will communicate
| via 9P. I implemented a unix library (libixp2) which is designed
| to allow very basic 9P client/server implementations, following
| the specs from the 9P man pages.
|
| In contrast to wmii I also packaged 9base, which I already
| announced on this list long ago, based on plan9port, the mk unix
| port - all by Russ and my Makefiles for wmii (because 9base does
| not depend on mk). We use 9base to configure wmii with rc
| scripts and included all useful userland tools we need for
| writing rc scripts. In contrast to plan9port we also link
| statically against libc. The license details of 9base are
| included in the tarball, I'll add them also to the 9base wiki
| page to clarify those things, because it seems to confuse people
| as this discussion shows.
|
| > their man pages seem to indicate that this is just a window manager.
|
| That is true. The next version will be simply a dynamic window
| manager with some tools around and the 9P interface.
|
| Regards,
| --
| Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361
next prev parent reply other threads:[~2005-11-21 2:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 2:08 David Leimbach
2005-11-20 2:44 ` Russ Cox
2005-11-20 4:14 ` erik quanstrom
2005-11-20 4:04 ` lucio
2005-11-20 4:35 ` erik quanstrom
2005-11-20 12:30 ` Anselm R. Garbe
2005-11-20 14:35 ` Russ Cox
2005-11-20 15:01 ` Anselm R. Garbe
2005-11-20 14:59 ` Russ Cox
2005-11-21 2:18 ` erik quanstrom [this message]
2005-11-21 18:08 ` David Leimbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051121021824.1862E2F6AF@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=garbeam@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).