27.Mar.2004 : Boise, Idaho (USA) : Project Update with Manu
Agenda: 10AM Project update with Manu, Cory and Scott after their return from Microsoft.
Coding party! We will eat, drink, and code. The plan will be to work together as a team on 1 or more of the actual project items and get some code written. Remote contributors are encouraged to join us and participate for a few hours while the team is available to help and work with you live.
16.Mar.2004 : Boise, Idaho (USA) : Data and Localization
The follow up on last weeks topics were quick and to get to the short and sweet of it we need our Source Code Management vault set up and to continue to work on our collaboration tools (blogs, forums, etc).
Nobody attended on line. Hopefully after this Saturday we can start to set up more online events and get more involvement from the entire community in our events.
Data Project
We worked through our object persistence model and we believe we have something that will at least provide a very good starting point. We created some UML models and will be uploading those to the Data Project page on this web site shortly. If you would like to be involved in the data project please let me know. Initial construction is set to begin on the framework data persistence then moving onto persistence providers for module developers to use if they would like to.
Localization
We spent about 5 minutes on this before defering futher conversation until Saturday. Initial conscensus is that we'll want to tie this off of our data layer implementation.
We are still looking for people to step up and lead the indivudual projects. You don't have to code the whole thing we're just looking for people who can keep the project communicating and moving forward providing technical guidance as needed. Of course if you would like to code the whole thing this weekend then we could use that too :-)
I hope to see more of you at our next event - Andrew
9.Mar.2004 : Boise, Idaho (USA) : v.Next planning continues
We began to standardize our documentation and mangement projects. Our dicussion actually drifted into QA a little bit with some good dicussion on nUnit and fxCop.
- We went through the resources and moved what we could to the actual project pages they belonged to.
- A documentation standards document has been created and is now available on the Documentation project page
- Those present wanted to create a Build project to handle source code control task. There may not be enough work here to break out so a task was created for the managment project to create a configuration managment plan. The SCM decisions can be made there.
- It sounds like we're going to use Subversion and CruiseControl so simply formalizing this might be all we need
There were a couple of questions and request that arose during the meeting
- Should the project team blogs be created on the v.Next site or should be try to host them on a community side? or both? Can we most to one an publish to the other? We need the input of the blog God's here.
- Also, do we want to create a project specific blog and individual blogs or just create an aggregated list of pertinent blog entries for each project?
- We've done a lot of email type communication. It would be nice to have very specific forums on the v.Next site to discus the individual projects in a manner that would alow people to catch up to what's going on
- It was suggested that a project matrix be created to communicate the status of the various projects
- Some high level architecture artifacts would be nice to have as the project progresses. Cory might already have these but I haven't seen them outside his head yet :-)
We didn't complete everything for the management project but we felt confident that with the documentation standards we have set we have enough for the project leads to start with. I'm sure they'll change as we start using them and move forward but it is a good foundation.
2.Mar.2004 : Boise, Idaho (USA) : v.Next planning continues
The bulk of thevents and httpmodules for authorization. This is the pattern we want to follow for plug-ins. #2 we began discussing how to break up the projects into sub-projects.e discussion centered around a couple of topics. #1 was teh observer or events design pattern. We looked at how ASP.NET uses this pattern with
24.Feb.2004 : Boise, Idaho (USA) : v.Next planning continues
We discussed several tools including: nDoc, nUnit, fxCop. More discussion was held about how to architect v.Next so that we could easilly do a plug-in model. We also discussed the advantages and disadvantages of having an XML layer for modules to have to read and write data through.
17.Feb.2004 : Boise, Idaho (USA) : v.Next planning continues
Attended in person by (Boise, USA) : Cory, Scott N, Scott S, Shaun, Kelly, Denis, Rob, Aaron.
Attended online by (USA): Leo (Denver), Jon (Boise)
This meeting was spent reqiviewing current erquirements, talking about who could help with the web site, and beginning discussions about the goals and architecture possibilities. We discussed moving away from Content Managed Portals to Content Management with Portal Interfaces.
10.Feb.2004 : Boise, Idaho (USA) : v.Next Project Kickoff
Attended in person by (Boise, USA): Cory, Scott N, Scott S, Rob, Chris W, Shaun, Kelly, Jon
Attended online by (USA): Dan (Georgia), Andrew (Boise), John B (Michigan)
After 6 hours many ideas were discussed. It was clear that a project targeting ASP.NET 2.0 only would not work as most involved need a solution today. The consensus was that Rainbow and DNN both have limitations today that need to be overcome. Why not put the effort into a whole new project rewrite. Any existing code that can be used will be used in the rewrite, but it will be a whole new project. The vision is large, but the excitement is intense. Nothing short of world domination is the goal. The number of interested people in Boise alone indicates that it is highly likely that we will succeed. Requirements definitions were started. Framework architecture concepts were introduced to get people thinking about how to the project might be architected.
20.Jan.2004 : London (UK) : Core Team Meeting
Attended in person by: Manu (IT), Graz (IT), Jakob (Denmark), John M (UK), Ed (UK), Thierry (AU), Jeremy (Portugal)
Attended online by: Cory (USA)
Over 3 hours spent meeting each other and discussing the past, present and future of Rainbow. Cory was appointed to work with Jakob and take the lead on a version to target ASP.NET 2.0 Whidbey.