On Wednesday 04 April 2007 14:49, Baishampayan Ghose wrote:
> On Wednesday 04 April 2007 10:12 AM, Gora Mohanty cobbled together
> some glyphs to say:
>
> Hello,
>
> >>  Well i have a functional prototype of required to be
> >> pushed to http://sourceforge.net/projects/tangent/ .
> >> But i dont think I will be able to commit anyhting to
> >> cvs before 12th April. If you guys can hold till then?
> >
> > I think that the consensus was to get the call for papers
> > out soon so that we hopefully get a larger response. Can
> > you take this up with Baishampayan, maybe send him the
> > code that you have so that he can take a call on which
> > one to use? Since he volunteered to do this, it makes
> > sense for him to make that decision.
>
> OK, guys I have some bad news. I talked to the Continue people and
> they have told me that they can't release the source (or give it to
> me) at this stage, all they can do is host the app for us at Brown
> Univ. (which is obviously not acceptable). This is extremely
> disappointing for me since I never expected them to be like that
> since they have already released so many useful Free Software apps
> in the past.

Their call, maybe one of the packages we write would supersede their 
work :)

> So what I propose is that instead of waiting for somebody else to
> provide something, we should just start writing something for
> ourselves. I can kick-start an app quickly in Python & PostgreSQL
> and other members can also contribute by enhancing the app, or
> sending in bug reports.
>
> Vivek too has promised a similar app which he can deliver after
> April 12, which is absolutely fine. We can just throw-away our code
> if Vivek's app is superior and just use that, no issues. But
> instead of just waiting now, we better start writing something
> right now. If any one of you have a public Subversion repository it
> will be of help, else I can just use Bazaar-NG and host my branch
> somewhere.

So now there's 3 apps in the pipeline... Vivek's, yours and the one 
that Suman and Mary were getting done.  I'm eagerly awaiting the 
conference application shoot-out!

We'd made some notes on requirements from the application, am 
enclosing those, along with some ideas that came later.  This is 
mostly brainstorming, please ask for clarifications ON THE FREEDEL 
LIST ONLY.

Finally, please hard-code as little stuff as possible.  Should be 
possible, e.g. to add a talk category (theme) or remove one without 
having to muck around in the source.  Then the app would be truly 
general-purpose and not Yet Another Use-and-Discard Perl One-liner. 
(That's patented, so if you want to use that phrase you have to pay 
me royalties.)

Regards,

-- Raju
-- 
Raj Mathur           [EMAIL PROTECTED]   http://kandalaya.org/
       GPG: 78D4 FC67 367F 40E2 0DD5  0FEF C968 D0EF CC68 D17F
                      It is the mind that moves

ORIGINAL REQUIREMENTS
---------------------

From: Gora Mohanty <[EMAIL PROTECTED]>
 
Hello,
  Here is a list of requirements for the new freedel.in website
that Raj and I came up with. Please add your comments.

1. Existing web site pages (freedel.in seems to be down at the 
moment).

2. Login page

3. Talk submission form: Should cover at least the following items,
   which are in no particular order.
  - Name
  - Affiliation
  - Background (write-up/introduction)
  - Track (with track listing and description displayed)
  - Talk or workshop
  - Equipment required
  - Abstract
  - Title
  - Location
  - Travel information
  - Accommodation
  - Travel assistance
  - E-mail
  - Personal URL
  - Level (with description): Introductory, Intermediate or Advanced
  - Comments
  - Photograph

4. Subsequently
  - Edit personal information
  - Upload collateral
  - Allow versions

5. Let admin give:
  - Nickname to uniquely identify talk
  - Duration

6. Scheduling framework
  - Slots
  - Rooms
  - Select slot
  - Select talk
  - Multiple views and access formats

7. Registration form
  - All items under the speakers category
  - Occupation
  - Category (with list of questions to categorise)
  - List of tracks of primary interest
  - Comments
  - Links to ILUGD web site, mailing list registration
  - Assign unique ID

8. Feedback form
  - Per-talk options
  - General feedback
[I'm not sure whether we wanted feedback before or after selecting the 
talk]

FURTHER NOTES
-------------

Tracks: Need listing of all the tracks. Andrew is naming them, we can 
put each one out there.  Will also have to put an ``Other'' track 
with a one-line field for explanation on why other and what the other 
track is.

[Ah, caught Andrew!]

Talk or Workshop: explanation of what each is.  Quick guideline on  
how to select either on.

Equipment required -- list of equipment that will be available.   
Caveat that special equipment may not be available, keep equipment 
requirements down to a minimum.


_______________________________________________
ilugd mailinglist -- [email protected]
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/[email protected]/

Reply via email to