I installed Ruby, Rails, Gems, Tracks, etc on Ubuntu 8.04 last night and am so far very pleased.

I am very new to Ruby, Tracks, etc but not new to Linux.

I found a few posts to allow emails to be sent to a monitored email address which will create a task/todo out of that email.  I will be tackling that as my next project.  Has anyone written the complete “how-to” on the proper way to handle this emailing into Tracks issue, or are the forum threads the best option?

Also - Is there a way to get Tracks setup to accept file attachments to an Action or a Note?

I have a few items required for me to use a GTD system and emailing tasks with attachments as well as file attachments are certainly at the top of that list.

Are these items scheduled for future releases?

thank you for your time,
Michael

I’ve documented my personal solution here, which uses a perl script to ‘forward’ and email from sendmail to tracks

http://www.balt.nu/lrbalt/archives/2006/10/03/email-tracks-integration/

Eric is working on better email integration in Tracks, but there is no specific date for that (“when it is ready”

There is currently no way to attach a file to a task. It is high on the wish list though…

Hi,

I am working with another developer on adding file attachments to notes and tasks.  We are using the attachment_fu plug in and we have it working on our end.  We will post it to git when we get it working for potential inclusion into Tracks.

Matt

Also, we are working on a backgroundrb script to monitor an email address for each user to add tasks to tracks, along with whatever files are attached to them.  This is a little bit rougher right now than the file attachments, but we will post this to github as well for inclusion into the main branch.

Matt

very cool! Are you guys on github?

Would be very nice to also have an api besides the backroundrb script to push email with attachments, but that’s just my setup…

I am getting setup on github so that we can contribute our changes back.  Once we get our first round of enhancements put together with the attachments and emailing capability, we can look at adding an api.  It doesn’t seem like it would be too difficult to setup a RESTful set of apis for task management, but I haven’t looked at that part in all that much detail yet.

I think is wise indeed to first getting attachments working before adding api’s and stuff.

There is already an REST and SOAP api for task management, but is does not support attachments (of course). There are scripts around to push email to that api to add tasks to Tracks. So, it’s a matter of adding attachments to the api.