> Tirveni willing to come to give a talk about freed.in anyway, why not go
> with that?  Technical topics should be slotted for the main event, not
> mini-events at each college.  What do you think?
>
> Regards,
>
> -- Raju


[blaring ship horn]

are we turning into misers of sharing-knowledge?
in trying to hold back or be reluctant to share gyaan, thinking that
just a 'snake-oil' talk on freed.in at a college at their time will
work in freed.in's favour and entice people to turn up?

this is not how knowledge-sharing, community-building, and
value-systems of what i consider foss work.

seems like we're more bankrupt than bankrupt, already.

looks like there's hardly any knowledge or gyaan or inspiration to
share with college-kids thirsty for any spark, from the foss
community. too little of it around. artificial scarcity, or artifical
intelligence, killed all our natural intelligence?

gaurav, why would you let everyone just get away with this.

a talk at a college does not make it into a mini-conference or event.
for instance, we're not talking about intro to gpg at freed.in. we
could talk about that to college kids who wish to write love-letters
to their heart-throbs, hidden in plain view. i can think of a hundred
more topics from the vast ecosystem of foss that we could share with
them, and also tell them about the glimmering freed.in event coming up
ahead.

the more you share, the more enriched you and they get.
the more you share, the more they love foss,
the more you share, the more credibility freed.in gets.


[every night in my shell,
i see you i feel you,
that is how i know you go on.
near, far, wherever you are,
i believe the FOSS will go on,
once more, you open the port,
and you're here in my login
and my cron will go on]

!
niyam

_______________________________________________
ilugd mailinglist -- [email protected]
http://frodo.hserus.net/mailman/listinfo/ilugd
Next Event: http://freed.in - September 28-29, 2007
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/[email protected]/

Reply via email to