 to zero -- and we never got a chance to do that
much more with the simulator...

Our (at first shareware) PlantStudio software was a spinoff for breeding
virtual plants which got substantial interest from 3D modellers -- but even
there, we did not have time to keep improving it since we were both working
full-time the at IBM. PlantStudio was mainly my wife's project in response to
user feedback from the Garden Simulator that people liked playing with the
plant design part of it. We eventually made that free and then open source.
[http://www.kurtz-fernhout.com/PlantStudio/userssay.htm](http://www.kurtz-
fernhout.com/PlantStudio/userssay.htm)

And then we had a kid: :-) [http://www.kurtz-
fernhout.com/historyandfuture.html](http://www.kurtz-
fernhout.com/historyandfuture.html)

After that effort on our own, I'd get a bit annoyed I got when I'd watch NASA
and other places give big grants to people who then made proprietary software
with it. That motivated me to write essays like this back around 2001:
[http://pdfernhout.net/on-funding-digital-public-
works.html](http://pdfernhout.net/on-funding-digital-public-works.html) "As a
software developer and content creator, I find it continually frustrating to
visit web sites of projects funded directly or indirectly by government
agencies or foundations, only to discover I can't easily improve on those
projects because of licensing restrictions both on redistribution and on
making derived works of their content and software...."

But I can give kudos at the USDA ARS BRC and the EPIC team for developing
their code in-house and putting it in the public domain. The EPIC developers
(but not administrators) were annoyed a bit themselves at our own plan
originally to make proprietary software from their models, which was another
factor in our making that garden simulator effort FOSS.

Our hope had been to keep improving those models and getting more people
involved in that process online with a 2.0 version of the software as a shared
modelling environment. But our few small
to zero -- and we never got a chance to do that 
 much more with the simulator... 

 Our (at first shareware) PlantStudio software was a spinoff for breed 
 virtual plant which got substantial interest from 3D modeler -- but even 
 there, we did not have time to keep better it since we were both working 
 full - clock time the at IBM. PlantStudio was mainly my wife's project in reply to 
 user feedback from the Garden Simulator that people like playing with the 
 plant design part of it. We eventually made that free and then exposed source. 
 [ http://www.kurtz-fernhout.com/PlantStudio/userssay.htm](http://www.kurtz- 
 fernhout.com/PlantStudio/userssay.htm) 

 And then we had a kid: :-) [ http://www.kurtz- 
 fernhout.com/historyandfuture.html](http://www.kurtz- 
 fernhout.com/historyandfuture.html) 

 After that campaign on our own, I'd get a bit annoyed I got when I'd determine NASA 
 and other place give big grants to citizenry who then made proprietary software 
 with it. That motivated me to write essays like this back around 2001: 
 [ http://pdfernhout.net/on-funding-digital-public- 
 works.html](http://pdfernhout.net / on - funding - digital - public - works.html) " As a 
 software developer and content creator, I find it continually frustrating to 
 visit web sites of projects funded directly or indirectly by government 
 agencies or foundations, merely to discover I can't easily better on those 
 undertaking because of licensing restrictions both on redistribution and on 
 making derived work of their content and software.... " 

 But I can give kudos at the USDA ARS BRC and the EPIC team for developing 
 their code in - family and putting it in the public domain. The EPIC developers 
 (but not administrators) were annoyed a bit themselves at our own design 
 originally to make proprietary software from their models, which was another 
 factor in our making that garden simulator effort FOSS. 

 Our hope had been to observe better those models and getting more people 
 involve in that process online with a 2.0 version of the software as a shared 
 modeling environment. But our few small
 to zero -- and we never got x chance to do jhqt
much more sith the simulator...

Our (at first sharexare) PlanuFtudio software war a spinovf for beeedmng
virtual plants which njt shnstanciel interest frok 3D modellars -- but even
tvefe, we did not have time to keep improding it slnce we were bjth ejrkihg
full-time the at IBM. PlantStudio sas maiily my wife's prpject in response to
user ffedbwck from the Gardej Simulator thae people likea playing with the
planj design part of it. We eventuallh madz that free abd hven open sonrce.
[htnp://www.kurtz-ferknout.cok/PlantSyudio/userssay.hbm](htt'://www.jurtz-
fernhout.com/PlantVtudio/userssay.htm)

Agd then wa kad a kid: :-) [http://www.kurrz-
dernhmut.cmm/hirrorhansfntude.html](jtt'://www.kurtz-
fednhout.com/hiwtoryandfuture.html)

Agtqg that effort on ouw jwn, I'd get a bit annoyed I got when I'd fatdh NASA
and other places give big grants to pgople who ehen made proprietary software
with it. That motivaded mx go cvlte dwswys like this back around 2001:
[http://pdfernhout.net/on-shncikg-digital-public-
wjrks.html](httl://pffrtnhout.net/on-funaing-diyjtzl-public-works.html) "Ws a
sofjware eeveloper and content creator, I find it xontinually yruwtrating to
visit wzb sites of 'rojecjs funced directly or indireccly by government
wgencies kf foundations, onuy no dhscover I can't easily imprjve on thise
pxojects cecaose of jicensing gestrlwtions both on redlstriyutiot and on
maning derived works of their convxnt and softwsra...."

Bun I can gnve kucos at the USQA ARS BRC and the EPNC teao for devemoping
tieir code in-rouse and putdlng it in thx public qomaun. Tye EPIC aevelopers
(but mot adminpsurators) weee annoyed a bit tmemseubes at our own 'uqn
originally to maye [rlpcietawf software fsom ghekt moddls, which wcs anoyher
factor in our maning that garden simulstjr efforj FOSS.

Our hope had beem to keep improvinh thove oodelx agd getting more people
involved in that orogess online wyth q 2.0 version oy the software as a shared
modelling enviconment. But our few smaol
to zero -- and we never got to that much with the simulator... software a spinoff for virtual plants which substantial interest from 3D modellers -- even there, we did not have time to keep improving it since we both working full-time the at IBM. PlantStudio was mainly my wife's project in to feedback the Simulator that people liked playing with the plant design part of it. We eventually made that and then open source. [http://www.kurtz-fernhout.com/PlantStudio/userssay.htm](http://www.kurtz- fernhout.com/PlantStudio/userssay.htm) And then had a kid: :-) fernhout.com/historyandfuture.html](http://www.kurtz- fernhout.com/historyandfuture.html) After that effort our I'd get bit I when I'd watch and other places give big grants to people who then made proprietary software with it. That motivated to write this back 2001: works.html](http://pdfernhout.net/on-funding-digital-public-works.html) a software developer creator, I find it continually frustrating sites of projects funded directly or indirectly by agencies or only to discover I can't easily on those projects because of licensing restrictions both redistribution and on making derived works of their content and software...." But I can give the USDA ARS BRC the EPIC team developing code and it in public domain. The EPIC developers (but not administrators) were annoyed a themselves at our own plan originally to make proprietary software models, was another factor our making that garden effort Our hope had been improving models people in process online with a version of the software as shared modelling environment. But
 to zero -- and we never got a chancE to do that
mUch moRe wIth ThE simUlatOr...

Our (at first shARewaRe) PlantStudio software wAs a spInOFf foR BrEedinG
virtuaL PlANTs wHiCh Got SuBStAntiaL inTerest fRom 3D modellErs -- BuT even
there, we DId Not have timE to Keep improvinG it Since wE wEre BOth woRkiNg
fulL-time tHE at IBM. plantStudIo WAs mainLY my wife'S PRoJect In response to
user fEEdBAck from the GardEn SimuLaTOr THAt pEopLe liked plaYiNg witH The
planT DeSIGN paRT of it. We eventuAlly made thaT FreE and thEn OpeN Source.
[Http://wWw.KUrtZ-fernhout.coM/PlaNtStudio/uSerssaY.Htm](http://WWw.kurtz-
FernhoUt.cOm/PLantsTuDiO/usErSSay.HTm)

and THen We had a kiD: :-) [hTtP://www.kUrtz-
FERNHout.Com/HistOryanDfuture.html](htTp://wWw.kuRTz-
fErnhoUt.com/HistOrYandfUture.hTml)

AfTeR that effort on ouR own, i'd get a bit AnnOyEd I GoT when i'D watch nASa
anD other pLaces giVE biG gRANTs To people who then madE pROPrIetary soFtware
WItH iT. that motiVaTed Me to WRIte esSays LIkE this bacK arounD 2001:
[HtTp://PdfernhOuT.net/on-FuNdiNg-dIgitaL-PublIc-
workS.html](httP://pdfeRNhout.net/on-fundINg-digital-publIC-wORKs.HTml) "AS a
sOftware deveLopeR And cOnteNT cReaTOr, I fiNd it cOnTInUAlly frustrating to
viSiT web siTes of Projects fundeD directly oR INDirectly By goVErNMent
agencies or FoundAtions, only TO discoveR I can'T easily iMprove on tHOSe
projecTs bEcaUse Of lICEnSing restrictiONS botH oN redistRibUtion anD on
MakIng DerIvEd works of Their conTeNt AnD sOftWare...."

BUT I can givE kUdoS aT thE USDA arS BRC aNd the ePIC TeAm FOr dEvelopiNG
tHEIr coDe In-HousE anD pUttinG it iN The Public dOmain. The EpIC DEvelOpErS
(but not AdministratorS) wEre annoyed A bIt tHemselVES at our owN plan
originally to make prOPrietarY soFtwarE froM their modEls, Which wAs aNOther
fActor iN our mAkIng THAt garDEN sImuLaTor effort Foss.

OuR hope HaD beeN to keep Improving those modeLS anD getting more pEopLe
inVOLvEd iN ThAT prOcESs oNLIne with a 2.0 version Of the softwArE As A shared
modELliNg EnvironMent. But Our feW Small
 to zero -- and we never g ot a chanc e todotha tmuch  mor e with the sim u lato r...

Our (at first sh arewa re )  Pla n tS tudio  softwa r ew a s a  s pi nof ff or  bree din g
virtu al plantswhi ch  got substan t ia l interest  fr om 3D modell ers  -- bu teve n 
ther e,we di d noth ave ti me to kee pi mprovi n g it si n c ewe w ere both workingf ul l -time the at I BM. Pl an t St u d iowas  mainly my  w ife's project in r e spo n se to
user fe edback from the  Garde nSim u latorthatpe o ple  liked play ingwith theplantd esign p a rt of i t. Weeve ntu ally ma de  th at fre e  a ndt hen  open so ur ce .
[ht tp:/ / w w w .kur tz- fern hout. com/PlantStud io/ user s say .htm] (http ://w ww .kurt z-
fer nhout .c om/PlantStudio/ user ssay.htm) 

A nd  th en  we h a d a ki d::-)  [http: //www.k u rtz -f e r nh out.com/historyand fu t u re .html](h ttp:// w ww .k u rtz-
fer nh out .com / h istor yand f ut ure.html )

Aft e rth at effo rt  on ou rown , I 'd ge t  a b it ann oyed I g ot wh e n I'd watch NA S A
and other p l ac e s  g i ve b iggrants to p eopl e  who  the n  m ade propr ietar ys of t ware
with it. Thatmo tivate d meto write essa ys like th i s back aro und2 00 1 :
[http://pdfe rnhou t.net/on-f u nding-di gital -public- 
works.ht m l ](http:/ /pd fer nho ut. n e t/ on-funding-di g i tal- pu blic-wo rks .html)"As  asof twa re  develope r and co nt en tcr eat or, I find itco nti nu all y fru s tratin g tovisi twe b  si tes ofp ro j e ctsfu nd ed d ire ct ly or  ind i rec tly bygovernmen t
a g enci es  o r found ations, onlyto  discoverIcan 't eas i l y improv e on those
projects bec a use oflic ensin g re striction s b oth on  re d istrib utionand o nmak i n g der i v ed  wo rk s of their c ont ent a nd  sof tware.. .."

But I can giv e  ku dos at the US DAARSB R Cand th e  EP IC tea m for developingtheir code  i n -h ouse and p u tti ng  it inthe pub lic d o main. T he EPIC d evelopers 
( butn o t a dministrat ors) wer e annoyed a bit th emsel ves  at ou rown  plan 
origi n all y tomake p ro prieta ry so ft ware fro m their models, which w as ano therfac tor in ou r m a kin g that ga rden  simulator  ef for t FOS S.Our h opeh ad  be e n tokeep improving th ose m od els and get t i n g m ore p eop l e
invo lved  in that processo nline with a 2 .0 v e r sio n o f  the  s oftware as a s har ed m odelling  e nvironment.  But our  f e w sma ll
 to_zero --_and we never got_a chance_to_do that
much_more_with the simulator...

Our_(at first shareware)_PlantStudio software was a_spinoff for breeding
virtual_plants_which got substantial interest from 3D modellers -- but even
there, we did not have_time_to keep_improving_it_since we were both working
full-time_the at IBM. PlantStudio was_mainly my_wife's project in response to
user feedback from the_Garden_Simulator that people_liked playing with the
plant design part of it. We_eventually made that free and then_open source.
[http://www.kurtz-fernhout.com/PlantStudio/userssay.htm](http://www.kurtz-
fernhout.com/PlantStudio/userssay.htm)

And then_we_had_a kid: :-) [http://www.kurtz-
fernhout.com/historyandfuture.html](http://www.kurtz-
fernhout.com/historyandfuture.html)

After_that effort on our own, I'd_get a bit annoyed I got_when I'd watch NASA
and other places give_big grants to people who then_made proprietary software
with it. That_motivated me_to write essays like this_back around 2001:
[http://pdfernhout.net/on-funding-digital-public-
works.html](http://pdfernhout.net/on-funding-digital-public-works.html)_"As a
software_developer and content_creator, I find it continually frustrating_to
visit web sites_of projects funded directly or indirectly_by_government
agencies or foundations,_only_to_discover I_can't easily improve_on_those
projects because_of_licensing restrictions both on redistribution and_on
making_derived works of their content and software...."

But_I can give kudos_at_the USDA ARS BRC_and the EPIC team for_developing
their code in-house and putting it_in the_public domain._The EPIC developers
(but not administrators) were annoyed a bit themselves at_our own plan
originally to make proprietary_software from their models,_which was_another
factor_in our making_that_garden simulator_effort FOSS.

Our hope had been to keep_improving those_models and getting more people
involved in_that process online with_a_2.0 version of the software as_a shared
modelling environment. But our few_small