Once a week is right for me.
We can chat about details when you have some time.
Emmanuele De Andreis
Internet Solutions Provider
Main portal - http://www.rainbowportal.net
Sourceforge CVS - http://sourceforge.net/projects/rainbowportal/
Support Forums - http://www.rainbowportal.net/ASPNetForums
Da: John M [mailto:howdymatey@...
Inviato: marted=EC 20 maggio 2003 17.22
A: manudea@...; rainbowportal-devel@...
Oggetto: RE: [Rainbowportal-devel] Rainbow releases (was: DotNetNuke =
I can do this once a week probably on a wednesday (As that is when I =
the most free time). But I dont think a daily upgrade would be =
because it might be too fast a rate of change for them (Those that want=20
up-to-the minute can still use cvs).
>From: "manu" <manudea@...>
>Subject: RE: [Rainbowportal-devel] Rainbow releases (was: DotNetNuke
>Version 1.0.8 Released...)
>Date: Tue, 20 May 2003 17:12:36 +0200
>Hi Mark and all guys on list,
>sorry but I cannot do more than this. I'm very busy in all Rainbow and=20
>I cannot handle more. I agree with you: I do not speak English as=20
>native language... sorry: I'm doing my best.
>I need some help.
>I think that we have tons of new features tha are only available on=20
>tons of bugs are fixed in latest versions.
>If we could we should do all release we can (even one per day if we =
>See this page as example:
>With a lot of release I think we could have more installed rainbow and=20
>more bug submitted. Many peoples are still reporting old bugs,=20
>corrected weeks ago.
>Releasing a rainbow version should be pretty easy and need no more that =
>I need one or more volunteer for doing that. (English mother tongue if
>- Get latest code from CVS (export) (5 minutes)
>- Drop and recreate db: test if all go fine... (10 minutes)
>- Do additional tests (we can decide later: at least we need to show=20
>home page and logon as admin) (15 minutes)
>- Documentation: (10 minutes)
> Release notes: Write in plain English some notes of current release.
> Changes: cut and paste latest history (diff between older and latest
>- Add release as zip file on Source forge. (10 minutes)
>- Do announces: (10 minutes)
> - Rainbow home: (announces box) http://www.rainbowportal.net
> - Rainbowportal forums:=20
> - Asp.net Forums: Ibuyspy:=20
>&ForumID=3D2 (post Changes)
> - Asp.net Forums: Announcements:=20
>(post Release notes)
>Please contact me if you can do this for Rainbow community.
>I will give you all the needed rights and all help for doing this.
> >So again, are we at a code freeze for 1.0 yet? (whine whine whine)
>As you can see I have almost freezed all features and I'm concentrate=20
>fixing and esperantus release (almost done).
>Emmanuele De Andreis
>Internet Solutions Provider
>Main portal - <http://www.rainbowportal.net/>=20
>http://www.rainbowportal.net Sourceforge CVS -=20
>Support Forums - <http://www.rainbowportal.net/ASPNetForums>
>[mailto:rainbowportal-devel-admin@...] Per conto di=20
>Inviato: luned=EC 19 maggio 2003 9.18
>Oggetto: RE: [Rainbowportal-devel] DotNetNuke Version 1.0.8 Released...
>At one point in time I think DNN actually got some monetary sponsoring=20
>from Microsoft. This probably would not be that difficult to do.
>I agree that the Rainbow site needs a major overhaul. I appreciate the
>work Manu and others have done, but it still needs a fair amount of =
>become an exemplary site. I think some of the problem is delivering =
>content in a language (english) that is not the native language of the
>authors. We also have that dilemma where there is content duplicated
>between SourceForge and Rainbow.net, and as a new user it is very =
>to find things.
>One significant difference between Rainbow and DNN is Rainbow is C#,=20
>DNN is VB. This is the primary reason I choose Rainbow. I=20
>participated briefly in DNN but I just didn't have any interest in=20
>doing VB development, I wanted to
>learn C# - although the bulk of what we rally do is ASP.NET and the
>differences between VB and C# are pretty slim.
>I sent an email around last week on cleaning up the 'admin this' page=20
>and I sent one several weeks ago about a way edit 'tabs' without ever=20
>going to the 'admin this' page. I think both of these ideas will help=20
>Of course, I should just do the work myself but I don't have the time. =
>having enough difficulty keeping the discussion module up to date in =
>of architecture changes, and updating the installation document, and=20
>all the email in this list :)
>Whatever happened to the Help icons in the module titles?
>I can't overstate how important a 1.0 release will be to Rainbow's wide =
>spread adoption, along with exceptional documentation on features,=20
>We also need an interesting default installation that showcases all of=20
>the modules. There is a LOT of work someone must do after installation =
>before they can really see what the features are and how things work. =20
>I built test site last weekend that exercises all of the modules,=20
>perhaps I could turn that into the default installation with 10 or 20=20
>hours more work. My biggest concern here is that if someone goes and=20
>changes the data model, or security architecture again it will break=20
>the site and I won't do it twice.
>So again, are we at a code freeze for 1.0 yet? (whine whine whine)
>I agree we need a well documented way for users to add new modules and=20
>edit existing ones. Manu and others have again done a great job=20
>putting together short papers on various topics, but even with my level =
>of familiarity with Rainbow the documents are too terse, and often=20
>confusing. We have a great start here, but a LOT more work is needed.
>So rather than whining, I guess I need to volunteer for something.
>1) I'll update the install document this week to deal with the recent=20
>(last 2 months) changes in installation, and to deal with the scenario=20
>where the db and web server are on different machines.
>2) I'll build a default installation site that showcases all of the=20
>current modules. I won't be able to test it well because I can't get=20
>several to work (Dilbert, Maps, Google Search, etc) apparently due a=20
>3) I am also willing to make suggestions on how to improve=20
>www.rainbow.net, if anyone is willing to do the effort to change the=20
>Maybe for the default installation I can make a prototype replacement=20
>for Rainbow.net? Maybe this isn't a good idea, I need to think through=20
>what the 'best' default install would look and feel like.
>--> Who wants to update the module writing tutorial or create a single
>guideline document? and add in discussions about the new <tra:=20
>controls, localization, data access philosophy, installation scripts,=20
>how authorization is implemented, why to use stored procedures, .... =20
>Half of the articles at=20
>should be folded into a single 'module writes guidelines/tutorial'
>[mailto:rainbowportal-devel-admin@...] On Behalf Of=20
>Sent: Sunday, May 18, 2003 7:35 PM
>Subject: RE: [Rainbowportal-devel] DotNetNuke Version 1.0.8 Released...
>One of the things that DNN does a lot better than rainbow is=85 that =
>has an ease for developers that want to look through the code. There=20
>is a standard to the code and how it is assembled is easily put=20
>together. Right now with Rainbow there is none of that and if you area =
>developer there is a lot greater learning curve than with DNN=20
>especially with the designing of the modules.
>I think with 2.0 we need to do a total over haul of the design of=20
>rainbow portal and create it from the ground up with the current code=20
>we have. By ground up I mean we need to think about the architecture=20
>of Rainbow and put a SDK together.
>My 2 cents,
>[mailto:rainbowportal-devel-admin@...] On Behalf Of=20
>Sent: Sunday, May 18, 2003 12:20 PM
>Mark and all,
>On Friday night I had dinner with a Rob Collins who is working a lot=20
>with DNN. His site WillowTree is listed on the DNN site. Anyhow, we=20
>did some comparisons of the 2 products. Rainbow more features, but DNN =
>has put more effort into the ease of use. The biggest thing I saw that =
>we need to do is make it easier to edit a tab and add modules to it=20
>without going to the back end to do it. They are not yet localized,=20
>and they do not have workflow. Other than that I did not see a lot if=20
>differences in functionality or available modules. One of the things=20
>that DNN has going for it is that they
>have made a 1.0 release and their site and software is clean. The =
>Portal site has so many things on it now that one can easilly get lost.
>I think we need to get our 1.0 release out there and then has a clearly =
>defined roadmap for the next releases.
>I also asked my DNN friend how they got on ASP.NET and he said Shaun=20
>has some inside connections with Microsoft.
>Mark McFarlane <mark.mcfarlane@...> wrote:
>I'm not sure how many of you follow this parallel effort but hee's the=20
>latest blurb. Shaun is doing a MUCH better job than we are at=20
>From: shaunw1@... [mailto:shaunw1@...]
>Sent: Thursday, May 15, 2003 11:54 AM
>Subject: DotNetNuke Version 1.0.8 Released...
>Dear Mark McFarlane,
>DotNetNuke Version 1.0.8 is now available for official download (=20
>Its been just over a month between releases... a month with almost=20
>exponential growth for our community. We have gone from approximately=20
>4,000 registered users to 8,000 registered users during this time=20
>period. There are conservatively 2,500 websites running DotNetNuke=20
>internationally. The DotNetNuke Forum on ASP.NET has over 7,000 posts=20
>and is rapidly gaining on the IBuySpy Portal ( an amazing achievement=20
>considering the IBuySpy Portal has nearly a 12 month lead time on=20
>DotNetNuke ). Yet another interesting metric is the number of downloads =
>on SourceForge.Net. The Rainbow Portal currently has 4,300+ downloads=20
>since November 10, 2002 whereas DotNetNuke has 6,100+ downloads since=20
>March 22, 2003! This project has achieved incredible momentum which=20
>will definitely continue in the months ahead.
>This latest release offers a variety of defect corrections and=20
>enhancements over the previous release version. The most significant of =
>these items are identified below.
>There has been much talk lately of private assemblies in the ASP.NET=20
>Forums. Essentially, private assemblies allow developers to create=20
>custom modules which are compiled into their own private DLL and yet=20
>interact seamlessly with the core DotNetNuke framework. The benefits=20
>are that the private assemblies can be developed, revised, and deployed =
>independently from the core application. Installation and=20
>uninstallation of private assemblies has been automated in this version =
>through the use of simple XML installation scripts ( *.dnn ). Module=20
>files can be uploaded to the web server using the Host / File Manager=20
>tab and then installed directly from the Module Definitions tab without =
>requiring any modifications/recompilation in VS.NET. Please review the=20
>PrivateAssemblies directory included in the release for examples of how =
>to create the required files ( including XML installation scripts and=20
>uninstallation scripts ).
>The Auto Upgrade logic included in previous versions has been improved=20
>to ensure the application version matches the database version. A few=20
>caveats to remember: 1) when compiling DotNetNuke please be sure that=20
>you have the proper version of the AssemblyInfo.vb file and 2) in order =
>for the Auto Upgrade process to execute the SQL script file(s) must be=20
>deployed to the \database directory. The Auto Upgrade process will=20
>create a *.log file in the \database directory for each script=20
>executed. These logs can be viewed at the bottom of the Host / Host=20
>Settings tab. If you insist on running the database scripts manually,=20
>you must also manually add the associated record to the Version=20
>Although the administrative icons included with version 1.0.7=20
>represented a huge improvement in professional appearance for=20
>DotNetNuke, there were many people who voiced their complaints=20
>regarding their rather large size. Well I am happy to report that Jason =
>Graves ( http://www.dotnetnuked.com ) has once again taken the=20
>intiative and created a much smaller administrative icon set which is=20
>included with the latest release.
>Yet another new cosmetic feature added in this release enables you to=20
>create your own customized HTML container script for modules.=20
>Containers can be defined on a module-by-module or global basis. If you =
>wish to add the same "rounded-corner" container as the DotNetNuke.com=20
>site, please refer to the default \Portals directory in the=20
>installation package for the necessary image files and HTML code (=20
>The author of the SolPart menu control has been working hard to=20
>stabilize a new version which supports style sheet specifications as=20
>well as better browser compatibility features. The control was not=20
>ready for this release but you should expect an announcement shortly=20
>regarding its availability.
>A multitude of enhancements have been incorporated into the File=20
>Manager module. The Upload File interface has been upgraded to allow=20
>you to upload multiple files in a single session. In addition, the=20
>Administrator now has the ability to define multiple file upload Roles. =
>A new security related Host Settings option has also been added for=20
>restricting file uploads to specific file types.
>In the past, to reduce administrative overhead, we have only maintained =
>a single code base for each release. This meant that application defect =
>corrections as well as large scale enhancements were maintained in the=20
>same project which severely impacted our ability to release service=20
>packs on a timely basis. Starting with this version we will maintain=20
>two seperate code bases - one for defect corrections which can be=20
>released regularly as service packs and one for development=20
>enhancements which will form the basis for the next major release. This =
>change will increase the amount of administration required but should=20
>result in obvious benefits to the community.
>In an attempt to dispel critisism regarding the communication ( or lack =
>thereof ) related to the management of the DotNetNuke community, I will =
>be creating a new tab on the DotNetNuke site. The new tab will attempt=20
>to provide a roadmap of the expected features for upcoming versions of=20
>the application. In addition I will attempt to write a blog on a=20
>periodic basis to provide insight into the various activities and=20
>issues facing the community.
>An email was sent to the membership earlier this month regarding a new=20
>hosting option for DotNetNuke. PortalWebHosting (=20
>http://www.portalwebhosting.com ) provides a comprehensive hosting=20
>package tailored specifically to the DotNetNuke application. The=20
>feedback related to this service has been extremely positive and we=20
>hope to offer more value-added services to the community in the months=20
>We deeply appreciate your dedication, patience, and enthusiasm for=20
>Thank you, we appreciate your support...
>This SF.net email is sponsored by: If flattening out C++ or Java code=20
>to make your application fit in a relational database is painful, don't =
>do it! Check out ObjectStore. Now part of Progress Software.=20
>Rainbowportal-devel mailing list=20
>Online Status Indicator <aim:goim?screenname=3Dcwisakson>
>3.9 Cents/min. No Fees or Minimums!
>Do you Yahoo!?
>The New =20
>Yahoo! Search - Faster. Easier. Bingo.
On the move? Get Hotmail on your mobile phone =