phpicalendar-devel Mailing List for PHP iCalendar

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

anyone home?

bill.

Hi Mikhael,

Mikhael MYARA <my...@op...> 
am Mittwoch,  9. September 2015, 10:53:05:

>  I would like
> to add the display of the  « location » field to the Week View. I
> don’t know if this is simply a problem of configuration or if I
> should have some code (perhaps in the default template file ?). 

I am sorry, but that is no simple configuration thing, but you may want
to have a look at functions/template.php -> function draw_week() as a
starting point for havin a look where to add code, as far as I'd think.

Greetings,
Alek

Dear all,

   I installed today phpicalendar, a beautiful software. I would like to add the display of the  « location » field to the Week View. I don’t know if this is simply a problem of configuration or if I should have some code (perhaps in the default template file ?). May someone help ?

   Best Regards,
     Mike

Hi,

Just wanted to drop you a quick note thanking you for phpicalendar.  I needed a quick and dirty way of sharing my iCal calendar with my boss (who only runs Linux), so was looking for a php/web based solution.  phpicalendar fits the bill perfectly.

One slight problem though.  I'm using the $list_webcals array in config.inc.php to automatically pull in my calendar that I share using Apple's iCloud (formerly MobileMe) service.  The URL they use for sharing calendars is a long and nasty one that looks like this:

webcal://p03-www.icloud.com/ca/subscribe/1/Y_jEnt59gNQZbG1l9AbOuw5Pq4EU0fk07eHmgNsXbvjnSv7HNqpLLKjgOSQtNTKh

Well, believe it or not, it works, except that in the legend showing all available calendars, instead of a pretty name (e.g. "Work calendar") it shows a long and nasty string of alphanumeric characters.  Here's a screenshot showing what I mean:

http://dl.dropbox.com/u/169813/phpicalendar_fail.jpg

It would be nice if there were some way to set a custom display name for calendars listed in $list_webcals.

Other than that, very happy with the software.  Thanks for writing this and making it available.

Cheers,
Donald
-- 
Donald Burr
E-mail: db...@bo...
Website: http://DonaldBurr.com/

On Dec 6, 2010, at 11:02 AM, Jim Hu wrote:
> I think there are many good suggestions here, including the core one of moving on to phpicalendar 3.  My only problem with switching to Git/Mercurial and Trac is that I think it's beneficial to maintain a presence on Sourceforge.  But we could at least move to subversion while staying on Sourceforge.
> 

Git and Trac are features that can be enabled on SourceForge. Again, I don't have any practical experience with Git, but I highly recommend it (a distributed SCM) over CVS and SVN. There's a learning curve to it, but I would argue it's easier to understand and work with than either of the two former options.

> I also think that despite my intention to get back to phpicalendar, the data from the past couple of years indicate that I'm not putting in the time needed for the project.
> 
> Jim
> 

While PHPiCalendar is a fairly popular project, it doesn't see a whole lot of regular updates.  My primary motivation so far has been using it in a production environment within my workplace.  It's entirely likely that once I move on, I won't be around any longer to help maintain it.  So, no worries there, Jim.

On Dec 3, 2010, at 4:40 PM, Jason Oster wrote:

> TL;DR:
>
> 1) Scrap phpiCalendar 2.x.
> 2) Pick up work on phpiCalendar 3.x. (Follow coding and style  
> conventions!)
> 3) Move the code to Git or Mercurial.
> 4) Move the issue tracker to Trac.
> 5) Reimplement the user interface in CSS3 using a simple template  
> engine
> like phpSavant.

+1 to the concept, certainly.

I'm not great fan of Mercurial or Git. Of the two, I think that Git is  
a wiser choice, in that you won't be excluding quite as many people  
due to SCM-ignorance. However, I think that svn is a wiser move, in  
terms of learning curve. Of course, I suppose that's wholly a matter  
of preference.

The more modular and OO the code can become, the easier it is for  
someone to plug into the development effort without having to  
understand every other part perfectly, but learn it over time.

--
Rich Bowen
rb...@rc...

On Dec 3, 2010, at 3:40 PM, Jason Oster wrote:

> This may not be the most popular mailing list ever, but I need to throw 
> the idea out there: It's time to reboot phpiCalendar.
> 
> phpiCalendar 3 was in the planning stages for a while, but fell out of 
> development while the 2.x series saw most of the work (in the form of 
> maintenance).  At this point, maintaining the 2.x branch is getting very 
> difficult.  There's a lot of weird code in it, no standard code style, a 
> custom template engine (which would require significant PHP transplants 
> to actually re-style some things, like the week view), ...
> 
> As far as I can tell, phpiCalendar was actively maintained by the 
> original developers, where it saw a great deal of development, but also 
> received its fair share of hacks and workarounds to get it to where it 
> is today.
> 
> The size of the codebase is quite significant, even for an ICS parser. 
> An ideal parser could probably be written in about half as many lines, 
> and be more robust and accurate.
> 
> I really liked Jim Hu's idea when he started on phpiCalendar 3: an 
> object-oriented API for the parser, which can be made reusable in other 
> projects.  (Or at least, that's what I was able to infer from the random 
> forum and list posts.)
> 
> So I had a brief (very brief) look at the phpicalendar3 repo at SF, and 
> the code looks nice.  The code looks *really nice*, but there's a lot 
> missing, and a lot of TODOs sprinkled throughout.
> 
> I would like to make a proposal, and I'll wait another year if I have 
> to, until I get some feedback on the thought.  But it would be a good 
> time to drop support for the 2.x branch, and focus on 3.x.  I believe 
> it's also important to move from CVS to Mercurial or Git.  (I have 
> practical experience with Mercurial, but I am very interested in using Git!)
> 
> And not only replacing the SCM, but also the issue tracker.  SF's 
> default issue tracker is ugly, hard to navigate, and doesn't provide any 
> information beyond what users think is broke, and what developers think 
> is fixed.  My suggestion for a replacement is Trac.
> 
> *AND THEN* there's the issue of actually writing some code to make 
> phpiCalendar 3 happen.  I'm considering hacking on the current base 
> repo, rather than rebooting even that.  There may be some big 
> architectural changes that I want to make, though.  The most obvious 
> example: I don't believe every feature of the ICAL spec needs its own 
> class.  That sounds like OOPs-overkill, to me.  Jeff Atwood's lovely 
> (and aptly named!) Coding Horror blog covers the problem well enough 
> without reiteration:
> 
> http://www.codinghorror.com/blog/2007/03/your-code-oop-or-poo.html
> 
> But it's probably a safe bet that the whole thing won't necessarily be 
> scrapped.
> 
> Next, it needs a user interface.  The 2.x branch is actually quite 
> pretty.  You'd never know how terrible the PHP is, just by looking at 
> one of the rendered calendars!  So yeah, that came as quite a shock when 
> I dived in for my first bug fix.  This interface needs to be there, 
> ported in some form.
> 
> The CSS (and the HTML) will see some serious overhaul, for certain. 
> CSS3 is widely supported, itself supporting features like drop-shadows, 
> which the current templates simulate using GIF images.  The template 
> engine needs some TLC, as well.  My suggestion at this time is using a 
> very simple template engine called phpSavant:
> 
> http://phpsavant.com/
> 
> It's a template engine without its own special language syntax. 
> Instead, you just use PHP when you need to iterate over data (page 
> content), rather than the clunky, proprietary macro-things provided by 
> engines like Smarty.
> 
> This means that pure template designers are pretty much screwed when 
> they don't know PHP, but that problem can be eradicated with
> 
> <?php require_once('draw_week.php'); ?>
> 
> at the top, and
> 
> <?php draw_week_header(); ?>
> 
> wherever the template wants to place the HTML for the week header, etc. 
>  It still presents a Model-View-Controller level of separation.
> 
> 
> TL;DR:
> 
> 1) Scrap phpiCalendar 2.x.
> 2) Pick up work on phpiCalendar 3.x. (Follow coding and style conventions!)
> 3) Move the code to Git or Mercurial.
> 4) Move the issue tracker to Trac.
> 5) Reimplement the user interface in CSS3 using a simple template engine 
> like phpSavant.

I think there are many good suggestions here, including the core one of moving on to phpicalendar 3.  My only problem with switching to Git/Mercurial and Trac is that I think it's beneficial to maintain a presence on Sourceforge.  But we could at least move to subversion while staying on Sourceforge.

I also think that despite my intention to get back to phpicalendar, the data from the past couple of years indicate that I'm not putting in the time needed for the project.

Jim

> 
> ------------------------------------------------------------------------------
> Oracle to DB2 Conversion Guide: New IBM DB2 features make compatibility easy. 
> Learn about native support for PL/SQL, new data types, scalar functions, 
> improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, 
> best practices and more - all designed to run applications on both DB2 and 
> Oracle platforms. http://p.sf.net/sfu/oracle-sfdev2dev
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054

This may not be the most popular mailing list ever, but I need to throw 
the idea out there: It's time to reboot phpiCalendar.

phpiCalendar 3 was in the planning stages for a while, but fell out of 
development while the 2.x series saw most of the work (in the form of 
maintenance).  At this point, maintaining the 2.x branch is getting very 
difficult.  There's a lot of weird code in it, no standard code style, a 
custom template engine (which would require significant PHP transplants 
to actually re-style some things, like the week view), ...

As far as I can tell, phpiCalendar was actively maintained by the 
original developers, where it saw a great deal of development, but also 
received its fair share of hacks and workarounds to get it to where it 
is today.

The size of the codebase is quite significant, even for an ICS parser. 
An ideal parser could probably be written in about half as many lines, 
and be more robust and accurate.

I really liked Jim Hu's idea when he started on phpiCalendar 3: an 
object-oriented API for the parser, which can be made reusable in other 
projects.  (Or at least, that's what I was able to infer from the random 
forum and list posts.)

So I had a brief (very brief) look at the phpicalendar3 repo at SF, and 
the code looks nice.  The code looks *really nice*, but there's a lot 
missing, and a lot of TODOs sprinkled throughout.

I would like to make a proposal, and I'll wait another year if I have 
to, until I get some feedback on the thought.  But it would be a good 
time to drop support for the 2.x branch, and focus on 3.x.  I believe 
it's also important to move from CVS to Mercurial or Git.  (I have 
practical experience with Mercurial, but I am very interested in using Git!)

And not only replacing the SCM, but also the issue tracker.  SF's 
default issue tracker is ugly, hard to navigate, and doesn't provide any 
information beyond what users think is broke, and what developers think 
is fixed.  My suggestion for a replacement is Trac.

*AND THEN* there's the issue of actually writing some code to make 
phpiCalendar 3 happen.  I'm considering hacking on the current base 
repo, rather than rebooting even that.  There may be some big 
architectural changes that I want to make, though.  The most obvious 
example: I don't believe every feature of the ICAL spec needs its own 
class.  That sounds like OOPs-overkill, to me.  Jeff Atwood's lovely 
(and aptly named!) Coding Horror blog covers the problem well enough 
without reiteration:

http://www.codinghorror.com/blog/2007/03/your-code-oop-or-poo.html

But it's probably a safe bet that the whole thing won't necessarily be 
scrapped.

Next, it needs a user interface.  The 2.x branch is actually quite 
pretty.  You'd never know how terrible the PHP is, just by looking at 
one of the rendered calendars!  So yeah, that came as quite a shock when 
I dived in for my first bug fix.  This interface needs to be there, 
ported in some form.

The CSS (and the HTML) will see some serious overhaul, for certain. 
CSS3 is widely supported, itself supporting features like drop-shadows, 
which the current templates simulate using GIF images.  The template 
engine needs some TLC, as well.  My suggestion at this time is using a 
very simple template engine called phpSavant:

http://phpsavant.com/

It's a template engine without its own special language syntax. 
Instead, you just use PHP when you need to iterate over data (page 
content), rather than the clunky, proprietary macro-things provided by 
engines like Smarty.

This means that pure template designers are pretty much screwed when 
they don't know PHP, but that problem can be eradicated with

<?php require_once('draw_week.php'); ?>

at the top, and

<?php draw_week_header(); ?>

wherever the template wants to place the HTML for the week header, etc. 
  It still presents a Model-View-Controller level of separation.

TL;DR:

1) Scrap phpiCalendar 2.x.
2) Pick up work on phpiCalendar 3.x. (Follow coding and style conventions!)
3) Move the code to Git or Mercurial.
4) Move the issue tracker to Trac.
5) Reimplement the user interface in CSS3 using a simple template engine 
like phpSavant.

Dear developers,

Find attached a non-intrusive patch that adds an agenda view to
phpicalendar (upstream cvs).

This is a particularly useful feature for managing a seminar or a series of
talks with different speakers. My patch contains some logic with this
application in mind (like splitting an event name "Speaker - Title" into its
components), but it should with minor modifications work just as well for other
applications. Find an example website here:
http://www2.informatik.hu-berlin.de/logik/lehre/SS10/MitarbSem/

I'd be very happy if this patch could be included into the main repository.
$ patch -p1 < agenda_patch.diff

You can also see the changes here:
http://github.com/yllohy/phpicalendar/commit/28ff9e3adb4ac36a4a6ac84cce29b0c5422a16df

Best,
Holger.

Version 2.4 represents a lot of big changes, mostly under-the-hood.  
Over a year of development went into this one.  We've released some 
release candidates over the last month, and it's proven to be fairly 
stable so far.  There is just one thing I need to fix before it finally 
launches: 
http://phpicalendar.net/forums/viewtopic.php?f=45&t=4140#p14451 
<http://phpicalendar.net/forums/viewtopic.php?f=45&t=4140#p14451>

A big THANK YOU! to all of our testers for this one.  It's been a long 
haul, and the wait will definitely be worth it.

While I'm at it, I'd like to get some additional feedback on the current 
version in CVS.  If anything major jumps out at you, please post here or 
on the forums.  With any luck, I'll be pushing RC6 soon with the 
previously mentioned bug fixed, and it will land as v2.4 final.  Any 
bugs that aren't caught between now and then will become features of 
v2.4.  :P

Finally, I'd also like to point out that I've been working on v2.5, as 
well. It's going to be the next big release, and I have some nice plans 
for it:

    * Allow HTML in event descriptions throughout the phpiCalendar
      system.  (Event pop-up windows, Nicetitle/tool tip/hover thingies,
      etc.)
    * Rewrite a good deal of the CSS to use new CSS3 features like drop
      shadows, rounded borders, background gradients, and just make
      phpiCalendar look even prettier.
    * Maybe some AJAX-ish features like replacing those pop-up windows
      with content-modal hovering divs; which is a popular thing to do
      today, and looks a *lot* prettier.
    * Fix all those calendar display name issues!!
    * And more!

I'm fine with any of the "you can do pretty much whatever you want"  
licenses.
--
Wesley Miaw
we...@we...

On Sep 10, 2009, at 11:29 AM, Chad Little wrote:

> BTW this was me preferring to just move to the Apache License.
>
> -C
>
> On Sep 10, 2009, at 8:29 AM, Chad Little wrote:
>
>> Yep,
>>
>> http://www.apache.org/licenses/LICENSE-2.0
>>
>>
>>
>> On Sep 10, 2009, at 8:00 AM, Rich Bowen wrote:
>>
>>> Or, you could go all the way to ASL2.0 and make even more people  
>>> happy.
>>>
>>> On Sep 10, 2009, at 10:58 AM, Jim Hu wrote:
>>>
>>>> Does anyone have a problem with making a change from GPL to LGPL?
>>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: Steven Oxley <ste...@gm...>
>>>>> Date: September 10, 2009 9:31:48 AM CDT
>>>>> To: Jim Hu <ji...@ta...>
>>>>> Subject: Re: Licensing Issues
>>>>>
>>>>> I believe that is all that would be required, but everyone who  
>>>>> has contributed code to the project has a copyright to their  
>>>>> code and in order to release their code under a different  
>>>>> license, their consent would be required.  (At least that's what  
>>>>> I have picked up from other open source projects I've been  
>>>>> "around").
>>>>>
>>>>> Steven Oxley
>>>>>
>>>>> On Thu, Sep 10, 2009 at 10:27 AM, Jim Hu <ji...@ta...> wrote:
>>>>> Hi Steven,
>>>>>
>>>>> That would be OK with me.  Not being a licensing expert, do I  
>>>>> just change the license file?
>>>>>
>>>>> Jim
>>>>>
>>>>> On Sep 10, 2009, at 9:01 AM, Steven Oxley wrote:
>>>>>
>>>>>> Hi guys,
>>>>>>
>>>>>> I was looking at the PHP iCalendar package you have on  
>>>>>> sourceforge and I was thinking that I might like to use some of  
>>>>>> the iCalendar parsing code in a library of my own.  The problem  
>>>>>> is that your license is GPL v2 and I will be using this  
>>>>>> "library" that I want to create in a software package that I  
>>>>>> cannot release under GPL v2.  I was wondering if it might be  
>>>>>> possible to release the parsing code under LGPL so that I can  
>>>>>> modify it and use it in my own code without having to release  
>>>>>> my entire software package under GPL v2.
>>>>>>
>>>>>> Thanks for considering it,
>>>>>> Steven Oxley

BTW this was me preferring to just move to the Apache License.

-C

On Sep 10, 2009, at 8:29 AM, Chad Little wrote:

> Yep,
>
> http://www.apache.org/licenses/LICENSE-2.0
>
>
>
> On Sep 10, 2009, at 8:00 AM, Rich Bowen wrote:
>
>> Or, you could go all the way to ASL2.0 and make even more people  
>> happy.
>>
>> On Sep 10, 2009, at 10:58 AM, Jim Hu wrote:
>>
>>> Does anyone have a problem with making a change from GPL to LGPL?
>>>
>>> Begin forwarded message:
>>>
>>>> From: Steven Oxley <ste...@gm...>
>>>> Date: September 10, 2009 9:31:48 AM CDT
>>>> To: Jim Hu <ji...@ta...>
>>>> Subject: Re: Licensing Issues
>>>>
>>>> I believe that is all that would be required, but everyone who  
>>>> has contributed code to the project has a copyright to their code  
>>>> and in order to release their code under a different license,  
>>>> their consent would be required.  (At least that's what I have  
>>>> picked up from other open source projects I've been "around").
>>>>
>>>> Steven Oxley
>>>>
>>>> On Thu, Sep 10, 2009 at 10:27 AM, Jim Hu <ji...@ta...> wrote:
>>>> Hi Steven,
>>>>
>>>> That would be OK with me.  Not being a licensing expert, do I  
>>>> just change the license file?
>>>>
>>>> Jim
>>>>
>>>> On Sep 10, 2009, at 9:01 AM, Steven Oxley wrote:
>>>>
>>>>> Hi guys,
>>>>>
>>>>> I was looking at the PHP iCalendar package you have on  
>>>>> sourceforge and I was thinking that I might like to use some of  
>>>>> the iCalendar parsing code in a library of my own.  The problem  
>>>>> is that your license is GPL v2 and I will be using this  
>>>>> "library" that I want to create in a software package that I  
>>>>> cannot release under GPL v2.  I was wondering if it might be  
>>>>> possible to release the parsing code under LGPL so that I can  
>>>>> modify it and use it in my own code without having to release my  
>>>>> entire software package under GPL v2.
>>>>>
>>>>> Thanks for considering it,
>>>>> Steven Oxley
>>>>
>>>> =====================================
>>>> Jim Hu
>>>> Associate Professor
>>>> Dept. of Biochemistry and Biophysics
>>>> 2128 TAMU
>>>> Texas A&M Univ.
>>>> College Station, TX 77843-2128
>>>> 979-862-4054
>>>>
>>>>
>>>>
>>>
>>> =====================================
>>> Jim Hu
>>> Associate Professor
>>> Dept. of Biochemistry and Biophysics
>>> 2128 TAMU
>>> Texas A&M Univ.
>>> College Station, TX 77843-2128
>>> 979-862-4054
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports  
>>> 2008 30-Day
>>> trial. Simplify your report design, integration and deployment -  
>>> and focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
>>> Phpicalendar-devel mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>>
>> --
>> Rich Bowen
>> rb...@rc...
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports  
>> 2008 30-Day
>> trial. Simplify your report design, integration and deployment -  
>> and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
>> Phpicalendar-devel mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

I'm OK with LGPL.

On 09/10/2009 07:58 AM, Jim Hu wrote:
> Does anyone have a problem with making a change from GPL to LGPL?
>
> Begin forwarded message:
>
>> *From: *Steven Oxley <ste...@gm...
>> <mailto:ste...@gm...>>
>> *Date: *September 10, 2009 9:31:48 AM CDT
>> *To: *Jim Hu <ji...@ta... <mailto:ji...@ta...>>
>> *Subject: **Re: Licensing Issues*
>>
>> I believe that is all that would be required, but everyone who has
>> contributed code to the project has a copyright to their code and in
>> order to release their code under a different license, their consent
>> would be required. (At least that's what I have picked up from other
>> open source projects I've been "around").
>>
>> Steven Oxley
>>
>> On Thu, Sep 10, 2009 at 10:27 AM, Jim Hu <ji...@ta...
>> <mailto:ji...@ta...>> wrote:
>>
>>     Hi Steven,
>>
>>     That would be OK with me. Not being a licensing expert, do I just
>>     change the license file?
>>
>>     Jim
>>
>>     On Sep 10, 2009, at 9:01 AM, Steven Oxley wrote:
>>
>>>     Hi guys,
>>>
>>>     I was looking at the PHP iCalendar package you have on
>>>     sourceforge and I was thinking that I might like to use some of
>>>     the iCalendar parsing code in a library of my own. The problem is
>>>     that your license is GPL v2 and I will be using this "library"
>>>     that I want to create in a software package that I cannot release
>>>     under GPL v2. I was wondering if it might be possible to release
>>>     the parsing code under LGPL so that I can modify it and use it in
>>>     my own code without having to release my entire software package
>>>     under GPL v2.
>>>
>>>     Thanks for considering it,
>>>     Steven Oxley
>>
>>     =====================================
>>     Jim Hu
>>     Associate Professor
>>     Dept. of Biochemistry and Biophysics
>>     2128 TAMU
>>     Texas A&M Univ.
>>     College Station, TX 77843-2128
>>     979-862-4054
>>
>>
>>
>
> =====================================
>
> Jim Hu
>
> Associate Professor
>
> Dept. of Biochemistry and Biophysics
>
> 2128 TAMU
>
> Texas A&M Univ.
>
> College Station, TX 77843-2128
>
> 979-862-4054
>
>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Yep,

http://www.apache.org/licenses/LICENSE-2.0

On Sep 10, 2009, at 8:00 AM, Rich Bowen wrote:

> Or, you could go all the way to ASL2.0 and make even more people  
> happy.
>
> On Sep 10, 2009, at 10:58 AM, Jim Hu wrote:
>
>> Does anyone have a problem with making a change from GPL to LGPL?
>>
>> Begin forwarded message:
>>
>>> From: Steven Oxley <ste...@gm...>
>>> Date: September 10, 2009 9:31:48 AM CDT
>>> To: Jim Hu <ji...@ta...>
>>> Subject: Re: Licensing Issues
>>>
>>> I believe that is all that would be required, but everyone who has  
>>> contributed code to the project has a copyright to their code and  
>>> in order to release their code under a different license, their  
>>> consent would be required.  (At least that's what I have picked up  
>>> from other open source projects I've been "around").
>>>
>>> Steven Oxley
>>>
>>> On Thu, Sep 10, 2009 at 10:27 AM, Jim Hu <ji...@ta...> wrote:
>>> Hi Steven,
>>>
>>> That would be OK with me.  Not being a licensing expert, do I just  
>>> change the license file?
>>>
>>> Jim
>>>
>>> On Sep 10, 2009, at 9:01 AM, Steven Oxley wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I was looking at the PHP iCalendar package you have on  
>>>> sourceforge and I was thinking that I might like to use some of  
>>>> the iCalendar parsing code in a library of my own.  The problem  
>>>> is that your license is GPL v2 and I will be using this "library"  
>>>> that I want to create in a software package that I cannot release  
>>>> under GPL v2.  I was wondering if it might be possible to release  
>>>> the parsing code under LGPL so that I can modify it and use it in  
>>>> my own code without having to release my entire software package  
>>>> under GPL v2.
>>>>
>>>> Thanks for considering it,
>>>> Steven Oxley
>>>
>>> =====================================
>>> Jim Hu
>>> Associate Professor
>>> Dept. of Biochemistry and Biophysics
>>> 2128 TAMU
>>> Texas A&M Univ.
>>> College Station, TX 77843-2128
>>> 979-862-4054
>>>
>>>
>>>
>>
>> =====================================
>> Jim Hu
>> Associate Professor
>> Dept. of Biochemistry and Biophysics
>> 2128 TAMU
>> Texas A&M Univ.
>> College Station, TX 77843-2128
>> 979-862-4054
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports  
>> 2008 30-Day
>> trial. Simplify your report design, integration and deployment -  
>> and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
>> Phpicalendar-devel mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
> --
> Rich Bowen
> rb...@rc...
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Or, you could go all the way to ASL2.0 and make even more people happy.

On Sep 10, 2009, at 10:58 AM, Jim Hu wrote:

> Does anyone have a problem with making a change from GPL to LGPL?
>
> Begin forwarded message:
>
>> From: Steven Oxley <ste...@gm...>
>> Date: September 10, 2009 9:31:48 AM CDT
>> To: Jim Hu <ji...@ta...>
>> Subject: Re: Licensing Issues
>>
>> I believe that is all that would be required, but everyone who has  
>> contributed code to the project has a copyright to their code and  
>> in order to release their code under a different license, their  
>> consent would be required.  (At least that's what I have picked up  
>> from other open source projects I've been "around").
>>
>> Steven Oxley
>>
>> On Thu, Sep 10, 2009 at 10:27 AM, Jim Hu <ji...@ta...> wrote:
>> Hi Steven,
>>
>> That would be OK with me.  Not being a licensing expert, do I just  
>> change the license file?
>>
>> Jim
>>
>> On Sep 10, 2009, at 9:01 AM, Steven Oxley wrote:
>>
>>> Hi guys,
>>>
>>> I was looking at the PHP iCalendar package you have on sourceforge  
>>> and I was thinking that I might like to use some of the iCalendar  
>>> parsing code in a library of my own.  The problem is that your  
>>> license is GPL v2 and I will be using this "library" that I want  
>>> to create in a software package that I cannot release under GPL  
>>> v2.  I was wondering if it might be possible to release the  
>>> parsing code under LGPL so that I can modify it and use it in my  
>>> own code without having to release my entire software package  
>>> under GPL v2.
>>>
>>> Thanks for considering it,
>>> Steven Oxley
>>
>> =====================================
>> Jim Hu
>> Associate Professor
>> Dept. of Biochemistry and Biophysics
>> 2128 TAMU
>> Texas A&M Univ.
>> College Station, TX 77843-2128
>> 979-862-4054
>>
>>
>>
>
> =====================================
> Jim Hu
> Associate Professor
> Dept. of Biochemistry and Biophysics
> 2128 TAMU
> Texas A&M Univ.
> College Station, TX 77843-2128
> 979-862-4054
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

--
Rich Bowen
rb...@rc...

No problem on my end.
--
Wesley Miaw
we...@we...

On Sep 10, 2009, at 7:58 AM, Jim Hu wrote:

> Does anyone have a problem with making a change from GPL to LGPL?
>
> Begin forwarded message:
>
>> From: Steven Oxley <ste...@gm...>
>> Date: September 10, 2009 9:31:48 AM CDT
>> To: Jim Hu <ji...@ta...>
>> Subject: Re: Licensing Issues
>>
>> I believe that is all that would be required, but everyone who has  
>> contributed code to the project has a copyright to their code and  
>> in order to release their code under a different license, their  
>> consent would be required.  (At least that's what I have picked up  
>> from other open source projects I've been "around").
>>
>> Steven Oxley
>>
>> On Thu, Sep 10, 2009 at 10:27 AM, Jim Hu <ji...@ta...> wrote:
>> Hi Steven,
>>
>> That would be OK with me.  Not being a licensing expert, do I just  
>> change the license file?
>>
>> Jim
>>
>> On Sep 10, 2009, at 9:01 AM, Steven Oxley wrote:
>>
>>> Hi guys,
>>>
>>> I was looking at the PHP iCalendar package you have on sourceforge  
>>> and I was thinking that I might like to use some of the iCalendar  
>>> parsing code in a library of my own.  The problem is that your  
>>> license is GPL v2 and I will be using this "library" that I want  
>>> to create in a software package that I cannot release under GPL  
>>> v2.  I was wondering if it might be possible to release the  
>>> parsing code under LGPL so that I can modify it and use it in my  
>>> own code without having to release my entire software package  
>>> under GPL v2.
>>>
>>> Thanks for considering it,
>>> Steven Oxley
>>
>> =====================================
>> Jim Hu
>> Associate Professor
>> Dept. of Biochemistry and Biophysics
>> 2128 TAMU
>> Texas A&M Univ.
>> College Station, TX 77843-2128
>> 979-862-4054
>>
>>
>>
>
> =====================================
> Jim Hu
> Associate Professor
> Dept. of Biochemistry and Biophysics
> 2128 TAMU
> Texas A&M Univ.
> College Station, TX 77843-2128
> 979-862-4054
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Does anyone have a problem with making a change from GPL to LGPL?

Begin forwarded message:

> From: Steven Oxley <ste...@gm...>
> Date: September 10, 2009 9:31:48 AM CDT
> To: Jim Hu <ji...@ta...>
> Subject: Re: Licensing Issues
>
> I believe that is all that would be required, but everyone who has  
> contributed code to the project has a copyright to their code and in  
> order to release their code under a different license, their consent  
> would be required.  (At least that's what I have picked up from  
> other open source projects I've been "around").
>
> Steven Oxley
>
> On Thu, Sep 10, 2009 at 10:27 AM, Jim Hu <ji...@ta...> wrote:
> Hi Steven,
>
> That would be OK with me.  Not being a licensing expert, do I just  
> change the license file?
>
> Jim
>
> On Sep 10, 2009, at 9:01 AM, Steven Oxley wrote:
>
>> Hi guys,
>>
>> I was looking at the PHP iCalendar package you have on sourceforge  
>> and I was thinking that I might like to use some of the iCalendar  
>> parsing code in a library of my own.  The problem is that your  
>> license is GPL v2 and I will be using this "library" that I want to  
>> create in a software package that I cannot release under GPL v2.  I  
>> was wondering if it might be possible to release the parsing code  
>> under LGPL so that I can modify it and use it in my own code  
>> without having to release my entire software package under GPL v2.
>>
>> Thanks for considering it,
>> Steven Oxley
>
> =====================================
> Jim Hu
> Associate Professor
> Dept. of Biochemistry and Biophysics
> 2128 TAMU
> Texas A&M Univ.
> College Station, TX 77843-2128
> 979-862-4054
>
>
>

=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054

Hi Wesley and Riva,

I agree that this looks like php is not set up.  I should also point  
out that once you get php working... the structure of the config was  
changed in 2.3 to use a singleton object to hold configurations.  So  
in the current config setup, the line should be

	'calendar_path' => 'D:\Inetpub\wwwroot\php\monket-calendar\monket-cal- 
source\phpicalendar-karl',

note the comma not semicolon at the end.

Jim

On Apr 17, 2009, at 11:16 PM, Wesley Miaw wrote:

> Hi Reva,
>
> You mean you see the text that is inside of index.php? Instead of a
> web page?
>
> Perhaps you don't have PHP set up in IIS? Or PHP isn't working?
>
> You do need to set $default_path to something else. And I don't know
> where CALENDAR_DIR is defined, but it needs a $ in front of it.
> --
> Wesley Miaw
> we...@we...
>
> On Apr 17, 2009, at 7:07 PM, REVA REVA wrote:
>
>> Hi Wesley,
>>
>> I am not getting any error messages.  When I opened the index.php
>> file using Internet Explorer it shows me the information that is in
>> the index.php page.
>>
>> Attached is a copy of my config.inc.php file that I modified by
>> changing the $calander_path.
>>
>> Does this help?
>>
>> --- On Fri, 4/17/09, Wesley Miaw <we...@we...> wrote:
>> From: Wesley Miaw <we...@we...>
>> Subject: Re: [PHPiCalendar-DEV] config.inc.php
>> To: ryp...@sb..., "PHPiCalendar Devel" <php...@li...
>>>
>> Date: Friday, April 17, 2009, 5:48 PM
>>
>> Hi Reva,
>>
>> Can you check your server logs to see what error message it prints?
>> --
>> Wesley Miaw
>> we...@we...
>>
>> On Apr 17, 2009, at 4:42 PM, REVA REVA wrote:
>>
>>> I am trying to change the calendar_path to the directory where my
>> folder
>> is located.
>>>
>>> I entered
>> D:\Inetpub\wwwroot\php\monket-calendar\monket-cal-source
>> \phpicalendar-karl;
>>> but when I opened the index.php page it did not show me the
>> calendar.
>>>
>>> What am I doing wrong in order to see the calendar?
>>>
>>> Thanks
>>> Reva
>>>
>> ------------------------------------------------------------------------------
>>> Stay on top of everything new and different, both inside and
>>> around Java (TM) technology - register by April 22, and save
>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32.
>> http://p.sf.net/sfu/p_______________________________________________
>>> Phpicalendar-devel mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>>
>> <config.inc.php>
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054

Hi Reva,

You mean you see the text that is inside of index.php? Instead of a  
web page?

Perhaps you don't have PHP set up in IIS? Or PHP isn't working?

You do need to set $default_path to something else. And I don't know  
where CALENDAR_DIR is defined, but it needs a $ in front of it.
--
Wesley Miaw
we...@we...

On Apr 17, 2009, at 7:07 PM, REVA REVA wrote:

> Hi Wesley,
>
> I am not getting any error messages.  When I opened the index.php  
> file using Internet Explorer it shows me the information that is in  
> the index.php page.
>
> Attached is a copy of my config.inc.php file that I modified by  
> changing the $calander_path.
>
> Does this help?
>
> --- On Fri, 4/17/09, Wesley Miaw <we...@we...> wrote:
> From: Wesley Miaw <we...@we...>
> Subject: Re: [PHPiCalendar-DEV] config.inc.php
> To: ryp...@sb..., "PHPiCalendar Devel" <php...@li... 
> >
> Date: Friday, April 17, 2009, 5:48 PM
>
> Hi Reva,
>
> Can you check your server logs to see what error message it prints?
> --
> Wesley Miaw
> we...@we...
>
> On Apr 17, 2009, at 4:42 PM, REVA REVA wrote:
>
> > I am trying to change the calendar_path to the directory where my  
> folder
> is located.
> >
> > I entered
> D:\Inetpub\wwwroot\php\monket-calendar\monket-cal-source 
> \phpicalendar-karl;
> > but when I opened the index.php page it did not show me the  
> calendar.
> >
> > What am I doing wrong in order to see the calendar?
> >
> > Thanks
> > Reva
> >
> ------------------------------------------------------------------------------
> > Stay on top of everything new and different, both inside and
> > around Java (TM) technology - register by April 22, and save
> > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> > 300 plus technical and hands-on sessions. Register today.
> > Use priority code J9JMT32.
> http://p.sf.net/sfu/p_______________________________________________
> > Phpicalendar-devel mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
> <config.inc.php>

Hi Reva,

Can you check your server logs to see what error message it prints?
--
Wesley Miaw
we...@we...

On Apr 17, 2009, at 4:42 PM, REVA REVA wrote:

> I am trying to change the calendar_path to the directory where my  
> folder is located.
>
> I entered D:\Inetpub\wwwroot\php\monket-calendar\monket-cal-source 
> \phpicalendar-karl;
> but when I opened the index.php page it did not show me the calendar.
>
> What am I doing wrong in order to see the calendar?
>
> Thanks
> Reva
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p_______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

I am trying to change the calendar_path to the directory where my folder is located.

I entered D:\Inetpub\wwwroot\php\monket-calendar\monket-cal-source\phpicalendar-karl;
but when I opened the index.php page it did not show me the calendar.

What am I doing wrong in order to see the calendar?

Thanks
Reva
Hi, Jim.  Let me know if you need my help in any way.

I am no longer using phpicalendar - but I still have it installed and  
I can do some testing with it.  But I think we should assume that I  
won't be on board for 3.x development.  I'm now syncing all my  
calendars to Google and using them to display them.   For my needs,  
this is working just fine.

On Dec 27, 2008, at 5:23 PM, Jim Hu wrote:
> After a long delay, I've taken advantage of the holiday break to  
> work on 2.3. This isn't the OO version planned for 3.0, but it  
> involves a major rewrite of the recurrence handling, new  
> preferences, better timezone support and more.  It's currently in  
> cvs and I plan on doing a release in the next few days.
>
> Jim
>
>
> =====================================
> Jim Hu
> Associate Professor
> Dept. of Biochemistry and Biophysics
> 2128 TAMU
> Texas A&M Univ.
> College Station, TX 77843-2128
> 979-862-4054
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness

After a long delay, I've taken advantage of the holiday break to work  
on 2.3. This isn't the OO version planned for 3.0, but it involves a  
major rewrite of the recurrence handling, new preferences, better  
timezone support and more.  It's currently in cvs and I plan on doing  
a release in the next few days.

Jim

=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054

Thanks Yuri,

The admin system should be completely removed for now, as it has not  
been worked on since I took over the project.

Jim

On Apr 29, 2008, at 8:35 AM, Yuri D'Elia wrote:

> Greetings,
>
> We've been trying to use your PHPiCalendar interface on our internal  
> network
> and found some bugs and security issues you might want to be aware of.
>
> The 'admin' page allows to delete or upload (read: overwrite)  
> arbitrary files
> even if the user is not logged in (or logged in as a normal user). We
> introduced a check to disable those actions if the user is not  
> correctly
> authenticated.
>
> Also, we introduced a check to verify that the file to be deleted is  
> a known
> calendar (which is not perfect, since the path name is disclosed,  
> but at
> least is not arbitrary).
>
> The delete functionality was broken anyway. sanitize.php was  
> stripping off all
> the filenames, so the exploitability was limited.
>
> PHPiCalendar did not work properly with http authentication, despite  
> the
> relative option in the config.inc.php file. We commented the  
> additional
> (broken) code present to check pre-authenticated information. This  
> allows
> the 'internal' scheme to work (which is enough for our purposes,  
> since admin
> is the only user that needs extra authentication).
>
> I'm attaching the diff against 2.24, in case should you need it for  
> reference.
>
> Regards
>
> -- 
> Yuri D'Elia
> Institute of Genetic Medicine
>
> EURAC research
> Viale Druso 1, I-39100 Bolzano
> t +39 0471 055 534
> f +39 0471 055 599
> m +39 348 922 5095
> yur...@eu...
> www.eurac.edu
>
> This transmission is intended only for the use of the addressee and  
> may
> contain confidential or legally privileged information.
> If you receive this transmission by error, please notify the author
> immediately by mail and delete all copies of this transmission and any
> attachments.
> Any use or dissemination of this communication is strictly  
> prohibited by
> the "Privacy-Code", D.Lgs. 196/2003 and may lead to penal  
> prosecution and
> liability for damages.
> <phpicalendar-2.24.diff>

=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054

I'm back.  I was just annoyed that this has been going on for a  
while ;-)

On Mar 14, 2008, at 2:13 PM, Jim Hu wrote:
> OK, after some back and forth with the vBulletin support folks, the  
> problem on the bbs is fixed.  It turns out that it's a cache  
> problem - when you log in and goes back to that URL, the browser  
> may try to use a cached copy that has the login form instead of the  
> new version that redirects to the edit form.  The fix is to force  
> no caching via the html headers.  I hope this doesn't make server  
> load go up too much.
>
> I hope Jo will come back - I really need help dealing with publish  
> support requests!
>
> Jim
>
>
> On Mar 13, 2008, at 4:50 PM, Jo Rhett wrote:
>
>> I'm sorry, but I'm not going to play with the forums any more.   
>> You go,
>> it says you aren't logged in.  You log in, it says thank you, then  
>> puts
>> you back on the login page.
>>
>> This means that every time I go, I have to use the search to find the
>> original thread to reply to it.
>>
>> It's a stupid, easily reproducable bug.  Fix it, and I'll play in the
>> forums again.
>>
>> -------- Original Message --------
>> Subject: Reply to thread 'A small utility to upload iCal calendars'
>> Date: Thu, 13 Mar 2008 16:29:59 -0500 (CDT)
>> From: phpicalendar Forums <php...@gm...>
>> To: jr...@ne...
>>
>> Dear jorhett,
>>
>> blizzard has just replied to a thread you have subscribed to  
>> entitled -
>> A small utility to upload iCal calendars - in the Publish/Subscribe
>> problems forum of phpicalendar Forums.
>>
>> This thread is located at:
>> http://phpicalendar.org/forums/showthread.php?t=1216&goto=newpost
>>
>> Here is the message that has just been posted:
>> ***************
>> Hi there,
>>
>> I'd really like to get this program working, but I cannot seem to  
>> make
>> that work for "Managed Users" in 10.3.9.
>>
>> I keep adding the application to their allowed list, and it shows up
>> checked, yet when I try to open it, the Finder says not allowed,  
>> contact
>> your administrator.
>>
>> Any ideas?
>>
>> Cheers!
>> ***************
>>
>>
>> There may also be other replies, but you will not receive any more
>> notifications until you visit the forum again.
>>
>> All the best,
>> phpicalendar Forums
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Unsubscription information:
>>
>> To unsubscribe from this thread, please visit this page:
>> http://phpicalendar.org/forums/subscription.php? 
>> do=removesubscription&type=thread&subscriptionid=102&auth=27ceab68cd5 
>> 87a5932dddf14aa750b81
>>
>> To unsubscribe from ALL threads, please visit this page:
>> http://phpicalendar.org/forums/subscription.php? 
>> do=viewsubscription&folderid=all
>>
>> --------------------------------------------------------------------- 
>> ----
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Phpicalendar-devel mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
> =====================================
> Jim Hu
> Associate Professor
> Dept. of Biochemistry and Biophysics
> 2128 TAMU
> Texas A&M Univ.
> College Station, TX 77843-2128
> 979-862-4054
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness

2002	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (5)	Oct (159)	Nov (123)	Dec (27)
2003	Jan (6)	Feb (11)	Mar (21)	Apr (29)	May (13)	Jun (2)	Jul (13)	Aug (5)	Sep (14)	Oct (21)	Nov (71)	Dec
2004	Jan (18)	Feb (12)	Mar	Apr (6)	May (29)	Jun (9)	Jul (3)	Aug (4)	Sep (7)	Oct (6)	Nov	Dec (20)
2005	Jan (6)	Feb (27)	Mar (4)	Apr (16)	May (61)	Jun (6)	Jul (4)	Aug (18)	Sep (19)	Oct (5)	Nov (55)	Dec (30)
2006	Jan (11)	Feb (9)	Mar (9)	Apr (26)	May (17)	Jun (3)	Jul (1)	Aug	Sep (20)	Oct	Nov (6)	Dec (9)
2007	Jan	Feb	Mar (5)	Apr	May (8)	Jun (2)	Jul	Aug	Sep	Oct (3)	Nov	Dec
2008	Jan	Feb (17)	Mar (11)	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (2)
2009	Jan	Feb	Mar	Apr (4)	May	Jun	Jul	Aug	Sep (7)	Oct	Nov	Dec
2010	Jan	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec (4)
2011	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec
2015	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (2)	Oct	Nov	Dec
2022	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

phpicalendar-devel Mailing List for PHP iCalendar

phpicalendar-devel — Mailing list for PHP iCalendar Developers