Congratulations Columbus!
]]>Ingy update:
I'm a bit behind on finishing YAML::Perl. This is due mostly to a focus on TestML. So far I have the spec: http://ingydotnet.github.com/testml/spec/ and a Perl 5 implementation: http://github.com/ingydotnet/testml-pm/
These are undergoing last minute changes.
The reason I'm doing this and telling you about it, is that I am using TestML to write all the PyYAML tests and run them against Perl and Python implementations. In that way we we have more guaranteed accuracy.
I have TestML ready to standardize all the PyYaml tests in a language independent way. This has been a little bit a a tangent to the TPF project, but I think it is the right approach. It ensures that Python and Perl (and others) are passing the exact same tests.
Alan has no progress to report at this time.
No update from Michael.
No update from Vadim.
No update from Vadim.
KD has not resumed work yet, but should soon.
No updates from Sebastian for some weeks.
On hiatus due to school work. Hopefully back up and running in the Summer.
Eric update:
I decided to scrap the combust setup and redo the site layout without being constrained by the existing template. I solicited some feedback on the design, and got some (though I would really prefer that somebody just hand me a CSS.)
Ultimately, I can't say whether the final site will look like that or be wedged back into the original templates or what. I'm trying to focus on the content and just want to come up with something reasonably approachable for navigation and layout.
I haven't been able to do any new content in May, but should have a few more articles done in June.
As always - you can get the latest progress on the GitHub project http://github.com/masak/web and their blog posts:
Ricardo did a decent amount of work so far, and has blogged about it: check it out!
]]>Rejected proposals:
Funded proposal:
]]>We thank Jonathan for his grant application and we look forward to its success. Jonathan will keep the Perl community informed of his progress on this grant work through the Rakudo.org blog and in his own use.perl.org journal.
Thank you to everyone who participated in the call for feedback regarding this grant application. Your feedback is essential in the decision process regarding Hague grants.
]]>The new version of this proposal is available here. It has been revised considerably based on community comment and discussion within TPF. Highlights of the changes between the original version and the current one are:
The TPF board of directors will have a new meeting shortly that will discuss this new version of the proposal and most likely include a vote on whether to accept. Additionally, though it is not commented upon in the attached POD the arrangement with the board would include my stepping down from the presidency (and the associated board seat) for the duration of the grant.
Thanks to everyone who participated in this process. Your feedback has been very valuable.
]]>When making your proposal, in addition to venue information and possible dates, please make sure to include details on airport locations, local public transit (as well as transit to the venue from the airport!), local cultural attractions, and accommodation information. The more information you provide, within reason, the better. Also, please include contact information for the members of your team.
With a June 10 deadline, you don't have much time to get your bid completed and submitted to the Conferences Committee. Don't wait, get started now!
Hosting YAPC is a rewarding experience and provides a great opportunity to give back to the Perl community. Good luck and we look forward to receiving your bid!
Send any questions and completed bids to the TPF conferences group: tpf-conferences (at) perl (dot) org
]]>What we don't know is the best way to accomplish these goals and have a polished presence at OSCON.
This year, we'd like to solicit the Perl community for their ideas. What do you want The Perl Foundation booth to communicate at OSCON and how do you suggest us doing it? Please leave your commentary here or feel free to email pr at perlfoundation dot org.
]]>Please comment on each grant proposal post:
* Perl 6 Pages
* Pod Mangling Utility Improvements
* Project nival
* Project ruddy
Igor Sanchez-Puls and
Rene Sanchez-Puls.
Front end 1000
Back end 1000
Total = 2000
The name ruddy comes from a kind of dove.
Ruddy is intended to be version 0 (actually exists a prealpha version) of a nntp/rss reader an a web based email system.
]]> Benefits to the Perl Community
It will be an extensible web mail system written with perl and jquery, allowing to build mail based sites in an easy way.
It won't require any experience on perl or jquery or css to build the sites.
It will be delivered a front end with a page for entering the data and the page that shows that data.
There will be perl code jquery code and html code mainly plus the manuals.
A more detailed description.
This version will serve to build email systems, something similar to project nival.
All the documents and code will be the Parrot Foundation copyright and will have The Artistic licence 2.0
The first month it will have a "user" page that shows the content to the user.
The second and third month a template for allowing for the user to change positions of diferente elemens and the color of the page an type of letter.
The third and fourth month will be used for trying to make the application as user friendly as posible and for making the programmer and user guides.
The project will take 4 months
I can begin work one week after I am advised
I am a perl programmer and graphic programmer and I've been a parrot cage cleaner for about 8 months.
]]>
Igor Sanchez-Puls and
Rene Sanchez-Puls.
Front end 1000
Back end 1000
Total = 2000
The name nival comes from a kind of owl.
Nival is intended to be version 0 of a Content Management System (CMS)
]]>
It will be an extensible CMS written with perl and jquery, allowing to build sites in an easy way.
It won't require any experience on perl or jquery or css to build the sites.
It will be delivered a beta version with a front end with an "administrator" page for entering the data and a "user" page that shows that data. A back end with a sqlite database integrated There will be perl code jquery code and css code mainly
A programmers manual and a users manual.
A more detailed description.
This version 0 will serve for documenting projects, with functionality similar to perldoc having the option of making static text web site for production environments.
Is intended that in subsecuent versions nival evolve to be as powerful as "trac" and as user friendly as "joomla".
All the documents and code will be the Parrot Foundation copyright and will have The Artistic licence 2.0
The first month it will have a "user" page that shows the content to the user and the administrator page for entering data.
The second month the back end (perl module with sqlite database) will be added.
The third month a template for allowing for the user to change color of the page an type of letter.
The third and fourth month will be used for trying to make the application as user friendly as posible and for making the programmer and user guides.
The project will take 4 months I can begin work one week after I am advised
I am a perl programmer and graphic programmer and I've been a parrot cage cleaner for about 8 months.
]]>
Ricardo Signes
[hidden email]
$2000
This grant is for the completion of design and implementation of basic versions of three pieces of software currently under development:
All three modules exist and have been in use by a number of people for some time. The main thrust of the grant is to improve the usability and reliability of Pod::Weaver. Pod::Weaver is one of the key components of Dist::Zilla. D::Z was presented to good response at the Pittsburgh Perl Workshop in 2008.
]]>
Pod::Elemental and Pod::Weaver provide very powerful tools for POD manipulation. They're designed to be easy to understand and extend, and should make it much easier to write POD-reading and POD-munging tools.
The flagship example of such a tool, right now, is Dist::Zilla's Pod::Weaver
plugin. When writing a distribution that is will be munged by Pod::Weaver, the
author needn't write any POD save for that which actually documents his code.
This means no writing (or updating) of the LICENSE section, the NAME, the
VERSION, or the COPYRIGHT. Sections like METHODS or FUNCTIONS are built
automatically from =method commands. If the author decides he'd like to
radically change how he lays out his POD, this can be done by reconfiguring the
weaver, since the documentation itself doesn't have to change. The next time
the dist is built, everything is new.
This is summarized in this SlideShare presentation:
http://www.slideshare.net/rjbs/distzilla-presentation/
I've been told by several people that "without Dist::Zilla, I would not have released [my distribution] to the CPAN." Dist::Zilla makes it much easier to release code, because it removes a lot of the boring overhead of building a dist.
While my goal for this grant is to advance the state of Dist::Zilla, Pod::Weaver has always been meant for operation as a standalone library. It will be useful for anyone who wants to do work rewriting or maintaining POD documents, as will Pod::Elemental, which provides a much simpler interface to POD documents than Pod::Simple (at the cost of some specific features).
Pod::Elemental::Nester and Pod::Elemental::Document will be completed, documented, and tested.
Pod::Weaver will be updated to munge Pod::Elemental::Documents instead of queues of Pod::Elemental::Elements. It will be able to rewrite documents without clobbering order. It will be documented and support external configuration.
Dist::Zilla will integrate the new Pod::Weaver configuration to allow Dist::Zilla::Plugin::PodWeaver to provide all the power of Pod::Weaver.
Pod::Elemental is a library for handling POD documents (like this grant application) as trees of elements. This is not an entirely straightforward operation, as POD is primarily event-based and most of its notions of containers or trees are assumed or implicit, rather than well defined.
Pod::Elemental is built atop Pod::Eventual, which handles reading the POD events. Pod::Elemental already exists and is in use, but requires work to correct design problems in the Nester and Document components, which convert event streams to nested trees in two distinct ways.
Pod::Weaver is a framework for rewriting POD trees. For example, it can be
configured to find all =method trees and collect and rewrite them into
=head2 events under a =head1 METHOD heading. Weavers make it very easy
to turn a document that contains only a few, nonstandard events into a
perfectly normal looking POD document, fleshed out with all the boilerplate the
most translators (and readers) would expect.
In addition to being blocked by Pod::Elemental's design needs, Pod::Weaver needs a few of its planned Weaver plugins implemented before it can be safely used on many POD trees. Among these, it needs plugins that focus on leaving unknown content in place relative to rewritten content.
Both of the above libraries were written to support Dist::Zilla, a distribution
construction kit that replaces not h2xs and Module::Starter, but rather
make dist. Among other things, it can be configured to add boilerplate POD
and translate minimal custom POD into verbose standard POD.
The Pod::Weaver plugin for Dist::Zilla will need some minor tweaks to take advantage of the configurability of the new Pod::Weaver code to be written.
These are more obnoxious than they sound, as they will require, at least, rewriting all the existing Weavers to not assume they work linearly.
This can hopefully be cribbed from Dist::Zilla's config code.
This is to allow things like Pod::WikiDoc to apply to portions of a POD document before weaving occurs.
I predict the project will take between four and eight weekends of hard work, plus some random work here and there when I have to dump ideas that strike me in the shower. This may go up or down, based on luck, setbacks, or moments of Satori, but I find it hard to imagine reaching a point where I would abandon or massively delay this work.
I write Perl code to pay my bills, and that's what I've been doing for almost ten years now. I have released a lot of code to the CPAN, and I've taken over maintenance of almost as much. Well over 2,000 distributions that I didn't write declare dependencies on my code, either directly or indirectly.
I wrote Dist::Zilla and Pod::Weaver because of the number of CPAN distributions (and contained POD documents) that I maintain, and have worked to make it possible for the lessons that I've learned to benefit those who haven't yet gotten to painful levels of code maintenance, so that the CPAN can continue to be the easiest way to reliably distribute open source code.
]]>
(working title can be changed)
Herbert Breunung
[hidden email]
600$ -> €
comprehensive lexicon-like tutorial
]]>
It will become easy to learn Perl6, because this way people can easily grab the bits they want to learn now about Perl 6. Once ready it may become also a communication channel with people not so involved into perl 6 (p6l readers).
8-10 larger Pages in the TPF perl 6 Wiki. See german Version for comparsion, that is more than half ready. (http://wiki.perl-community.de/bin/view/Wissensbasis/PerlTafel)
Synopses are large not always easy to read. what we need is an indexed and crosslinked set of wiki pages, where every info hast its place and is explained in short but plain language.
The reading requires some basic programming skills but could be done even without any Perl knowledge if you smart enough.
Yeah, its almost same as last year, except I now know more about Perl 6. the idea isn't that new but I just time to update and enlarge the German version bit, but this is about the English version. Some pages i would just have to translate but some aren't still written.
are the single pages, even chapter could be counted as millimeters. :)
2,3 days/page, more for the last ones. Begin i could now even after Perl-Workshop there will be bit more time for me.
Herbert Breunung, with moritz probably the German guy who knows most about perl 6. I'm involved since some times and wrote a series of more novel like tutorial, gave some talks about that stuff so i already chewed many bits through (p6 you don't learn in a day). my dedication for perl 6 since 2 years shows that i am serious about it.
]]>Jonathan's grant request is included here, below. Any interested Perl community members may provide their comments regarding this grant request here.
]]> NameProject Title
Traits, Introspection and More Dispatch Work For Rakudo
Synopsis
This project aims to add additional functionality specified in S12 and
S14 to Rakudo Perl 6.
Benefits to Perl 6 Development
Today, Rakudo is one of the most advanced, and certainly the most actively developed, Perl 6 implementation. I am seeking this grant to fund my time to continue implementing features in Rakudo that are on the path to it being a complete implementation of the Perl 6.0.0 specification. In fact, the work proposed under this grant would bring us very close to a complete implementation of S14, and fill out a substantial amount of the bits of S12 that Rakudo currently does not support.
Deliverables
D1. Implementation of .WALK, .can returning an iterator, dispatches of the form $foo.@candidates, and all of callsame, callwith, nextsame, nextwith and lastcall, as specified in S12. This work will also give coverage of the section of S12 under the heading "Interface Consistency". Furthermore, it will layer Rakudo's dispatch more neatly onto Parrot's own dispatch mechanisms, improving Rakudo performance.
D2. Refactoring of .wrap and .unwrap, as specified in S06 to work in terms of the same candidate lists as these S12 features.
D3. Implementation of the parallel dispatch section in S12.
D4. Filling out of the default Perl 6 metaclass to support the introspection capabilities specified in S12.
D5. Implementation of defining methods on the metaclass, as described in the Class methods section of S12.
D6. Implementation of traits, as specified in S14.
Project Details
In my last grant, I did some significant improvements to dispatch in Rakudo. However, there's still some work to go. D1, D2, D3 and D5 aim to fill out what is missing, and will incorporate a refactor that will bring improvements to method dispatch performance in Rakudo.
Rakudo currently allows very limited introspection. D4 will fill out the meta-model and provide much fuller introspection capabilities. This work will also bring us closer to implementing the HOW API suggested by the smop project, which is likely to be incorporated into S12. This also means the foundations for people to define their own metaclasses will have been laid by the end of this grant. Completing this section of the
grant will require getting input and consensus on some currently under-specified bits of the introspection interface and ensuring those clarifications are made explicit in S12.
Currently we cheat a bit to support the Perl 6 built-in traits in Rakudo. In D6, I aim to implement the traits section of S14, refactoring existing trait handling to match up with this model while providing support for user-defined traits.
Project Schedule
Work will begin as soon as the grant is approved. I expect to accomplish the majority of the deliverables during May, and if all goes smoothly aim to wrap up the grant for the end of June or early July. Here is a rough timetable.
Middle of May: Substantial progress on D1, D4 started
End of May: D1 and D2 mostly complete, notable progress on D3, D4 and D5
Middle of June: D1 through D5 mostly complete, clear plan for how to do D6
End of June: Progress on implementation of D6, tweaks as needed to D1 through D5
Early July: Completion of all deliverables
Report Schedule
Blog posts will be made throughout the duration of the work on rakudo.org blog as well as my blog on use.perl.org.
Public Repository
All code, documentation and other relevant files that relate to Rakudo will be checked into the Rakudo repository. All code, documentation and other relevant files that relate to any Parrot fixes/additions arising as a result of this grant will be checked into the Parrot repository. All contributions to the specification and specification tests will be
checked into the Pugs repository.
Grant Deliverables ownership/copyright and License Information
All work on produced as a result of this grant will be licensed under the Artistic License Version 2.0. I already have signed the relevant CLAs for both The Perl Foundation and The Parrot Foundation regarding ownership.
Bio
I first started contributing to Parrot in 2003, and since then have contributed to both the design and implementation of Parrot. I have been involved in Rakudo development since December 2007, and have implemented a wide range of features, with a focus on the object model and the type system. In addition to writing code, I am also a frequent speaker on Perl 6 and Parrot at European Perl conferences and workshops.
As well as my extensive Rakudo development experience, I also have strong academic underpinnings, holding a first class Computer Science degree with honours from the University of Cambridge.
I believe that my unique combination of Parrot internals knowledge and in-depth knowledge of Rakudo Perl 6, as well as my academic background and existing contributions to Parrot and Rakudo so far, put me in a very strong position to successfully deliver an implementation of the features described in this proposal.
Country of Residence
Slovakia
Nationality
United Kingdom
Amount Requested
$6000 USD
Okay to publish proposal?
Yes
Suggestions for Grant Manager
Patrick Michaud has indicated that he is willing to act as grant manager for this grant.
Deliverables Status
All deliverables have been achieved. In places, my work has gone beyond
what the grant required. Reactions to my work have been positive, both
from users and other developers.
D1. We now register types in the symbol table at compile time and the
hack that saw us through the early days is removed. Furthermore, I have
used this to build some other features, including compile time detection
of type re-declaration.
D2. Junction auto-threading is now fully implemented for both single and
multiple dispatch. The Perl 6 multi-dispatcher knows how to generate and
cache junction dispatchers for future performance too. As various
built-ins have moved over to the Perl 6 prelude, they too have gained
the auto-threading automatically. I also reviewed and added a range of
tests1 to exercise the auto-threading, including ensuring that
interaction with multis and auto-threading as well as nested junctions
work as expected.
D3. I implemented submethods and reviewed and enabled the tests for them.
D4. The handles trait verb has been extensively refactored and now
handles many more cases. I reviewed, enabled and added to the spectest
suite tests2 relating to this, to improve test coverage.
D5. This has by far been the most significant and complicated
deliverable of the grant, and what has been achieved in this area
exceeds what was originally required. First and foremost, we now have an
implementation of parametric roles. They can be declared, composed and
mixed in, the selection falling naturally out of the usual
multi-dispatch semantics as is specified.
In addition to this, I have converted the Positional, Associative and
Callable roles to be parametric. This, along with a little bit of extra
work in the compiler, has now given us typed arrays, hashes and routines
- features from S09 and S06. This has served as a great concrete test of
parametric roles. It has also won us sigil-based multi-dispatch and
multi-dispatch based upon typed data structures too.
Test coverage for parametric roles was weak (understandable, because
nobody had implemented them before), and I have expanded this greatly
during my work3,4,5. Some tricky areas - including parametric roles
recursively parametrized and parametric role subtyping - a feature not
in the specification at the time I started the grant - are now well
exercised.
I rounded this work off by updating S146 (the specification for roles,
which has been broken out from S12 since I started this grant). It is
now more detailed and complete.
Dissemination
I have written several blog posts on use.perl.org7 and rakudo.org
during my time working on this grant.
I have remained active on the #perl6 channel, explaining my work to
people there as they asked questions. I have also spoken on Perl 6 at
four workshops8 during the duration of the grant, and covered the work
I have been doing there. I also attended the Nordic Perl Workshop
hackathon to get feedback from Larry and tie up some of the last loose
ends in parametric roles.
Conclusions
My work under this grant has moved Rakudo forwards, not just in the
things listed in the deliverables but also in many tangential things
that I did along the way to enable me to make progress on the grant too.
Overall - despite finishing a little later than originally planned - I
feel that this grant has been a success and a win for Rakudo.
References
1 http://svn.pugscode.org/pugs/t/spec/S03-junctions/autothreading.t
2 http://svn.pugscode.org/pugs/t/spec/S12-attributes/delegation.t
3 http://svn.pugscode.org/pugs/t/spec/S12-role/parameterized-basic.t
4 http://svn.pugscode.org/pugs/t/spec/S12-role/parameterized-type.t
5 http://svn.pugscode.org/pugs/t/spec/S12-role/parameter-subtyping.t
6 http://svn.pugscode.org/pugs/docs/Perl6/Spec/S14-roles-and-parametric-types.pod
7 http://use.perl.org/~JonathanWorthington/journal/
8 http://www.jnthn.net/articles.shtml