Geçtiğimiz Çarşamba itibari ile DEU Bilgisayar Mühendisliği doktora programına kaydımı yaptırdım. Yüksek lisanstan mezun olduğumda tez sürecinden sonra doktora felan yapmam arkadaş diyordum. Şimdi hayatımda başka parametreler  de var , var olanların bazıları da değişti. O zamanki bakış açım ile şimdiki fikirlerim arasında farklılıklar var. Artık şimdilerde doktora ile ilgili başarmak istediğim hedefler belirleyebiliyorum.

Doktoraya başlayacağım için biraz heyecanlıyım. Beraber çalışmayı planladığım hocanın bundan 4-5 sene sonrası için bir tez yapmayı planlıyor olmam ve bilgisayar dünyasında bu süre düşünülecek olursa ortaya koymam gereken çalışmanın ciddiyetini hatırlatması doktorada düzenli çalışmanın gerekliliğini bir kere daha hatırlamamı sağladı. Şu ana kadarki doktoraya alım ve kayıt süreci bence memnunluk vericiydi. Dokuz Eylül bu konuda gayet sistematik çalışıyor demeliyim. Çalışmak istediğiniz bir konu ve hoca bulmak işin kabul kısmını büyük ölçüde çözüyor. Bir takım sınav değerlerinin üzerinde notlarınızın olması, sınav ve mülakatta asgari başarı sağlamanız işinizi garantiliyor. Sonrası düzenli derse gitmek, hocayla çalışmak ve bir takım hedefleri gerçeklemeye çalışarak geçecek gibi.

Just a quick update to let you know that I just released the Ubuntu Italian Remix 10.04.1.

With the updated official Ubuntu ISO, it was time to rebuild all Ubuntu Mini Remix images, for both 32 and 64bit architectures, so here you have!

Ubuntu Mini Remix 10.04.1

Baby, originally uploaded by gabi_menashe.

(This is a guest post by Asheesh Laroia of OpenHatch, an “open source involvement engine.” OpenHatch is a website and ongoing project to help new contributors find their place in free software projects. A few months ago, he imported some bugs in KDE’s bug tracker into the OpenHatch volunteer opportunity finder. I invited him to write about it for my blog. OpenHatch has its own blog, too.)

KDE is doing something wonderful with its Junior Jobs. These are issues (often small feature requests) that are appropriate for a first-time contributor. When maintainers create these opportunities, they take information that would otherwise be trapped in their head — how easy or hard an issue is — and make it available as hint to new contributors. Conveniently, creating a “Junior Job” doesn’t take any special work: maintainers just have to find the relevant bug in KDE Bugzilla and add the junior-jobs keyword.

But KDE Bugzilla isn’t necessarily a friendly welcome mat. Probably everyone reading this post can remember a time when Bugzilla seemed like a difficult, arcane tool. Bugzilla works well (enough) as an interface for project maintainers to share the status of what they’re working on with each other.

But imagine you are a prospective contributor. Aim your web browser at the list of junior jobs. (To get that link, I went to KDE Bugzilla and clicked the “Junior Jobs” link on the left side.) This is what I saw when writing this post:

Here are some questions I might have as a new contributor (and some commentary as myself):

• What do “wis” and “UNCO” mean?
• Who is JJ? (Maybe that’s a person’s initials; maybe he or she plans to fix it.)
• What project are these bugs in? (I can guess from the assignee….)
• Where do I get the source code? (The wrong answer might lead the new contributor to submit a patch against the most recent release; that patch might not apply against trunk.)
• If I get started on this, who can help me when I get stuck? (Otherwise, a new contributor might make an effort, become confused by something, and fall away.)

I like to joke that bug trackers say lots of information about what the problem is, but they don’t provide any information on how to solve it.

We at OpenHatch noticed that a great number of projects were in a similar situation: they label bugs as “easy”, “bitesize”, or “Junior Jobs” and point first-time contributors straight at the bug tracker. So we created what we call the volunteer opportunity finder to help people find something to work on. It wakes up late at night to download issues from bug trackers representing hundreds of projects. (Since OpenHatch is itself a free software project, we also import the bitesize bugs from our own bug tracker.)

When you browse the available issues, you can click on the project name and see its page on OpenHatch. (We make one for every project that someone says they’ve contributed to, or where we’ve imported bugs for it.) The pages showcase the people who have listed themselves as possible mentors. Contributors can also write instructions or suggestions for how to get involved; for example, the page for Gally does a great job of answering “Other than writing code, how can I contribute?”

If you don’t know how to get involved, you can also browse opportunities by programming language, the kind of help you want to give (such as writing documentation) or flip through a few projects you might want to work on. You can narrow your search to just the ones we call “bitesize” (“Junior Jobs” in KDE, bugs labeled as “easy” in the Python programming language, and so forth).

So OpenHatch is a project to think through how people join free software communities and to build technical tools and social structures to make that better. This browsing tool is one thing we’ve built. It’s a community project, so you can help out! Say hi on IRC or email if you want to join in.

I’d like to hear (in the comments on this post) from you guys and gals: What do you think about our “volunteer opportunity finder”? What works about it for you? What would you change?

If Lydia invites me back, I plan to write about getting non-coders more involved in free software projects. During the weekend I first met Lydia and Jeff Mitchell of Amarok, I had a crazy idea for something you can build on top of OpenHatch. If you want to stay in touch until then, join our IRC channel or subscribe to us on Identi.ca/Twitter/RSS!

On Saturday, 28th August 2010 1:00pm - 9:00pm at the kwartzlab, The Kitchener/Waterloo Chapter of Ubuntu Canada will participate in the Global Jam. Everybody is invited. We will have lots of fun, socializing and will learn and teach how everybody can help and contribute to the Ubuntu project.

If you are in Quebec, please look at our friends event in that part of Canada!

read more

It’s time for another Geeknic, this one will be happening in Oaks, PA, just off of route 422 for easy access from the suburbs and the city.

We’ll be gathering at Lower Perkiomen Park for food, games, and fun from 2pm to 6pm on Saturday Sept 11th, 2010.  The location includes various sports fields, playgrounds, and walking trails, and there are a few geocaches near our location as well.  The event is free and food will be provided in a potluck fashion: we ask that attendees bring something along with them.   You can indicate what you will bring on the wiki when signing up.

Our last picnic geeknic was in the summer of 2009, and you can see pictures here.

Head over to http://wiki.geeknic.org/index.php/Lower_Perkiomen_Geeknic to sign up.  Contact jonathand@geeknic.org with any questions.

Just a quick reminder: as part of our awesome Ubuntu Global Jam I am organizing the Ubuntu California Rockridge Jam at A’cuppa Tea, College Ave, Berkeley. The jam is from 10am – 6pm – I hope to see you there!

Don’t live near me? Go and find your nearest jam or organize your own!

This week’s Bug Day target is *drum roll please* Ubuntu Translations!

The task is to assign to the right package and triage those as well:

• 15 New bugs need a hug
• 31 Incompletes bugs need a status check
• 42 Confirmed bugs need a review

Bookmark it, add it to your calendars, turn over those egg-timers!

• Thursday, 26 August 2010
• https://wiki.ubuntu.com/UbuntuBugDay/20100826

Are you looking for a way to start giving some love back to your adorable Ubuntu Project?

Did you ever wonder what Triage is? Want to learn about that?

This is a perfect time!, Everybody can help in a Bug Day! Open your IRC Client and go to #ubuntu-bugs (freenode) the BugSquad will be happy to help you to start contributing!

Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page!

We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning

If you’re new to all this, head to https://wiki.ubuntu.com/Bugs

[Discuss Announcing this week’s Bug Day target - Ubuntu Translations! - Thursday, August 26, 2010! on the Forums]

Originally sent to the Ubuntu Devel Announce Mailing List by Kamus on Mon Aug 23 17:31:28 BST 2010

Some time back the Ayatana project introduced the Application Indicator Framework, based upon technology created by the KDE project. We have been shipping this technology in Ubuntu for a few releases now and it makes the top-right part of the desktop a smooth, efficient, and pleasant experience, getting over the inconsistent and limiting notification area we had before.

To help build integration in the GNOME panel for this indicator work we had Ted Gould, Cody Somerville, and Jason Smith produce an implementation complete with C, Python and C# bindings, had Aurélien Gâteau continue to perform his excellent work with KDE, and Jorge Castro to help spread awareness of this work. In addition to this we contracted some developers to port apps with notification indicators that we ship in Ubuntu to the new framework, and this included apps such as Brasero, GNOME Bluetooth, GNOME Power Manager, Gnome Settings Daemon, XChat-GNOME, iBus, Nautilus, Policykit GNOME, Empathy, Gwibber and more. All of these patches are publicly available if other distros would like to use them.

The community has really got involved with the technology too, with community patches for Lernid, Banshee, LottaNZB, and DejaDup, and System Monitor, Weather, Screenshotting, Workspaces, Device Mounting indicators, support for the indicator framework built into AWN and Lubuntu, and more. I am absolutely delighted to see so much interest from application developers in the technology.