>From another outside developer ;) <br><br><div class="gmail_quote">On Wed, Oct 14, 2009 at 10:32 AM, Doug Williams <span dir="ltr"><<a href="mailto:m.douglas.williams@gmail.com">m.douglas.williams@gmail.com</a>></span> wrote: <br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div></div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Fourth, Is there a formal roadmap for the Planet libraries - a sort of wishlist from the core development group<br>
or user community vote/consensus. Similarly, is there an up to date raodmap for the core PLT system?<br>
<br></blockquote></div></div></blockquote><div>I personally consider anything (not necessarily everything though) in perl's CPAN is a fair game to add to planet. CPAN is a good bar to measure against and can act as a roadmap, at least for people into using PLT for everyday purposes. <br>
<br><div class="gmail_quote">On Wed, Oct 14, 2009 at 6:54 AM, Scott McLoughlin <span dir="ltr"><<a href="mailto:scott@adrenaline.com">scott@adrenaline.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I have never been a "high ceremony" guy, but I can imagine partitioning<br>
subsystems and assigning responsibility outside of the core group: Documentation,<br>
Kernel/Compiler/GC/RTS documentation, SRFI maintenance, typed-scheme / scheme<br>
integration, porting, core language evolution (immutable cons cells, lazy expressions<br>
or whatever) and so forth and so on. Here we can maintain and publish a simple<br>
"Core PLT scheme language roadmap."<br></blockquote></div></div><div><br>I do feel like that finding a way to have user-contributed documentations would be helpful to have others quickly provide incremental improvements, especially for smaller things like typos. Scribble isn't designed for that right now, and we might need a wiki. <br>
<br>That being said - I agree with Noel that the core group needs to focus their energy on tasks that produces the highest value and that isn't to document everything in their heads. To have such documentations someone will need to pickup the mantle to get the knowledge out, just like to have a particular non-existent planet lib someone needs to suck it up and write it. In this sense it isn't so different from other open source projects. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
To boil all this down to a general scheme community question, PLT has become *very* popular in the<br>
scheme community (programmer community, to a lesser degree) at large. How stable a platform does<br>
it present for a future canonical open source project should the academic group behind PLT abandon<br>
the platform for one reason or another (lack of funding, changing research focus, etc.)<br>
<br></blockquote></div><div><br>Several of us non-academics (although I am an ex-academic) have enough faith in the core group and the product use PLT Scheme in our work.<br><br></div></div></blockquote><div><br>I feel like the current system is mature enough that it can stay stale for a few years and I can still be productive using it, YMMV of course. <br>
<br></div></div>