Desperate plea for help on the GHOP program
GHOP: Google Contest. Week-long tasks (coding, documentation, or otherwise) that 13-18 year olds knock out of the park. See http://drupal.org/node/195913 for contest details. Good news: These students are frickin' awesome. Check out our list of completed tasks so far: http://code.google.com/p/google-highly-open-participation-drupal/issues/list... Bad news: We need *help* to maintain this momentum. Current stats are available at: http://groups.drupal.org/node/7569 Python is currently kicking everyone's ass in terms of tasks completed by their students. This is directly related to the amount of focus their reviewers are able to give. We have had the following tasks have been under review for > 24 hours and are *actively halting these students from taking on more tasks*, as well as likely creating sour feelings towards Drupal as a project for holding them back. *Reviews needed here ASAP please.* * Performance profile Drupal 6: http://drupal.org/node/196907 * User experience usability report: http://drupal.org/node/197221 * Drupal 6 Theme: http://drupal.org/node/197227 * Mockups for hard-to-use pages: http://drupal.org/node/197311 * Port Text CAPTCHA to 6.x: http://drupal.org/node/198598 * Display module memory usage: http://drupal.org/node/198053 For a full list of GHOP issues that need review at any given time (ideally this is always at zero), please see: http://drupal.org/project/issues/?text=GHOP&states=8 Drupal is also currently tied for *second fewest* open tasks available. This means that there's a far more likely chance of a student going to a project like Joomla! or MoinMoin that has a better task selection. Please help by creating additional, high-quality tasks. Everyone has "little" things they wish they had time to work on. Write them up as task ideas to http://drupal.org/node/add/project-issue/ghop as a "Task idea" according to the guidelines at http://code.google.com/p/google-highly-open-participation-drupal/wiki/HowToW.... Remember that tasks don't have to be just about coding (documentation, translation, usability, etc. are also on topic), although coding tasks _are_ popular. :) Thanks for your attention to this. If GHOP continues to go as well as it has, it looks like we'll gain some very valuable long-term contributors (and in fact, I think we already have). -Angie
On Dec 10, 2007, at 11:11 PM, Angela Byron wrote:
Please help by creating additional, high-quality tasks.
Interested parties should read the following lists of issues would benefit the d.o infrastructure in some way, since many of them would be good GHOP tasks: http://groups.drupal.org/node/1830 http://groups.drupal.org/node/4970 http://groups.drupal.org/node/6186 If nothing else, someone could contribute by finding and writing up the best GHOP tasks from these lists. webchick and aclight have done an amazing job with this so far, but there's plenty to go around, so please pitch-in. Extra points for those who mentor/review the resulting efforts of the students. Thanks, -Derek (dww)
On 11 Dec 2007, at 9:11 AM, Angela Byron wrote:
* Port Text CAPTCHA to 6.x: http://drupal.org/node/198598
perhaps check for some other simple modules that haven't been ported to 6 yet ? cross reference something like LOC (not really a good indicator, but still) versus their positions in the d.o usage stats.
Perhaps we should also put together guidelines for doing a security review / code style check (maybe with the assistance of coder.module), to help us boost the quality of the contribs repository. We could also flag modules that need documentation somehow.
On Dec 11, 2007, at 1:39 AM, adrian rossouw wrote:
Perhaps we should also put together guidelines for doing a security review / code style check (maybe with the assistance of coder.module), to help us boost the quality of the contribs repository.
Agreed. Oh, and a patch against coder.module so that it generated a patch that corrected, not just a report about, all violations it knows how to fix: http://drupal.org/node/159364
We could also flag modules that need documentation somehow.
Lovely idea. See http://drupal.org/node/161085 for suggested documentation standards/practices for d.o projects. On Dec 11, 2007, at 1:36 AM, adrian rossouw wrote:
perhaps check for some other simple modules that haven't been ported to 6 yet ? cross reference something like LOC (not really a good indicator, but still) versus their positions in the d.o usage stats.
Another lovely idea! Adrian, you rock. ;) Thanks, -Derek (dww)
On 11 Dec 2007, at 12:36 PM, Derek Wright wrote:
Oh, and a patch against coder.module so that it generated a patch that corrected, not just a report about, all violations it knows how to fix: http://drupal.org/node/159364
That's beyond my abilities =) i hate regex' =P
We could also flag modules that need documentation somehow.
Lovely idea. See http://drupal.org/node/161085 for suggested documentation standards/practices for d.o projects.
Perhaps we can do that as part of the upgrade process.
perhaps check for some other simple modules that haven't been ported to 6 yet ? cross reference something like LOC (not really a good indicator, but still) versus their positions in the d.o usage stats.
Another lovely idea! Adrian, you rock. ;)
I'd be willing to help put tasks together for this, but i'd need access to the metrics, and the downloads. Perhaps we could make one of the items in the upgrade task , that they should document what questions they have about the functioning of the module, so we can create documentation tasks for modules that require it. Even more so, we have programmers documentation (doxygen) we could write tasks for as well. Writing Doxygen would give them a good understanding of how the modules are put together too.
On Tue, 11 Dec 2007 17:25:25 +0200, adrian rossouw <adrian@bryght.com> wrote:
perhaps check for some other simple modules that haven't been ported to 6 yet ? cross reference something like LOC (not really a good indicator, but still) versus their positions in the d.o usage stats.
Another lovely idea! Adrian, you rock. ;)
I'd be willing to help put tasks together for this, but i'd need access to the metrics, and the downloads.
We had proposals for a couple of "upgrade this module" tasks, but if we could get usage metrics to pick a couple from, that would be even better. The catch here is that we really do need the contrib author's buy-in, because they will need to review whatever patch the student submits.
Perhaps we could make one of the items in the upgrade task , that they should document what questions they have about the functioning of the module, so we can create documentation tasks for modules that require it.
Even more so, we have programmers documentation (doxygen) we could write tasks for as well. Writing Doxygen would give them a good understanding of how the modules are put together too.
http://drupal.org/node/197314 One is in progress. I'm hoping that after it's closed we can re-open it for another student to do a few more core modules. This one was already completed, which totally rocks: http://drupal.org/node/196667 --Larry Garfield
On Dec 11, 2007, at 7:25 AM, adrian rossouw wrote:
Oh, and a patch against coder.module so that it generated a patch that corrected, not just a report about, all violations it knows how to fix: http://drupal.org/node/159364
That's beyond my abilities =) i hate regex' =P
But that's the point -- I'm not asking you to do it, I'm just asking someone to write it up as a GHOP task. An aspiring regex ninja can claim it and solve the thing which you don't have the chops for and I don't have the time for. ;) Either way, it's not getting done now, but it might get done if we farm it out to GHOP. And, worst case that it doesn't get claimed by the end of the pilot program, at least it's in a more visible place for non-GHOP "newbies" who want to start contributing to Drupal can find it... I can imagine a post-GHOP "here's all the stuff that didn't get done, look here if you weren't eligible but still wanted to help" effort of some kind. Cheers, -Derek (dww)
On Dec 11, 2007, at 7:25 AM, adrian rossouw wrote:
I'd be willing to help put tasks together for this, but i'd need access to the metrics, and the downloads.
LOC you can get via your shell. Downloads we don't have easy access to yet, but see here: http://drupal.org/node/188993 http://drupal.org/node/32124 update_status usage is almost entirely ready to make visible on d.o, but is blocked on some simple UI/URL questions: http://drupal.org/node/165380 In general, interested parties are encouraged to read the meta document about project quality metrics here: http://groups.drupal.org/node/7191 Cheers, -Derek (dww)
Do you have to be in a certain group to be able to select the type and owner of a task on code.google.com? I created task 81 but am unable to select either, or to update the task for that matter. Not having a "preview" button is a pain. Wim Quoting Angela Byron <drupal-devel@webchick.net>:
GHOP: Google Contest. Week-long tasks (coding, documentation, or otherwise) that 13-18 year olds knock out of the park. See http://drupal.org/node/195913 for contest details.
Good news: These students are frickin' awesome. Check out our list of completed tasks so far: http://code.google.com/p/google-highly-open-participation-drupal/issues/list... Bad news: We need *help* to maintain this momentum.
Current stats are available at: http://groups.drupal.org/node/7569
Python is currently kicking everyone's ass in terms of tasks completed by their students. This is directly related to the amount of focus their reviewers are able to give.
We have had the following tasks have been under review for > 24 hours and are *actively halting these students from taking on more tasks*, as well as likely creating sour feelings towards Drupal as a project for holding them back. *Reviews needed here ASAP please.*
* Performance profile Drupal 6: http://drupal.org/node/196907 * User experience usability report: http://drupal.org/node/197221 * Drupal 6 Theme: http://drupal.org/node/197227 * Mockups for hard-to-use pages: http://drupal.org/node/197311 * Port Text CAPTCHA to 6.x: http://drupal.org/node/198598 * Display module memory usage: http://drupal.org/node/198053
For a full list of GHOP issues that need review at any given time (ideally this is always at zero), please see: http://drupal.org/project/issues/?text=GHOP&states=8
Drupal is also currently tied for *second fewest* open tasks available. This means that there's a far more likely chance of a student going to a project like Joomla! or MoinMoin that has a better task selection.
Please help by creating additional, high-quality tasks. Everyone has "little" things they wish they had time to work on. Write them up as task ideas to http://drupal.org/node/add/project-issue/ghop as a "Task idea" according to the guidelines at http://code.google.com/p/google-highly-open-participation-drupal/wiki/HowToW.... Remember that tasks don't have to be just about coding (documentation, translation, usability, etc. are also on topic), although coding tasks _are_ popular. :)
Thanks for your attention to this. If GHOP continues to go as well as it has, it looks like we'll gain some very valuable long-term contributors (and in fact, I think we already have).
-Angie
Here's a quickie way to boost the quality and maintainability, (and # of tasks:-)). For each module task, add an additional task to create a rich Simpletest for it. Later that might become a requirement for a module. -Bruce Angela Byron <drupal-devel@webchick.net> wrote: GHOP: Google Contest. Week-long tasks (coding, documentation, or otherwise) that 13-18 year olds knock out of the park. See http://drupal.org/node/195913 for contest details. Good news: These students are frickin' awesome. Check out our list of completed tasks so far: http://code.google.com/p/google-highly-open-participation-drupal/issues/list... Bad news: We need *help* to maintain this momentum. Current stats are available at: http://groups.drupal.org/node/7569 Python is currently kicking everyone's ass in terms of tasks completed by their students. This is directly related to the amount of focus their reviewers are able to give. We have had the following tasks have been under review for > 24 hours and are *actively halting these students from taking on more tasks*, as well as likely creating sour feelings towards Drupal as a project for holding them back. *Reviews needed here ASAP please.* * Performance profile Drupal 6: http://drupal.org/node/196907 * User experience usability report: http://drupal.org/node/197221 * Drupal 6 Theme: http://drupal.org/node/197227 * Mockups for hard-to-use pages: http://drupal.org/node/197311 * Port Text CAPTCHA to 6.x: http://drupal.org/node/198598 * Display module memory usage: http://drupal.org/node/198053 For a full list of GHOP issues that need review at any given time (ideally this is always at zero), please see: http://drupal.org/project/issues/?text=GHOP&states=8 Drupal is also currently tied for *second fewest* open tasks available. This means that there's a far more likely chance of a student going to a project like Joomla! or MoinMoin that has a better task selection. Please help by creating additional, high-quality tasks. Everyone has "little" things they wish they had time to work on. Write them up as task ideas to http://drupal.org/node/add/project-issue/ghop as a "Task idea" according to the guidelines at http://code.google.com/p/google-highly-open-participation-drupal/wiki/HowToW.... Remember that tasks don't have to be just about coding (documentation, translation, usability, etc. are also on topic), although coding tasks _are_ popular. :) Thanks for your attention to this. If GHOP continues to go as well as it has, it looks like we'll gain some very valuable long-term contributors (and in fact, I think we already have). -Angie
On Dec 11, 2007 1:11 AM, Angela Byron <drupal-devel@webchick.net> wrote:
Please help by creating additional, high-quality tasks. Everyone has "little" things they wish they had time to work on. Write them up as task ideas to http://drupal.org/node/add/project-issue/ghop as a "Task idea" according to the guidelines at
http://code.google.com/p/google-highly-open-participation-drupal/wiki/HowToW... . Remember that tasks don't have to be just about coding (documentation, translation, usability, etc. are also on topic), although coding tasks _are_ popular. :)
Hi Everyone I wanted to quickly follow up with an additional link to the "I'd like to help with the administration of the GHOP program! How do I start?" page that webchick created at http://groups.drupal.org/node/7360 Before creating a task on the Google issue tracker, *please* read section 2 of this page (http://groups.drupal.org/node/7360#tasks). The Google issue tracker is--how should I say it--limited in it's feature set. For example, it's not possible for anyone (even the project owners) to edit tasks once they are created. As Angie said, these students for the most part do a really great job on the tasks. The more focused and detailed the task description is, the more likely you are to get the results you're hoping for. So please be very explicit in your task description as to what you expect, how you expect it (ie. file format for non code/documentation tasks, what version of Drupal the code should be written for if it's not a porting task, etc.), and who the student can contact if they have questions (it would be great if you could include your d.o username and/or IRC nick). Finally, because most d.o users aren't following the Google issues closely, we've found that it's best if each GHOP task has a separate issue on drupal.org in the appropriate issue queue. This helps the students to get as many people looking at their work as possible, and it also helps them to gain experience in how normal tasks and issues are handled in Drupal. Please provide a link to your d.o issue in the Google issue, and also a link to the Google issue in your d.o issue. I know this is a little extra work on the part of the person who creates the task, but ultimately you're more likely to get great results this way. Again, thanks to those of you who have created issues, helped review issues, and helped to administer the issues either on d.o or the Google tracker. Please keep the ideas coming! Thanks Adam Light
One more thing--in case you're interested to see how Drupal is doing in comparison to the other GHOP projects, there are some nice charts that are updated periodically at http://opentouch.info/tmp/ghop/ghop-stats.html Adam Light
Angela Byron wrote:
GHOP: Google Contest. Week-long tasks (coding, documentation, or otherwise) that 13-18 year olds knock out of the park. See http://drupal.org/node/195913 for contest details.
Good news: These students are frickin' awesome. Check out our list of completed tasks so far: http://code.google.com/p/google-highly-open-participation-drupal/issues/list...
Bad news: We need *help* to maintain this momentum.
Ok, well. First, my sincere thanks to the handful of amazing people who heeded my cry for help and created some *excellent* task ideas at http://drupal.org/project/issues/ghop, as well as the team who's been helping with the ongoing GHOP administration/mentoring/reviewing/etc. With your efforts, we were able to add 5 new tasks in the past 48 hours (4 of which have since been claimed), with probably another 5 to come as soon as minor revisions are made. To the rest of you, I don't really know what else to do. I've tried asking for help on the mailing lists. I've tried asking for help on Drupal Planet. I've tried asking for help in IRC. I've tried RE-asking for help on the devel list. I've now tried asking for help on the front page of Drupal.org, as well. We have /tons/ of students who are literally chomping at the bit to work with the Drupal community, and snapping up tasks as quickly as we can make them. And we have /tons/ of stuff around here that needs doing and would make a great learning experience for a student. But yet only a tiny fraction of our community is stepping up to help join those two needs together. It's quite frustating, I have to say. :( We're now down to a whopping *8 available tasks* for students to choose from: http://opentouch.info/tmp/ghop/ghop-stats.html Plone has 70, MoinMoin has 50, and Joomla! and Plone have 35. I know where I would be focusing my energies if I were a student in this contest, and it wouldn't be with Drupal. This is a real shame. The results from the first two weeks of this program were absolutely phenomenal: http://drupal.org/node/200510 -Angie
My earlier idea on having a Simpletest task accompany each module task is a way to double those tasks and improve quality. I know if you have almost no module tasks this does no good! When things are bad it's often interesting to consider radical ideas. What about having the students submit tasks to a moderated queue that then gets approved/rejected. -Bruce Angela Byron <drupal-devel@webchick.net> wrote: Angela Byron wrote:
GHOP: Google Contest. Week-long tasks (coding, documentation, or otherwise) that 13-18 year olds knock out of the park. See http://drupal.org/node/195913 for contest details.
Good news: These students are frickin' awesome. Check out our list of completed tasks so far: http://code.google.com/p/google-highly-open-participation-drupal/issues/list...
Bad news: We need *help* to maintain this momentum.
Ok, well. First, my sincere thanks to the handful of amazing people who heeded my cry for help and created some *excellent* task ideas at http://drupal.org/project/issues/ghop, as well as the team who's been helping with the ongoing GHOP administration/mentoring/reviewing/etc. With your efforts, we were able to add 5 new tasks in the past 48 hours (4 of which have since been claimed), with probably another 5 to come as soon as minor revisions are made. To the rest of you, I don't really know what else to do. I've tried asking for help on the mailing lists. I've tried asking for help on Drupal Planet. I've tried asking for help in IRC. I've tried RE-asking for help on the devel list. I've now tried asking for help on the front page of Drupal.org, as well. We have /tons/ of students who are literally chomping at the bit to work with the Drupal community, and snapping up tasks as quickly as we can make them. And we have /tons/ of stuff around here that needs doing and would make a great learning experience for a student. But yet only a tiny fraction of our community is stepping up to help join those two needs together. It's quite frustating, I have to say. :( We're now down to a whopping *8 available tasks* for students to choose from: http://opentouch.info/tmp/ghop/ghop-stats.html Plone has 70, MoinMoin has 50, and Joomla! and Plone have 35. I know where I would be focusing my energies if I were a student in this contest, and it wouldn't be with Drupal. This is a real shame. The results from the first two weeks of this program were absolutely phenomenal: http://drupal.org/node/200510 -Angie
Bruce Gordon wrote:
My earlier idea on having a Simpletest task accompany each module task is a way to double those tasks and improve quality. I know if you have almost no module tasks this does no good!
When things are bad it's often interesting to consider radical ideas. What about having the students submit tasks to a moderated queue that then gets approved/rejected.
-Bruce
As far as I know it's against the rules for students to propose their own tasks.
Bruce Gordon wrote:
My earlier idea on having a Simpletest task accompany each module task is a way to double those tasks and improve quality. I know if you have almost no module tasks this does no good!
When things are bad it's often interesting to consider radical ideas. What about having the students submit tasks to a moderated queue that then gets approved/rejected.
Much better than _ideas_ (which lots of people have) are actual task _proposals_ (which take actual time/effort to think about and write properly, and is therefore what we really need help with), along with people able and available to mentor them. So if you are offering to take on mentoring of this idea, please read http://groups.drupal.org/node/7360#tasks if you'd like to turn it into an actual task. -Angie
Angela Byron wrote:
Bruce Gordon wrote:
My earlier idea on having a Simpletest task accompany each module task is a way to double those tasks and improve quality. I know if you have almost no module tasks this does no good!
When things are bad it's often interesting to consider radical ideas. What about having the students submit tasks to a moderated queue that then gets approved/rejected.
Oops. Should read all the post first. I do realize that your particular task idea is dependent on module proposals, but I'm trying to stem off yet another "well what if we did something about $thingy?" thing which is ultimately unhelpful and frustrating. To the second point, students /are/ able to submit tasks to the same approval queue as everyone else (http://drupal.org/project/issues/ghop), but they can't claim tasks that they've proposed, due to the contest rules. So that eliminates a lot of the incentive there. However, creating tasks like "Research $foo area and come up with 5 GHOP tasks that could help improve it" _are_ legitimate tasks. But again, it takes people to actually step up and take the time to write them up and do the follow-up mentorship/guidance. *That* is what we need here. Not more ideas. -Angie
participants (8)
-
Adam Light -
adrian rossouw -
Angela Byron -
Bruce Gordon -
catch -
Derek Wright -
Larry Garfield -
Wim Mostrey