Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Update "development" section for OPfW.
  • Loading branch information
oalders committed Sep 16, 2014
1 parent a7f9e1a commit 267acb2
Showing 1 changed file with 17 additions and 32 deletions.
49 changes: 17 additions & 32 deletions root/about/development.html
Expand Up @@ -24,38 +24,23 @@
volunteers take items on, but here's a sampling of what we'd love for you to
consider working on.


## Module tagging

This is one of the most important things which MetaCPAN potentially can offer
to the Perl community at large. A way for users to contribute to the
categorizing and organization of the many, many available modules on CPAN.
"There's more than one way to do it" is a good thing, but it can also get in
the way of solving a problem when you are faced with too many choices. [Some
thoughts on
tagging](http://blogs.perl.org/users/olaf_alders/2013/03/sifting-through-the-cpan.html)
make for a good starting point.


## Web of Trust

Dave Rolsky, back in 2010, posted an idea he had about how to mark modules as
trustworthy (ie used by people he trusts). He said:

"I've long wanted some sort of "web of trust" system for CPAN. A CPAN user
would mark authors and/or distributions as trusted. We’d take the graph of
trust relationships and try to figure out which authors and modules are most
trusted. Trust here would be some combination of good code, good docs,
responsive author, whatever. The idea is to organically highlight the best of
CPAN, and in particular help people discover the best modules in their class. I
think this would be really useful for new users, and a lot more useful than the
current CPAN rating system."

Using ++ data (which we already have) and possibly module tagging, we can
provide "web of trust" data. This does not, however, require the module
tagging implementation to be useful and this would be of great value to many in
the Perl community.

## Improve Search

metacpan.org already has workable search functionality, but it could be
improved a lot. This is our main pain point. We need help in the following
areas:

* Porting our Elasticsearch from 0.21 to 1.x
* Optimizing current searches so that they return results faster
* Improving the current search to return more relevant results
* Adding the ability to search on other things, like authors
* Including TRIAL releases in search results

You do not need to have any working knowledge of Elasticsearch in order to take
this on. We are here to point you at the resources you need to be successful
with this. Taking this on means you'll learn a lot about Elasticsearch and
you'll get experience working with a lot of data at once. These are skills
which can benefity you greatly in your professional life working in IT.

## Bug Fixes

Expand Down

0 comments on commit 267acb2

Please sign in to comment.