You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Simon Funnell <si...@googlemail.com> on 2009/11/25 16:32:47 UTC
Release Date
Hi,
I've been working on a few wiki pages and feel as if I am at a juncture.
I've been looking at the version 3 code base (rather than version 2...)
and getting a better idea of the big picture. I would like to expand the
documentation further but would like some feedback as to whether they
are appropriate descriptions. It's a little bit sketchy and there are a
few things I have missed because I haven't had time to look them up yet,
but I think its fairly comprehensive. I think the JamesUserTypes is
important because this is how I currently view/manage James (and other
projects).
http://wiki.apache.org/james/JamesUserTypes
http://wiki.apache.org/james/JamesTools
http://wiki.apache.org/james/JamesArchitecture
James weakest point, and something I would certainly like help to
improve is the Administrator services, which are basically, very
minimal. I think its important to stress that large parts of the
configuration, basically the mailet configuration and related items,
while it is a configuration, it is more importantly a
organisation/business application. This aspect of the configuration
changes regularly and needs to be deployable, like a web application.
The version 3 code base is much better and has encouraged me a lot,
there is a lot more reusable stuff. It has also convinced me that
Platformed can be of significant benefit to James. Platformed is not
comparable to Guice and unfortunately a lot of inversion of control
containers are indeed injection frameworks. Platformed is not an
injection framework, it is a multi-threaded server application framework
and it uses, amongst other things, injection. At this stage, I am still
happy to create documentation in a non-obtrusive manner as this will
allow me to offer more constructive propositions.
Is there an expected release date for version 3?
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Release Date
Posted by Simon Funnell <si...@googlemail.com>.
Ok, I can continue with what I am doing for version 3, what I am doing
is fairly useful regardless. I will try to relate the concepts to the
code base in the documentation as I come to understand it more.
Thanks,
Simon
Stefano Bagnara wrote:
> 2009/11/26 Simon Funnell <si...@googlemail.com>:
>
>> Hi,
>>
>> Thanks, I have the latest code base and have been taking a look around. I
>> have also been looking at JSR250 and OSGI. If version 3 is well on its way
>> it is probably best I look towards version 4, which attempts to refine
>> existing feature definitions for the purpose of adding management services.
>> This will allow me to continue working on documentation without disturbing
>> anyone else as you can look at it any time over the next month :) don't be
>> surprised if I go berserk (in the sense of ruthless).
>>
>
> Version 3 is in trunk since years and there is no roadmap. Version
> numbers are not important at all and we already understood that there
> is no way to define a roadmap in JAMES. Simply contribute things
> against the codebase: the choice to include it before or after the
> release will be made once the proposed patch is real and ready to be
> committed.
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Release Date
Posted by Stefano Bagnara <ap...@bago.org>.
2009/11/26 Simon Funnell <si...@googlemail.com>:
> Hi,
>
> Thanks, I have the latest code base and have been taking a look around. I
> have also been looking at JSR250 and OSGI. If version 3 is well on its way
> it is probably best I look towards version 4, which attempts to refine
> existing feature definitions for the purpose of adding management services.
> This will allow me to continue working on documentation without disturbing
> anyone else as you can look at it any time over the next month :) don't be
> surprised if I go berserk (in the sense of ruthless).
Version 3 is in trunk since years and there is no roadmap. Version
numbers are not important at all and we already understood that there
is no way to define a roadmap in JAMES. Simply contribute things
against the codebase: the choice to include it before or after the
release will be made once the proposed patch is real and ready to be
committed.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Release Date
Posted by Simon Funnell <si...@googlemail.com>.
Hi,
Thanks, I have the latest code base and have been taking a look around.
I have also been looking at JSR250 and OSGI. If version 3 is well on its
way it is probably best I look towards version 4, which attempts to
refine existing feature definitions for the purpose of adding management
services. This will allow me to continue working on documentation
without disturbing anyone else as you can look at it any time over the
next month :) don't be surprised if I go berserk (in the sense of
ruthless).
Regards,
Simon
Norman Maurer wrote:
> Hi Simon,
>
> first of I can't give you feedback for the wiki pages because I had no
> time yet to read them. But I will come back to you later ;)
>
> About the release date.. I think I will try to get all things done for
> a milestone when I have complete the avalon -> guice move, which
> should be within the next month. To complete this I will lookin into
> replace phoenix with osgi as proof-of-concept for using OSGI.
>
> Bye,
> Norman
>
>
>
> 2009/11/25 Simon Funnell <si...@googlemail.com>:
>
>> Hi,
>>
>> I've been working on a few wiki pages and feel as if I am at a juncture.
>> I've been looking at the version 3 code base (rather than version 2...) and
>> getting a better idea of the big picture. I would like to expand the
>> documentation further but would like some feedback as to whether they are
>> appropriate descriptions. It's a little bit sketchy and there are a few
>> things I have missed because I haven't had time to look them up yet, but I
>> think its fairly comprehensive. I think the JamesUserTypes is important
>> because this is how I currently view/manage James (and other projects).
>>
>> http://wiki.apache.org/james/JamesUserTypes
>> http://wiki.apache.org/james/JamesTools
>> http://wiki.apache.org/james/JamesArchitecture
>>
>> James weakest point, and something I would certainly like help to improve is
>> the Administrator services, which are basically, very minimal. I think its
>> important to stress that large parts of the configuration, basically the
>> mailet configuration and related items, while it is a configuration, it is
>> more importantly a organisation/business application. This aspect of the
>> configuration changes regularly and needs to be deployable, like a web
>> application.
>>
>> The version 3 code base is much better and has encouraged me a lot, there is
>> a lot more reusable stuff. It has also convinced me that Platformed can be
>> of significant benefit to James. Platformed is not comparable to Guice and
>> unfortunately a lot of inversion of control containers are indeed injection
>> frameworks. Platformed is not an injection framework, it is a multi-threaded
>> server application framework and it uses, amongst other things, injection.
>> At this stage, I am still happy to create documentation in a non-obtrusive
>> manner as this will allow me to offer more constructive propositions.
>>
>> Is there an expected release date for version 3?
>>
>> Regards,
>>
>> Simon
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Release Date
Posted by Norman Maurer <no...@googlemail.com>.
Hi Simon,
first of I can't give you feedback for the wiki pages because I had no
time yet to read them. But I will come back to you later ;)
About the release date.. I think I will try to get all things done for
a milestone when I have complete the avalon -> guice move, which
should be within the next month. To complete this I will lookin into
replace phoenix with osgi as proof-of-concept for using OSGI.
Bye,
Norman
2009/11/25 Simon Funnell <si...@googlemail.com>:
> Hi,
>
> I've been working on a few wiki pages and feel as if I am at a juncture.
> I've been looking at the version 3 code base (rather than version 2...) and
> getting a better idea of the big picture. I would like to expand the
> documentation further but would like some feedback as to whether they are
> appropriate descriptions. It's a little bit sketchy and there are a few
> things I have missed because I haven't had time to look them up yet, but I
> think its fairly comprehensive. I think the JamesUserTypes is important
> because this is how I currently view/manage James (and other projects).
>
> http://wiki.apache.org/james/JamesUserTypes
> http://wiki.apache.org/james/JamesTools
> http://wiki.apache.org/james/JamesArchitecture
>
> James weakest point, and something I would certainly like help to improve is
> the Administrator services, which are basically, very minimal. I think its
> important to stress that large parts of the configuration, basically the
> mailet configuration and related items, while it is a configuration, it is
> more importantly a organisation/business application. This aspect of the
> configuration changes regularly and needs to be deployable, like a web
> application.
>
> The version 3 code base is much better and has encouraged me a lot, there is
> a lot more reusable stuff. It has also convinced me that Platformed can be
> of significant benefit to James. Platformed is not comparable to Guice and
> unfortunately a lot of inversion of control containers are indeed injection
> frameworks. Platformed is not an injection framework, it is a multi-threaded
> server application framework and it uses, amongst other things, injection.
> At this stage, I am still happy to create documentation in a non-obtrusive
> manner as this will allow me to offer more constructive propositions.
>
> Is there an expected release date for version 3?
>
> Regards,
>
> Simon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org