You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2012/08/03 22:36:50 UTC

handling optional GPL dependencies

I'm trying to figure out the best way to handle an optional GPL
dependency.  We may have other non-AL2 licensed deps that we can work
through later, but my current task involves importing from mediawiki to
Allura and the GPL lib from
https://github.com/zikzakmedia/python-mediawiki seems like the best way
to do it.  This isn't core functionality to Allura, so according to
http://www.apache.org/legal/resolved.html#optional it should be ok for
the importer code to depend on it.

So, on to technical matters - how to make that work.   So far I'm
ensuring that "import mediawiki" is in the importer code, so everything
else functions without it installed.  Trickier bits are:

1) How to run the importer tests.  I'm thinking they should
automatically skip if the mediawiki package is not present.  An
alternative would be to move them to some location so that they are not
run by default, and would have to be manually run.

2) Where to define the dependency.  Currently all deps are listed in
requirements-common.txt which is used during regular installation.  It
should not be there since it'll be optional.  We could have a
requirements-optional.txt and put all optional deps there.  But that
could grow to be a hodge-podge and only useful if someone wants
absolutely everything (e.g. during a test suite run).  I think also the
importer script should give specific installation instruction if it is
attempted to be run.

How does that sound?  I expect this won't be the only time we have to
deal with it, so a pattern would be good to establish.




-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: handling optional GPL dependencies

Posted by Greg Stein <gs...@gmail.com>.
Agreed, on both points.
On Aug 3, 2012 4:44 PM, "Wayne Witzel III" <ww...@gmail.com> wrote:

> On Friday, August 3, 2012 at 1:36 PM, Dave Brondsema wrote:
> >
> > 1) How to run the importer tests. I'm thinking they should
> > automatically skip if the mediawiki package is not present. An
> > alternative would be to move them to some location so that they are not
> > run by default, and would have to be manually run.
>
> I like the idea of checking for the mediawiki package and then marking
> them as skip if that package is not found.
> >
> > 2) Where to define the dependency. Currently all deps are listed in
> > requirements-common.txt which is used during regular installation. It
> > should not be there since it'll be optional. We could have a
> > requirements-optional.txt and put all optional deps there. But that
> > could grow to be a hodge-podge and only useful if someone wants
> > absolutely everything (e.g. during a test suite run). I think also the
> > importer script should give specific installation instruction if it is
> > attempted to be run.
> >
> This won't be the only time we run in to this ( we have reps now that are
> GPL) and I think having a requirements-optional.txt is a fine way to deal
> with it. I think it will let us prune down our current requirements some as
> well, which is good. I'd rather have a core set of requirements and have
> the hodge-podge exist in a file named optional.
>
> Wayne

Re: handling optional GPL dependencies

Posted by Wayne Witzel III <ww...@gmail.com>.
On Friday, August 3, 2012 at 1:36 PM, Dave Brondsema wrote:
> 
> 1) How to run the importer tests. I'm thinking they should
> automatically skip if the mediawiki package is not present. An
> alternative would be to move them to some location so that they are not
> run by default, and would have to be manually run.

I like the idea of checking for the mediawiki package and then marking them as skip if that package is not found. 
> 
> 2) Where to define the dependency. Currently all deps are listed in
> requirements-common.txt which is used during regular installation. It
> should not be there since it'll be optional. We could have a
> requirements-optional.txt and put all optional deps there. But that
> could grow to be a hodge-podge and only useful if someone wants
> absolutely everything (e.g. during a test suite run). I think also the
> importer script should give specific installation instruction if it is
> attempted to be run.
> 
This won't be the only time we run in to this ( we have reps now that are GPL) and I think having a requirements-optional.txt is a fine way to deal with it. I think it will let us prune down our current requirements some as well, which is good. I'd rather have a core set of requirements and have the hodge-podge exist in a file named optional. 

Wayne

Re: handling optional GPL dependencies

Posted by Dave Brondsema <da...@brondsema.net>.
On 8/15/12 11:48 AM, Greg Stein wrote:
> On Wed, Aug 15, 2012 at 11:14 AM, Dave Brondsema <da...@brondsema.net> wrote:
>> ...
>> PySVN can be very difficult to build, so that should be optional for
>> sure during installation.
> 
> I would assume that PySVN would be pre-installed on the system (via
> some package, or PyPI). Why would this one need to be built?

PySVN isn't a typical python package, so it can't be installed from
PyPI.  On Ubuntu (what our README assumes you'll use) installing a
system package does work, but then you can't get it into the python
virtualenv like other normal python packages.  I'm not sure exactly how
it would work out for other platforms (I'm sure it's possible) but my
understanding is that there will always be extra hoops to jump through
for pysvn.

> 
>> Going with #2 and keeping git as a default part of Allura installation
>> (but removable) is fine with me.  IIRC, it's not too hard to install the
>> git libraries, and git is a pretty popular SCM.  And all libraries
>> needed for ForgeGit to work are BSD licensed (gitdb, gitpython, async,
>> smmap)
> 
> Similar for the Git-related packages.

Yes, all the git python packages can be installed normally from pypi,
using the normal process for all our dependencies (pip install -r
requirements.txt)


-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: handling optional GPL dependencies

Posted by Greg Stein <gs...@gmail.com>.
On Wed, Aug 15, 2012 at 11:14 AM, Dave Brondsema <da...@brondsema.net> wrote:
>...
> PySVN can be very difficult to build, so that should be optional for
> sure during installation.

I would assume that PySVN would be pre-installed on the system (via
some package, or PyPI). Why would this one need to be built?

> Going with #2 and keeping git as a default part of Allura installation
> (but removable) is fine with me.  IIRC, it's not too hard to install the
> git libraries, and git is a pretty popular SCM.  And all libraries
> needed for ForgeGit to work are BSD licensed (gitdb, gitpython, async,
> smmap)

Similar for the Git-related packages.

Cheers,
-g

Re: handling optional GPL dependencies

Posted by Dave Brondsema <da...@brondsema.net>.
On 8/12/12 1:19 PM, Peter Hartmann wrote:
> On11.08.2012 03:33, Greg Stein wrote:
>> IMO, perform as little core re-engineering as possible, and move rapidly
>> towards a release. So, strip Hg rather than rebuild.
>>
>> Second, as a consumer of this project, having *no* SCM is simply
>> ridiculous
>> and a non-starter. I cannot imagine any possible installation or use-case
>> without SCM. My view is that you start with SCM, and build on top of that
>> with something like Allura.
> I see what you mean. As I understand from ticket #3883, there were plans
> to make Hg (Mercurial) default SCM in Allura. But since dev team
> realized it's GPL'd, Hg will be moved to separate package and possibly
> even out of Allura's source tree. So now we have two options:
> 1) make SCM support non-default so that Allura will be less opinionated, or
> 2) choose default SCM from the other ones left (Git or Subversion).
> 
> Note that even with 2), with the work i'm doing, SCM support can still
> be optional, i.e. user would be able to remove it from default
> installation. This is relevant to me because if 1) is chosen - which
> Dave seems to favor - things like Git repos in default installation will
> have to be pruned. I imagine this would be troublesome for new users,
> who clearly expect code hosting to be available by default, even though
> there certainly are use cases that don't require it.
> 

PySVN can be very difficult to build, so that should be optional for
sure during installation.

Going with #2 and keeping git as a default part of Allura installation
(but removable) is fine with me.  IIRC, it's not too hard to install the
git libraries, and git is a pretty popular SCM.  And all libraries
needed for ForgeGit to work are BSD licensed (gitdb, gitpython, async,
smmap)


-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: handling optional GPL dependencies

Posted by Peter Hartmann <ma...@gmail.com>.
On11.08.2012 03:33, Greg Stein wrote:
> IMO, perform as little core re-engineering as possible, and move rapidly
> towards a release. So, strip Hg rather than rebuild.
>
> Second, as a consumer of this project, having *no* SCM is simply ridiculous
> and a non-starter. I cannot imagine any possible installation or use-case
> without SCM. My view is that you start with SCM, and build on top of that
> with something like Allura.
I see what you mean. As I understand from ticket #3883, there were plans 
to make Hg (Mercurial) default SCM in Allura. But since dev team 
realized it's GPL'd, Hg will be moved to separate package and possibly 
even out of Allura's source tree. So now we have two options:
1) make SCM support non-default so that Allura will be less opinionated, or
2) choose default SCM from the other ones left (Git or Subversion).

Note that even with 2), with the work i'm doing, SCM support can still 
be optional, i.e. user would be able to remove it from default 
installation. This is relevant to me because if 1) is chosen - which 
Dave seems to favor - things like Git repos in default installation will 
have to be pruned. I imagine this would be troublesome for new users, 
who clearly expect code hosting to be available by default, even though 
there certainly are use cases that don't require it.

Re: handling optional GPL dependencies

Posted by Greg Stein <gs...@gmail.com>.
IMO, perform as little core re-engineering as possible, and move rapidly
towards a release. So, strip Hg rather than rebuild.

Second, as a consumer of this project, having *no* SCM is simply ridiculous
and a non-starter. I cannot imagine any possible installation or use-case
without SCM. My view is that you start with SCM, and build on top of that
with something like Allura.

Cheers,
-g
On Aug 10, 2012 4:44 PM, "Peter Hartmann" <ma...@gmail.com> wrote:

> W dniu 07.08.2012 03:22, Dave Brondsema pisze:
>
>  Yep. Each "tool" is a separate pluggable discoverable python package. We
>> could just bring it back into the main repo then. (The work Peter's doing
>> on #3883 is to remove some unnecessary coupling between the core package
>> and the scm tools - tests mostly iirc)
>>
>
> As I mentioned on IRC, coupling proved to be more tight than tests and
> I've started looking into separating SCM support altogether. Which brings
> up the question: how much separated do we want it to be? For example,
> should Allura's vanilla install not mention any SCM at all, or should it
> point that "SCM support is available once you install a Tool of your
> choosing", or something else?
>
> In my opinion, it would be more pragmatic to leave any notion of SCM to
> individual Tools, so that Allura's core becomes less "opinionated" about
> the choice of tools to use. But that would of course be much harder (if
> possible at all) and perhaps require api changes :) But then again, perhaps
> it's better to do it now, when most (all?) of publicly available tools are
> maintained in Allura's repo source tree and can be adjusted at will.
>
> Hence i'm asking for input here.
>

Re: handling optional GPL dependencies

Posted by Peter Hartmann <ma...@gmail.com>.
W dniu 07.08.2012 03:22, Dave Brondsema pisze:

> Yep. Each "tool" is a separate pluggable discoverable python package. 
> We could just bring it back into the main repo then. (The work Peter's 
> doing on #3883 is to remove some unnecessary coupling between the core 
> package and the scm tools - tests mostly iirc) 

As I mentioned on IRC, coupling proved to be more tight than tests and 
I've started looking into separating SCM support altogether. Which 
brings up the question: how much separated do we want it to be? For 
example, should Allura's vanilla install not mention any SCM at all, or 
should it point that "SCM support is available once you install a Tool 
of your choosing", or something else?

In my opinion, it would be more pragmatic to leave any notion of SCM to 
individual Tools, so that Allura's core becomes less "opinionated" about 
the choice of tools to use. But that would of course be much harder (if 
possible at all) and perhaps require api changes :) But then again, 
perhaps it's better to do it now, when most (all?) of publicly available 
tools are maintained in Allura's repo source tree and can be adjusted at 
will.

Hence i'm asking for input here.

Re: handling optional GPL dependencies

Posted by Dave Brondsema <da...@brondsema.net>.
On Aug 6, 2012, at 6:26 PM, Greg Stein <gs...@gmail.com> wrote:

> On Mon, Aug 6, 2012 at 6:07 PM, Dave Brondsema <da...@brondsema.net> wrote:
>> On 8/6/12 5:57 PM, Peter Hartmann wrote:
>> ...
>>> I just did some work on the issue mentioned above (ticket #3883). Patch
>>> needs testing, which I will probably do tomorrow. However, my ultimate
>>> goal is to help Allura's making pypi release as soon as possible, to
>>> ease overall deployment and thus make futher development easier. With
>>> this in mind, if Hg begs for the same treatment as Git and SVN, I would
>>> need to see to it next. I guess final decision on how to handle this
>>> requires futher input from other devs as well?
> 
> Seems that svn and git support should come built-in, since that fits
> within our licensing regime.
> 
> And yeah: if Hg support can be a "plugin" that users can install into
> an Allura installation, then spinning that to another project (on SF,
> I presume) would make sense.
> 
>> Great to hear :)
>> 
>> It seems pretty clear to me that the ForgeHg package needs the same
>> treatment (making the core Allura package not depend on it), and even
>> more so: to make it a separate GPL-licensed project/repo.  The only
>> other option I see is to write an Apache-licensed Mercurial library, but
>> that seems unrealistic IMO.
> 
> You never know what motivates people :-P ... entirely possible that
> it'll scratch somebody's itch. I'm assuming that it would be possible,
> and if/when somebody does it in the future, then we could support Hg
> out of the box. Right?

Yep.  Each "tool" is a separate pluggable discoverable python package. We could just bring it back into the main repo then. (The work Peter's doing on #3883 is to remove some unnecessary coupling between the core package and the scm tools - tests mostly iirc)

Re: handling optional GPL dependencies

Posted by Greg Stein <gs...@gmail.com>.
On Mon, Aug 6, 2012 at 6:07 PM, Dave Brondsema <da...@brondsema.net> wrote:
> On 8/6/12 5:57 PM, Peter Hartmann wrote:
>...
>> I just did some work on the issue mentioned above (ticket #3883). Patch
>> needs testing, which I will probably do tomorrow. However, my ultimate
>> goal is to help Allura's making pypi release as soon as possible, to
>> ease overall deployment and thus make futher development easier. With
>> this in mind, if Hg begs for the same treatment as Git and SVN, I would
>> need to see to it next. I guess final decision on how to handle this
>> requires futher input from other devs as well?

Seems that svn and git support should come built-in, since that fits
within our licensing regime.

And yeah: if Hg support can be a "plugin" that users can install into
an Allura installation, then spinning that to another project (on SF,
I presume) would make sense.

> Great to hear :)
>
> It seems pretty clear to me that the ForgeHg package needs the same
> treatment (making the core Allura package not depend on it), and even
> more so: to make it a separate GPL-licensed project/repo.  The only
> other option I see is to write an Apache-licensed Mercurial library, but
> that seems unrealistic IMO.

You never know what motivates people :-P ... entirely possible that
it'll scratch somebody's itch. I'm assuming that it would be possible,
and if/when somebody does it in the future, then we could support Hg
out of the box. Right?

Cheers,
-g

Re: handling optional GPL dependencies

Posted by Peter Hartmann <ma...@gmail.com>.
On 07.08.2012 00:07, Dave Brondsema wrote:
> If you give me your SourceForge username, I can add you as a developer 
> on the SF project so that you can assign #3883 to yourself. 
Thanks. I'm registered under username "peterhartmann".

Re: handling optional GPL dependencies

Posted by Dave Brondsema <da...@brondsema.net>.
On 8/6/12 5:57 PM, Peter Hartmann wrote:
> On 06.08.2012 23:27, Dave Brondsema wrote:
>> On 8/6/12 3:53 PM, Peter Hartmann wrote:
>>>
>>> How does this affect planned switch to hg as default SCM in Allura?
>>> Seems kinda contradicting to me:
>>> https://sourceforge.net/p/allura/tickets/3883/ .
>>>
>>> Also, it's my first post here, so hi everyone.
>>>
>> Hi :)
>>
>> I don't think it's necessarily contradictory.  We can make Hg, Git, and
>> SVN all optional tools.  Git & SVN would still be packaged with the rest
>> of Allura, but not necessary for the base platform (the "Allura"
>> package) and its tests to run.
>>
>> I'm sure there are many use-cases where people would want to deploy
>> Allura without any scm tool.
>>
>> The downside, is that the platform's SCM support (base models,
>> controllers and templates) would not have much test coverage on their
>> own.  They'd still be covered when a specific tool's (hg, git, svn)
>> tests run.  If that were to be a problem we could also add more tests in
>> the Allura package, maybe even a dummy scm implementation.
>>
>> -Dave
>>
> I just did some work on the issue mentioned above (ticket #3883). Patch
> needs testing, which I will probably do tomorrow. However, my ultimate
> goal is to help Allura's making pypi release as soon as possible, to
> ease overall deployment and thus make futher development easier. With
> this in mind, if Hg begs for the same treatment as Git and SVN, I would
> need to see to it next. I guess final decision on how to handle this
> requires futher input from other devs as well?
> 

Great to hear :)

It seems pretty clear to me that the ForgeHg package needs the same
treatment (making the core Allura package not depend on it), and even
more so: to make it a separate GPL-licensed project/repo.  The only
other option I see is to write an Apache-licensed Mercurial library, but
that seems unrealistic IMO.

If you give me your SourceForge username, I can add you as a developer
on the SF project so that you can assign #3883 to yourself.


-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: handling optional GPL dependencies

Posted by Peter Hartmann <ma...@gmail.com>.
On 06.08.2012 23:27, Dave Brondsema wrote:
> On 8/6/12 3:53 PM, Peter Hartmann wrote:
>>
>> How does this affect planned switch to hg as default SCM in Allura?
>> Seems kinda contradicting to me:
>> https://sourceforge.net/p/allura/tickets/3883/ .
>>
>> Also, it's my first post here, so hi everyone.
>>
> Hi :)
>
> I don't think it's necessarily contradictory.  We can make Hg, Git, and
> SVN all optional tools.  Git & SVN would still be packaged with the rest
> of Allura, but not necessary for the base platform (the "Allura"
> package) and its tests to run.
>
> I'm sure there are many use-cases where people would want to deploy
> Allura without any scm tool.
>
> The downside, is that the platform's SCM support (base models,
> controllers and templates) would not have much test coverage on their
> own.  They'd still be covered when a specific tool's (hg, git, svn)
> tests run.  If that were to be a problem we could also add more tests in
> the Allura package, maybe even a dummy scm implementation.
>
> -Dave
>
I just did some work on the issue mentioned above (ticket #3883). Patch 
needs testing, which I will probably do tomorrow. However, my ultimate 
goal is to help Allura's making pypi release as soon as possible, to 
ease overall deployment and thus make futher development easier. With 
this in mind, if Hg begs for the same treatment as Git and SVN, I would 
need to see to it next. I guess final decision on how to handle this 
requires futher input from other devs as well?

Re: handling optional GPL dependencies

Posted by Dave Brondsema <da...@brondsema.net>.
On 8/6/12 3:53 PM, Peter Hartmann wrote:
> On 03.08.2012 22:55, Dave Brondsema wrote:
>> On 8/3/12 4:41 PM, Rick Copeland wrote:
>>> As an FYI, ForgeHg is GPL as well due to its Mercurial dependency.
>>>
>> Well that's not fun :)  I didn't expect we'd have such a big GPL
>> dependency.  I don't think we'll want to find or write an alternate
>> Apache library to do the mercurial work, so we may have to split off
>> ForgeHg to somewhere else and not provide it as part of the core Allura.
> How does this affect planned switch to hg as default SCM in Allura?
> Seems kinda contradicting to me:
> https://sourceforge.net/p/allura/tickets/3883/ .
> 
> Also, it's my first post here, so hi everyone.
> 

Hi :)

I don't think it's necessarily contradictory.  We can make Hg, Git, and
SVN all optional tools.  Git & SVN would still be packaged with the rest
of Allura, but not necessary for the base platform (the "Allura"
package) and its tests to run.

I'm sure there are many use-cases where people would want to deploy
Allura without any scm tool.

The downside, is that the platform's SCM support (base models,
controllers and templates) would not have much test coverage on their
own.  They'd still be covered when a specific tool's (hg, git, svn)
tests run.  If that were to be a problem we could also add more tests in
the Allura package, maybe even a dummy scm implementation.

-Dave

-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: handling optional GPL dependencies

Posted by Peter Hartmann <ma...@gmail.com>.
On 03.08.2012 22:55, Dave Brondsema wrote:
> On 8/3/12 4:41 PM, Rick Copeland wrote:
>> As an FYI, ForgeHg is GPL as well due to its Mercurial dependency.
>>
> Well that's not fun :)  I didn't expect we'd have such a big GPL
> dependency.  I don't think we'll want to find or write an alternate
> Apache library to do the mercurial work, so we may have to split off
> ForgeHg to somewhere else and not provide it as part of the core Allura.
How does this affect planned switch to hg as default SCM in Allura? 
Seems kinda contradicting to me: 
https://sourceforge.net/p/allura/tickets/3883/ .

Also, it's my first post here, so hi everyone.

Re: handling optional GPL dependencies

Posted by Dave Brondsema <da...@brondsema.net>.
On 8/3/12 5:01 PM, Wayne Witzel III wrote:
> 
>> Well that's not fun :) I didn't expect we'd have such a big GPL
>> dependency. I don't think we'll want to find or write an alternate
>> Apache library to do the mercurial work, so we may have to split off
>> ForgeHg to somewhere else and not provide it as part of the core Allura.
>>
> That does kind of stink, but fortunately it is very easy in Allura to move that in to its own repo as a separate tool, put it on pypi and add a dependency for it in our requirements.txt. 
> 

Yep, although I think it'd have to be an optional dependency and not in
the default requirements.txt



-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: handling optional GPL dependencies

Posted by Wayne Witzel III <ww...@gmail.com>.
> Well that's not fun :) I didn't expect we'd have such a big GPL
> dependency. I don't think we'll want to find or write an alternate
> Apache library to do the mercurial work, so we may have to split off
> ForgeHg to somewhere else and not provide it as part of the core Allura.
> 
That does kind of stink, but fortunately it is very easy in Allura to move that in to its own repo as a separate tool, put it on pypi and add a dependency for it in our requirements.txt. 

Wayne


Re: handling optional GPL dependencies

Posted by Dave Brondsema <da...@brondsema.net>.
On 8/3/12 4:41 PM, Rick Copeland wrote:
> As an FYI, ForgeHg is GPL as well due to its Mercurial dependency.
> 

Well that's not fun :)  I didn't expect we'd have such a big GPL
dependency.  I don't think we'll want to find or write an alternate
Apache library to do the mercurial work, so we may have to split off
ForgeHg to somewhere else and not provide it as part of the core Allura.



-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: handling optional GPL dependencies

Posted by Rick Copeland <ri...@arborian.com>.
As an FYI, ForgeHg is GPL as well due to its Mercurial dependency.

On Fri, Aug 3, 2012 at 4:36 PM, Dave Brondsema <da...@brondsema.net> wrote:

> I'm trying to figure out the best way to handle an optional GPL
> dependency.  We may have other non-AL2 licensed deps that we can work
> through later, but my current task involves importing from mediawiki to
> Allura and the GPL lib from
> https://github.com/zikzakmedia/python-mediawiki seems like the best way
> to do it.  This isn't core functionality to Allura, so according to
> http://www.apache.org/legal/resolved.html#optional it should be ok for
> the importer code to depend on it.
>
> So, on to technical matters - how to make that work.   So far I'm
> ensuring that "import mediawiki" is in the importer code, so everything
> else functions without it installed.  Trickier bits are:
>
> 1) How to run the importer tests.  I'm thinking they should
> automatically skip if the mediawiki package is not present.  An
> alternative would be to move them to some location so that they are not
> run by default, and would have to be manually run.
>
> 2) Where to define the dependency.  Currently all deps are listed in
> requirements-common.txt which is used during regular installation.  It
> should not be there since it'll be optional.  We could have a
> requirements-optional.txt and put all optional deps there.  But that
> could grow to be a hodge-podge and only useful if someone wants
> absolutely everything (e.g. during a test suite run).  I think also the
> importer script should give specific installation instruction if it is
> attempted to be run.
>
> How does that sound?  I expect this won't be the only time we have to
> deal with it, so a pattern would be good to establish.
>
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>               <><
>