time

We are NYC-based (USA) Web & Mobile App Development and Design Company with 50+ developers in Ukraine and Goa.

We are currently looking for Drupal developers from Bangladesh who can work from our Dhaka office.

If you are interested or if you know anyone with such expertise, please provide us the following information about the developer:

• Resume
• Salary expectation
• Education
• Years of experience
• Skill details
• Portfolio / websites URL the developer has worked on (in any)
• Current job (if any)
• Current location
• Gender
• Age
• Contact Number
• Email

Allo,

Connaissez-vous des modules de gestion du temps qui fonctionnent en drupal 6 ?
Nous cherchons à gérer des agenda en drupal, avec case tracker, pour rajouter des alertes, par exemple.

Nous avons essayer due date, time tracker, case tracker time, sans grand succès.

Merci !!

I am in the market for a VPS in the 15ドル-30ドル/mth range, and I've been shopping it around with the help of some feedback I've received from the WebHostingTalk forums. So I came up with a few new benchmarking tests that I haven't seen mentioned before. The results of my benchmarks can be found here: HTML format and Spreadsheet format

The new tests using time+drush+devel I came up with are:

1. time drush generate users 2000 - This test will give you the amount of time it took to create 2000 users on your drupal site
2. time drush generate content 5000 2 - This test will give you the amount of time it took to create 5000 nodes (page,story,book,blog,forum) with 7500 comments
3. time drush generate taxonomy 15 250 - This test will give you the amount of time it took to create 15 vocabulary with 250 terms

My appologises if this has already been discussed but I was wondering if there is a patch (or otherwise) which allows the signup schedule module to more exactly specify the opening and closing time than just midnight on the said day. And if there isn't I was hoping someone would be willing to create said patch as I think it would be very useful for event signups to give more control over the signup period.

for my issue tracking needs at my day job (http://www.cs.wisc.edu/condor), we'd like to start keeping track of how long we spend on a given issue. mostly, we'd use this for our internal development tasks, not so much the "helpdesk" style end-user support (though i could see us caring about time spent in those issues, too).

clearly, this is something a lot of issue tracking systems already support, and lots of people need this kind of functionality (though often in more corporate environments). however, i'm not sure we'd want anything like this in the issue queues for drupal.org (though i'm not really sure... i could potentially see it being useful, even there, though for different reasons). generally, i'm leaning away from wanting to have any of this functionality on drupal.org.

In my opinion, the use of timestamps for the representation of dates in Drupal core is problematic. It is fine for recording all events that happen now, and it is even fine for recording historical events, as long as they happened 1970 or later. They are utterly useless if you want to make a geneology site.

More disturbingly, the event module also relies on timestamps for representation of events. As far as I can tell, this is a huge limitation. The CCK date field uses the ISO 8601 standard which saves times as as string: 20060610T20:47:48+01:00. While there are lots of arguments about how the data should be persisted in the database, to me, it is clear that the ISO 8601 string is ideal for representing the date in Drupal code (unless you're doing archeology, then I've got no idea what you do with BC dates).