re[4]: [Rainbowportal-devel] Why CVS is unused?

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40"
 xmlns:v = "urn:schemas-microsoft-com:vml"
 xmlns:o = "urn:schemas-microsoft-com:office:office"
 xmlns:w = "urn:schemas-microsoft-com:office:word"
 xmlns:st1 = "urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=Content-Type content="text/html;
 charset=us-ascii">
<META content="MSHTML 6.00.2800.1498" name=GENERATOR>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
shape {behavior:url(#default#VML);}
</STYLE>
<o:SmartTagType name="PostalCode" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
 name="State" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
 name="City" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
 name="Street" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
 name="place" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
 name="PlaceType" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
 name="PlaceName" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
 name="address" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
 name="PersonName" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>

<STYLE>
<!--
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
shape {behavior:url(#default#VML);}
st1\:*{behavior:url(#default#ieooui) }

 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Times New\000D\000A Roman";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-believe-normal-left:yes;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:924848860;
	mso-list-type:hybrid;
	mso-list-template-ids:-1769447230 67698705
 67698713 67698715 67698703 67698713 67698715
 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:2037389159;
	mso-list-type:hybrid;
	mso-list-template-ids:1743914546 -1393642806
 67698691 67698693 67698689 67698691 67698693
 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0F0;
	mso-level-tab-stop:37.5pt;
	mso-level-number-position:left;
	margin-left:37.5pt;
	text-indent:-19.5pt;
	font-family:Wingdings;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US style="MARGIN: 3pt 3pt 0.75pt"
 vLink=blue link=blue leftMargin=1 topMargin=1
 rightMargin=1><FONT face=Tahoma size=2>
<DIV>Hang on, Jonathan... don't fan that
 particular fire again... NOBODY ever said
 "it's OS, so if you want it fixed, do it&nbsp;yourself"
 (or ANY variation on that) as a generalization
 of the Rainbow OS project policy. One or
 two people (myself included) were VERY irritated
 by Charles Carroll, who arrived on the scene
 brimming with self-importance, DEMANDING
 improvements and behaving in a totally obnoxious
 and arrogant manner. Such remarks as "fix
 it yourself" were only ever directed at that
 one pompous individual, in response to his
 vitriolic attacks and criticisms. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Of course people are unsettled by change...
 that's human nature. As one of the instigators
 of that change, you have a responsibility
 to plan and execute it with the least possible
 disruption (which I fully acknowledge is
 exactly what you are trying to do). Nevertheless,
 after dozens of messages on this subject,
 I am STILL not clear on how/where I should
 be receiving/sending code updates. And I'm
 STILL not clear about the role of The Beta
 Team and the relationship between "The Beta
 Version" (as maintained by The Beta Team)
 and "the current CVS" (whether it's in SF-CVS
 or Subversion). </DIV>
<DIV>&nbsp;</DIV>
<DIV>When I complete my current work (within
 the next few days), where I am going to send
 those code changes? The "Beta Team" or the
 CVS? If it goes to the Beta Team, how/when
 is it&nbsp;then merged into the CVS? If it
 does go to the Beta Team first, what is the
 role of the CVS? Stable versions only? I
 thought the point of CVS was to have "the
 latest version", irrespective of whether
 it works or not, i.e. that the CVS is the
 mechanism of dissemination for all code changes,
 so that testing can be performed by all.
 Exactly HOW am I meant to transmit my code
 changes to "The Beta Team" if it is separate
 and distinct from "The CVS"? From where should
 I pull the latest updates for integration
 with my code - the CVS or some unspecified
 repository that is "The Beta Team's version".</DIV>
<DIV>&nbsp;</DIV>
<DIV>Please lay it all out for us: diagrams,
 explanations, rules, addresses, procedures,
 etc. Don't waste any more time on the justifications...
 I think we've flogged that one to death ;-)</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jeremy (jes1111)</DIV>
<DIV><BR><BR><BR>&nbsp;</DIV></FONT>
<DIV style="FONT-SIZE: x-small; FONT-FAMILY:
 Tahoma">
<DIV>----------------------- <B>Original
 Message</B> -----------------------</DIV>
<DIV>&nbsp;&nbsp;</DIV>
<DIV><B>From:</B>&nbsp;"Jonathan Minond"
 <A href="mailto:jon...@jo..."><FONT
 color=#0000ff>&lt;jon...@jo...&gt;</FONT></A></DIV>
<DIV><B>To:</B>&nbsp;<A href="mailto:rai...@li..."><FONT
 color=#0000ff>&lt;rai...@li...&gt;</FONT></A></DIV>
<DIV><B>Date:</B>&nbsp;Thu, 5 May 2005 18:54:29
 +0200</DIV>
<DIV><B>Subject:&nbsp;<U>RE: re[2]: [Rainbowportal-devel]
 Why CVS is unused?</U></B></DIV>
<DIV>&nbsp;&nbsp;</DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy
 size=2><SPAN style="FONT-SIZE: 10pt; COLOR:
 navy; FONT-FAMILY: Arial">&#8220;</SPAN></FONT><FONT
 face=Arial color=navy size=2><SPAN lang=EN-AU
 style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
 Arial">Lets get it out into the open. If
 you are on the rainbow-devel group you&#8217;re
 not having to put up with XXXX. But be aware
 that if you &#8220;volunteer&#8221; to move
 to the yahoo groups, expect the unexpected&#8221;<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">What
 "unexpected" things will happen? &nbsp;Well
 I guess they will get delivered faster than
 SF (perhaps you did not expect that). The
 users<BR>will have file areas to drop off
 (instead of attachments that can't appear
 in archives). There will be no more unviewable
 messages in the<BR>web interface (sourceforge
 bugs meant many messages in archives are
 unviewable). Google will find the YahooGroup
 posts where it does not find SF ones. I guess
 that is the unexpected stuff or am I off
 base?<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">&#8220;</SPAN></FONT><FONT
 face=Arial color=navy size=2><SPAN lang=EN-AU
 style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
 Arial">Lets get it out into the open. If
 you are on the rainbow-devel group you&#8217;re
 not having to put up with XXXX. But be aware
 that if you &#8220;volunteer&#8221; to move
 to the yahoo groups, expect the unexpected.&#8221;<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">[rainbowportal-devel]
 has traffic for developers that are beginners,
 intermediate and veterans. And tons of installation,
 usage and general<BR>questions come here
 (although Rahul's group <A href="http://groups.yahoo.com/group/RainbowPortal/"
 target=_blank>http://groups.yahoo.com/group<WBR>/RainbowPortal/</A>
 has been great about answering a lot of User
 questions and reducing the load here)<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">It
 is a "mixed" list, not pure. Because whoever
 organized/created these sourceforge lists
 never created a list for users/installers/admins/module
 builders (Perpetual Intermediates and
<SCRIPT>
<!--
D(["mb","Beginners in Alan Cooper terms)
 so these things get mixed with<br>developer/core
 issues constantly. &nbsp;Not all of you are
 &quot;users&quot; but only<br>LESS THAN &nbsp;1%
 of the members on this list are the movers
 and shakers.<br>The other 99% are indeed
 users and they are the ones that will make<br>this
 project a success or not in the marketplace.<br><br>&gt;
 Some of us have been around for more than
 a week<br>&gt; (like the current movers and
 shakers) and have always used<br>&gt; rainbowportal-devel.
 Users go to the forums and the <a onclick=\"return
 top.js.OpenExtLink(window,event,this)\" href=\"http://asp.net\"
 target=_blank>asp.net</a> forum.<br>And none
 of the Rainbow team answer them there. DNN
 questions and<br><a onclick=\"return top.js.OpenExtLink(window,event,this)\"
 href=\"http://ASP.net\" target=_blank>ASP.net</a>
 questions get great responses on the Forums.
 The Rainbowteam<br>neglects the forums so
 bad it hurts Rainbow severely -- people see
 DNN<br>getting great suport and tons of 0
 replies and 1 replies without<br>resolution
 in the Forums and never want to use Rainbow.<br><br>So
 savvy users who want answers rather than
 posting to a forum where<br>no one ever replies
 or finishes issues raised there (and the
 Rainbow<br>team never announces much there)
 post to [ainbowportal-devel] and<br>Rahul\'s
 group which at least have 80% answer ratios.<br><br>&gt;
 Really, there is so much garbage being put
 around now, it never happened<br>&gt; in
 the Rainbow community until late 2004 onwards.<br>You
 call the hundreds of improvements in Rainbow
 for example:<br>=&gt; short URLs<br>=&gt;
 80% of the leaks getting plugged<br>=&gt;
 Manu\'s installer<br>=&gt; better clearer
 icons<br>=&gt; SVN instead of CVS<br>=&gt;
 a new standard &quot;admin&quot; so newbies
 don\'t have to build their own and<br>documentation
 can assume a standard set of two dozen+ admin
 modules<br>rather than 3 cluttered one.<br>=&gt;
 &nbsp;Jon fixing severe Zen perf. flaws and
 documenting it, without Jes<br>saying thank
 him<br>=&gt; &nbsp;the improved <a onclick=\"return
 top.js.OpenExtLink(window,event,this)\" href=\"http://RainbowPortal.net\"
 target=_blank>",1]
);

//-->
</SCRIPT>
 Beginners in Alan Cooper terms) so these
 things get mixed with<BR>developer/core issues
 constantly. &nbsp;Not all of you are "users"
 but only a small fraction of the members
 on this list are the movers and shakers.
 The other majority are indeed users and they
 are the ones that will make this project
 a success or not in the marketplace.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">&#8220;</SPAN></FONT><FONT
 face=Arial color=navy size=2><SPAN lang=EN-AU
 style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
 Arial">Really, there is so much garbage being
 put around now, it never happened in the
 Rainbow community until late 2004 onwards.&#8221;<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">You
 call the hundreds of improvements in Rainbow
 for example:<BR>=&gt; short URLs<BR>=&gt;
 80% of the leaks getting plugged<BR>=&gt;
 Manu's installer<BR>=&gt; better clearer
 icons<BR>=&gt; SVN instead of CVS<BR>=&gt;
 a new standard "admin" so newbies don't have
 to build their own and documentation can
 assume a standard set of two dozen+ admin
 modules rather than 3 cluttered one.<BR>=&gt;
 &nbsp;Making an option to Zen perf. flaws
 and documenting it, igniting interest and
 use in Zen after so long<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">the
 improved <A href="http://RainbowPortal.net"
 target=_blank><FONT color=black><SPAN style="COLOR:
 windowtext; TEXT-DECORATION: none">
<SCRIPT>
<!--
D(["mb","RainbowPortal.net</a> site<br>=&gt;
 100s of fixes Charles demanded that expands
 our UI appeal getting<br>made in weeks instead
 of months, Manu\'s installer, etc.) garbage?<br>=&gt;
 an active constructively critical community
 rather than quiet<br>fearful one afriad of
 OS zealots insisting complaints not allowed
 --<br>unless the complainer personally fixes
 it - no PRIDE in workmanship<br>(or false
 pride at least in objectively shoddy work
 of past releases)<br>as someone said so well.<br><br>Please
 define garbage! This looks like massive improvement.
 Where is<br>this &quot;garbage&quot;?<br><br>&gt;
 I see many people who have contributed over
 such a long time that are<br>&gt; unhappy
 with what has happened, it disappoints me<br>Who
 are these unhappy people? Our user base and
 people downloading the<br>latest Rainbows
 with Manu\'s nifty new installer are super
 happy, The<br>grumbling by THE PUBLIC that
 Rainbow sucks and DNN is 10 x better has<br>been
 replaced with much effort to catch up and
 pass DNN -- and people<br>are no longer afraid
 to list the flaws in RB and feel that the
 team<br>will fix it promptly instead of saying
 &quot;Its OS do it yourself&quot;, &quot;what<br>do
 you expect it\'s free&quot; and &quot;how
 dare you say we have any flaws&quot; &nbsp;an<br>embarassing
 style that was the only way they reacted
 in past and drove<br>off so many people to
 the arms of DNN.<br><br>&gt;. However, if
 the<br>&gt; people working on Rainbow now
 want to do this, and the project managers<br>&gt;
 are happy to do it, then so be it.<br> &gt;
 Please don&quot;t forget to send a message
 to rainbowportal-devel when a new<br>&gt;
 version is ready. Us &quot;users&quot; might
 like to know so we can use it.<br>We have
 been constantly informing the SF list. &nbsp;
 (once again) Not all<br>of you are &quot;users&quot;
 but only less than a 1% of the members on
 this list<br>are the movers and shakers.
 The other 99% are indeed users and they<br>are
 the ones that will make this project a success
 or not in the<br>marketplace. And even the
 movers and shakers wear a &quot;user&quot;
 hat when<br>",1]
);

//-->
</SCRIPT>
</SPAN></FONT>RainbowPortal.net</A> site
 with many updated including all the work
 being done on confluence<BR>=&gt; 100s of
 fixes Charles demanded that expands our UI
 appeal getting made in weeks instead of months,
 Manu's installer, etc.) garbage?<BR>=&gt;
 an active constructively critical community
 rather than quiet fearful one afriad of OS
 zealots insisting complaints not allowed
 --<BR>unless the complainer personally fixes
 it - no PRIDE in workmanship (or false pride
 at least in objectively shoddy work of past
 releases)<BR>as someone said so well.<BR><BR>Please
 define garbage! This looks like massive improvement.
 Where is this "garbage"?<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy
 size=2><SPAN style="FONT-SIZE: 10pt; COLOR:
 navy; FONT-FAMILY: Arial">&#8220;</SPAN></FONT><FONT
 face=Arial color=navy size=2><SPAN lang=EN-AU
 style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
 Arial">I see many people who have contributed
 over such a long time that are unhappy with
 what has happened, it disappoints me. However,
 if the people working on Rainbow now want
 to do this, and the project managers are
 happy to do it, then so be it.</SPAN></FONT><FONT
 face=Arial color=navy size=2><SPAN style="FONT-SIZE:
 10pt; COLOR: navy; FONT-FAMILY: Arial">&#8221;</SPAN></FONT><FONT
 face=Arial color=navy size=2><SPAN lang=EN-AU
 style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
 Arial"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">Who
 are these unhappy people? Our user base and
 people downloading the latest Rainbows with
 Manu's nifty new installer are super happy,
 The grumbling by THE PUBLIC that Rainbow
 sucks and DNN is 10 x better has been replaced
 with much effort to catch up and pass DNN
 -- and people are no longer afraid to list
 the flaws in RB and feel that the team will
 fix it promptly instead of saying "Its OS
 do it yourself", "what do you expect it's
 free" and "how dare you say we have any flaws"
 &nbsp;an embarassing style that was the only
 way they reacted in past and drove off so
 many people to the arms of DNN.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">As
 for the developers, I don&#8217;t think they
 are Unhappy&#8230; I think they are voicing
 valid concerns to assure a smooth and flawless
 transition from older flawed wasy of managing
 that worked when the project was small, to
 new and improved ways of organizing a project
 that continues to grow in number of contributers,
 developers, documenters, users, and more.
 </SPAN></FONT><FONT face=Arial color=navy
 size=2><SPAN style="FONT-SIZE: 10pt; COLOR:
 navy; FONT-FAMILY: Arial"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">&#8220;However,
 if the people working on Rainbow now want
 to do this, and the project managers<BR>are
 happy to do it, then so be it.&#8221;<BR>&#8221;Please
 don"t forget to send a message to rainbowportal-devel
 when a new version is ready. Us "users" might
 like to know so we can use it.&#8221;<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
 Roman" size=3><SPAN style="FONT-SIZE: 12pt">We
 have been constantly informing the SF list.
 &nbsp; (once again) Not all of you are "users"
 but only less than a 1% of the members on
 this list<BR>are the movers and shakers.
 The other 99% are indeed users and they are
 the ones that will make this project a success
 or not in the<BR>marketplace. And even the
 movers and shakers wear a "user" hat when
<SCRIPT>
<!--
D(["mb","they install new versions or upgrade
 their site however briefly.<br><br>You and
 others who are posting complaints about rapid
 change and<br>multiple support avenues could
 spend time better helping with the new<br>builds
 and not posting so much &quot;I hate change,
 I hate more than 1<br>support avenue, this
 all sucks the team worked so well before&quot;.
 The<br>old system resulted in releases twice
 a year if that (when OS projects<br>are supposed
 to be updated daily) and those releases had
 leaks, far<br>too many bugs to be acceptable,
 and a very unhappy user base and<br>people
 quietly fleeing the project to DNN, and declaring
 Rainbow &nbsp;dead<br>rather than volunteering.
 If you are nostalgic for that or deny that<br>the
 past system produced buggy releases -- sure
 you don\'t want any big<br>changes so all
 this change upsets you. The people who are
 debating<br>Rainbow vs. DNN or the Starter
 Kits demanded change and we could<br>ignore
 it or inconvenience the veterans by shaking
 up the team and<br>giving people more support,
 better support, and more frequent builds,<br>and
 increase download and community activity
 ten-fold....<br>",1]
);

//-->
</SCRIPT>
 they install new versions or upgrade their
 site however briefly. You and others
 who are posting complaints about rapid change
 and multiple support avenues could spend
 time better helping with the new builds
 and not posting so much "I hate change, I
 hate more than 1 support avenue, this all
 sucks the team worked so well before". The old
 system resulted in releases twice a year
 if that (when OS projects are supposed to
 be updated daily) and those releases had
 leaks, far too many bugs to be acceptable,
 and a very unhappy user base and people quietly
 fleeing the project to DNN, and declaring
 Rainbow dead rather than volunteering. If
 you are nostalgic for that or deny that the
 past system produced buggy releases -- sure
 you don't want any big&nbsp; changes so all
 this change upsets you. The people who are
 debating Rainbow vs. DNN or the Starter Kits
 demanded change and we could ignore it or
 inconvenience the veterans by shaking up
 the team and giving people more support,
 better support, and more frequent builds,
 and increase download and community activity
 ten-fold....<o:p></o:p>
<o:p>&nbsp;</o:p>
-
 Jonathan<o:p></o:p>
<DIV>
<DIV class=MsoNormal style="MARGIN: 0in 0in
 0pt; TEXT-ALIGN: center" align=center>
<HR tabIndex=-1 align=center width="100%"
 SIZE=2>
</DIV>
From: rai...@li...
 [mailto:rai...@li...]
 On Behalf
 Of Mark Gregory Sent: Wednesday, May 04,
 2005 9:18 AM To: <st1:PersonName w:st="on">rai...@li...</st1:PersonName> Subject:
 RE: re[2]: [Rainbowportal-devel] Why CVS
 is unused?<o:p></o:p></DIV>
<o:p>&nbsp;</o:p>
Lets
 get it out into the open. If you are on the
 rainbow-devel group you&#8217;re not having
 to put up with XXXX. But be aware that if
 you &#8220;volunteer&#8221; to move to the
 yahoo groups, expect the unexpected.<o:p></o:p>
To
 say that the rainbowportal-devel group is
 for users and not the developers is wrong.
 Some of us have been around for more than
 a week (like the current movers and shakers)
 and have always used rainbowportal-devel.
 Users go to the forums and the asp.net forum.
 Really, there is so much garbage being put
 around now, it never happened in the Rainbow
 community until late 2004 onwards.<o:p></o:p>
I
 see many people who have contributed over
 such a long time that are unhappy with what
 has happened, it disappoints me. However,
 if the people working on Rainbow now want
 to do this, and the project managers are
 happy to do it, then so be it.<o:p></o:p>
Please
 don&#8217;t forget to send a message to rainbowportal-devel
 when a new version is ready. Us &#8220;users&#8221;
 might like to know so we can use it.<o:p></o:p>
Mark<o:p></o:p>
<o:p>&nbsp;</o:p>
<DIV>
<DIV class=MsoNormal style="MARGIN: 0in 0in
 0pt; TEXT-ALIGN: center" align=center>
<HR tabIndex=-1 align=center width="100%"
 SIZE=2>
</DIV>
From: rai...@li...
 [mailto:rai...@li...]
 On Behalf
 Of Jeremy Esland Sent: Wednesday, 4 May 2005
 1:07 PM To:
 <st1:PersonName w:st="on">rai...@li...</st1:PersonName> Subject:
 re[2]: [Rainbowportal-devel] Why CVS is unused?<o:p></o:p></DIV>
<o:p>&nbsp;</o:p>
<DIV>
Hmmmm indeed....<o:p></o:p></DIV>
<DIV>
&nbsp;<o:p></o:p></DIV>
<DIV>
I'm confused.
 I'm working on major enhancements to global.asax,
 Rewriter, Exception Management (including
 updating log4net to latest version and utilising
 new features thereof), a new SmartError page,
 Portal locking capabilities, etc. So from
 where should I now be pulling down the latest
 enhancements from others so I can integrate/test?
 And to&nbsp;where will I subsequently point
 my update?<o:p></o:p></DIV>
<DIV>
&nbsp;<o:p></o:p></DIV>
<DIV>
When was the rainbowportal-devel
 listed "demoted" to only dealing with "users"...
 I thought the "devel" part stood for "development"
 ;-)<o:p></o:p></DIV>
<DIV>
&nbsp;<o:p></o:p></DIV>
<DIV>
Jeremy (jes1111)<o:p></o:p></DIV>
<DIV>
&nbsp;<o:p></o:p></DIV>
<DIV>
&nbsp;<o:p></o:p></DIV>
<DIV>
<DIV>
-----------------------
 Original
 Message -----------------------<o:p></o:p></DIV>
<DIV>
&nbsp;&nbsp;<o:p></o:p></DIV>
<DIV>
From:&nbsp;"Jonathan
 Minond" <A href="mailto:jon...@jo...">&lt;jon...@jo...&gt;</A><o:p></o:p></DIV>
<DIV>
To:&nbsp;<A href="mailto:rai...@li...">&lt;rai...@li...&gt;</A><o:p></o:p></DIV>
<DIV>
Date:&nbsp;Mon, 2 May
 2005 15:19:13 +0200<o:p></o:p></DIV>
<DIV>
Subject:&nbsp;RE:
 [Rainbowportal-devel] Why CVS is unused?<o:p></o:p></DIV>
<DIV>
&nbsp;&nbsp;<o:p></o:p></DIV></DIV>
Hmmm&#8230;&#8230;Well,
 <o:p></o:p>
The aim is that
 over the course of the next few weeks we
 are doing a few things,<o:p></o:p>
1)&nbsp;&nbsp;&nbsp;&nbsp;
 stabilize
 the solution to represent 1.5 SP1, this means
 reproducing any changes that have been made
 to CVS that haven&#8217;t been reproduced
 yet one of the reasons I encourage any active
 developer to contact the <A href="mailto:bet...@ra...">bet...@ra...</A>,
 so that you can be working on making that
 happen.<o:p></o:p>
2)&nbsp;&nbsp;&nbsp;&nbsp;
 Introduce
 the new Page Manager, Forum Module, File
 Manager and whatever else gets done in time<o:p></o:p>
3)&nbsp;&nbsp;&nbsp;&nbsp;
 Finish
 testing and familiarizing ourselves with
 working with SVN. The goal being moving development
 to there so we get to benefit from all the
 SVN offers. <o:p></o:p>
4)&nbsp;&nbsp;&nbsp;&nbsp;
 Introduce
 the different layers of development. Dev-&gt;test-&gt;staging-&gt;release
 . This way the code to be considered for
 release has gone through the process of being
 developed, tested, received its feedback
 and should then be considered ready to be
 a public release. This can then happen more
 regularly and with less issues if the processes
 are ironed out through a multi step process.<o:p></o:p>
5)&nbsp;&nbsp;&nbsp;&nbsp;
 Ability
 to manage module images and css in theme
 directories<o:p></o:p>
6)&nbsp;&nbsp;&nbsp;&nbsp;
 Some
 changes/updates to modules such as discussion,
 sitemap, file directory tree and others<o:p></o:p>
Currently
 we have a functioning SVN solution for the
 beta solution, we are just working on learning
 to administer it better and with more ease,
 ironing out any issues so to speak, so that
 when the masses move from CVS to SVN hopefully
 it&#8217;s as smooth as possible.<o:p></o:p>
I
 think that over the next few weeks, things
 will become much clearer and easier for everyone,
 as more instructions and transitions come
 into play. For now I just Urge that anyone
 who is actively coding currently, should
 be making an effort to work with or on the
 betateam at this point, so that we can roll
 out a top notch SP1 for RB 1.5 as well as
 implement some much needed upgrades in the
 organization, switching from CVS -&gt; SVN,
 and assuring a better development process
 that guarantees rainbow continues to improve
 on its reputation and quality while still
 growing both its community and code base.<o:p></o:p>
I
 think that it&#8217;s amazing that so many
 people seem to be getting excited and showing
 lots of interest. I can assure you that although
 there are concerns, and a few bumps here
 and there, I strongly believe, and I think
 after following in the discussions and agreemenets
 over the past few months, what we are trying
 to do is put some of those things into action,
 that have been being spoken about more many
 months. I think its a lot of reasons to get
 excited, and like any changes it&#8217;s
 hard at first and nerve recking but most
 often for the best.<o:p></o:p>
The
 fact that there are so many updates to the
 CVS solution as well as the beta solution
 just means we have a great many people excited
 about working and coding for rainbow, making
 it a better project than ever before I believe.
 But with a growth in numbers, we need more
 organization as well to support the community.
 To many people download CVS to have it be
 a test solution. <o:p></o:p>
So
 If anyone is an SVN wizard, and want to help
 us get on the ball quicker, you can contact
 the beta team.<o:p></o:p>
If
 you are actively working on the cvs core
 or modules, fixing bugs, or working on something
 you want to make for SP1 then I suggest you
 contact the beta team.<o:p></o:p>
Ok,
 well&#8230; If there are any questions, feel
 free to ask more, maybe some other people
 working on the beta stuff and pushing on
 getting &#8220;order to the chaos&#8221;,
 you can review the message boards in the
 beta yahoo group to see some of the discussion
 and details as to the design plans.<o:p></o:p>
<o:p>&nbsp;</o:p>
Regards,<o:p></o:p>
Jonathan<o:p></o:p>
<o:p>&nbsp;</o:p>
<DIV>
<DIV class=MsoNormal style="MARGIN: 0in 0in
 0pt; TEXT-ALIGN: center" align=center>
<HR tabIndex=-1 align=center width="100%"
 SIZE=2>
</DIV>
From: rai...@li...
 [mailto:rai...@li...]
 On Behalf
 Of <st1:PersonName w:st="on">Mike
 Stone</st1:PersonName> Sent: Monday, May 02, 2005
 3:22 PM To:
 <st1:PersonName w:st="on">rai...@li...</st1:PersonName> Subject:
 Re: [Rainbowportal-devel] Why CVS is unused?<o:p></o:p></DIV>
<o:p>&nbsp;</o:p>
<DIV>
Yes, I see your
 point.&nbsp; How can you go to Jira and work
 on issues when CVS is no longer being maintained
 with code changes.&nbsp; The Beta Team does
 have a lot of changes and is only a small
 number of us.&nbsp; I know they are working
 hard to get a place for everyone to hook
 back up and be a community again.&nbsp; Now
 if you make changes to CVS (which I guess
 you can) then someone will have to run back
 to CVS and find out what you changed and
 move it to the new Beta Project. <o:p></o:p></DIV>
<DIV>
&nbsp;<o:p></o:p></DIV>
<DIV>
Jonathan, can
 you or Rahul share with the DeV list what
 is coming and the time line for it.&nbsp;
 <o:p></o:p></DIV>
<DIV>
&nbsp;<o:p></o:p></DIV>
<DIV>
<st1:PersonName w:st="on">Mike Stone</st1:PersonName> Director of Computer
 Information Services <st1:place w:st="on"><st1:PlaceName
 w:st="on">Kaskaskia</st1:PlaceName> <st1:PlaceType
 w:st="on">College</st1:PlaceType></st1:place> <st1:Street
 w:st="on"><st1:address w:st="on">27210 College
 Road</st1:address></st1:Street> <st1:place
 w:st="on"><st1:City w:st="on">Centralia</st1:City>,
 <st1:State w:st="on">IL</st1:State> <st1:PostalCode
 w:st="on">62801</st1:PostalCode></st1:place> 618-545-3201 <A
 href="http://www.kaskaskia.edu">www.kaskaskia.edu</A> &gt;&gt;&gt;
 jvi...@po... 5/2/2005 03:33:53
 &gt;&gt;&gt;<o:p></o:p></DIV>
<DIV>
In the last weeks there are a lot
 of new development make by people work in groups
 controlled by leader's. This is dangerous
 for the project. The new sources are not
 accessible to all the people and there
 are a risk for repeated or not compatible
 development. A lot of valid developers
 can not have time now to create new sources,
 but they have time to testear and to solve
 small problems. I agree in some cases
 work in groups, but I'm absolutly desagree
 with not use CVS like a normal container
 for sources, included the new aggregations.<o:p></o:p></DIV></DIV>-------------------------------------------------------
 This SF.Net email is sponsored by: NEC IT
 Guy Games. Get your fingers limbered up and
 give it your best shot. 4 great events, 4
 opportunities to win big! Highest score wins.NEC
 IT Guy Games. Play to win an NEC 61 plasma
 display. Visit http://www.necitguy.com/?r=20
 _______________________________________________
 Rainbowportal-devel mailing list Rai...@li...
 https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel</BODY></HTML>