DROP

How can China be of services to Drupal -- practically?

john.zhu — Wed, 16 Apr 2008 18:50:06 +0000

We have been pondering about how to best evangelize China into the Drupal community -- and in droves.

After operating in China for two years, and despite of our best trying such as holding the Drupal BootCamp event in Beijing http://www.drupalchina.org/node/3638, our biggest challenge is the practicality of getting Chinese acquainted with Drupal -- BEFORE we can even talk about having them participate into the DROP program, let alone directly contribute into module or theme writing.

Meanwhile, after our Boston DrupalCon session http://boston2008.drupalcon.org/session/drupal-china-how-who-and-why, we were in London for CFUnited Europe http://europe.cfunited.com/, during which we shared our thinking to run a two months long, 50-100 college-students, China Open-Source Summer-Camp (ChinaOpen), in Beijing this summer with excitement built around the sites and sound of the 2008 Olympics.

Within the first two hours, we received 7 Open-Source projects to work on.

That was 1-month ago. And we have been contemplating about how this ChinaOpen can be of direct service to the Drupal community ever since.

Our latest epiphany/idea is to solicit ideas/projects to build web-sites for the non-profit community -- this summer -- in order to “graduate” the ChinaOpen participants into the DROP/SoC program, (say) next summer and give back to a few deserving organizations that need to get the word out but don't have the budget or resources. We imagine some participants may even be able to directly contribute to writing Drupal modules after this.

We could obviously open to For-Profit (kind of like the old “dotcom”) style web-sites/ideas, but we figure this would open the flood-gate too much.

What do you think?

Ideas, suggestions, critics, helping out?

Finally, we are trying to decide, whether this ChinaOpen should be pursued forward this summer, since logistically speaking, we are rapidly approaching the absolute deadline time to get the words out, and arrange all the logistic issues as May will be here in 2-weeks -- which is our other way to ask, for those of you who have participated either DROP or SoC before:
-- What kind of general rule-of-thumb in terms of operational-support that we should estimate?
-- For example, for each student, how much "mentoring" and backoffice support that we would need to factor?

Thanks!

SoC 2008

Best Way to Get In Contact With Your Task's Mentor?

nikkiana — Thu, 13 Mar 2008 01:16:16 +0000

Perhaps the answer to this question is blatantly obvious and I'm just being oblivious, but I wanted to ask publicly just in case anyone else is unclear as well. Besides going onto IRC and tracking down the mentor of the task you're working on (which may or may not be useful depending on if you're both actually online at the same time), what's the best way of contacting the mentor in charge? Posting a comment on the task? Leaving a message in this group?

DROP

Views 2 Drop tasks

catch — Tue, 11 Mar 2008 20:54:19 +0000

It looks like there's going to be an explosion in the number of people doing Drop tasks soon (see http://lists.drupal.org/archives/development/2008-03/msg00105.html for more), so it'd be good to get some Views 2 ones up.

merlinofchaos mentioned that although he has a bunch of stuff which could be done, he doesn't enough time to write them all up properly. So I figured this wiki would be a decent way of speccing out potential tasks so we can distribute the work of writing them up for Drop and as issues on the views queue.

So feel free to post ideas here or write up tasks already posted. Would be handy if people could use <del></del> tags when they've transferred something over.

We don't need to keep track of anything on here - Drop and the issue queue are for that, hopefully it should just be a quick way to get the tasks written up.

Views Developers

SimpleTest DROP Tasks

cwgordon7@drupal.org — Tue, 11 Mar 2008 00:00:30 +0000

Some SimpleTests would make great DROP tasks. So I propose we create a list of the most-needed SimpleTests, and at any given time, the top 3-5 are active DROP tasks. Edit the table below; I'll be updating the DROP issue queue(s) as necessary.

Take a look at http://groups.drupal.org/node/9408 ... here are the first items from that list that I see ... chx has asked that he be contacted if you begin working on an item from his list

Title	Description	Status
blog_module	User has access to create, edit or delete their own blog entries when given the permission. User has access to create, edit or delete any blog entries when given the permission. Verify the “View recent blog entries” links to the user's blog page. (Url: blog/%uid) Verify the “View recent blog entries” link is on the user page when they have permission to create blog entries. (Url: user/%uid) Displays help information on the help page and only viewable for users that have access into the admin area. (Url: admin/help/blog) Display a blog editing form when viewing the url node/%nid/edit and the user has permission to edit blog entries. Check for both permissions (edit own blog entries and edit any blog entry). Verify the breadcrumbs are being displayed on the blog pages. Adds a link to the user's blogs on the blog page and the full node view of the blog. Display a blog feed starting with the latest blog. (Url: blog/feed) Display a blog feed per user when that user has permission to create a blog. (Url: blog/%uid/feed) Display a blog page per user when that user has permission to create a blog. (Url: blog/%uid) Display a blog page containing all published blogs. (Url: blog) Display a recent blogs block when the block is enabled.	Posted to DROP site.
color_module	Suggested tests needed....	Awaiting suggested tests.
dblog_module	Displays help information on the help page and only viewable for users that have access into the admin area. (url: admin/help/blog) Setting the database logging settings to 100 (url: admin/reports/page-not-found). Fill up the error log with more then 100 and verify that it only keeps hundred. Displays the database log and only user with admin rights are able to access it. (url: admin/reports/dblog) Displays a listing of page not found and only user with admin rights are able to access it. (url: admin/reports/page-not-found) Displays a page listing of pages that users do not have access to. (url: admin/reports/access-denied) Displays a page listing with more detail of the event. (url: admin/reports/event/%) Verify that css is being applied on admin/reports pages. When cron gets run the watchdog table gets clean up per the user's setting or the default settings. Deleting a user the watchdog table gets updated from the current user id to user id of 0. Verify watchdog table has the new errors inserted into it. Only users with access to the admin section have access to the watchdog logs. The watchdog types getting returned from the database is returned as an array.	Posted to DROP site.
statistics_module	Enable node view counter Create a node View it with another user Check the counter is now 2 Check that the user's tracker contains the node View it with anonymous Check the counter is now 3 View it with anonymous but page cache on Check the counter is now 4 Check that the node is in recent hits	Posted to DROP site.
Help Module	When a module does not have help info it should display “No help is available for module %module_name”. When the module does have help info then it should display the help information. Check to make sure help page exists and only users with permission have access rights.	Awaiting suggested tests.
Node module	Create a node. Assure that the operation was successful. Edit an existing node. Assure that the operation was successful. Delete an existing node. Before delete, check that the rss.xml contains the new node and that the new node is on the home page (i.e. test the /node callback). Filter the admin/content/node page and then apply each operation in the dropdown and assure that is succeeded Create, rename, and delete a content type and assure that it succeeds as expected. Check that the node_info hook is fired (or whatever it is called when you rename a content type). Put simpletest_nodeapi() in a test and just record there each call to the API. Create/Edit/Delete a node and assure that all the nodeapi hooks are called. Create a node and render it. Assure that the title, body, date, links, etc. are visible upon display. Create a new revision of an existing node. Revert to a previous revision of an existing node.	Awaiting suggested tests.
openid_module	Awaiting suggested tests.	Awaiting suggested tests.
php_module	The help PHP filter help information is on the php help page and the link to the admin help page is on the help page. (admin/help and admin/help/php) User with permission to post php can post php and users with no permission can't post any php. Ensure the filter tips page the php filter information. (filter/tips) Ensure that the php filter option is available when customizing input formats. (admin/settings/filters/1)	Awaiting suggested tests.
ping_module	Awaiting suggested tests.	Awaiting suggested tests.
taxonomy_module	[Starter list, many more needed. Please crosspost tests status / thoughts to the taxonomy group.] User has access to create, edit or delete any vocabulary when given the 'administer taxonomy' permission. User has access to create, edit or delete any taxonomy term when given the 'administer taxonomy' permission. Display a teaser list of nodes for each taxonomy term. (Url: taxonomy/term/%tid) Display an RSS feed per taxonomy term. (Url: taxonomy/term/%tid/0/feed) Display a teaser list of nodes for a union of taxonomy terms. (Url: taxonomy/term/%tid1+%tid2) Display an RSS feed for a union of taxonomy terms. (Url: taxonomy/term/%tid1+%tid2/0/feed)	Awaiting suggested tests.
throttle_module	Ensure the throttle admin page has been created. (admin/settings/throttle) The admin help page has a link to the throttle help page and the throttle help page exists. Other modules are able to access the throttle status to turn on certain features when the server is under heavy load with $throttle = module_invoke('throttle', 'status'); Setting up the throttle settings (admin/settings/throttle) with x number of anonymous user online and x number of authenticated user online. When the specific numbers are hit the throttle module is run. Enter in non-numeric values in the throttle admin page in the auto-throttle on anonymous users and auto-throttle on authenticated users fields.	Awaiting suggested tests.
tracker_module	Link provided on the help page (url: admin/help) Tracker help page exists (url: admin/help/tracker) User page contains the track link. User id 1 can view track post and page visits. All other users can track posts. Check to see if tracker/all page exists and only logged in users can view the page.	Awaiting suggested tests.
system_module	Awaiting suggested tests.	Awaiting suggested tests.

DROP

Ready to DROP!

qbnflaco — Fri, 07 Mar 2008 21:11:41 +0000

I just want to say how great is was this past week at Drupalcon. There's such a great vibe in the air with everyone working together. I'm also glad I learned about the DROP project. I myself work as a themer on a totally different CMS. However, I'm very insterested in getting into drupal and being able to develop my own modules. After hearing about Summer of Code and GHOP, both aimed at students, it's nice to know there's also room for us non-students to be mentored on drupal!

DROP

Drupal 7 Usability Linkstorm

birdmanx35@drupal.org — Sun, 24 Feb 2008 01:10:48 +0000

In order to draw attention to the biggest feature in Drupal 7, Usability, let's all collectively look through our resources for our best Usability links, tips, and tricks! Post them below in the comments, with commentary (pun intended) on how they could be implemented in Drupal. If you are feeling inspired, tackle one with a patch (or mentor a DROP task).

Usability

Welcome to DROP!

birdmanx35@drupal.org — Thu, 21 Feb 2008 23:34:25 +0000

I'd just like to give a warm welcome to everyone involved with DROP- students, mentors, and admins alike! For those of you that don't know, DROP is a successor to the just-closed GHOP program- we want all that learning and contributing to continue all year. So, head on over to the DROP site, sign up for a task, or create one yourself. Let us know how we can help you!

Google Highly Open Participation Contest (GHOP)