commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Min Cha <minslo...@gmail.com>
Subject Re: [DISCUSSION] The way for Chain2
Date Wed, 29 Apr 2009 01:37:51 GMT
 Hi Christian.
Thanks for your interest and advices. :)

>>>is it possible to enhance Chain1 with RobustTask features instead of a
complete replacement?

Yes, It`s a possible job.

>>> All is very similar, and sometimes even Chain1
looks better to my eyes than RobustTask (for example i don't think
that throwing with RuntimExceptions is a very good idea). But there
are some cool things in chain2. Why not join forces?

I am trying to find an right way to incubate Robust-Task. It can be the best
way to join forces with original Chain but not a easy way. With providing
Chain2`s features, ensuring backward compatibility with Chain might make
Chain2 dizzy. I wonder this approach is a good way because I have been
trying to keep Chain2 simple as possible.

>>> Its usually a good start to work in issues first and dive into code.
If you want, lets discuss about some features of RobustTask coming
into Chain.

Thank you very much. I will consider your advices. :)

On Tue, Apr 28, 2009 at 6:39 PM, Christian Grobmeier <grobmeier@gmail.com>wrote:

> Hi Min Cha,
>
> is it possible to enhance Chain1 with RobustTask features instead of a
> complete replacement? All is very similar, and sometimes even Chain1
> looks better to my eyes than RobustTask (for example i don't think
> that throwing with RuntimExceptions is a very good idea). But there
> are some cool things in chain2. Why not join forces?
>
> There are some issues in Jira:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310462&fixfor=-1
>
> Its usually a good start to work in issues first and dive into code.
> If you want, lets discuss about some features of RobustTask coming
> into Chain.
>
> Best,
> Christian
>
> On Sun, Apr 26, 2009 at 9:57 AM, Min Cha <minslovey@gmail.com> wrote:
> > Hi all,
> >
> > I suggested the ideas for Chain2 incubation to Commons mailing but didn`t
> > receive any answers. So, I have written a short document to compare
> Chain2
> > against the original Chain.
> >
> > http://code.google.com/p/robust-coupe/wiki/ChainAndChain2
> >
> > I would really like to start this project with Commons sponsoring so
> Commons
> > PMC`s interest is needed. Please, feel free to give me any advice.
> >
> > ---------- Forwarded message ----------
> > From: Min Cha <minslovey@gmail.com>
> > Date: Thu, Apr 16, 2009 at 10:46 AM
> > Subject: Re: [DISCUSSION] The way for Chain2
> > To: Commons Developers List <dev@commons.apache.org>
> >
> >
> > Oh, I`m so sorry to pick up this issue impatiently. I thought that
> > discussion was over but it wasn`t. Now, the discussion is still
> progressing
> > at Incubator mailing.
> >
> >
> > On Wed, Apr 15, 2009 at 10:33 AM, Min Cha <minslovey@gmail.com> wrote:
> >
> >> Hi all.
> >>
> >> Unfortunately, Commons Incubator proposal seems not accepted by IPMC.
> This
> >> result is not a good news to me who wanted to start with Commons
> Incubator.
> >>
> >> I would like to develop the next version of Chain and the seed for it is
> >> Robust-Task which was introduced through a previous mail(
> >> http://www.nabble.com/Robust-Task-introduction-td22571002.html). Now,
> two
> >> ways may be available in my opinion.
> >>
> >> 1. Proposal to IPMC
> >> In this case, I would like that some of Commons PMCs and committers
> become
> >> mentors for Chain2. Also, as mentioned on Common Incubator proposal
> >> discussion, I would like to use an option to graduate to Commons rather
> than
> >> TLP. In my opinion, this approach can be a good practice for Commons
> which
> >> may meet similar problems in the future.
> >>
> >> 2. Sandbox
> >> In this case, I would become a contributor or a committer which should
> >> learn Apache way. This is up to Commons PMC but I have already seen
> Commons
> >> PMC`s opinion about this problem through discussion. Of course, I
> respect
> >> and understand Commons PMC`s point of view.
> >>
> >> What is the better way? Please give me advice.
> >>
> >> --
> >> Min Cha, Dreaming Developer
> >> Task Framework :
> >> http://code.google.com/p/robust-coupe/wiki/RobustTaskIntroduction
> >> English : http://minslovey.blogspot.com
> >> Korean : http://minslovey.tistory.com
> >>
> >
> >
> >
> > --
> > Min Cha, Dreaming Developer
> > Task Framework :
> > http://code.google.com/p/robust-coupe/wiki/RobustTaskIntroduction
> > English : http://minslovey.blogspot.com
> > Korean : http://minslovey.tistory.com
> >
> >
> >
> > --
> > Min Cha, Dreaming Developer
> > Task Framework :
> > http://code.google.com/p/robust-coupe/wiki/RobustTaskIntroduction
> > English : http://minslovey.blogspot.com
> > Korean : http://minslovey.tistory.com
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
Min Cha, Dreaming Developer
Task Framework :
http://code.google.com/p/robust-coupe/wiki/RobustTaskIntroduction
English : http://minslovey.blogspot.com
Korean : http://minslovey.tistory.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message