Please add your suggestions for projects, etc here. We will put them to dedicated pages. Alternativly, you can contact domm AT cpan.org to get proper access to the wiki...

• Perl IDE

Add your suggestions using the comment feature:

• Push Perl6
• Embedded Perl (focusing on PDA, Smartphones, etc)
• Push Perl-GTK (or other graphic toolkit)
• Improve perlcc utility

contributed by guest@hidden on Dec 21 12:20am

As a Newbie to the internet, I am always searching online for stuff that can help me. Thanks for the information.

femmes russes
Einsame russische Frauen
Mujeres solteras rusas
Ukrainian women
donne russe
Russiske jenter

contributed by guest@hidden on Jul 16 9:00am

YAPC::Europe 2007 left Vienna.pm with quite a lot of money. We want to give part of this money back to the Perl community by hosting the Winter of Code (with apologies to Google...).

Our total budget for this project is approximately €20,000. Yay! Additionally, we'll support YAPC::Europe 2008 in Copenhagen with €5,000, and YEF with €2,000.

Thanks to all the sponsors and attendents of YAPC::Europe 2007 who made it possible for Vienna.pm to fund this project!

After some discussions on the vienna.pm mailinglist, we decided what to do with the money during the Orga Meeting 2007-11-21:

Decided Grants

• Work 1 day per week on Rakudo to Jonathan Worhington
• p5p Summaries (€3,000) to David Landgren
• Management System for TODO Test Bounties (€1,000) to Matt S Trout / Shadowcat

Still open / in progress

• TODO Test Bounties (€4,000) will start in January
• YAPC Community Awards (€3,000) Jan / Feb 2008
• YAPC Orga Award (€1,000) Jan / Feb 2008
• TPF Donation (amount still undecided) March / April 2008
• YAPC Speaker Awards (€2,000) will be awarded during YAPC::Europe 2008 in Copenhagen

Please note that these projects are not (yet) cast in stone. If you have further suggestions or any criticism, please post them here (by clicking on the "Comment"-Button at the top of the page).

We have a lot of work ToDo!

If you have any ideas about what we should sponsor, leave them as comments on the suggestions page!

(IDE Suggestion by Alvar moved to Perl IDE)

Please note that even though this page has been widely linked to from the blogosphere / perl community I have just spent 30 min looking and I can't find the link to the actual todo bounty system. My guess is that I may be missing it, but it is definitely not prominent / linked to enough. Please someone fix it because you are wasting good publicity since the website is so hard to locate

--groditi

contributed by guest@hidden on Apr 12 10:32am

When I open your site in your browser, Safari 4 in Mac OS X, some elements of the page and off to the side and the text is broken: ( Please help me How can I remove the problem?
Single Russian Women

<a href="http://rudiva.com/">Single Russian Women</a> | <a href="http://ukrainianwomens.com/">Ukrainian Women</a> | <a href="http://dating.lovedove.ru/">Russian Date</a>

contributed by Russian Girls Russian Girls on Jan 3 2:36am

Excellent topics. I really like this topics, I found this from online that, each recipe has been tested and each one has come out perfect If not, they are not added to the site. All you need to know is how to make the perfect dishes.

contributed by guest@hidden on May 13 2:28am

Great post. Machine embroidery is now so heavily utilized for product branding and personal use. http://www.janome-embroidery-machine.com

contributed by guest@hidden on May 16 9:22am

The iPad speakers are amazing. I'm on mine right now listening to the iPod and it's rather loud. <a href="http://www.ipadspeakers.org">ipad speakers</a>

contributed by guest@hidden on May 18 7:01am

The iPad speakers are amazing. I'm on mine right now listening to the iPod and it's rather loud. http://www.ipadspeakers.org

contributed by guest@hidden on May 18 7:13am

The attractive offer. Thanks.

Single Russian women
Single Russian girls

contributed by guest@hidden on Jun 10 9:25am

http://www.rus-women.com

contributed by guest@hidden on Jun 20 1:45pm

<a href="http://alanwattsbooks.blogspot.com/" >alan watts books</a> | <a href="http://facebookofsex.over-blog.com/" >facebooksex</a> | <a href="http://facebooksluts.over-blog.com/" >facebook sluts</a>

contributed by guest@hidden on Jun 22 3:51pm

I think you covered it quite well, was a very interesting blog post to read.

Russian women photos
Free Russian Brides
Single Russian Women

contributed by guest@hidden on Jul 6 2:45pm

Great post. Machine embroidery is now so heavily utilized for product branding and personal use. [janome embroidery machine]

contributed by guest@hidden on May 16 9:25am

Great post. Machine embroidery is now so heavily utilized for product branding and personal use. www.janome-embroidery-machine.com

contributed by guest@hidden on May 16 9:27am

Well, its not always possible to make code that does incredibly complex stuff with good efficiency to be very simple but it is always possible to make the API to USE YOUR CODE simpler.
“The simpler your code is, the fewer bugs you will have. ” ;) "-essay writer"<http://http://www.superiorpapers.com/

contributed by Luke Sam on Oct 20 8:16pm

How it works

1. Project maintainers submit links to TODO tests to the Management System for TODO Test Bounties. TODO tests should either test for a known bug, or for a yet unimplemented feature. The submission includes a link to some discussion of the issue, an estimate on the time needed to implement it, and a 'price tag' (which will be paid by Vienna.pm to whoever fixes the bug / implements the feature).
2. We prefer small and cheap things over big and expensive things. Something that can be done in a few hours / a weekend (or ~€250) would be ideal.
3. Vienna.pm reviews submitted TODO tests. We will prefer big projects (like Perl 5, Perl 6, etc) and widely used CPAN modules over something that's only used by few. Vienna.pm might change the price tag (up or down...).
4. Vienna.pm publishes a list of accepted TODO tests
5. People willing to implement the features / fix the bugs say that they want to do so
6. If the project maintainers agree, the implementor gets some time to do his/her work
7. As soon as the implementor is done, the project maintainers review his/her work
8. If the project maintainers are happy, Vienna.pm pays the specified amount into the implementor's bank account.

Budget

Our total budget for this project is €4,000.

Any money left will probably be donated to TPF for their grants.

Prototype

http://todo.useperl.at

Timeframe

We first need the Management System for TODO Test Bounties which should be ready by Jan 2008.

As we're doing the Winter of Code, the first run of this project will last until 31st March 2008. Depending on the success (and our funding), we might extend it, or stop earlier.

Trivia

Thanks to Nicholas Clark for suggesting this.

Maybe some of this bounties could go to how Todo's are handled (not eliminating Todo's from known modules). There has been a discussion on perl-qa which stated with "shouldn't "UNEXPECTEDLY SUCCEEDED" mean failure?" and continued with "TODO -> MAYBE tests?".

I have informed the perl-qa people about this bounties.

Cheers, Nadim.

contributed by guest@hidden on Dec 8 2:16am

To me that would seem like something that should be part of a separate grant application, rather than one of the specific TODO test bounties. My opinion isn't "no", just "not right here" - it sounds like something worth suggesting via the main Winter of Code page.

contributed by guest@hidden on Dec 23 3:40am

Well, its not always possible to make code that does incredibly complex stuff with good efficiency to be very simple but it is always possible to make the API to USE YOUR CODE simpler.
“The simpler your code is, the fewer bugs you will have. ” ;) http://www.superiorpapers.com/ -essay writer

contributed by Luke Sam on Oct 20 8:13pm

hi

contributed by guest@hidden on Aug 5 2:13am

My Proposal for a project (from Alvar, http://alvar.a-blast.org/)

Create and support a project, which delivers an easy installable IDE for Perl, which can be used by persons who are no CLI freaks (new users!), with debugger, editor with syntax check while typing, support of Perl::Critic in GUI, support of perltidy within the GUI, with lots of essential modules, mod_perl, Catalyst, Jifty, Gantry, good tutorial in more languages than englich (german, french, spanish, ...), ...
The package should be ready for use for the most common OS: Windows, OS X, Linux; FreeBSD, Solaris, ... -- the X11 systems are more or less the same ;-)

And the project website should be placed good visible on the usual Perl websites, with fast download links (like Firefox: http://www.mozilla-europe.org/de/products/firefox/)

After that, create press releases ("business", "professional" and other bullshit bingo words).

You say: too much work?
No, at least for the beginning: take Eclipse and E.P.I.C (http://e-p-i-c.sourceforge.net/), use some not so ugly colors ;) and create bundles for each OS with this - including Perl, Modules and perhaps some other related Eclipse plugins (SQL, HTML, ...)

You say: vim is much more better?
Maybe better for you. But such developers are in danger of extinction.

contributed by guest@hidden on Dec 1 5:46am

Whatever you may say about IDEs - there are many programmers out there who won't even think about using a particular programming language if there's no IDE for it.
Judging about a language based on the tools available for it may not be fair but there is some sense in it, because they do save time especially for the not-so-experienced users.
So I strongly second Alvars suggestion.
If we want Perl to attract more attention then a good cross plattform IDE would be a major step in the right direction.
Perhaps it needn't be an IDE for Perl 5.x (there's EPIC and Komodo, which basically work) but having a fully functional (syntax highlighting and checker, debugger, code completion, etc.) IDE (based, e.g., on Eclipse Dynamic Languages Toolkit) ready for Parrot/Perl 6 would be sufficient.

Just my 2 cents

contributed by guest@hidden on Dec 2 3:48am

Please do not create a new IDE, if you want there to be good IDEs for Perl, please improve the ones that already exist. It would probably do more good for more people to improve the debugger and other tools then to start a new project.

contributed by guest@hidden on Dec 10 10:49pm

I know about only two sensible cross platform IDEs for Perl: EPIC and Komodo.
Last one is closed source.
First one is free but - as I understand - heavily tied to Perl 5 and not using newer developments for Eclipse like DLTK.
I like the idea of having sth. ready for Perl 6 / Parrot when - or before ;) it´s finally there.
Perhaps a general debugging interface for Parrot is possible which could be reused for a Perl 6 IDE?
May be bullsh*t - don´t know enough about Parrot internals...

contributed by guest@hidden on Dec 11 11:09am

Might be worth chatting with Andy about the work he did for his refactoring engine grant http://www.perlfoundation.org/march_25_2007_adam_kennedy_s_refactoring_editor_grant

contributed by Adrian Howard on Dec 13 5:46am

Basic rules to success!

• Improve any IDE you like adding support and special features focused on Perl
• Configurable to work with any key-binding (vim, emacs, eclipse, etc)
• Fast, easy and extensible

contributed by guest@hidden on Dec 21 12:16am

I'm very pleased to find your comment, since it's an issue overdue to be addressed. It's not that good Perl programmers need a real IDE -- I'm quite happy using mostly Emacs, and I like the ability to modify the Perl mode (with lisp) as desired. But Perl6 is a different matter -- a lot of new constructs to learn, and a lack of general information about syntax and behavior. Even just the discipline of compiling a "help" menu for a Perl6 ide would help centralizing this information -- web searches alone bring up contradictory summaries of many new features, reflecting different stages in the evolution of Perl6 or different writer's opinions on what would be in the final specs. Developing code completion and syntax highlighting tools would be a great way to learn the langauge inside out -- and someone actually doing that work would have a good rationale to write to the big fellas to ask how something works.

I'd also like to opine that the initial use of Perl6 may largely be as a kind of "paradevelopment" language, and those of us who believe in it should promote its usefulness in that area. What I mean by "paradevelopment" is that even a project whose actual shipped, or open-sourced, code is in some other language (C++, C#, Lisp, whatever) could use Perl6 for things like testing, versioning, ensuring stlyistic and policy-driven consistency across a compilation unit (or project or whatever), and code-generation. Perl6 grammars are wonderful, and they seem to look and act like a cross between regular expressions and parsing expression grammars (I noticed that the author of the new "spirit" parsing library on boost cited Perl6 as an inspiration). Someone needs to prosletyze them more in computer science circles, 'cause the world still hasn't caught on to how great even Perl5 regexes are (entire algorithms can be embedded in regexes with lots of $+s and ?({})s). I happened to learn a little about the regex 'make' function at Frozen Perl '09 and it has only gradually dawned on me how theoretically interesting and subtle it is -- in effect, it embeds a concept of types directly in the regex system, implying a kind of typed Kleene algebra. Anyhow, Perl6 makes it easy to define grammers for any language and therefore analyze source code, so it can be a great tool even when the primary development occurs in some other language ("progamming with Perl6 is not necessarily programming in Perl6"). This should help jump-start acceptance of it, because it can be used strickly backstage -- but we need to develop modules which promote this usage.

Anyhow, a Perl6 IDE could exemplify that concept even if it is written, say, in C++; Perl6 could be used to test and analyze the C++ code as it is under development. I admit to being skeptical about a good IDE written only in Perl; MOST IDEs written in the same language as they target don't work well. (I have Java IDEs written in Java that are so slow as to be worthless.) Of course, since parrot would have to be embedded for debugging (all the existing Perl IDEs seem to run scripts by forking an external process -- is that really necessary?), users could write extension scrips (like Emacs macros) in Perl (if one of the parrot lisps get done maybe we could support porting emacs settings also and emacs-like key sequences). I'd love to work on such as IDE and, if folks disagree about these suggestions/ideas, perhaps we could work independently but touch base over time and potentially merge at some point. Meanwhile, there are several people whose suggestions I'd like to court re Perl6 IDEs and related topics, so perhaps I'll try to gather some other opinions and post them as I get them. Thanks for initiating this needed discussion!

contributed by guest@hidden on Mar 14 8:31am

At the Oslo QA Hackathon 2008, during one evening meal, it became evident that Jonathan Worthington would be able to spend even more time hacking on Rakudo Perl if he would get paid a little money for it. As Vienna.pm still has some money earmarked for Perl development, we encouraged Jonathan to send us a proposal for funding him. Which he did. And which we accepted.

Objective

• Work on Rakudo one full day a week (minimum of 8 hours of work)
• Post about the work on the rakudo.org blog and cross-post it to use.perl.org

Budget

Jonathan will recieve € 150 per day spend working on Rakudo. We estimate that on average he will work 4 days per month. We agreed on funding three months (~ €1,800) and evalute the grant after that time. If everybody is happy, we will continue the grant until the end of 2008, where we will evaluate again (and check if we still have money left).

Results

• http://www.rakudo.org/2008/05/todays-progress-object-initial.html
• http://www.rakudo.org/2008/05/grammars-get-classlike-and-oth.html
• http://www.rakudo.org/2008/05/more-oo-support-captures-and-r.html
• http://www.rakudo.org/2008/05/rakudo-hacking-and-talks.html
• http://www.rakudo.org/2008/06/ranges-parameters-and-many-fix.html
• http://www.rakudo.org/2008/06/attributes-attributes-attribut.html
• http://www.rakudo.org/2008/06/mixins-generic-routines-and-en.html
• http://www.rakudo.org/2008/07/lexical-fixes.html

Jonathans proposal

** About Rakudo
Rakudo is the name of the Perl 6 compiler running on top of Parrot. After
many years of work by many people to build a powerful and feature rich VM,
along with a couple of years of work led by Patrick Michaud to implement a
large chunk of the Perl 6 grammar engine along with a set of compiler
tools, we now have a platform that is allowing Perl 6 language
implementation to proceed relatively rapidly.

Already we have a whole host of features, including:
* Basic control structures (loops and conditionals)
* A wide range of built-in operators
* Declaration of subroutines, along with positional, named and slurpy
parameters
* Classes, roles, methods, attributes, inheritance, role composition
* Named and non-named regeses, calling named regexes from each other
* Match object functionality, using named and positional regex captures
* Declaration and use of subset types
* Use of types on my and our declarations as well as in function signatures
* Arity based multi-dispatch (not typed yet)
* The basics of junctions
However, the Perl 6 spec is rather large, so there's more than a little bit
left to do. :-)

** About Me
I've been involved in the Perl 6 project since 2003, when I started sending
in some basic patches to Parrot, to improve its Windows support. I earned
my commit bit on Parrot in 2005, after my first YAPC::Europe, where I
agreed to (and went on to) implement the Parrot bytecode linker, pbc_merge.
I wrote the bytecode design document and was heavily involved in the
specification and implementation of the Parrot OO model as it stands today,
complete with introspection and role composition.

Shortly after the Perl 6 on Parrot implementation reached the stage where
it was now written largely in Perl 6 itself (the grammar being in Perl 6
rules and the grammar actions being in NQP, a small subset of Perl 6), I
started to contribute to it. Since then, I've implemented a range of
features in the previous list, including the OO features, pairs (needed to
make named paramters work), junctions, subset types, type declarations and
other bits and pieces here and there.

I'm actively involved in the Perl community, having attended a range of
conferences and workshops to talk about Parrot, Perl 6 and Rakudo.
Qualification wise, I hold a first class honors degree in Computer Science,
the course I took featuring modules on compilers, type theory and formal
semantics of programming languages. You can see more on my CV.
http://www.jnthn.net/cv.shtml

** The Funding
Without funding, I can work on Rakudo in my free time (evenings and
weekends) when I have the energy, as well as at Hackathons and workshops.
I'm seeking funding to allow me to dedicate whole days of my working week
to Rakudo. The ability to spend a day focussed on the project will make it
much easier to make progress than doing things in the odd hour here and
there. It also means that when real life gets busy and work hours are all I
have, I can use some of those to work on Rakudo, knowing that it will put
food on the table and pay the rent.

My proposal is to work on Rakudo one full day a week (minimum of 8 hours of
work) at a rate of 150 euros per day. I would report, once a month or
another timescale agreed between us, how many days meeting this criteria I
have worked on Rakudo within that month. If I take vacation, obviously I
don't get any funding for not doing anything - I just send in a report of
what I did and payouts are based upon that.

Obviously, I will still do bits and pieces on Rakudo in bits of spare time
and at workshops and hackathons too. The aim of the funding is to increase
the amount of time I spend on Rakudo and allow me to spend time more
regularly, so we get a more constant rate of progress.

** Reporting
I will post about my work on the rakudo.org blog and cross-post it to
use.perl.org, just as I have been doing in recent weeks and months.

Objective

Develop a website to manage TODO Test Bounties

More info available in the TODO Management System Specs

The winner of the call for proposals

The proposal from Matt S Trout / Shadowcat convinced us. The technical part looks very promising (and we're honoured by a core Catalyst developer coding an app for us), but the social aspects of his proposal is what set it apart from the rest:

Shadowcat would like to defer the bounty to fund additional Catalyst or DBIC related WoC projects. This means we get twice the value for our (your!) money. Additionally, they want to put the app in the Reaction repository under a perl license to serve as an example of Reaction development. Which makes this effort even better, because good, real-live example apps are very valuable when learning a new technology.

You can follow the design / implementation process in Matts Vienna WoC TODO Manager development blog

Prototype

http://todo.useperl.at

Budget

By request from Shadowcat, we won't pay them the planned €1,000. Instead, we will put the money into other Catalyst / DBIC releated projects or bounties.

Timeframe

As this project has to be finished before we can start with TODO Test Bounties, we target 31st Dec 2007 as the release date of the first prototype.

Plan B

As Plan A worked out, there's no need for a Plan B anymore..

Comments

Since nobody else seems to have come forward yet. Have a proposal:

• I shall write it in Perl
• It shall be built with TT2, various CPAN modules & duct tape
• I can host it if necessary
• I shall get a minimal version up and running ASAP and then implement extra features until I get bored
• If this sounds like a vaguely good idea somebody with some vague approximation of authority should e-mail adrianh@quietstars.com and tell me to start writing it

contributed by Adrian Howard on Dec 10 2:11am

I've just got fired - so I guess I have some time for that. I would do it with Catalyst, DBIx::Class and TT2. I can collaborate with Adrian - if he is willing to do that.

contributed by guest@hidden on Dec 10 1:39pm

I've just got fired - so I guess I have some time for that. I would do it with Catalyst, DBIx::Class and TT2. I can collaborate with Adrian - if he is willing to do that.

contributed by Zbigniew Lukasiak on Dec 10 1:46pm

Some more submissions were received from:

• http://www.shadowcat.co.uk/catalyst/ (who would immediately donate the bounty back to sponsor development of other Catalyst-related stuff)
• Rene Bäcker
• Michael Schwern
• David Nicol http://www.tipjar.com/bounties/TJDSBF.html

Actually, it's not specifically the Catalyst team that's offering to do this but Shadowcat - which probably means mostly me doing the implementation work while I'm trying to avoid talking to senile family members over christmas :)

However, Shadowcat does not want the bounty, what we want is to have the bounty recycled to sponsor development of other Catalyst-related stuff.

We'd be more than happy to have collaborators and just have our portion of the bounty recycled as such, but I was intending to use the reaction libraries to implement this since it'll need much less code than a plain Catalyst app would.

I discussed this with people at LPW but didn't realise I was supposed to post on here to confirm until now :)

You can contact me at mst ($array_sigil) shadowcatsystems.co.uk as usual.

contributed by guest@hidden on Dec 18 9:01am

Sorry about the confusion. I've corrected the above text to reflect this.

Objective

• Write weekly summaries of the happenings on p5p (perl5-porters)
• Post them to p5p, perl5-summary, use.perl (and maybe other places like PerlBuzz)

Budget

€3,000 for 2008, payed in two parts

The Summarist

After a lot of internal discussions, Vienna.pm decided to choose David Landgren to write p5p summaries for one year (2008). David already did the summaries in 2006 (and collaborated on some earlier issues).