We upgraded drupal.org from Drupal 4.3.0 straight to Drupal HEAD. So in good Drupal tradition, we are once again using the development version of Drupal on drupal.org. That is, we (developers) get to "eat our own dog food" and you (users) get to see and test that latest changes. The updated site caters to the each of us with better project pages (check the navigation menu), better performance and improved usability.
Upgrading the site was easy and took no longer than 15 minutes. Though, Kjartan and I spent most of the afternoon implementing small improvements and updating some of the contributed modules that we use here on drupal.org. Everything seems to work fine, but please let us know if you find anything out of whack.
In addition to the upgrade, comment posting for anonymous users has been disabled in an attempt to improve the overall quality of the discussions. We found that many anonymous posters don't take the time to adhere the (minimal) punctuation and capitalization conventions we all learned in elementary school. In future, more and better changes might be implemented to maintain a high quality of content and to improve the quality of our communication.
Lastly, we are considering to reorganize the forums. If you have concrete suggestions for improving the forums (what forums to create, delete, split, merge or group), please let us know in the comments.
Comments
Developer Forums Subcategories
Please could you consider creating sub-forums in Developers forum as discussed here:
http://drupal.org/node/view/3975
It would be nice if projects like WebCalendar as a Module had their own fixed place in the forum where we could go and discuss before any code gets written, then help code/test once work is underway.
It would also help in judging how active a module is being worked on, and where it is going
------------------------------------------
Drupal Specialists: Consulting, Development & Training
Robert Castelo, CTO
Code Positive
London, United Kingdom
----
A forum for each module or theme
Creating a forum for each module or theme is suboptimal as we would have about 150 forums in total, and ever more in future as new modules and themes are added frequently. With the current layout of the forum overview page it would become nearly impossible to read all the forum topics posted in such a large number of forums.
A better idea is to create an additional projects-vocabulary to tie nodes (i.e. forum topics) to projects. The good thing about an additional vocabulary is that it is orthogonal to the existing forum vocabulary. Thus, people could, for example, post a forum topic about the image project to the usage, support and troubleshooting forum but also - and this is the interesting part - filter the usage, support and troubleshooting forum to show image module related problems only. However, for this to work, the project module should be extended to maintain a projects-vocabulary.
Wow
That sounds excellent.
At the moment the Project module limits collaboration, your solution would definetly make developing as a group much quicker and easier.
------------------------------------------
Drupal Specialists: Consulting, Development & Training
Robert Castelo, CTO
Code Positive
London, United Kingdom
----
nice idea
I too like that idea a lot. It would be easy for project.module to add/delete terms from a project vocabulary ... I think you can ignore the problem that might arise if an Admin manually deleted on of those terms
i would rather say: drink you
i would rather say: drink your own champagne instead of eat your own dogfood!
:-)
on a sitenote, since drupal is not on /., it take the stats parameters have been changed?
There are currently 5 users and 2054 guests online.
--
groets
bertb
--
groets
bert boerland
Frequency of Drupal.org upgrade
How often is Drupal.org upgraded? My understanding is that HEAD is always changing. So is Drupal.org running HEAD as it existed on December 6 when you upgraded, or have you upgraded it regularly since then?
The reason I ask is that I'd like to run Drupal HEAD, but I'd like the site to be relatively usable. My guess is that you run cron to upgrade the site to use the latest code on Drupal.org fairly regularly, but I'd like some guidance on this. Is it possible to do this and have a usable site? Please advise.
Upgrading drupal.org
When I'm confident the development tree is stable, I upgrade drupal.org at least once a week. The tree is quite stable now but that is not always the case, especially early on in a development phase. Also, we use a couple of contributed modules such as the image, project and feature module, and sometimes it takes somewhat longer for these modules to catch up with the changes in core. We don't automate upgrades using crontab.