webical-developers — developers

[Webical-developers] Webical releases

[Ivo v. D. <ivo...@gm...>]

Hi,

I was trying to release the caldav plugin today, but I ran into a couple
of problems with the latest webical release:

    * There is no 0.4.1 build (or any other release version for that
      matter) to be found in the maven repository. I've added the 0.4.1
      release to the repo, please make it a part of the release process
      to deploy the artifacts for the release as our continues
      integration server only builds and deploys trunk.
    * The version number in the 0.4.1 build is set to 0.4-SNAPSHOT. This
      must be correctly set as plugins depend on it. This should have
      been done by maven automatically, but the macro in
      applicationContext.xml was overwritten and committed. Please don't
      do this! I've reverted it for 0.5-SNAPSHOT, but it's to late for
      the current release. Please always check the configuration that is
      committed.

Regards,
Ivo

Re: [Webical-developers] release 0.4

[Zoran K. <zo...@fu...>]

Great news! How about sending an invite to all current subscribers? I 
will send you a list off-list.

Zz.

Mattijs Hoitink wrote:
> Hi all,
> 
> today I tagged the trunk for release 0.4! :D
> 
> A lot of modifications have been done to webical, enough for a new 
> release. But this is not the end, it sure is not! With this release done 
> we are ready to move webical from sourceforge to google code.
> 
> We chose google code because it has a better issue tracker and an 
> integrated wiki. I already begun moving wiki pages from twiki to the 
> google code wiki. With some more moving today the wiki should be ready 
> for the first visitors.
> I hope to copy the svn trunk from sourceforge to google code next week.
> 
> I'm posting an announcement on the blog later this day, and upload the 
> release to the new project page.
> The new webical project page can be found at 
> http://webical.googlecode.com (http://code.google.com/p/webical).
> 
> With the move to google code we are also moving the mailinglist. I 
> created a new group on google groups where future communication will 
> take place. The new mailinglist can be found at 
> http://groups.google.com/group/webical-developers. So if you want to 
> keep track of webical i suggest you join this group.
> 
> cheers
> 


-- 
Zoran Kovacevic
Func. Internet Integration
W http://www.func.nl
M +31 6 48104284
T +31 20 4230000
F +31 20 4223500
GPG http://www.func.nl/keys/z.k...@fu...

[Webical-developers] release 0.4

[Mattijs H. <ma...@fu...>]

Hi all,

today I tagged the trunk for release 0.4! :D

A lot of modifications have been done to webical, enough for a new 
release. But this is not the end, it sure is not! With this release done 
we are ready to move webical from sourceforge to google code.

We chose google code because it has a better issue tracker and an 
integrated wiki. I already begun moving wiki pages from twiki to the 
google code wiki. With some more moving today the wiki should be ready 
for the first visitors.
I hope to copy the svn trunk from sourceforge to google code next week.

I'm posting an announcement on the blog later this day, and upload the 
release to the new project page.
The new webical project page can be found at 
http://webical.googlecode.com (http://code.google.com/p/webical).

With the move to google code we are also moving the mailinglist. I 
created a new group on google groups where future communication will 
take place. The new mailinglist can be found at 
http://groups.google.com/group/webical-developers. So if you want to 
keep track of webical i suggest you join this group.

cheers

-- 
Mattijs Hoitink
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

[Webical-developers] [Fwd: Webical 0.4-rc1]

[Ivo v. D. <ivo...@gm...>]

Hey,

Good news, but I don't see any links to the release. Also there doesn't
seem to be a release on the sf page, is this still coming?
Perhaps a list of added features, fixed bugs and the likes would be nice
as well to catch the interest of possible users. Even better with some
screenshots (or a link to it).

Regards,
Ivo

In reference to:
http://blog.webical.org/archives/18-guid.html

Re: [Webical-developers] Tracker use

[Ivo v. D. <ivo...@gm...>]

Well, actually no. To make bug management viable we need some support from
our users in making sure bugs aren't reported over and over. One tracker
with a clear layout would make it easy for a user to search for a known
issue before reporting a new one. If we keep a separated tracker we can't
expect users to search both of them (we're  lucky if they take the time to
report a bug at all :)).

On a side note: How do we move issues from one tracker to another? This
would be very useful to move some bugs to the features tracker.

Ivo

On Jan 3, 2008 10:13 AM, Mattijs Hoitink <ma...@fu...> wrote:

> I just had a look at the SF tracker system and saw the option to add a
> new tracker. The add screen contains the following text:
>
> "You can use this system to track virtually any kind of data, with each
> tracker having separate user, group, category, and permission lists. You
> can also easily move items between trackers when needed."
>
> Would it be a good idea to create a developer tracker where we van put
> the core issues for developers. We could create detailed core categories
> in that tracker. This would make sense as we don't want to hassle user
> with development issues.
> Bugs can stay in the separate tracker for bugs where user can report
> them with the global categories.
>
> Sounds good?
>
> cheers
>
>
> Mattijs Hoitink wrote:
> >>  How about something like this:
> >>
> >> Frontend
> >> Core
> >> Configuration
> >> Packaging
> >> Plugin system
> >> Documentation
> >> Other (facilities like maven repo, demo, nightly, etc)
> >>
> > I can agree with the more general categories, it seems less complex for
> > other users. Still, I think it would be wise to have a little more
> > categories for the core. If developers want to use the tracker to place
> > issue that need to be addressed within the core, and assign issues to
> > other developers, it would be nice if they could be a little bit more
> > specific in the part the issue is concerned with.
> >
> > Maybe it's a good idea to have a little more core categories? Like:
> >
> > Frontend
> > Core
> > Core - Presentation
> > Core - Managers
> > Core - DAO
> > Core - Datebase
> > Configuration
> > Packaging
> > Plugin system
> > Documentation
> > Other (facilities like maven repo, demo, nightly, etc)
> >
> > I don't think the SF tracker supports sub categories (stupid!), so the
> > prefix Core should make it clear for non developers what the category is
> > about.
> >
> > cheers
> >
> > --
> > Mattijs Hoitink
> > Func. Internet Integration
> > W http://www.func.nl
> > T +31 20 4230000
> > F +31 20 4223500
> >
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Webical-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/webical-developers
> >
>
> --
> Mattijs Hoitink
> Func. Internet Integration
> W http://www.func.nl
> T +31 20 4230000
> F +31 20 4223500
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>



-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Tracker use

[Mattijs H. <ma...@fu...>]

I just had a look at the SF tracker system and saw the option to add a 
new tracker. The add screen contains the following text:

"You can use this system to track virtually any kind of data, with each
tracker having separate user, group, category, and permission lists. You
can also easily move items between trackers when needed."

Would it be a good idea to create a developer tracker where we van put 
the core issues for developers. We could create detailed core categories 
in that tracker. This would make sense as we don't want to hassle user 
with development issues.
Bugs can stay in the separate tracker for bugs where user can report 
them with the global categories.

Sounds good?

cheers


Mattijs Hoitink wrote:
>>  How about something like this:
>>
>> Frontend
>> Core
>> Configuration
>> Packaging
>> Plugin system
>> Documentation
>> Other (facilities like maven repo, demo, nightly, etc)
>>     
> I can agree with the more general categories, it seems less complex for
> other users. Still, I think it would be wise to have a little more
> categories for the core. If developers want to use the tracker to place
> issue that need to be addressed within the core, and assign issues to
> other developers, it would be nice if they could be a little bit more
> specific in the part the issue is concerned with.
>
> Maybe it's a good idea to have a little more core categories? Like:
>
> Frontend
> Core
> Core - Presentation
> Core - Managers
> Core - DAO
> Core - Datebase
> Configuration
> Packaging
> Plugin system
> Documentation
> Other (facilities like maven repo, demo, nightly, etc)
>
> I don't think the SF tracker supports sub categories (stupid!), so the
> prefix Core should make it clear for non developers what the category is
> about.
>
> cheers
>
> --
> Mattijs Hoitink
> Func. Internet Integration
> W http://www.func.nl
> T +31 20 4230000
> F +31 20 4223500
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>   

--
Mattijs Hoitink
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Tracker use

[Ivo v. D. <ivo...@gm...>]

On Jan 3, 2008 10:04 AM, Mattijs Hoitink <ma...@fu...> wrote:

>
> >  How about something like this:
> >
> > Frontend
> > Core
> > Configuration
> > Packaging
> > Plugin system
> > Documentation
> > Other (facilities like maven repo, demo, nightly, etc)
> I can agree with the more general categories, it seems less complex for
> other users. Still, I think it would be wise to have a little more
> categories for the core. If developers want to use the tracker to place
> issue that need to be addressed within the core, and assign issues to
> other developers, it would be nice if they could be a little bit more
> specific in the part the issue is concerned with.


Fine by me, but I don't get the difference between dao and database. We use
a database in our current dao setup (although this is ot set in stone) but
we're not about to fix bugs in mysql are we? The dao category could already
include the java classes and the mapping files as they sort of go together
anyway.


>
> Maybe it's a good idea to have a little more core categories? Like:
>
> Frontend
> Core
> Core - Presentation
> Core - Managers
> Core - DAO
> Core - Datebase
> Configuration
> Packaging
> Plugin system
> Documentation
> Other (facilities like maven repo, demo, nightly, etc)
>
> I don't think the SF tracker supports sub categories (stupid!), so the
> prefix Core should make it clear for non developers what the category is
> about.


The bugtracker uses Category and group. You can combine these two as you see
fit, but prefixing is fine as well.


>
> cheers
>
> --
> Mattijs Hoitink
> Func. Internet Integration
> W http://www.func.nl
> T +31 20 4230000
> F +31 20 4223500
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>



-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Tracker use

[Mattijs H. <ma...@fu...>]

>  How about something like this:
>
> Frontend
> Core
> Configuration
> Packaging
> Plugin system
> Documentation
> Other (facilities like maven repo, demo, nightly, etc)
I can agree with the more general categories, it seems less complex for 
other users. Still, I think it would be wise to have a little more 
categories for the core. If developers want to use the tracker to place 
issue that need to be addressed within the core, and assign issues to 
other developers, it would be nice if they could be a little bit more 
specific in the part the issue is concerned with.

Maybe it's a good idea to have a little more core categories? Like:

Frontend
Core
Core - Presentation
Core - Managers
Core - DAO
Core - Datebase
Configuration
Packaging
Plugin system
Documentation
Other (facilities like maven repo, demo, nightly, etc)

I don't think the SF tracker supports sub categories (stupid!), so the 
prefix Core should make it clear for non developers what the category is 
about.

cheers

--
Mattijs Hoitink
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Tracker use

[Ivo v. D. <ivo...@gm...>]

Nice! Although I agree with zoran that a more generic batch of labels would
probably be more useful. Also I don't think a separate catagory for hml and
css is necessary, it will be handled by the same developers I think. How
about something like this:

Frontend
Core
Configuration
Packaging
Plugin system
Documentation
Other (facilities like maven repo, demo, nightly, etc)

Regards,
Ivo


On Jan 3, 2008 9:06 AM, Zoran Kovacevic <zo...@fu...> wrote:

> > I was busy reorganising the wiki a bit, when I came across the
> OpenIssues
> > page. On this page I saw a huge list of issues that have to be fixed.
> But
> > when I started reading some of the issues, some of them were already
> fixed
> > or are not applicable anymore.
> >
> > I would like to see that issues are posted in the tracker instead of the
> > wiki. I find it helpfull if i can report an issue i'm going to fix in a
>
> Obviously the best place is the tracker. Nice merciless refactoring :)
>
>  > (...)
> > I guess it would be smart to use a bit of both. Bugs can be reported
> > without assigning them to a category. Once a developer picks up the bug
> > and finds out (throught the reporter) what the issue is, he can assign
> it
> > to a specific category. And the bug/issue can be fixed.
>
> Good process.
>
> > I want to propose the following tracker categories for bugs/issues:
> >
> >  - None
> >  - Not sure
>
> Why both of them? Can't the default be Not sure?
>
> >  - Frontend
> >    - html
> >    - css
> >  - Core
> >    - Wicket
> >    - Spring
> >    - Dao
> >    - Datebase (Hibernate)
>
> Perhaps make it technology independent? I.e. layers: presentation,
> service, data.
>
> What do the other developers and testers think?
>
> Best, Zoran
>
> --
> Zoran Kovacevic
> Func. Internet Integration
> W http://www.func.nl
> M +31 6 48104284
> T +31 20 4230000
> F +31 20 4223500
> GPG http://www.func.nl/keys/z.k...@fu...
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>



-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Tracker use

[Zoran K. <zo...@fu...>]

> I was busy reorganising the wiki a bit, when I came across the OpenIssues
> page. On this page I saw a huge list of issues that have to be fixed. But
> when I started reading some of the issues, some of them were already fixed
> or are not applicable anymore.
> 
> I would like to see that issues are posted in the tracker instead of the
> wiki. I find it helpfull if i can report an issue i'm going to fix in a

Obviously the best place is the tracker. Nice merciless refactoring :)

 > (...)
> I guess it would be smart to use a bit of both. Bugs can be reported
> without assigning them to a category. Once a developer picks up the bug
> and finds out (throught the reporter) what the issue is, he can assign it
> to a specific category. And the bug/issue can be fixed.

Good process.

> I want to propose the following tracker categories for bugs/issues:
> 
>  - None
>  - Not sure

Why both of them? Can't the default be Not sure?

>  - Frontend
>    - html
>    - css
>  - Core
>    - Wicket
>    - Spring
>    - Dao
>    - Datebase (Hibernate)

Perhaps make it technology independent? I.e. layers: presentation, 
service, data.

What do the other developers and testers think?

Best, Zoran

-- 
Zoran Kovacevic
Func. Internet Integration
W http://www.func.nl
M +31 6 48104284
T +31 20 4230000
F +31 20 4223500
GPG http://www.func.nl/keys/z.k...@fu...

[Webical-developers] Tracker use

[<ma...@fu...>]

hi all,

I was busy reorganising the wiki a bit, when I came across the OpenIssues
page. On this page I saw a huge list of issues that have to be fixed. But
when I started reading some of the issues, some of them were already fixed
or are not applicable anymore.

I would like to see that issues are posted in the tracker instead of the
wiki. I find it helpfull if i can report an issue i'm going to fix in a
later state. This way I won't forget about it, and when the issue is
resolved I can easily close it. The proces is made more transparent as
other people can see what issues are there and who is working on. Progress
will be easier to see.

Issue should be assigned to a specific category so developers can pick
them up easily. I think issues can be kept more up to date in the tracker
and issues will be more clear to the outside.

I'm not sure about the the titles for the tracker categories. I think
there are two directions: Global category names or Specific category
names.
I guess it would be smart to use a bit of both. Bugs can be reported
without assigning them to a category. Once a developer picks up the bug
and finds out (throught the reporter) what the issue is, he can assign it
to a specific category. And the bug/issue can be fixed.

I want to propose the following tracker categories for bugs/issues:

 - None
 - Not sure
 - Frontend
   - html
   - css
 - Core
   - Wicket
   - Spring
   - Dao
   - Datebase (Hibernate)

I hope you guys have some thoughts on this and maybe some remarks on my
(proposed) approach and category names.

cheers,

Mattijs

Re: [Webical-developers] Webical release?

[Mattijs H. <ma...@fu...>]

hmm, I didn't know that :S

I got everything packaged now, it's going on the download page today. 
I'll dubble check if the package is working. An announcement will be 
posted on the blog and sf page.

I'll check out the maven release mechanism for the next release 
(hopefully January 4th).

cheers,

mattijs

Ivo van Dongen wrote:
> Hey,
>
> Looking at the commits I see that there is a release forthcoming? I 
> see a lot of work being done to create a branch and such, I wanted to 
> remind you that maven has an excellent release mechanism (check out 
> the documentation 
> <http://maven.apache.org/plugins/maven-release-plugin/>). It should be 
> as simple as mvn release:prepare and mvn release:perform. It creates 
> the branch, updates the versions in the pom, creates a package without 
> svn stuff, and so on. Manually doing all of this is a little error 
> prone...
>
> Regards,
> Ivo 

--
Mattijs Hoitink
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

[Webical-developers] Webical release?

[Ivo v. D. <ivo...@gm...>]

Hey,

Looking at the commits I see that there is a release forthcoming? I see
a lot of work being done to create a branch and such, I wanted to remind
you that maven has an excellent release mechanism (check out the
documentation <http://maven.apache.org/plugins/maven-release-plugin/>).
It should be as simple as mvn release:prepare and mvn release:perform.
It creates the branch, updates the versions in the pom, creates a
package without svn stuff, and so on. Manually doing all of this is a
little error prone...

Regards,
Ivo

[Webical-developers] mod caldav for apache

[Martin T. <m....@fu...>]

Hi,

I found this:
http://linux.softpedia.com/get/Internet/HTTP-WWW-/mod-caldav-31764.shtml

didn't test it yet...

Regards,

Martin



-- 
Martin Tilma
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

[Webical-developers] Webical License

[Mattijs H. <ma...@fu...>]

Hi all,

I wrote a little script to add a license file to the java files used in 
Webical. I want to add the license, but first we have to agree on the 
license to use.

I want to propose the GPL version 3 license and the following text at 
the start of each java file:

    /*
      *    Webical - http://www.webical.org
      *    Copyright (C) 2007 Func. Internet Integration
      *
      *    This file is part of Webical.
      *
      *    This program is free software: you can redistribute it and/or
    modify
      *    it under the terms of the GNU General Public License as
    published by
      *    the Free Software Foundation, either version 3 of the License, or
      *    (at your option) any later version.
      *
      *    This program is distributed in the hope that it will be useful,
      *    but WITHOUT ANY WARRANTY; without even the implied warranty of
      *    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
      *    GNU General Public License for more details.
      *
      *    You should have received a copy of the GNU General Public License
      *    along with this program.  If not, see
    <http://www.gnu.org/licenses/>.
      */


This text is the standard text for GPLv3 from the opensource website [1].

I found that a piece of code (LocalFileSystemStorage.class) used in 
Webical is licensed under the Apache 2.0 license.
I checked for compatibility and found this on the Apache website [2]:

    Is the Apache license compatible with the GPL (GNU Public License)?

     From the Free Software Foundation website:

    Apache License, Version 2.0

    This is a free software license, compatible with version 3 of the
    GPL. Please note that this license is not compatible with GPL
    version 2, because it has some requirements that are not in the
    older version. These include certain patent termination and
    indemnification provisions.


So the Apache 2.0 license is actually compatible with the GPLv3 license.

Let me know what you think of the license we should choose and the 
proposed text.

cheers,
Mattijs

[1] http://www.opensource.org/licenses/gpl-3.0.html
[2] http://www.apache.org/foundation/licence-FAQ.html#GPL

--
Mattijs Hoitink
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

[Webical-developers] =?utf-8?q?=5BFwd=3A_YUI_2=2E4=2E0_Released_?= =?utf-8?q?=E2=80=94_Selector=2C_Charts=2C_Profiler=2C_Script/CSS_Get=2C_a?= =?utf-8?q?nd_JSON_Support=5D?=

[Ivo v. D. <ivo...@gm...>]

Since the ajax part is still to be refactored perhaps an upgrade to the
latest version might be interesting:

http://yuiblog.com/blog/2007/12/04/yuii-240/

At the moment the yui files are mingled with our other resources, which
makes upgrading kinda hard. If we upgrade I'm for separating the yui
files in a seperate source folder. For example: src/main/yui. This
should be a simple matter of configuring an extra resource path in maven.

Regards,
Ivo

-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] [Fwd: [Webical-commits] SF.net SVN: webical: [534] trunk/webical-core/src]

[Mattijs H. <ma...@fu...>]

haha, true. I'm planning to re-program the tests after all the 
refactoring is. But a good test would be nice for these situations.

Ivo van Dongen wrote:
> Recurrence is probably fixed? This is one of those cases where a good
> unit test is really needed ;)
>
>   

--
Mattijs Hoitink
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

[Webical-developers] Bubbling library

[Ivo v. D. <ivo...@gm...>]

Hi,

I just came across a js library built on top of YUI. It has some cool
effects, perhaps we can use some to make webical even more flashy ;).
Check this one out for example:
http://bubbling-library.com/themes/bubbling/jscripts/yui-cms/examples/loading/index.html

Regards,
Ivo

-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Nightly deploy

[Ivo v. D. <ivo...@gm...>]

On Nov 7, 2007 9:43 AM, Mattijs Hoitink <ma...@fu...> wrote:

> I guess this is because the nightly build isn't building every night.
> When I log in, it's not the latest version from the repository. I
> pointed this out to you last week.


Well, I thought so as well. so I did a fresh deploy yesterday before
mailing. Sadly this doesn't work also. So I'm afraid it is something in the
code/profile.


> Adding events is working in my
> development version.


Please check out the differences.

>
>
> When I have some time left, I'll check out why the nightly build isn't
> building the latest version from the repository every night.


That's something for our system administrator I believe. Check with him
first.

>
>
> cheers,
> mattijs
>
> Ivo van Dongen wrote:
> > Hey,
> >
> > There seems to be some regression in webical. The current nightly
> > deploy doesn't work right. Just try to add an event. Is this due to
> > work-in-progress or is something not committed? When investigating
> > please try to figure out how to catch these sorts of errors with
> > automated tests to catch regressions while building.
> >
> > Regards,
> > Ivo
> >
> > --
> > Ivo van Dongen
> > Func. Internet Integration
> > W http://www.func.nl
> > T +31 20 4230000
> > F +31 20 4223500
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Webical-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/webical-developers
> >
>
> --
> Mattijs Hoitink
> Func. Internet Integration
> W http://www.func.nl
> T +31 20 4230000
> F +31 20 4223500
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>



-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Nightly deploy

[Mattijs H. <ma...@fu...>]

I guess this is because the nightly build isn't building every night. 
When I log in, it's not the latest version from the repository. I 
pointed this out to you last week. Adding events is working in my 
development version.

When I have some time left, I'll check out why the nightly build isn't 
building the latest version from the repository every night.

cheers,
mattijs

Ivo van Dongen wrote:
> Hey,
>
> There seems to be some regression in webical. The current nightly 
> deploy doesn't work right. Just try to add an event. Is this due to 
> work-in-progress or is something not committed? When investigating 
> please try to figure out how to catch these sorts of errors with 
> automated tests to catch regressions while building.
>
> Regards,
> Ivo
>
> -- 
> Ivo van Dongen
> Func. Internet Integration
> W http://www.func.nl
> T +31 20 4230000
> F +31 20 4223500
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>   

--
Mattijs Hoitink
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

[Webical-developers] Nightly deploy

[Ivo v. D. <ivo...@gm...>]

Hey,

There seems to be some regression in webical. The current nightly deploy
doesn't work right. Just try to add an event. Is this due to
work-in-progress or is something not committed? When investigating please
try to figure out how to catch these sorts of errors with automated tests to
catch regressions while building.

Regards,
Ivo

-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Fwd: [Announce] CalDAV4j now hosted at Google Code]

[Ivo v. D. <ivo...@gm...>]

Looks good. Hopefully  an official maven repository is set up soon.

On Oct 31, 2007 9:21 AM, Zoran Kovacevic <zo...@fu...> wrote:

> FYI
>
> -------- Original Message --------
> Subject:        [Announce] CalDAV4j now hosted at Google Code
> Date:   Tue, 30 Oct 2007 12:15:23 -0700
> From:   ann...@os...
> Reply-To:       ann...@os...
> To:     Cosmo List <cos...@os...>, OSAF Discussions
> <ge...@os...>, ann...@os...
> References:     <704...@os...>
>
>
>
> For those of you who don't know, CalDAV4j is a Java client library for
> talking to CalDAV servers. It's an OSAF project, but until now it's
> never really had a proper home of its own - folks would post to one of
> the various OSAF lists (usually Cosmo Dev) when they had questions.
>
> Recently, there has been a slow but steady increase in interest in the
> project - doubtless due in no small part to Apple's commitment to
> CalDAV. With the release of Leopard and its CalDAV enabled iCal
> application, and the increasing general interest in calendaring in
> general, we imagine that the interest in CalDAV and therefore CalDAV4j
> will only increase.
>
> To enable CalDAV4j to have the widest possible audience and resources
> (wiki, mailing list, source control, bug tracking) without placing undue
> burden on OSAF, we have decided to host CalDAV4j with Google Code. Check
> it out at:
>
>   http://code.google.com/p/caldav4j/
>
> Hope to see you there!
>
> Bobby Rullo
>
>
>
> --
> Zoran Kovacevic
> Func. Internet Integration
> W http://www.func.nl
> M +31 6 48104284
> T +31 20 4230000
> F +31 20 4223500
> GPG http://www.func.nl/keys/z.k...@fu...
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Announce" mailing list
> http://lists.osafoundation.org/mailman/listinfo/announce
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>
>


-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

[Webical-developers] Fwd: [Announce] CalDAV4j now hosted at Google Code]

[Zoran K. <zo...@fu...>]

FYI

-------- Original Message --------
Subject: 	[Announce] CalDAV4j now hosted at Google Code
Date: 	Tue, 30 Oct 2007 12:15:23 -0700
From: 	ann...@os...
Reply-To: 	ann...@os...
To: 	Cosmo List <cos...@os...>, OSAF Discussions
<ge...@os...>, ann...@os...
References: 	<704...@os...>



For those of you who don't know, CalDAV4j is a Java client library for
talking to CalDAV servers. It's an OSAF project, but until now it's
never really had a proper home of its own - folks would post to one of
the various OSAF lists (usually Cosmo Dev) when they had questions.

Recently, there has been a slow but steady increase in interest in the
project - doubtless due in no small part to Apple's commitment to
CalDAV. With the release of Leopard and its CalDAV enabled iCal
application, and the increasing general interest in calendaring in
general, we imagine that the interest in CalDAV and therefore CalDAV4j
will only increase.

To enable CalDAV4j to have the widest possible audience and resources
(wiki, mailing list, source control, bug tracking) without placing undue
burden on OSAF, we have decided to host CalDAV4j with Google Code. Check
it out at:

   http://code.google.com/p/caldav4j/

Hope to see you there!

Bobby Rullo



-- 
Zoran Kovacevic
Func. Internet Integration
W http://www.func.nl
M +31 6 48104284
T +31 20 4230000
F +31 20 4223500
GPG http://www.func.nl/keys/z.k...@fu...

Re: [Webical-developers] =?iso-8859-1?q?The_Chandler_Project_Blog_=BB?= =?iso-8859-1?q?_Blog_Archive_=BB_Chandler=2C_meet_Twitter?=

[Ivo v. D. <ivo...@gm...>]

On 10/22/07, Zoran Kovacevic <zo...@fu...> wrote:
>
> Ivo van Dongen wrote:
> > On 10/22/07, *Zoran Kovacevic* <zo...@fu... <mailto:zo...@fu...>>
> wrote:
> >     (continuuing in en on webical list)
> >
> >     This is a really cool idea for a frontend plugin. If I understand
> >     correctly, you configure your jabber account and webical sends
> reminders
> >     via im?
> >
> >
> > That would be the idea. The only problem is making things easy to set
> > up. For this to work you either need an existing account for the plugin
> > to connect with or a server of your own. I don't want to create to much
> > setup steps and configuration hassle (was just trying to get rid of that
> > in webical itself).
>
> how about letting the user provide account details to use as sender?


That's one option, but I would like to combine that with a system-wide user
the administrator can configure. This way you have some more freedom and you
can protect your users from such details. I'm working on the settings
implementation atm (well, when I have some time again) when that's finished
plugins can include configuration pages and store their settings.

-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>



-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] =?iso-8859-1?q?The_Chandler_Project_Blog_=BB?= =?iso-8859-1?q?_Blog_Archive_=BB_Chandler=2C_meet_Twitter?=

[Zoran K. <zo...@fu...>]

Ivo van Dongen wrote:
> On 10/22/07, *Zoran Kovacevic* <zo...@fu... <mailto:zo...@fu...>> wrote:
>     (continuuing in en on webical list)
> 
>     This is a really cool idea for a frontend plugin. If I understand
>     correctly, you configure your jabber account and webical sends reminders
>     via im?
> 
> 
> That would be the idea. The only problem is making things easy to set 
> up. For this to work you either need an existing account for the plugin 
> to connect with or a server of your own. I don't want to create to much 
> setup steps and configuration hassle (was just trying to get rid of that 
> in webical itself).

how about letting the user provide account details to use as sender?