Hi to all & congratulations to all the students who made it this year!
I am Dimitris and I am from Greece. I am a PhD student at the AKSW Group of
Leipzig University. I work on DBpedia, Libraries and Linked Data quality
and I've been involved in the DBpedia project for 3 years now.
For GSoC 2013 I try to lead the organizational stuff so besides your
mentors I can also be a point of contact for anything you need. I am also
the main mentor of Lazaros and co-mentor of Hady and Denis (and I might get
a little involved in Kasun).
This year we have many students & mentors so we need to make this process
as transparent as possible for all, especially the community as well. Thus,
all mentors created the following guidelines that you should follow
Student setup
Each student should set up:
1.
a public clone of a DBpedia GitHub repo (or a new repo if necessary),
you can talk to your mentors for that
2.
a progress page
3.
subscription to dbpedia-developers or dbp-spotlight-developers
A global place for making proposals public
http://wiki.dbpedia.org/gsoc2013/students
Accepted students are required to post a short version of their proposals
with links and pointers to their cloned repo and progress page, etc. This
can include:
1.
short proposal description
2.
link to longer description,
3.
mentors
4.
link to progress page
5.
link to commit rss feed
6.
links to other things (blog, twitter, linkedin, personal homepage)
Extra guidelines
1.
Commit everything you have at reasonable intervals and push at the end
of the day. Don’t worry: we are all developers and software is never
finished, so we know that code is dirty before it gets refactored at least
once or twice. You are mainly working on your personal clone, so see it as
a back up. Commits are one of the few measurable activity points. So many
commits means, you are working a lot.
2.
Communicate over the developers list. DBpedia+Spotlight normally uses
the dev lists to communicate. This creates transparency and documentation
and also allows your co-mentors and other people to help out with problems
and give feedback as well. We are a great fan of the Apache rule: “If it’s
not on the mailing list, it doesn’t exist”. Of course, private chats and
calls are also allowed :) but never ever consider any public email as spam.
3.
Short weekly reports on the progress page for everybody:
1.
Did you reach your goals this week?
2.
if yes, what did you do?
3.
if no, what do you think was the problem?
4.
what are your plans for next week?
5.
what phase are you in? What is your next milestone?
example from last year
https://github.com/dbpedia-spotlight/dbpedia-spotlight/wiki/GSoC2012-Progress-%28Jo%29
https://github.com/dbpedia-spotlight/dbpedia-spotlight/wiki/GSoC2012-Progress-%28Dirk%29
Best,
Dimirtis
--
Kontokostas Dimitris
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Dbpedia-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-developers
