<!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:jonathan@..."><FONT
color=#0000ff>&lt;jonathan@...&gt;</FONT></A></DIV>
<DIV><B>To:</B>&nbsp;<A href="mailto:rainbowportal-devel@..."><FONT
color=#0000ff>&lt;rainbowportal-devel@...&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&gt;
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.<BR><BR>You and others
who are posting complaints about rapid change
and multiple support avenues could spend
time better helping with the new<BR>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<BR>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<BR>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></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
Roman" size=3><SPAN style="FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New
Roman" size=3><SPAN style="FONT-SIZE: 12pt">-
Jonathan</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>
<DIV>
<DIV class=MsoNormal style="MARGIN: 0in 0in
0pt; TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt">
<HR tabIndex=-1 align=center width="100%"
SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT:
bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma"> rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf
Of </SPAN></B>Mark Gregory<BR><B><SPAN style="FONT-WEIGHT:
bold">Sent:</SPAN></B> Wednesday, May 04,
2005 9:18 AM<BR><B><SPAN style="FONT-WEIGHT:
bold">To:</SPAN></B> <st1:PersonName w:st="on">rainbowportal-devel@...</st1:PersonName><BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B>
RE: re[2]: [Rainbowportal-devel] Why CVS
is unused?</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New
Roman" size=3><SPAN style="FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=MsoNormal><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.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy
size=2><SPAN lang=EN-AU style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal><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.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy
size=2><SPAN lang=EN-AU style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy
size=2><SPAN lang=EN-AU style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">Mark<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy
size=2><SPAN lang=EN-AU style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="MARGIN: 0in 0in
0pt; TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt">
<HR tabIndex=-1 align=center width="100%"
SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT:
bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma"> rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf
Of </SPAN></B>Jeremy Esland<BR><B><SPAN style="FONT-WEIGHT:
bold">Sent:</SPAN></B> Wednesday, 4 May 2005
1:07 PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
<st1:PersonName w:st="on">rainbowportal-devel@...</st1:PersonName><BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B>
re[2]: [Rainbowportal-devel] Why CVS is unused?</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New
Roman" size=3><SPAN lang=EN-AU style="FONT-SIZE:
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">Hmmmm indeed....<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">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></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">When was the rainbowportal-devel
listed "demoted" to only dealing with "users"...
I thought the "devel" part stood for "development"
;-)<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">Jeremy (jes1111)<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">-----------------------
<B><SPAN style="FONT-WEIGHT: bold">Original
Message</SPAN></B> -----------------------<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT:
bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;"Jonathan
Minond" <A href="mailto:jonathan@...">&lt;jonathan@...&gt;</A><o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT:
bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">To:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;<A href="mailto:rainbowportal-devel@...">&lt;rainbowportal-devel@...&gt;</A><o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT:
bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Date:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;Mon, 2 May
2005 15:19:13 +0200<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT:
bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Subject:&nbsp;<U>RE:
[Rainbowportal-devel] Why CVS is unused?</U></SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma"><o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;&nbsp;<o:p></o:p></SPAN></FONT></P></DIV></DIV>
<P class=MsoNormal><FONT face=Arial color=navy
size=2><SPAN style="FONT-SIZE: 10pt; COLOR:
navy; FONT-FAMILY: Arial">Hmmm&#8230;&#8230;Well,
<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">The aim is that
over the course of the next few weeks we
are doing a few things,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in;
TEXT-INDENT: -0.25in; mso-list: l0 level1
lfo2"><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"><SPAN style="mso-list: Ignore">1)<FONT
face="Times New Roman" size=1><SPAN style="FONT:
7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;
</SPAN></FONT></SPAN></SPAN></FONT><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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:betateam@...">betateam@...</A>,
so that you can be working on making that
happen.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in;
TEXT-INDENT: -0.25in; mso-list: l0 level1
lfo2"><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"><SPAN style="mso-list: Ignore">2)<FONT
face="Times New Roman" size=1><SPAN style="FONT:
7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;
</SPAN></FONT></SPAN></SPAN></FONT><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">Introduce
the new Page Manager, Forum Module, File
Manager and whatever else gets done in time<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in;
TEXT-INDENT: -0.25in; mso-list: l0 level1
lfo2"><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"><SPAN style="mso-list: Ignore">3)<FONT
face="Times New Roman" size=1><SPAN style="FONT:
7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;
</SPAN></FONT></SPAN></SPAN></FONT><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in;
TEXT-INDENT: -0.25in; mso-list: l0 level1
lfo2"><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"><SPAN style="mso-list: Ignore">4)<FONT
face="Times New Roman" size=1><SPAN style="FONT:
7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;
</SPAN></FONT></SPAN></SPAN></FONT><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in;
TEXT-INDENT: -0.25in; mso-list: l0 level1
lfo2"><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"><SPAN style="mso-list: Ignore">5)<FONT
face="Times New Roman" size=1><SPAN style="FONT:
7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;
</SPAN></FONT></SPAN></SPAN></FONT><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">Ability
to manage module images and css in theme
directories<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in;
TEXT-INDENT: -0.25in; mso-list: l0 level1
lfo2"><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"><SPAN style="mso-list: Ignore">6)<FONT
face="Times New Roman" size=1><SPAN style="FONT:
7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;
</SPAN></FONT></SPAN></SPAN></FONT><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">Some
changes/updates to modules such as discussion,
sitemap, file directory tree and others<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">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></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">Regards,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT
face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">Jonathan<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"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="MARGIN: 0in 0in
0pt; TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt">
<HR tabIndex=-1 align=center width="100%"
SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT:
bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma"> rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf
Of </SPAN></B><st1:PersonName w:st="on">Mike
Stone</st1:PersonName><BR><B><SPAN style="FONT-WEIGHT:
bold">Sent:</SPAN></B> Monday, May 02, 2005
3:22 PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
<st1:PersonName w:st="on">rainbowportal-devel@...</st1:PersonName><BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B>
Re: [Rainbowportal-devel] Why CVS is unused?</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New&#13;&#10;
Roman" size=3><SPAN style="FONT-SIZE: 12pt;
FONT-FAMILY: 'Times New
Roman'"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">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></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">Jonathan, can
you or Rahul share with the DeV list what
is coming and the time line for it.&nbsp;
<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in
0pt"><st1:PersonName w:st="on"><FONT face=Tahoma
size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY:
Tahoma">Mike Stone</SPAN></FONT></st1:PersonName><BR><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE:
10pt; FONT-FAMILY: Tahoma">Director of Computer
Information Services<BR><st1:place w:st="on"><st1:PlaceName
w:st="on">Kaskaskia</st1:PlaceName> <st1:PlaceType
w:st="on">College</st1:PlaceType></st1:place><BR><st1:Street
w:st="on"><st1:address w:st="on">27210 College
Road</st1:address></st1:Street><BR><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><BR>618-545-3201<BR><A
href="http://www.kaskaskia.edu">www.kaskaskia.edu</A><BR><BR>&gt;&gt;&gt;
jviladiu@... 5/2/2005 03:33:53
&gt;&gt;&gt;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM:
12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in;
mso-margin-top-alt: 0in"><FONT face=Tahoma
size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY:
Tahoma">In the last weeks there are a lot
of new development make by people work in<BR>groups
controlled by leader's.<BR><BR>This is dangerous
for the project. The new sources are not
accessible to all<BR>the people and there
are a risk for repeated or not compatible
development.<BR>A lot of valid developers
can not have time now to create new sources,
but<BR>they have time to testear and to solve
small problems.<BR><BR>I agree in some cases
work in groups, but I'm absolutly desagree
with not<BR>use CVS like a normal container
for sources, included the new aggregations.<o:p></o:p></SPAN></FONT></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 Rainbowportal-devel@...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel</BODY></HTML&gt;

This is a draft, of the contibuter policies that we are trying to bring
forth. When reading this keep in mind that things are still either being
tested or in design and early implementation. This will undergo some
revision, feedback from all of you, and as things are ready to go, we will
post clear documentation on rainbowportal.net and confluence.
Rainbow Policy Plan: ( Draft 1)
None of this is fully existent yet, so there is no actual migration
yet. Once we find a suitable SVN administrator who can take
responsibility for managing the svn server, then we can proceed with
fully creating a user base. Currently, the whole solution is running
one only one user, which is unacceptable way to manage multiple users.
Two documenting the best and simpliest migration path.
The Final Goal:
Dev solution - this is a free for all so to speak solution, where
active devs are updating their solutions many times over and commiting
code, working alone or with others on whatever Task they've so chosen.
Anyone can be part of this solution, it's open source, but most people
are not going to be doing this. You have builds that are not even
going to compile possibly, and db's that might not run. But it's open
accesable code that dev's can work on together with all the power that
SVN brings ( once we get the administration worked out ).
Test solution - this is also free solution, that will have a clear
path of access for everyone, but this is what you would call qa, beta
stuff, your saying a feature is developed, its ready for some usage
and possibly submission to kernel or added download somewhere. You
want multiple people to download and test the code, installation, make
sure it's localized, make sure it something that won't cause problems
once it's in production. This gets a few extra pairs of eyes on some
code to make sure it's top notch RB make us proud gold
Beta / Staging Solution - if something has passed tests, than the code
is good and will be previewed life on rainbowbeta always, this gets
initial feedback going, this is still code you need to download and
compile yourself.. This is not release code, this is not Rainbow
Version, there is no support demanded for dev solution, or test
solutions, on the Forums and Support Groups you deal with current RB
versions, these are documented and easy to manage, beta is prerelease,
it can be buggy, it can have rough install although most stuff should
be weeded out in test solution.
Final Release and Version - By having the different steps, you have
what seems like a longer process but in fact, ends up being a simple
way for everyone to find a smooth place. Newbies, oldtimers, gurus
masters and students all the active coders will spend there free time
working in dev solution, modifying code, busting their heades..
Experienced people who have varying times will put ther time in test
solution and or beta staging, downloading what should be working code,
compiles installs, should be safe upgrades for your existing db's you
have people all around the world using rb in different scenarios who
know how to set it up and test on their different needs quickly and
efficeitnly, finding the common bugs and problems, making sure
installs and upgrades are safe and smooth, this happens quickly now,
so code that is moved from dev to test, goes quickly throuh in
intensive move in some cases might have to go back to dev, but in most
cases probably with minor bugs or issues moving inot final, letting
you have good clean releases more often, and with less issues, less
support needed,and more efficient use of everyones time doing what
they have time for whenever they do. Bugs and issues can be found
anywhere, and can be dealt with by any of the teams or solutions,
everyone has full access to everything, its just a matter of choosing
whats best for each at what time I think.
------------------------------------
In response the "1+4=5", if you take the time to manage the lists
properly, as many have pointed out, open a gmail account, have every
lists sf, yahoo, whatever you want point there and you have now only
one place you need to manage everything. If you have a big fat hard
drive you can even point your gmail to your outlook and do it all
locally. So "1+whatever you want still equals one If you put a little
effort into using the tools the way they can be used" and 1 is fine if
1 where a good tool, but sf mail list is TOO SLOW to be a good tool.
"I would simply like someone to indicate on rainbowportal.net what all
the lists are, where they are, what they are for and who to contact to
join them."
http://www.rainbowportal.net
<http://www.rainbowportal.net/site/3405/support.aspx&gt;
/site/3405/support.aspx all of the yahoo
groups have been posted on this page for some time. There posting was
announced to this list by Chris more than once if I am not mistaken.
How to update them and properly categorize them was even discussed on
this list.
Aslo the betateam mail was announced on this list for anyone
interested in coding against that solution to try and move its release
along faster. It started out as a solution by a new comer, and yes as
your worried stated backward compatibily were one of the issues that
came up, and this is why thanks to several more experienced and bright
team members with more experience Rob, Manu, Rick, Rahul, Charles,
Mark, Kieth, Jose and all those who have gone to the beta site and made
issues aware the solution is moving along and getting in shape with
regards to those concerns while still managing to move forward and
bring about lots of great updates.
------------------------------------
Back to the point, as each step is ready to go with proper
administration, and documented, everything is going to be posted on
rainbowportal.net, as well as all the groups, with how and where
everything is. That can't happen yet, because it's not all there yet.
If something is only in design or test right now, how do you want
everyone to go try and use it? It doesn't exist yet.
The same for New Genesis. Everyone wants to know how and where to code
it..but it doesn't exist yet, not even a kernel, it's still in design,
that's what the New Genesis group does, it discusses the design of the
code from the ground up, and as each component is optimized it is
slowly coming together starting with a high quality DB lead by Bill.
Where we stand currently:
Currently the dev solution is almost up and running, our major holdback is
SVN administration, but we are working on that end.
Once dev solution has administration it is a matter of one or two days to
set up the other solutions, test, beta and prodo. If you check the Yahoo
group, a discussion was even borught up that there is a way to sync svn and
cvs. SO that final release versions or very clean code are still accessable
on sourceforge with the anonymous accounts most people have today. This is
an interesting idea that could save lots of support problems later with
migration.
_____
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of Mark
Gregory
Sent: Wednesday, May 04, 2005 1:44 PM
To: rainbowportal-devel@...
Subject: RE: re[2]: [Rainbowportal-devel] Why CVS is unused?
As I said, go for it. All open source project teams change over time, it is
impossible to maintain a life and contribute to a project as much as we
would all like. If you have time to allocate to Rainbow, great news for all
of us. What you miss is that whilst some of us cannot code during busy
periods of the year, we like to keep abreast of what is happening. You are
making it harder to stay up with what is happening, by increasing the number
of lists we have to belong to. If you fail to understand that then what can
I say that you would understand? Let me try
1 + 4 = 5
I would simply like someone to indicate on rainbowportal.net what all the
lists are, where they are, what they are for and who to contact to join
them.
Having said that, it is important that we are all able to see the source
code progress, and Manu has said this will continue to be. It would be
devastating if changes are made that break part of the functionality. Some
of us have many years invested in Rainbow. We need to be able to migrate
from one db build to the next. I may be wrong, but when I have seen this
sort of spilt occur in other projects, the result is a loss of backwards
compatibility and no way to migrate. Jonathan, please keep this in mind.
Being able to migrate the db to new versions is a fundamental must. I can
survive most other problems.
I would appreciate being pointed at SVN and the tools needed to interact
with it.
mark
_____
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of
Jonathan Minond
Sent: Wednesday, 4 May 2005 6:27 PM
To: rainbowportal-devel@...
Subject: RE: re[2]: [Rainbowportal-devel] Why CVS is unused?
"..see many people who have contributed over such a long time that are
unhappy with what has happened, it disappoints me. ."
Are they actually unhappy? Or are they just voicing concerns, opening
discussion, which help guide the transision and try to make things as error
free and smooth as possible.
I might be wrong, but it was not the new people in the groups who started
the discussion of SVN months ago, its not the new people who started the
discussion of better testing and standards to the code, it was everyone in
this list, who has taken part in the overall discussions for many many
months. Now, there are some people actually trying to make those things
happen, and like an organization change, its not nessesarly easy or obvious
at first. But with a little patience and dilligance, everyone gets what they
wanted or begins to see things they wanted coming about.
.." it never happened in the Rainbow community until late 2004 onwards."...
yeah, and if you ask the public, rainbow wasn't even so active until late
2004 when it pushed to make 1.5. Before late 2004, RB's name was bad,
disapperarig and hurt. since late 2004, awareness is growing, downloads are
growing, and the community is growing. Every time you mention locking
discussion to this list.. It seems like you don't want any of those things
to happen.
".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.."
Right of the bat, I don't think that's a fair one. Unless I am completely
mistaken, since day one, the BetaTeam was announced before it existed,
inviting people to take part in it, getting advice on it from many older and
big contributers to Rainbow, from day one all the yahoo lists where
mentioned and listed in this list, and brought up for discussion on how to
show make them findable from rainbowportal.net. From day one every yahoo
group was open for anyone to join, with the complaints about this list being
that sf mail list is not good. It's slow, has big delays, and those message
delays cause confusion at many times. Yahoo groups offer the same thing as
this list, only better. From day one, I made the beta solutions available
for download, so that some of the better more experienced Rainbow developers
like yourself could download and help me test and debug it, becuyase there
was so much core changes, it would have been suicide to just shove this into
CVS, so it made as good a time as any to start pushing some other ideas that
THIS GROUP the dev list has discussed more than once, and then nothing
happens. This dev list was in charge of managing all the community, yet...
so what happened? As soon as the yahoo groups came into play, you got better
support on yahoo and on forums.
I think the problem is a lot of people are very uncomfortable in the old and
known.. And even though almost everyone can agree the new is better, it's
not always an easy and smooth transition for the people who are used to one
thing. Well, one of My aims, and I am sure that of all those involved in
trying to get SVN running smooth, in setting up betateam, dev solutions,
test solutions, etc.those who are working on organization in
rainbowportal.net, confluence, forums, those who are doing it in code,
servers, hosting, resources, those setting up non English support areas, and
building the community. I am sure that the point is to try to find a way to
make it as easy and smooth a transition for the developers, causal users,
newbies, everyone. And please, lets stop just generalizing everything.
If I said, 90% of users are interested in the newest "release" and not the
day to day tests, then don't take that personally and translate as saying
the whole devlist is users. Take into account, that before the yahoo groups,
the forums were on their way to dying, and the dev list was your only place
to find anything out about rainbow. so it's safe to say that not everyone on
this list is a developer. I am certain that not everyone on this list even
writes code, and I am certain that not all those who do contribute code to
public RB. Everyone who has contributed, is pretty aware they have done so,
and anyone who has peeked at the code is probably pretty familiar with a
fair number of those names. So please don't triviliaze my statements or
generalize them into making it seem like I am insulting any RB team member.
I have great respect for the entire RB team, coders and not, everyone makes
a big effort and dedicates time in whatever ways they can. Some people write
documentation, others help organize the sites, and community, others have
time to look at the sites and offer feedback and find bugs, others have time
to look at bugs and fix them, others have time to code new features.
Whatever you are doing, you all know that when you put something out there,
everyone appreciates it and is very greeatful. But let's be honest, THIS
LIST IS NOT ONLY DEVELOPERS, in fact I am inclined to believe that less than
HALF this list is actually coders. Then,, take into account the amount of
anonymous public users that have come across this message archive, how do
they separate what is working stable releases, from what is development.
when this is the only discussion forum for developers? Just let it go.. How
many times would you like to bring up the discussion that there is more than
one source of information and discussion? Oddly enough..
RainbowModules, RainbowThemes, RainbowBeta and RainbowRecruits never have
off topic discussions, they are all geared at not wasting peoples times.
_____
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of Mark
Gregory
Sent: Wednesday, May 04, 2005 9:18 AM
To: rainbowportal-devel@...
Subject: RE: re[2]: [Rainbowportal-devel] Why CVS is unused?
Lets get it out into the open. If you are on the rainbow-devel group you're
not having to put up with XXXX. But be aware that if you "volunteer" to move
to the yahoo groups, expect the unexpected.
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.
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.
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.
Mark
_____
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of Jeremy
Esland
Sent: Wednesday, 4 May 2005 1:07 PM
To: rainbowportal-devel@...
Subject: re[2]: [Rainbowportal-devel] Why CVS is unused?
Hmmmm indeed....
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 where will I
subsequently point my update?
When was the rainbowportal-devel listed "demoted" to only dealing with
"users"... I thought the "devel" part stood for "development" ;-)
Jeremy (jes1111)
----------------------- Original Message -----------------------
From: "Jonathan Minond" <mailto:jonathan@...> <jonathan@...>
To: <mailto:rainbowportal-devel@...>
<rainbowportal-devel@...>
Date: Mon, 2 May 2005 15:19:13 +0200
Subject: RE: [Rainbowportal-devel] Why CVS is unused?
Hmmm..Well,
The aim is that over the course of the next few weeks we are doing a few
things,
1) stabilize the solution to represent 1.5 SP1, this means reproducing
any changes that have been made to CVS that haven't been reproduced yet one
of the reasons I encourage any active developer to contact the
betateam@..., so that you can be working on making that happen.
2) Introduce the new Page Manager, Forum Module, File Manager and
whatever else gets done in time
3) 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.
4) Introduce the different layers of development.
Dev->test->staging->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.
5) Ability to manage module images and css in theme directories
6) Some changes/updates to modules such as discussion, sitemap, file
directory tree and others
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's as smooth as possible.
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 -> 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.
I think that it'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's hard at first and nerve recking but most
often for the best.
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.
So If anyone is an SVN wizard, and want to help us get on the ball quicker,
you can contact the beta team.
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.
Ok, well. If there are any questions, feel free to ask more, maybe some
other people working on the beta stuff and pushing on getting "order to the
chaos", you can review the message boards in the beta yahoo group to see
some of the discussion and details as to the design plans.
Regards,
Jonathan
_____
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of Mike
Stone
Sent: Monday, May 02, 2005 3:22 PM
To: rainbowportal-devel@...
Subject: Re: [Rainbowportal-devel] Why CVS is unused?
Yes, I see your point. How can you go to Jira and work on issues when CVS
is no longer being maintained with code changes. The Beta Team does have a
lot of changes and is only a small number of us. I know they are working
hard to get a place for everyone to hook back up and be a community again.
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.
Jonathan, can you or Rahul share with the DeV list what is coming and the
time line for it.
Mike Stone
Director of Computer Information Services
Kaskaskia College
27210 College Road
Centralia, IL 62801
618-545-3201
http://www.kaskaskia.edu
>>> jviladiu@... 5/2/2005 03:33:53 >>>
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.
------------------------------------------------------- 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 Rainbowportal-devel@...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel

"Lets get it out into the open. If you are on the rainbow-devel group you're
not having to put up with XXXX. But be aware that if you "volunteer" to move
to the yahoo groups, expect the unexpected"
What "unexpected" things will happen? Well I guess they will get delivered
faster than SF (perhaps you did not expect that). The users
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
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?
"Lets get it out into the open. If you are on the rainbow-devel group you're
not having to put up with XXXX. But be aware that if you "volunteer" to move
to the yahoo groups, expect the unexpected."
[rainbowportal-devel] has traffic for developers that are beginners,
intermediate and veterans. And tons of installation, usage and general
questions come here (although Rahul's group http://groups.yahoo.com/group
<http://groups.yahoo.com/group/RainbowPortal/&gt; /RainbowPortal/ has been
great about answering a lot of User questions and reducing the load here)
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 Beginners in Alan Cooper terms) so
these things get mixed with
developer/core issues constantly. 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.
"Really, there is so much garbage being put around now, it never happened in
the Rainbow community until late 2004 onwards."
You call the hundreds of improvements in Rainbow for example:
=> short URLs
=> 80% of the leaks getting plugged
=> Manu's installer
=> better clearer icons
=> SVN instead of CVS
=> 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.
=> Making an option to Zen perf. flaws and documenting it, igniting
interest and use in Zen after so long
the improved <http://RainbowPortal.net&gt; RainbowPortal.net site with many
updated including all the work being done on confluence
=> 100s of fixes Charles demanded that expands our UI appeal getting made in
weeks instead of months, Manu's installer, etc.) garbage?
=> an active constructively critical community rather than quiet fearful one
afriad of OS zealots insisting complaints not allowed --
unless the complainer personally fixes it - no PRIDE in workmanship (or
false pride at least in objectively shoddy work of past releases)
as someone said so well.
Please define garbage! This looks like massive improvement. Where is this
"garbage"?
"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."
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" an embarassing style that
was the only way they reacted in past and drove off so many people to the
arms of DNN.
As for the developers, I don't think they are Unhappy. 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.
"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."
"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."
We have been constantly informing the SF list. (once again) Not all of you
are "users" but only less than a 1% of the members on this list
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
marketplace. And even the movers and shakers wear a "user" hat when 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 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....
- Jonathan
_____
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of Mark
Gregory
Sent: Wednesday, May 04, 2005 9:18 AM
To: rainbowportal-devel@...
Subject: RE: re[2]: [Rainbowportal-devel] Why CVS is unused?
Lets get it out into the open. If you are on the rainbow-devel group you're
not having to put up with XXXX. But be aware that if you "volunteer" to move
to the yahoo groups, expect the unexpected.
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.
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.
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.
Mark
_____
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of Jeremy
Esland
Sent: Wednesday, 4 May 2005 1:07 PM
To: rainbowportal-devel@...
Subject: re[2]: [Rainbowportal-devel] Why CVS is unused?
Hmmmm indeed....
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 where will I
subsequently point my update?
When was the rainbowportal-devel listed "demoted" to only dealing with
"users"... I thought the "devel" part stood for "development" ;-)
Jeremy (jes1111)
----------------------- Original Message -----------------------
From: "Jonathan Minond" <mailto:jonathan@...> <jonathan@...>
To: <mailto:rainbowportal-devel@...>
<rainbowportal-devel@...>
Date: Mon, 2 May 2005 15:19:13 +0200
Subject: RE: [Rainbowportal-devel] Why CVS is unused?
Hmmm..Well,
The aim is that over the course of the next few weeks we are doing a few
things,
1) stabilize the solution to represent 1.5 SP1, this means reproducing
any changes that have been made to CVS that haven't been reproduced yet one
of the reasons I encourage any active developer to contact the
betateam@..., so that you can be working on making that happen.
2) Introduce the new Page Manager, Forum Module, File Manager and
whatever else gets done in time
3) 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.
4) Introduce the different layers of development.
Dev->test->staging->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.
5) Ability to manage module images and css in theme directories
6) Some changes/updates to modules such as discussion, sitemap, file
directory tree and others
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's as smooth as possible.
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 -> 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.
I think that it'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's hard at first and nerve recking but most
often for the best.
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.
So If anyone is an SVN wizard, and want to help us get on the ball quicker,
you can contact the beta team.
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.
Ok, well. If there are any questions, feel free to ask more, maybe some
other people working on the beta stuff and pushing on getting "order to the
chaos", you can review the message boards in the beta yahoo group to see
some of the discussion and details as to the design plans.
Regards,
Jonathan
_____
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of Mike
Stone
Sent: Monday, May 02, 2005 3:22 PM
To: rainbowportal-devel@...
Subject: Re: [Rainbowportal-devel] Why CVS is unused?
Yes, I see your point. How can you go to Jira and work on issues when CVS
is no longer being maintained with code changes. The Beta Team does have a
lot of changes and is only a small number of us. I know they are working
hard to get a place for everyone to hook back up and be a community again.
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.
Jonathan, can you or Rahul share with the DeV list what is coming and the
time line for it.
Mike Stone
Director of Computer Information Services
Kaskaskia College
27210 College Road
Centralia, IL 62801
618-545-3201
http://www.kaskaskia.edu
>>> jviladiu@... 5/2/2005 03:33:53 >>>
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.
------------------------------------------------------- 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 Rainbowportal-devel@...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel

In rainbow.config you have the references for IE7 scritps.
=20
Instead of what is written there, I have a line like this
<add key=3D"Ie7Script"
value=3D"/aspnet_client/x/x_core.js;/aspnet_client/x/x_event.js;/aspnet_c=
lient
/x/x_dom.js;/aspnet_client/Rainbow_scripts/xmenu4.js;/aspnet_client/Rainb=
ow_
scripts/MainMenu_Horizontal.js" />
=20
_____ =20
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of
HolonCom Support
Sent: Thursday, May 05, 2005 4:24 PM
To: rainbowportal-devel@...
Subject: [Rainbowportal-devel] xAPI
=20
Jonathan,
One month ago you said "to use xAPI you just have to switch =
rainbow.config
setting, and 2 small file, i'll write a readme on this,"
I can't find any reference to xAPI in rainbow.config, nor do I find a =
readme
that explains this.
Could you help me out on this?
I want to use ZEN for the first time now, but IE7 is no option because =
it's
too slow.
Rob Siera
on 12/04/2005 1:57 Jonathan Minond said the following:=20
I have set up a site http://d240194.u37.webhostingconsortium.net/
This is currently using the entire solution I have been discussing for =
the
past couple weeks. Including
"Tab"->"Page"
Page Manager
xAPI ( you can choose to keep using IE7 scripts If you like them, you =
just
have to switch rainbow.config setting, and 2 small file, ill write a =
readme
on this, however beware, I did test on site with anything like a large
number of pages.I tested 150 and more, IE7 scripts are no longer usable.
they take about 5-10 minutes in which they just freeze your computer,
therefore IE7scripts are unrealistic for a site with a big menu unless =
you
use custom menu but then you are already limiting things unnessasariliy =
)
A few more things.
File Manager ( also in cvs now )
=20
There are some open/known issues, that are being fixed daily.but I would
appreciate the more people who could have a look at things and give
feedback, find bugs, whatever..the quicker people give feedback, the =
quicker
I will be willing to move this to cvs so everyone can use what they =
want.
Maybe the consensus will be that some things are no good and will be
removed.
=20
Any RB user who let's me know they registered, I will give admin rights =
so
that you can see page manager in administration section, as well as =
settings
table in site settings, page layout, and module settings pages.
=20
Just to avoid argument here.. I am not demanding, nor forcing anyone to =
go
there.. I am politely asking that anyone who wants to help with some
testing, checking and feedback is welcome to. In the end these are =
things I
am working on that I would like to contribute to Rainbow, some people =
may
want, some may not. Things like xAPI are optional you do not have to use
them, in which case your page will render the old way with long scroll, =
or
whatever.
=20
- Jonathan=20
=20
_____ =20
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of
Jonathan Minond
Sent: Tuesday, April 12, 2005 1:06 AM
To: rainbowportal-devel@...
Subject: RE: [Rainbowportal-devel] RainbowForum Testers Needed
=20
A few issues with RainbowForum
=20
It should be called Forum, not RainbowForum. this will be an annoying =
naming
convention inside the application
Everywhere in the configs, setup, etc. that uses /rainbow/DesktopModules
should use /DesltopModules without the rainbow.=20
=20
_____ =20
From: rainbowportal-devel-admin@...
[mailto:rainbowportal-devel-admin@...] On Behalf Of k =
w
Sent: Monday, April 11, 2005 5:46 PM
To: rainbowportal-devel@...
Subject: RE: [Rainbowportal-devel] RainbowForum Testers Needed
=20
YAF has an option under Board Settings to view as threaded but it =
appears as
though it was never implemented. This will also be added to the todo =
list if
the task is feasible.
Thanks
----- Original Message -----=20
From: "Jonathan Minond"=20
To: rainbowportal-devel@...=20
Subject: RE: [Rainbowportal-devel] RainbowForum Testers Needed=20
Date: Mon, 11 Apr 2005 17:59:35 +0200=20
>=20
> To be honest... I like the old discussion... nice threaded views...=20
> something that new forums don't do in general. I wonder if we can add=20
> threaded view to the new RB forum Keith made from YAF.=20
>=20
> -----Original Message-----=20
> From: rainbowportal-devel-admin@...=20
> [mailto:rainbowportal-devel-admin@...] On Behalf Of =
Mark
> McFarlane=20
> Sent: Monday, April 11, 2005 3:59 PM=20
> To: rainbowportal-devel@...=20
> Subject: RE: [Rainbowportal-devel] RainbowForum Testers Needed=20
>=20
> It is a completely new full-fledged forum application, not built on=20
> Rainbow's semi-lame discussion module (which I wrote)=20
>=20
> Mark McFarlane=20
>=20
> -----Original Message-----=20
> From: rainbowportal-devel-admin@...=20
> [mailto:rainbowportal-devel-admin@...] On Behalf Of =
Mark
> Gregory=20
> Sent: Monday, April 11, 2005 11:41 AM=20
> To: rainbowportal-devel@...=20
> Subject: RE: [Rainbowportal-devel] RainbowForum Testers Needed=20
>=20
> Is this a new forum for rainbow?=20
>=20
> Is it built on the Discussion module or something else?=20
>=20
> Sorry if I missed earlier messages on this thread.=20
>=20
> Mark=20
>=20
>=20
> -------------------------------------------------------=20
> SF email is sponsored by - The IT Product Guide=20
> Read honest & candid reviews on hundreds of IT Products from real =
users.=20
> Discover which products truly live up to the hype. Start reading now.=20
> http://ads.osdn.com/?ad_id=3D6595
<http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick&gt;
&alloc_id=3D14396&op=3Dclick=20
> _______________________________________________=20
> Rainbowportal-devel mailing list=20
> Rainbowportal-devel@...=20
> https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------=20
> SF email is sponsored by - The IT Product Guide=20
> Read honest & candid reviews on hundreds of IT Products from real =
users.=20
> Discover which products truly live up to the hype. Start reading now.=20
> http://ads.osdn.com/?ad_id=3D6595
<http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick&gt;
&alloc_id=3D14396&op=3Dclick=20
> _______________________________________________=20
> Rainbowportal-devel mailing list=20
> Rainbowportal-devel@...=20
> https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel=20
--=20
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://www.mail.com/?sr=3Dsignup
<http://mail01.mail.com/scripts/payment/adtracking.cgi?bannercode=3Dadsfr=
eejum
p01>=20
------------------------------------------------------- SF email is
sponsored by - The IT Product Guide Read honest & candid reviews on =
hundreds
of IT Products from real users. Discover which products truly live up to =
the
hype. Start reading now. http://ads.osdn.com/?ad_ide95
<http://ads.osdn.com/?ad_ide95&alloc_id%14396&op=3Dick&gt; =
&alloc_id=14396&op=3Dick
_______________________________________________ Rainbowportal-devel =
mailing
list Rainbowportal-devel@...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel=20

Jonathan,
One month ago you said "to use xAPI you just have to switch
rainbow.config setting, and 2 small file, i'll write a readme on this,"
I can't find any reference to xAPI in rainbow.config, nor do I find a
readme that explains this.
Could you help me out on this?
I want to use ZEN for the first time now, but IE7 is no option because
it's too slow.
Rob Siera
on 12/04/2005 1:57 Jonathan Minond said the following:
> I have set up a site http://d240194.u37.webhostingconsortium.net/
>
> This is currently using the entire solution I have been discussing for
> the past couple weeks. Including
>
> "Tab"->"Page"
>
> Page Manager
>
> xAPI ( you can choose to keep using IE7 scripts If you like them,
> you just have to switch rainbow.config setting, and 2 small file, ill
> write a readme on this, however beware, I did test on site with
> anything like a large number of pages...I tested 150 and more, IE7
> scripts are no longer usable... they take about 5-10 minutes in which
> they just freeze your computer, therefore IE7scripts are unrealistic
> for a site with a big menu unless you use custom menu but then you are
> already limiting things unnessasariliy )
>
> A few more things.
>
> File Manager ( also in cvs now )
>
>
>
> There are some open/known issues, that are being fixed daily...but I
> would appreciate the more people who could have a look at things and
> give feedback, find bugs, whatever....the quicker people give
> feedback, the quicker I will be willing to move this to cvs so
> everyone can use what they want. Maybe the consensus will be that some
> things are no good and will be removed.
>
>
>
> Any RB user who let's me know they registered, I will give admin
> rights so that you can see page manager in administration section, as
> well as settings table in site settings, page layout, and module
> settings pages.
>
>
>
> Just to avoid argument here.... I am not demanding, nor forcing anyone
> to go there.... I am politely asking that anyone who wants to help
> with some testing, checking and feedback is welcome to. In the end
> these are things I am working on that I would like to contribute to
> Rainbow, some people may want, some may not. Things like xAPI are
> optional you do not have to use them, in which case your page will
> render the old way with long scroll, or whatever.
>
>
>
> - Jonathan
>
>
>
> ------------------------------------------------------------------------
>
> *From:* rainbowportal-devel-admin@...
> [mailto:rainbowportal-devel-admin@...] *On Behalf Of
> *Jonathan Minond
> *Sent:* Tuesday, April 12, 2005 1:06 AM
> *To:* rainbowportal-devel@...
> *Subject:* RE: [Rainbowportal-devel] RainbowForum Testers Needed
>
>
>
> A few issues with RainbowForum
>
>
>
> 1) It should be called Forum, not RainbowForum... this will be
> an annoying naming convention inside the application
>
> 2) Everywhere in the configs, setup, etc... that uses
> /rainbow/DesktopModules should use /DesltopModules without the rainbow...
>
>
>
> ------------------------------------------------------------------------
>
> *From:* rainbowportal-devel-admin@...
> [mailto:rainbowportal-devel-admin@...] *On Behalf Of
> *k w
> *Sent:* Monday, April 11, 2005 5:46 PM
> *To:* rainbowportal-devel@...
> *Subject:* RE: [Rainbowportal-devel] RainbowForum Testers Needed
>
>
>
> YAF has an option under Board Settings to view as threaded but it
> appears as though it was never implemented. This will also be added to
> the todo list if the task is feasible.
>
> Thanks
>
> ----- Original Message -----
> From: "Jonathan Minond"
> To: rainbowportal-devel@...
> Subject: RE: [Rainbowportal-devel] RainbowForum Testers Needed
> Date: Mon, 11 Apr 2005 17:59:35 +0200
>
>>
>> To be honest... I like the old discussion... nice threaded views...
>> something that new forums don't do in general. I wonder if we can add
>> threaded view to the new RB forum Keith made from YAF.
>>
>> -----Original Message-----
>> From: rainbowportal-devel-admin@...
>> [mailto:rainbowportal-devel-admin@...] On Behalf Of
> Mark
>> McFarlane
>> Sent: Monday, April 11, 2005 3:59 PM
>> To: rainbowportal-devel@...
>> Subject: RE: [Rainbowportal-devel] RainbowForum Testers Needed
>>
>> It is a completely new full-fledged forum application, not built on
>> Rainbow's semi-lame discussion module (which I wrote)
>>
>> Mark McFarlane
>>
>> -----Original Message-----
>> From: rainbowportal-devel-admin@...
>> [mailto:rainbowportal-devel-admin@...] On Behalf Of
> Mark
>> Gregory
>> Sent: Monday, April 11, 2005 11:41 AM
>> To: rainbowportal-devel@...
>> Subject: RE: [Rainbowportal-devel] RainbowForum Testers Needed
>>
>> Is this a new forum for rainbow?
>>
>> Is it built on the Discussion module or something else?
>>
>> Sorry if I missed earlier messages on this thread.
>>
>> Mark
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Rainbowportal-devel mailing list
>> Rainbowportal-devel@...
>> https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel
>>
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Rainbowportal-devel mailing list
>> Rainbowportal-devel@...
>> https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel
>
>
> --
>
> ___________________________________________________________
> Sign-up for Ads Free at Mail.com
> http://www.mail.com/?sr=signup
> <http://mail01.mail.com/scripts/payment/adtracking.cgi?bannercode=adsfreejump01&gt;
>
> ------------------------------------------------------- SF email is
> sponsored by - The IT Product Guide Read honest & candid reviews on
> hundreds of IT Products from real users. Discover which products truly
> live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id396&op=ick
> _______________________________________________ Rainbowportal-devel
> mailing list Rainbowportal-devel@...
> https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel
>

On 5/4/05, Mark McFarlane <markamcfarlane@...> wrote:
> 1) If we are moving off of CVS, does that mean we are also moving off
> sourceforge?=20
Not for now... SVN is under test.
> 2) Somewhat unrelated, should we drop this list and only use Yahoo groups=
?=20
> Why not?=20
Because list have their fan :)
You can follow both, or one or them....
I see no reason to close a space that is used...
New groups are mor focused, list is more general purpose.
A lot of people are subscibed only to one of two....
Manu