Slashdot Mirror
KDE Accepted To Google Summer of Code 2015
jrepin writes The KDE student programs team is happy to announce that KDE has been accepted as a mentoring organization for Google Summer of Code 2015. This will allow students from around the world to work with mentors on KDE software projects. Successful students will receive stipends from Google. Ideas on what a student entering Google Summer of Code 2015 with KDE might work on are listed on the Community Wiki.
Oh man! That's awesome!
The purpose of existence is to make money.
How can KDE shed some of its bloat by using some of the services and API provided by Systemd?
No thanks. Not interesting in having my computer running code written by amateurs being mentored by other amateurs. I'll stick to OSes like Windows and OS X that are developed by professionals.
Visit http://www.google-melange.com/... to see all the organizations accepted.
I am associated with RTEMS, Network Time Foundation, and GCC all of which are also participating.
Looks like they jumped over an inch high bar, yes. The requirements pretty much seem to be:
1) Do you use an OSI approved license?
2) Do you have ideas for improvement?
3) Can you provide mentors?
4) Are you a somewhat popular, established project?
Then you're good. I mean there's many obscure mentoring organizations there I've never heard about.
Live today, because you never know what tomorrow brings
Write your own Slashvertisement pal. This is about KDE and child labor. Hijacking a thread is something Systemd would do. - not kool.
GCC, please move out of the way for clang. Sundar's got the reigns, Larry and sergay are too senile drunk with money to run the company anymore. you got a fat belly of middle managers.
There are several very good projects on the Wiki page. My favourites are probably:
Project: Port Amarok to Qt5/Kf5/Plasma5: Something I use every day.
Project: Port KSystemLog to use journald as a backend: With systemd it is actually possible to make a distro agnostic GUI log viewer that isn't just a "less" with windows decorations. I like using the CLI "journalctl", but a GUI, perhaps with some log watch support and real time panel notifications about "syslog level: Error" events and above would be nice.
Project: Implement PDF Poppler features: I like Okular very much, so more features like linearized pdf support would be nice.
Yeah, really an only inch high bar!
That is why Mozilla, Tor and others were rejected!
http://blog.queze.net/post/2015/03/03/Mozilla-not-accepted-for-Google-Summer-of-Code-2015
KDE is the desktop environment of Kubuntu, which is a variant of Ubuntu, which will soon be switching to systemd.
See? That wasn't so hard.
I am pretty sure over 50% of the organizations that apply are not accepted in any given year.
The requirements you list are minimum ones. Speaking as an organization administrator for GSoC (and ESA SOCIS), there is a lot of work that must be done so an organization can do a good job with students. The ideas must be summer-sized projects with clear goals. You want an easy on-ramp for new developers with a welcoming community. You realistically need multiple mentors per student, to be responsive to those students, and to track them so they don't fall into a pit. You are also responsible for helping them set realistic mid-term and final goals that they can be evaluated against.
And this ignores helping promote the program, recruit students, and try to keep the students involved in your organization or free software in general after the summer is over.
If you haven't mentored or been an organization administrator for GSoC, then you don't know how seriously all organizations take being able to be prepared and do a good job for their students. The IRC meeting with discussions on why some organizations didn't make it this year is at: http://infobot.rikers.org/%23g.... It starts at 16:00. Not sure how much detail they got into. I just did a quick scan.
it's time to rewrite systemd in javascript
Ugh, that's bad. Ignoring exit statuses, swallowing stderr, and ignoring syslog messages are all pretty serious bugs.
Recently we downloaded the official MongoDB rpm, and it worked great for a few weeks until after a power loss it simply wouldn't restart with systemctl. The problem was the existence of the file "/var/lib/mongod/mongod.lock". mongod outputs that error to stderr. systemd didn't record that in the journal, and it had a zero (no error) exit status. Before systemd, that problem would take seconds to fix because of the clear error message. It took me most of a day to find the problem since systemd hid that message.
I have not understood why Systemd has binary logs why is it so hard to have human readable logs?
I'm wondering if there could be a project for the most "Systemd powered" distribution. How many packages can we trim and hand work over to Systemd?
> MongoDB...systemd didn't record that in the journal
Were you the person that posted about this before? If so, thank you because one of the replies helped us greatly. The problem is this line in /etc/init.d/mongod:
daemon --user "$MONGO_USER" --check $mongod "$NUMACTL $mongod $OPTIONS >/dev/null 2>&1"
stderr is redirected to /dev/null. That's why systemd doesn't log it on Red Hat 7. The thing I can't figure-out is why on Red Hat 6, that error is still output when you run "/etc/init.d/mongod start". It doesn't make any sense to me. I have about four dozen servers running 6 and three running 7 in a datacenter with unreliable power so not logging this error is causing a lot of grief.
Changing that line to:
daemon --user "$MONGO_USER" --check $mongod "$NUMACTL $mongod $OPTIONS"
Didn't help. The error about the lock file wasn't logged in the journal:
centos7test# journalctl -u mongod -r | head -10
-- Logs begin at Thu 2015-03-05 03:42:12 UTC, end at Sat 2015-03-07 21:30:42 UTC. --
Mar 07 21:29:50 centos7test systemd[1]: Unit mongod.service entered failed state.
Mar 07 21:29:50 centos7test systemd[1]: Failed to start SYSV: Mongo is a scalable, document-oriented database..
Mar 07 21:29:50 centos7test systemd[1]: mongod.service: control process exited, code=exited status=1
Mar 07 21:29:50 centos7test mongod[24944]: [FAILED]
Mar 07 21:29:50 centos7test runuser[24954]: pam_unix(runuser:session): session closed for user mongod
Mar 07 21:29:50 centos7test mongod[24944]: ERROR: child process failed, exited with error number 100
Mar 07 21:29:50 centos7test mongod[24944]: forked process: 24958
Mar 07 21:29:50 centos7test mongod[24944]: about to fork child process, waiting until server is ready for connections.
Mar 07 21:29:50 centos7test mongod[24944]: Starting mongod: note: noprealloc may hurt performance in many applications
Getting systemd to log stderr is something I don't grok.
Running it by hand:
su mongod mongod -f /etc/mongod.conf
Correctly outputs the error to /var/log/mongodb/mongod.log unlike when trying to start it with systemctl:
2015-03-07T21:33:32.427+0000 W - [initandlisten] Detected unclean shutdown - /var/lib/mongo/mongod.lock is not empty.
That error isn't logged anywhere I can tell when starting it with systemctl. I've wasted hours on this problem so far.
As an example of how to screw your users with ever more bloated code, resulting in a dogmatic paradigm that is essentially my-way-or-the-highway?
> binary logs
That doesn't bother me at all. You can always pipe the output to grep or whatever tools you need. Also, it gives you the advantage to easily show the log messages from a single unit. It is awesome to be able to do something like this:
vpn # journalctl -u sshd -r | head -5
-- Logs begin at Thu 2015-03-05 02:41:16 UTC, end at Sat 2015-03-07 21:41:46 UTC. --
Mar 07 21:26:13 vpn sshd[24793]: Failed password for invalid user admin from 27.115.0.210 port 34255 ssh2
Mar 07 21:26:12 vpn sshd[24793]: pam_unix(sshd:auth): check pass; user unknown
Mar 07 21:26:12 vpn sshd[24793]: Failed password for invalid user admin from 27.115.0.210 port 34255 ssh2
Mar 07 21:26:09 vpn sshd[24793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.115.0.210
That is a much more reliable way of finding just the log messages from a service than using grep and /var/log/messages. The problem is that so many messages do not make it into the log:
vpn # journalctl -p 0..3 | wc
-- Logs begin at Thu 2015-03-05 02:41:16 UTC, end at Sat 2015-03-07 21:47:03 UTC. --
vpn #
That is what you should be complaining about. We modified the OpenSSH source to log the messages to level 4 so they wouldn't be ignored by systemd. Dropping failed login log messages is a serious security problem.
Forget systemd - KDE is a common desktop choice on AIX and FreeBSD. The fact that it is much more Unix friendly then GNOME is a talking point in and of itself.
I'm starting to think GNU is the problem with "GNU/Linux" these days.
Only slightly on-topic, but I've been using KDE plasma 5 since 5.2 came out. And it's great. I was a refugee escaping from Gnome 3 who went to XFCE for a few years. But that never completely satisfied me.
But KDE does now. Which is funny, because in the days of Gnome 2, I really didn't like KDE.
Free the Quark 3 from asymptotic confinement! Bring your charm! Don't get down! All colours and flavours welcome!
Maybe rthey can pay students yo remove it.
You can't be serious.
I hope they'll also have a look at the issues with KDM running under systemd because LightDM is not everyone's choice.
Although, Plasma5 replaces KDM with SDDM which does work with systemd.
"The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
... the world's largest repository of mostly abandonware. A huge number of projects (actually most, I would say about 97%) are started by a student and completely abandoned by the end of the summer or at most a semester.
Many of them with great potential, but never completed.
No, it wont. Everything in KDE is optional, even Systemd. Unfortunately if you want to use Kwin on Wayland it will require Systemd, but that is not the fault of KDE developers.
What is dead may never die
And then this? https://www.youtube.com/watch?...
That is not dead which can eternal lie, And with strange aeons even death may die.