-
+1
Sorting out HOW to develop is an onerous as sorting out what you want your code to do in the first place. There's no ... developer roadmap, for lack of a better term. A "So you wanna help write WordPress code?" Even trying to sort out how to tell someone how to get involved in the WP language packs is convoluted.
-
The most intriguing thing to me about the drupal post is that my thoughts and feelings are just like his but for the developers and the WordPress.org website. Drupal.org appears to be shaped around development while WordPress.org is shaped around the ease of using the software and showcasing how it can be used and who is using it.
One of the things I've been waiting to see happen is a major overhaul of WordPress.org so that it can keep all the ease of use up front to the user but also provide a roadmap for everyone else. The developer parts of the project are like Islands and unless you really know where to go or where to look, finding a bridge to get to that island is difficult. I'm not sure if you can easily mix typical end user content with developer content all on one site. It seems it would be best for the WordPress.org website to be the trunk of a tree with branches to a developer portal and an end user portal. but then, I'm not sure making more islands would be the correct way to go about things.
It's just interesting to me that the main argument made in that thread can me made for WordPress.org but the opposite end of the spectrum.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules