Update: Direct link You can watch it live here. These talks are part of the National mission on education through ICT. More information available here.
Date: Friday, July 10th, 2009 Time: 2.30 pm IST ( 09:00 UTC )
Talk 1: 10 things a FOSS developer should know
Abstract: FOSS development is easy. A simple set of rules and protocols would get anyone started on FOSS development. In this talk, the 10 essential things are discussed in a form that is easy to remember and, easy to tell others. Mostly interactive and example-driven, the talk builds on the fundamental principles of Software Development and provides relevance within the FOSS model of doing things.
Speaker: Ramakrishna Reddy is a Sr Software Engineer at Red Hat. A self-confessed Python fan, Ramakrishna is currently involved in authoring a book teaching non-programmers the fundamentals of computing. He is a regular on various Python forums along side NLP related forums. Ramakrishna maintains various eclectic packages in Fedora and, is also active in the Debian community.
Talk 2: How to use infrastructure for FOSS Projects
Abstract: Infrastructure is an important part of a FOSS project’s lifecycle. In this talk, Prasad talks about how to set up a development environment for a developer and, how best to set up a development/project infrastructure. Touching upon the essential infrastructure aspects, Prasad takes an example of his own project to demonstrate how important infrastructure is for projects.
Speaker: Prasad J Pandit is a Software Engineer at Red Hat. A developer who professes a love for Perl and C, Prasad maintains packages in Fedora. He also provides guidance to new participants in FOSS development showing them how to get their feet wet.
Talk 3: Communication in a FOSS Project
Abstact: Any project is based on communication. Clear, precise and accurate information at the right time helps to build communities around projects. Rahul delves into his experience as a Fedora Community Wrangler to talk about the ways and means to maintain a dialogue with an evolving community as well as how best to build up communication skills.
Speaker: Rahul Sundaram has been working within the Fedora community for close to 5 years now. He works as a Software Engineer at Red Hat and, provides inputs and guidance in various aspects of The Fedora Project ensuring that concept of collaboration is well established. He also writes in various publications and online journals. His profile is available athttps://fedoraproject.org/wiki/RahulSundaram
The post is brought to you by lekhonee v0.6
I just released Pony v0.2 . It is still under constant development and will go some db changes before v1 release. Please delete .pony.db under your home before using the new release.
$rm ~/.pony.db
Among new features one can now see the EXIF information of an image.
Deleting tag option is also added.
Get the source or rpms from here.
Now I have to add TODO file as too many things need to be fixed. If you have any suggestions please mail me or file a ticket.
pyexiv2 is the python extension of Exiv2 library. It helps to find the EXIF information from an image.
The current rawhide version is broken, it just can not be imported.
[kdas@d80 ~]$ python
Python 2.6 (r26:66714, Mar 17 2009, 11:44:21)
[GCC 4.4.0 20090313 (Red Hat 4.4.0-0.26)] on linux2
Type “help”, “copyright”, “credits” or “license” for more information.
>>> import pyexiv2
Traceback (most recent call last):
File “<stdin>”, line 1, in <module>
File “/usr/lib/python2.6/site-packages/pyexiv2.py”, line 60, in <module>
import libexiv2python
ImportError: /usr/lib/python2.6/site-packages/libexiv2python.so: undefined
Tried to find what that symbol is using c++filt
[kdas@d80 ~]$ c++filt _ZNK5Exiv29Exifdatum6typeIdEv Exiv2::Exifdatum::typeId() constNow is this a very new pyexiv2 which contains symbols from latest exiv2-lib or a problem itself ? The bug is here.
Update: It seems to be a local symbol. It comes from exiv2-lib only , but it shows as local with “notype” from the eu-readelf output :(
You can find the wiki page here. This year we want to make groups such that there are two students in a group and make them work on any upstream project or a new project. They should start the work of finding the project ideas within first two weeks of the program. Comments/suggestions are welcome.
We have added a few buzz words in the poster to attract students. Generally students prefer to go to different small institutions to do summer project where most of the times they pay a good amount to get a certificate. Trying to change the situation slowly.
Thanks to Nicu for the poster.
Paul W. Frields, the fearless Fedora Project Leader and long time contributor to the Fedora Docs project, is going to conduct a session on Fedora Docs as part of dgplug’s summer training.
Venu: #dgplug on irc.freenode.net Date Time: September 4 , Thursday, 13:00 UTC
Máirín Duffy already conducted a session on Fedora Art , you can read the log here.
I came in between Ramki’s session on Python. It went well and he was not keen to give them lunch break :) Don’t remember when i slept, suddenly found my phone is ringing and Rahul is telling me to wake up and the all the attendees were looking at me :) Ramki was calling me from the first row, I was sitting in the last row.
After his talk Rahul gave a talk on Fedora project and how people can contribute to it, I wrote few lines about it in my last post.
Photos:
All photos.
Now I should run to the guesthouse.
I always feared shell scripts when I was in college. Always knew that it is very powerful if I use it properly, I never did.
Two days back, in I was trying to help one of my college junior to setup Qt4 and the environment to run it. I told him to follow this page. But Pradeepto said the idea of having another user is not so good. and he said:
Apr 30 00:48:21 pradeepto: you can even do make sure that as you changedirectories,
the env-vars are set automagically.So, I tried to something like that, asked few questions on #bash about how to write a function with same name of a shell command and then call the actual shell command. So, got the shell-builtin-command ‘builtin’ which executes other shell builtins. Also asked lots of questions to Jace about shell programming :p
My target was, as I change my directory to any directory named ‘pyqt4’ or sub-directories under it all environment variables should change accordingly to run Qt4 or PyQt4 codes and in other directories the normal environment should stay to run Qt3 :)
The result in my .bashrc :
export tQTDIR=“$QTDIR”export tPATH=“$PATH”
export tMANPATH=“$MANPATH”
export tLD_LIBRARY_PATH=“$LD_LIBRARY_PATH”
export tPKG_CONFIG_PATH=“$PKG_CONFIG_PATH”
export tQTINC=“$QTINC”
export tQTLIB=“$QTLIB”
export eFlag=0changePath()
changePath()
{QTDIR=“$tQTDIR”
PATH=“$tPATH”
MANPATH=“$tMANPATH”
LD_LIBRARY_PATH=“$tLD_LIBRARY_PATH”
PKG_CONFIG_PATH=“$tPKG_CONFIG_PATH”
QTLIB=“$tQTLIB”
QTINC=“$tQTINC”
export QTDIR PATH MANPATH LD_LIBRARY_PATH PKG_CONFIG_PATH QTINC QTLIB
}
cd ()
{
if [ “$#” -eq “0” ]
then
if [ “$eFlag” -eq “1” ]
then
changePath
export eFlag=0
fi
builtin cd
else
bname=echo "$1"|grep pyqt4
if [ “${bname}” = “$1” ]
then
QTDIR=/home/kdedev/src/kde/qt-copy
PATH=$QTDIR/bin:$PATH
MANPATH=$QTDIR/doc/man:$MANPATH
LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
PKG_CONFIG_PATH=$QTDIR/lib/pkgconfig:$PKG_CONFIG_PATH
QTINC=$QTDIR/include
QTLIB=$QTDIR/lib
export QTDIR PATH MANPATH LD_LIBRARY_PATH PKG_CONFIG_PATH QTINC QTLIB
export eFlag=1
builtin cd “$1”
else
if [ “$1” = “..” ]
then
builtin cd “$1”
dname=pwd
bname=echo "$dname"|grep pyqt4
if [ “$bname” != “$dname” ]
then
if [ “$eFlag” -eq “1” ]
then
changePath
export eFlag=0
fi
fi
else
if [ “$eFlag” -eq “1” ]
then
changePath
export eFlag=0
fi
builtin cd “$1”
fi
fi
fi
}
I think the code is not so much readable in my blog :)
Update: Pradeepto asked me to upload the code as a file, so here it is. Just copy paste the contents of this file into your $HOME/.bashrc .
Shell commands tutorial using Konsole, part 1 in bengali is out. You can check it out from here.