Hi Prakash,

> I really disappointed this word from Raman. The motivation of FOSSConf is
> not to concentrate like this. I dont know, why you mentioned this issue in
> the first. Want to create a big issue? or do you feel this slide hurt you
> more?. FYI, The author of this topic, Geetha joined with NRCFOSS recently.
> She is not an regular employee of NRCFOSS, as of now and i thing this is the
> first talk for her, after she joined with NRCFOSS. None of the regular
> NRCFOSS employee are familar with her; Even she did not took a talk for
> local people too. I dont like to insist here like, she is correct. Let her
> to learn it from her mistake and avoid in future. Otherwise, we will
> discourage a beginner/resource person on Ruby from this community. And there
> is no use we are discussing about it here, instead of inform it to her. Any
> body send a mail to her reg this issue?.
The motivation of Fossconf ( though I could not attend it ) is to
enocurage people to use FOSS and obviously a presentation made on a
proprietary software is not acceptable. I agree that it be conveyed to
the person who did the presentation and be rectified. I have no idea ,
why you are taking an apology mail from raman to a personal level(
which is clearly visible in the above section_), please don do this.

> I have few queries here. Suppose a person is interested in a open source
> topic, say example Python. She/he dont bother about whether she/he is going
> to work in Linux or Windows. Will this open source world accept her/his
> work?. Or you will denied?. This is wrong?.

As it has already mentioned , it is not a conference related to a
technology which is platform neutral ( like python), ... rather it has
been named "FOSSCONF" ( if you could read).

> If you say, ya she/he is wrong, then why this open source world allowed to
> work all our open source tools in Windows platform like GIMP, Open
> Office,.etc?.

You are confusing yourselves and probably other newbies on the list
with two entirely different aspects. FOSSCONF is different , it is a
"conference for FOSS.", where as providing windows compatible open
source software is entirely different. Please understand this ...

> And you decided that this is [(a)] big -ve point and mentioned in first. Why
> you accepted this topic when she uploaded her .ppt file when she
> registered?. You had the option to go through the files/content of the
> author's slides before she/he is going to take that topic. But you did not.
> A administrator can restrict these issues and the topics Wimax,.etc. Why we
> did not restrict them before we prepared the schedule?. I am sure, we did
> not yet defined our proper terms & conditions for Projects/demos/talks. Its
> some thing like our Administration fault. Not the speaker's mistake.

Raman did not say it is the speaker's mistake , he was talking about
entirely different things, again don't take it personally, .......


> Apologize is not the solution for -ve points. We have to recetify it. In the
> next Fossconf, defined the terms and conditions for Speakers section and add
> like should upload the slides in .odp/pdf format. Talks and the contents
> should be related to open source.
 yes agree that apologizing is not the "only" solution, I really
appreciate the tips you have given. But we should on the list
appreciate the fact that Raman came out to apoligize for the mishaps
and took responsibility for them. Couldn't you have given the tips in
a more plainer language ??

> What about the source code for all project demonstrations? If they upload it
> before they attend the fossconf, then I suggest you to add this point into
> +ve side and post that link here.
I clearly missed your point here ( there must be something very
intellectual about it) , can you please explain ???



Cheers
Satish
-- 
http://satish.playdrupal.com
_______________________________________________
To unsubscribe, email ilugc-requ...@ae.iitm.ac.in with 
"unsubscribe <password> <address>"
in the subject or body of the message.  
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc

Reply via email to