From ricli85 at gmail.com Sun Dec 6 19:44:32 2009 From: ricli85 at gmail.com (Rickard Lindberg) Date: Sun, 6 Dec 2009 19:44:32 +0100 Subject: [icalendar-dev] iCalendar for Timeline Message-ID: <890d8ab70912061044i3d83379cwa70090e40872b51a@mail.gmail.com> Hi, I am the main developer of Timeline (http://thetimelineproj.sourceforge.net/) and we are planning to implement support for ics files. iCalendar seems to provide a good library to do this in Python. So that is our use case. I also have a question. If I read an ics file with iCalendar and then write it out again, is it guarantied to produce the same result? Or are there some things not implemented or not supported that will make me loose data on write? -- Rickard Lindberg From sappj at ieee.org Tue Dec 8 03:34:09 2009 From: sappj at ieee.org (Joe Sapp) Date: Mon, 07 Dec 2009 21:34:09 -0500 Subject: [icalendar-dev] iCalendar for Timeline In-Reply-To: <890d8ab70912061044i3d83379cwa70090e40872b51a@mail.gmail.com> References: <890d8ab70912061044i3d83379cwa70090e40872b51a@mail.gmail.com> Message-ID: <4B1DBB21.6030508@ieee.org> Rickard Lindberg wrote: > I also have a question. If I read an ics file with iCalendar and then > write it out again, is it guarantied to produce the same result? Or > are there some things not implemented or not supported that will make > me loose data on write? In my experience using it, I haven't lost data when writing out a file. The file might get rearranged, but that shouldn't be a concern. It's pretty easy to add or remove components from the structure once it's read in, and unless a component in the file isn't supported (from the documentation, I think it would have to be pretty obscure), I don't see why it wouldn't be written out. Hope this helps, Joe From maccullt at gmail.com Wed Dec 9 05:40:26 2009 From: maccullt at gmail.com (Todd MacCulloch) Date: Tue, 8 Dec 2009 23:40:26 -0500 Subject: [icalendar-dev] Issues around RDATE with PERIOD Message-ID: <872a9f840912082040i5218434evcf13384757f3d58c@mail.gmail.com> I'm working on a small application to filter an exported ICS calendar, removing sensitive information and creating a smaller ICS for publishing on public site, e.g., google. While experimenting with icalendar I found some small problems around RDATE property and specifically RDATE with a list of PERIODs. I'm making some progress with fixes / extensions but I have two questions: 1) How do I run the complete unit tests for the icalendar package? I've got some of the doc tests to work by running the modules but there must be a better / more complete way. 2) Once I've worked out the fixes what do I do? Ask for commit privileges? Who does the code review? (I'm an open source contributor n00b -- sorry). Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://codespeak.net/pipermail/icalendar-dev/attachments/20091208/9d33d0c0/attachment-0001.htm From ricli85 at gmail.com Sat Dec 12 11:30:47 2009 From: ricli85 at gmail.com (Rickard Lindberg) Date: Sat, 12 Dec 2009 11:30:47 +0100 Subject: [icalendar-dev] Distributing icalendar with Timeline Message-ID: <890d8ab70912120230q21115365kee3a030f7b0f8d9a@mail.gmail.com> Hi again, We would like to distribute icalendar along with Timeline so that it is easy for users to install Timeline without thinking about dependencies. I am not sure how to do this with regard to licensing. (Timeline is licenced under GPLv3.) We create a binary debian package for Timeline. Would it be alright if we just included the source files of icalendar? Should we include somewhere were to get the full source package? Similar issues appear for the windows installers. For the source distribution we will put links to your website and instruct users how to install icalendar for use with Timeline. I'm not very experienced with these kinds of things, so I wanted to check with you. -- Rickard Lindberg From sappj at ieee.org Sat Dec 12 17:58:21 2009 From: sappj at ieee.org (Joe Sapp) Date: Sat, 12 Dec 2009 11:58:21 -0500 Subject: [icalendar-dev] Distributing icalendar with Timeline In-Reply-To: <890d8ab70912120230q21115365kee3a030f7b0f8d9a@mail.gmail.com> References: <890d8ab70912120230q21115365kee3a030f7b0f8d9a@mail.gmail.com> Message-ID: <4B23CBAD.7030106@ieee.org> On 12/12/2009 05:30 AM, Rickard Lindberg wrote: > We would like to distribute icalendar along with Timeline so that it > is easy for users to install Timeline without thinking about > dependencies. On Linux (and I would guess *BSD), this is typically handled by package managers. Not only will you probably hear complaints from them if you try to do this, it will be more difficult for users to get updates/security fixes for icalendar (you shouldn't have to worry about releasing a new version for that). > We create a binary debian package for Timeline. Would it be alright if > we just included the source files of icalendar? Should we include > somewhere were to get the full source package? If it doesn't already exist, it would probably be helpful to both projects to create a package for icalendar, make it available somewhere, and let the list know. Ideally, this would be handled downstream by Debian (Ubuntu, etc.). You could file bug requests with distributions you care about. > Similar issues appear for the windows installers. This is kind of tricky. I know pidgin packages a GTK+ runtime with its installer, so packaging the two together may be the route you want to go for Windows. I haven't done any python package installation on Windows, but you should at least try to check if a version >= to what you're bundling is installed if possible. > For the source distribution we will put links to your website and > instruct users how to install icalendar for use with Timeline. This is probably a good idea. The installation instructions for icalendar are pretty easy and are kept in INSTALL.txt . HTH, Joe From ricli85 at gmail.com Sat Dec 12 19:25:20 2009 From: ricli85 at gmail.com (Rickard Lindberg) Date: Sat, 12 Dec 2009 19:25:20 +0100 Subject: [icalendar-dev] Distributing icalendar with Timeline In-Reply-To: <4B23CBAD.7030106@ieee.org> References: <890d8ab70912120230q21115365kee3a030f7b0f8d9a@mail.gmail.com> <4B23CBAD.7030106@ieee.org> Message-ID: <890d8ab70912121025m1a25b52h180e19bbe2b86fec@mail.gmail.com> >> We would like to distribute icalendar along with Timeline so that it >> is easy for users to install Timeline without thinking about >> dependencies. > > On Linux (and I would guess *BSD), this is typically handled by package > managers. ?Not only will you probably hear complaints from them if you try to > do this, it will be more difficult for users to get updates/security fixes for > icalendar (you shouldn't have to worry about releasing a new version for that). > >> We create a binary debian package for Timeline. Would it be alright if >> we just included the source files of icalendar? Should we include >> somewhere were to get the full source package? > > If it doesn't already exist, it would probably be helpful to both projects to > create a package for icalendar, make it available somewhere, and let the list > know. ?Ideally, this would be handled downstream by Debian (Ubuntu, etc.). > You could file bug requests with distributions you care about. > You are right. That is the best way to go. I will try to create a Debian package myself and then share it with you. >> Similar issues appear for the windows installers. > > This is kind of tricky. ?I know pidgin packages a GTK+ runtime with its > installer, so packaging the two together may be the route you want to go for > Windows. ?I haven't done any python package installation on Windows, but you > should at least try to check if a version >= to what you're bundling is > installed if possible. In one of the installers we use py2exe which bundles all libraries. I guess a similar approach to packages could be used on Windows with and installer that just installs the icalendar library. -- Rickard Lindberg From ricli85 at gmail.com Fri Dec 25 12:14:43 2009 From: ricli85 at gmail.com (Rickard Lindberg) Date: Fri, 25 Dec 2009 12:14:43 +0100 Subject: [icalendar-dev] Distributing icalendar with Timeline In-Reply-To: <890d8ab70912121025m1a25b52h180e19bbe2b86fec@mail.gmail.com> References: <890d8ab70912120230q21115365kee3a030f7b0f8d9a@mail.gmail.com> <4B23CBAD.7030106@ieee.org> <890d8ab70912121025m1a25b52h180e19bbe2b86fec@mail.gmail.com> Message-ID: <890d8ab70912250314w5ef97594wf94a979b715b163c@mail.gmail.com> >>> We would like to distribute icalendar along with Timeline so that it is >>> easy for users to install Timeline without thinking about dependencies. >> >> On Linux (and I would guess *BSD), this is typically handled by package >> managers. ?Not only will you probably hear complaints from them if you try >> to do this, it will be more difficult for users to get updates/security >> fixes for icalendar (you shouldn't have to worry about releasing a new >> version for that). >> >>> We create a binary debian package for Timeline. Would it be alright if we >>> just included the source files of icalendar? Should we include somewhere >>> were to get the full source package? >> >> If it doesn't already exist, it would probably be helpful to both projects >> to create a package for icalendar, make it available somewhere, and let the >> list know. ?Ideally, this would be handled downstream by Debian (Ubuntu, >> etc.). You could file bug requests with distributions you care about. >> > You are right. That is the best way to go. I will try to create a Debian > package myself and then share it with you. I have now created a Debian package for icalendar. How would you prefer that I distribute it? I can upload it the SourceForge page for Timeline or you could put it on your website. If you are interested I can share the "debian" files I used to generate the package. Perhaps I will also share it with the Debian community so that they can eventually include it in a release. -- Rickard Lindberg From regebro at gmail.com Fri Dec 25 20:12:36 2009 From: regebro at gmail.com (Lennart Regebro) Date: Fri, 25 Dec 2009 20:12:36 +0100 Subject: [icalendar-dev] Issues around RDATE with PERIOD In-Reply-To: <872a9f840912082040i5218434evcf13384757f3d58c@mail.gmail.com> References: <872a9f840912082040i5218434evcf13384757f3d58c@mail.gmail.com> Message-ID: <319e029f0912251112q5ebf58cre95f4489605c4bc9@mail.gmail.com> On Wed, Dec 9, 2009 at 05:40, Todd MacCulloch wrote: > 1) How do I run the complete unit tests for the icalendar package? I've got > some of the doc tests to work by running the modules but there must be a > better / more complete way. python test.py > 2) Once I've worked out the fixes what do I do? Ask for commit privileges? Yup. But I don't know who can do that. Max? Martijn? > Who does the code review? Bah, humbug, If it works it works. :) -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64 From maxm at mxm.dk Fri Dec 25 22:42:41 2009 From: maxm at mxm.dk (Max M) Date: Fri, 25 Dec 2009 22:42:41 +0100 Subject: [icalendar-dev] Issues around RDATE with PERIOD In-Reply-To: <319e029f0912251112q5ebf58cre95f4489605c4bc9@mail.gmail.com> References: <872a9f840912082040i5218434evcf13384757f3d58c@mail.gmail.com> <319e029f0912251112q5ebf58cre95f4489605c4bc9@mail.gmail.com> Message-ID: <4B3531D1.60207@mxm.dk> Lennart Regebro skrev: > On Wed, Dec 9, 2009 at 05:40, Todd MacCulloch wrote: >> 1) How do I run the complete unit tests for the icalendar package? I've got >> some of the doc tests to work by running the modules but there must be a >> better / more complete way. > > python test.py > >> 2) Once I've worked out the fixes what do I do? Ask for commit privileges? > > Yup. But I don't know who can do that. Max? Martijn? I have bothing to do with acces to the repo. Probably Martijn. From ricli85 at gmail.com Tue Dec 29 12:50:57 2009 From: ricli85 at gmail.com (Rickard Lindberg) Date: Tue, 29 Dec 2009 12:50:57 +0100 Subject: [icalendar-dev] Distributing icalendar with Timeline In-Reply-To: <890d8ab70912250314w5ef97594wf94a979b715b163c@mail.gmail.com> References: <890d8ab70912120230q21115365kee3a030f7b0f8d9a@mail.gmail.com> <4B23CBAD.7030106@ieee.org> <890d8ab70912121025m1a25b52h180e19bbe2b86fec@mail.gmail.com> <890d8ab70912250314w5ef97594wf94a979b715b163c@mail.gmail.com> Message-ID: <890d8ab70912290350v7caf1b24vdbb81147510d863@mail.gmail.com> >>>> We would like to distribute icalendar along with Timeline so that it is >>>> easy for users to install Timeline without thinking about dependencies. >>> >>> On Linux (and I would guess *BSD), this is typically handled by package >>> managers. ?Not only will you probably hear complaints from them if you try >>> to do this, it will be more difficult for users to get updates/security >>> fixes for icalendar (you shouldn't have to worry about releasing a new >>> version for that). >>> >>>> We create a binary debian package for Timeline. Would it be alright if we >>>> just included the source files of icalendar? Should we include somewhere >>>> were to get the full source package? >>> >>> If it doesn't already exist, it would probably be helpful to both projects >>> to create a package for icalendar, make it available somewhere, and let the >>> list know. ?Ideally, this would be handled downstream by Debian (Ubuntu, >>> etc.). ?You could file bug requests with distributions you care about. >>> >> You are right. That is the best way to go. I will try to create a Debian >> package myself and then share it with you. > > I have now created a Debian package for icalendar. How would you prefer that I > distribute it? I can upload it the SourceForge page for Timeline or you could > put it on your website. > > If you are interested I can share the "debian" files I used to generate the > package. Perhaps I will also share it with the Debian community so that they > can eventually include it in a release. I have now uploaded the Debian package of icalendar to http://sourceforge.net/projects/thetimelineproj/files/. -- Rickard Lindberg