* Adjudicator Allocation has been completely redone. It takes into account the following:
* University - Adjudicator conflicts ('scratches'),
* Team - Adjudicator conflicts ('scratches'),
* Better adjudicators should be chairs
* Better debates get better panels
* Adjudicators should avoid previous co-panellists
* Adjudicators should avoid previous adjudicated teams
* Overview page made more clear - only currently possible options are shown
* Layout:
* Removed big "Tabbie" header to clear up some space
* Personalized Adjudicator Sheets in smaller font for longer names
* Removed confusing "settings" option
* Technical:
* Removed the website from the codebase to separate host
* GPL Licence header added to all code files
Meir.
Klaas knows about this, but this is just to open up the discussion to
everybody else interested. I have done a bit of work on a completely
new implementation of the Tab software using a framework called Ruby
on Rails http://rubyonrails.org . I will open source it, I just
haven't got around to it just yet. Ruby on Rails is a web framework
built on top of the Ruby programming language and has gained a lot of
traction nowadays.
I completely understand the concerns people might have about moving
away from a well tested and already working software to a completely
new framework. But I think we can make it happen quite smoothly if
there is a critical mass of people onboard in terms of their
willingness to use Ruby on Rails as a framework of choice.
I have a clean schema already nailed out. I have ported the SilverLine
algorithm to Ruby as part of my work on the simulation. So the real
work involved is just the input modules.
Let me see if I can get it out by the weekend. I had created a Google
Code project a long time ago. But we can work something out to merge
it with the existing Tabbie codebase.
Deepak
The main reason I stopped working on gentab and tryed working on Tabbie is that
Tabbie seems to be more popular amongst turnament orgenizers.
If we are considering a major rewrite, we should consider which code
base, is most
suitable.
I think gentab has a solid code base(perl and postgresql, draw written
in java), however I do not believe we have a big enough comunity of
debate software developers to make competing projects a good aproach.
So I suggest we discuss this on the mailing list,
I see if we can gather behind a coherent aproach, as I see we have at
least 3 projects using 3 diffrent technologies.
Meir.
We could go all out, but I do not see suppoting non-BP turnaments as a top
priority:
Alon altman and myself wrote gentab: http://sourceforge.net/projects/gentab/
which has a more flexable database schema. We could use something similar.
The main reason I stopped working on gentab and tryed working on Tabbie is that
Tabbie seems to be more popular amongst turnament orgenizers.
If we are considering a major rewrite, we should consider which code
base, is most
suitable.
I think gentab has a solid code base(perl and postgresql, draw written
in java), however I do not believe we have a big enough comunity of
debate software developers to make competing projects a good aproach.
So I suggest we discuss this on the mailing list,
I see if we can gather behind a coherent aproach, as I see we have at
least 3 projects using 3 diffrent technologies.
Alon altman and myself wrote gentab: http://sourceforge.net/projects/gentab/
which has a more flexable database schema. We could use something similar.
I'll take a look.