That's a good one. But other than the list, I would think that communities like this one would be good places to float suggestions for new modules.
The traditional way to find an unmet need is to have a continually annoying problem yourself. I've trained myself, over the years, to go looking for solutions to such problems on the net, before attempting to write my own code. If I don't find a solution, then I generally try to adapt one that is more or less near to addressing my problem. If I can't find anything even close, then I sit down and have a good cry. But I also realize that there's an opportunity at hand to bring succor and enlightenment to a troubled world, and maybe get someone to help write my solution.
Usually by then the problem has gone away. But if it hasn't, then I try to fix it myself. That usually results in some Perl code. If that isn't too embarrassing to see the light of day, I sometimes publish it. (That is, of course, a link to my most successful Open Source project. Um, well, my only successful Open Source project. The point is still valid. Really. Trust me.)
"Even if you are on the right track, you'll get run over if you just sit there." - Will Rogers
| [reply] |
I suggest giving the Phalanx project a look. If you really want to contribute to the overall perl community, this is a great project to get involved with. Just subscribe to their mailing list, and ask how you can help.
| [reply] |
| [reply] |
Thanks for the suggestion. The Perl Apprenticeship site:
1. Has had 16 projects (6 of which look like stubs) posted in three years. There is no indication of how many "apprentices" are active on the site, I suspect because this figure is also very low. This low usage should be accounted for.
2. Is not CPAN specific. Very few of the projects are CPAN modules.
3. Implies that anyone having the time available to make a contribution is an apprentice and anyone having/spotting a need is highly skilled. I do not see this connect.
Not shooting the Apprentice site down, I think it's a good idea. It just (A) hasn't been used and (B) may not be the best way to address what I am talking about. -Andrew.
| [reply] |
Personally, I don't know that such an undirected contribution is really what the community benefits from. I personally believe the best module writers are those who work intimately in the problem space they are dealing with, and the best people to add to an existing module are those who know the module intimately.
My recommendation to programmers looking for ways to contribute is to find a problem to solve or a software project to join directly. In the process of working on that, you'll either use some modules well enough to see where they need to be improved or else will wind up creating something that others can use.
-xdg
Code posted by xdg on PerlMonks is public domain. It has no warranties, express or implied. Posted code may not have been tested. Use at your own risk.
| [reply] |
| [reply] |
Naaah !
- Post a description of what you plan for your new module here (implying you've already done it); and
- Wait until merlyn asks you what's wrong with using the module that does just this that's already in CPAN
Not infallible, but works most of the time, anyway
:-)
| [reply] |