Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com
 designates 66.249.82.234 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:mime-version:in-reply-to:references:content-type:message-id:from:subject:date:to:x-mailer;
        b=VR9mVLAyYTwKt5pPt2sRuw0rZAxrkE1aTbvRLOJQcrGcvN9XyelTGdN7jah3owmNUu/aG6Fm87hqJ7F237p52moIsaMVg0bVxe1Di3MzEplAifblJXWmJ+qkEAtTYt85UFyjibfTuTrWhTXfAJ0qcjfg0kiLbIATmPUGw+4PH9k=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <22d56c4d0707272241v60d98c91ja5a1038efa06c083@mail.gmail.com>
References: <22d56c4d0707252221p6b2818abh21058ba0ce04372a@mail.gmail.com>
 <CAE82114-2FBA-4FB5-9982-5B9271BC2C97@gmail.com>
 <22d56c4d0707272241v60d98c91ja5a1038efa06c083@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-1--874132909
Message-Id: <1373B79F-D52A-4EC4-A090-4A128C8DCF40@gmail.com>
From: Kevan Miller <kevan.miller@gmail.com>
Subject: Re: [DISCUSS] Adding a "Tech Preview" portlet group in Admin Console
 in G 2.0
Date: Sun, 29 Jul 2007 15:56:20 -0400
To: dev@geronimo.apache.org


--Apple-Mail-1--874132909
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On Jul 28, 2007, at 1:41 AM, Vamsavardhana Reddy wrote:

>
>
> On 7/28/07, Kevan Miller <kevan.miller@gmail.com> wrote:
>
> On Jul 26, 2007, at 1:21 AM, Vamsavardhana Reddy wrote:
>
>> How about adding a "Tech Preview" portlet group in Admin Console  
>> in G 2.0 where we can include the portlets (for e.g., the "Create  
>> Plan" portlet Shiva is working on.  See https://issues.apache.org/ 
>> jira/browse/GERONIMO-3254 ) for which user feedback will play a  
>> great role in improving those further.  Once we decide on whether  
>> to retain those or not, we can either move them out to a different  
>> group or remove them from Admin Console accordingly.
>
> Some of the new pluggable console support would have helped, here.  
> But that's not going into 2.0. Personally, sounds like this should  
> go into trunk, if it's not ready... Can still get good feedback...
>
> --kevan
>
>
> The idea is that if these portlets go in as part of a release with  
> binaries readily available for download, we have a better chance of  
> getting more users to try the portlets and possibly provide some  
> feedback too in the linked wiki pages.  If it goes only into trunk,  
> the users will still have to build the binaries from trunk, which  
> they may not want to/may not succeed due to some reason or the other.

Yes, I understood the idea.

If a committer thinks that this code is ready and wants to commit it,  
then why isn't it in trunk? If it was in trunk, then we could  
evaluate and discuss getting it into branches/2.0. I'm currently  
doubtful that it should go into 2.0...

--kevan


--Apple-Mail-1--874132909
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><BR><DIV><DIV>On Jul 28, 2007, =
at 1:41 AM, Vamsavardhana Reddy wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><BR><BR><DIV><SPAN class=3D"gmail_quote">On 7/28/07, <B =
class=3D"gmail_sendername">Kevan Miller</B> &lt;<A =
href=3D"mailto:kevan.miller@gmail.com">kevan.miller@gmail.com</A>&gt; =
wrote:</SPAN><BLOCKQUOTE class=3D"gmail_quote" style=3D"border-left: 1px =
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: =
1ex;"> <DIV style=3D""><SPAN class=3D"q"><BR><DIV><DIV>On Jul 26, 2007, =
at 1:21 AM, Vamsavardhana Reddy wrote:</DIV><BR><BLOCKQUOTE =
type=3D"cite">How about adding a "Tech Preview" portlet group in Admin =
Console in G 2.0 where we can include the portlets (for e.g., the =
"Create Plan" portlet Shiva is working on.=A0 See <A =
href=3D"https://issues.apache.org/jira/browse/GERONIMO-3254" =
target=3D"_blank" onclick=3D"return =
top.js.OpenExtLink(window,event,this)"> =
https://issues.apache.org/jira/browse/GERONIMO-3254 </A>) for which user =
feedback will play a great role in improving those further.=A0 Once we =
decide on whether to retain those or not, we can either move them out to =
a different group or remove them from Admin Console accordingly. =
<BR></BLOCKQUOTE><BR></DIV></SPAN><DIV>Some of the new pluggable console =
support would have helped, here. But that's not going into 2.0. =
Personally, sounds like this should go into trunk, if it's not ready... =
Can still get good feedback... </DIV><SPAN =
class=3D"sg"><DIV><BR></DIV><DIV>--kevan</DIV></SPAN></DIV></BLOCKQUOTE></=
DIV><BR><BR>The idea is that if these portlets go in as part of a =
release with binaries readily available for download, we have a better =
chance of getting more users to try the portlets and possibly provide =
some feedback too in the linked wiki pages.=A0 If it goes only into =
trunk, the users will still have to build the binaries from trunk, which =
they may not want to/may not succeed due to some reason or the other.<BR =
class=3D"khtml-block-placeholder"></BLOCKQUOTE><BR></DIV><DIV>Yes, I =
understood the idea.=A0</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>If a committer thinks that =
this code is ready and wants to commit it, then why isn't it in trunk? =
If it was in trunk, then we could evaluate and discuss getting it into =
branches/2.0. I'm currently doubtful that it should go into =
2.0...</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>--kevan</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><BR></BODY></HTML>=

--Apple-Mail-1--874132909--