febbraio 2006 - Posts
This is an extention to my automated builds blog post earlier. I think it's a good idea to precompile the "product" releases since not every end user actually cares to mess with the rainbow code. Most people that want to put up a website don't care how
Read More...
At Rainbow we use JIRA, a decent Bug Tracking/Project Management software. JIRA is great for software developers and project managers,but it isn't the tool for the normal end user. As noted earlier, Rainbow users should be encouraged to look at documentation,
Read More...
One of the coolest things in the .NET 2.0 framework is the msbuild tool which is basically a ripoff of the famous "ant" build tool, later ported to .NET as "nant". MSBuild like the others uses an XML file with build tasks such as "SVNUpdate", "FileUpload"
Read More...
The only way we can work together is to work towards a common vision for what product to work on. Because the Rainbow team consists of private individuals with their own lives and agendas, changes are made from all directions to satisfy their own needs
Read More...
There will be two month iterations where Teams and their leaders will be evaluated for their performance.Of course each team is supposed to be reporting to their leaders every week or so. The Overall near the bottom of this post is only a guide for what
Read More...
I want only the best designers working for Rainbow. I have worked for a graphic design firm and I have done quite a bit of graphic design myself in my past and I know what looks good and what doesn't. Yes, there are a lot of "designers" even ones that
Read More...
The Rainbow project is going through an era of change. A new 2.0 Product is being worked on by several developers. Currently the next big steps as far as features go are MagicAjax and ASP.NET 2.0 Feature integration. The software currently compiles on
Read More...
For a more organized and professional software production organization, I have drafted a team structure which I think will be good. Currently we don't anything close to the number of people we need to man all these teams, so that means in the beginning,
Read More...
Generally speaking the development process in open source projects is very organic and depends on the process. I have seen development in small groups ( 5 people ) to large groups ( 100 people) and have seen the things that work and the things that don't.
Read More...
As noted in my first blog post, I have been working on reorganizing the Rainbow project both administratively and finding ways to make it into a Professional Grade/Commercial Grade product. Here's a little of what I've been working on.
Read More...
And thus begins a new page in Rainbow's history. A brief message about my past and future involvement in the Rainbow project.
Read More...