Re: Bijiben
On Tue, Mar 12, 2013 at 06:44:24PM +0100, Pierre-Yves Luyten wrote: I'm requesting a new module inclusion : Bijiben It's another note taking application [1] - goal is to implement Notes design [2] Shown as a preview app in 3.8 release notes: https://help.gnome.org/misc/release-notes/3.8/more-apps.html.en username/password: gnome / ftw -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Google Summer of Code: ideas wanted!
Hiya GNOME lovers! It's that time of the year again: Google Summer of Code is approaching. We've updated our program pages [1] to have the latest information and we need your help in creating a list of great project ideas. It's essential that we have a well-prepared ideas page when GNOME applies as a mentoring organization on March 29. So what should you do? Please visit the ideas page [2] and enter your project ideas under the Untriaged Ideas section. * Discuss your ideas with designers in #gnome-design to get their input and plan collaboration, especially if your ideas are related to one of the core GNOME modules. If you are not sure who to speak to, start with Allan Day (aday). * Consider manageable ideas consisting of multiple smaller features that share a common theme, in addition to single large feature ideas. See the information for mentors page [3] for more on preferred project formats and other mentoring resources. If you are interested in being a mentor this year or at any point find yourself drafted to be one, please join soc-mentors-list [4] to receive future communications about GNOME's participation in GSoC, including the information about important deadlines. Finally, if you would like to throw your hat in the ring for triaging the ideas and proposals, helping students find their way in GNOME, and do other GSoC related tasks, pop on over to #soc-admin and join the team of friendly administrators. So far, it consists of Alexandre Franke, Christophe Fergeau and Marina Zhurakhinskaya, and we would welcome a couple more members. Cheers, The GNOME Google Summer of Code Administrators [1] https://live.gnome.org/SummerOfCode2013 [2] https://live.gnome.org/SummerOfCode2013/Ideas [3] https://live.gnome.org/SummerOfCode/Mentors [4] https://mail.gnome.org/mailman/listinfo/soc-mentors-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Bijiben
Hi Pierre-Yves, Pierre-Yves Luyten p...@luyten.fr wrote: On Tue, 12 Mar 2013 17:31:21 +0100, Andre Klapper ak...@gmx.net wrote: (...) Still we *highly* encourage you to communicate your plans for your projects early. I'm requesting a new module inclusion : Bijiben It's another note taking application [1] - goal is to implement Notes design [2] Thanks for your work on Bijiben so far: it is coming along very nicely! Pierre-Yves has done a great job implementing the Notes [1] design, which is intended to provide a core application for note taking. There are still a few rough edges but I'm hopeful that we can work those out over the next release and have something solid ready for 3.10. Allan [1] https://live.gnome.org/Design/Apps/Notes -- IRC: aday on irc.gnome.org Blog: http://afaikblog.wordpress.com/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild continuous integration testing: status and plans
On Fri, Mar 8, 2013 at 12:48 AM, Martin Pitt martin.p...@ubuntu.com wrote: Hello fellow GNOMErs, after the first round of discussions a month ago[1] about the jhbuild CI building/testing [2] I'd like to give some status update. Along the same topic, I wanted to bring to light something that was recently raised in EDS bugzilla [0]. Vadim filed this bug, and apparently copied the makefile from another module... I was wondering if standardizing this would be interesting for the Continuous Integration servers... the html output it creates is certainly interesting to have, an example of the output can be found here [1]. My thoughts were mostly that in that proposed patch, the included Makefile is a bit crack and hacked out, I would be interested in standardizing that a bit. My thoughts were: a.) Create an m4 macro implementing the gtester rules which could be included in gnome-common and easy to integrate into various GNOME modules b.) Perhaps extend the .doap format (who defines the .doap format anyway ?).. so that the build server (or jhbuild directly perhaps) could introspect whether a module supports the 'make gtester-report' target. In that way, the CI server could automatically collect these reports only for modules which support them. Is it interesting for more modules to implement the more fine grained report ? Did I miss some important information (i.e. is this already done somewhere at least partially and I'm not aware of it) ? Any additional thoughts on this ? Cheers, -Tristan [0]: https://bugzilla.gnome.org/show_bug.cgi?id=695688 [1]: http://dl.dropbox.com/u/8686253/test-report.html Since then, Jean-Baptiste has worked quite a bit on the scripts: Updating git checkouts as well as building modules are now parallelized (building still respects the dependency tree), so that we can now rebuild all the 160 modules in something like 15 minutes now. This brings us much closer to useful commit-level testing. It now also uses jhbuild sysdeps and a much smaller hardcoded list of extra build dependencies (which are not exposed by the module lists). If a build or test fails it now uses jhbuild's -C option to restart with a clean checkout, to avoid tripping over build system cruft from autotools file changes. I spent some time chasing down long-standing failures in some modules, as well as filing bugs for newly identified regressions. Since the announcement, the system has stabilized a lot, and the set of test failures is now quite stable. The thing that hurts most currently is that the machine is behind a proxy. This causes quite a lot of test failures (like libgdata's youtube test), as well as spurious build failures like [3]. We do plan to move this machine into the DMZ soon, so that it has unrestricted network access. I'd like to postpone sending out notifications until that happens, as otherwise we'll spam people too much about irrelevant issues. Once that happens, we'll set up email notifications for state changes (e. g. pass → fails to build, or test fail → pass) and send them to Jean-Baptiste and myself first, to give this some more real-world testing. If that has a low enough noise ratio, we were planning to mail the maintainers of the affected modules (if the module has a .doap file), with some hint to notify us if they want to opt out of notifications. Then we can investigate for some time how this works, and debate if filing bugs would be better or not. Does that sound like an acceptable plan? Thanks, Martin [1] https://mail.gnome.org/archives/desktop-devel-list/2013-February/msg00025.html [2] https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/ [3] https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/job/jhbuild-amd64-libgee/92/artifact/libgee.log -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild continuous integration testing: status and plans
On Wed, Mar 13, 2013 at 6:54 AM, Tristan Van Berkom t...@gnome.org wrote: Did I miss some important information (i.e. is this already done somewhere at least partially and I'm not aware of it) ? I'd really rather get off gtester - as you've noticed, it is somewhat lacking, and the Makefile integration is really not great. See https://bugzilla.gnome.org/show_bug.cgi?id=692125 for my attempt at this. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild continuous integration testing: status and plans
On Tue, Mar 12, 2013 at 04:00:29PM -0400, Colin Walters wrote: That said - I'm just going to add the authors of DEP8 to this discussion in the hopes of making it look more like fully installed tests (my proposal does kind of lack a name, and that's the best I can come up with at the moment...) Thanks for getting us in the loop. I'm kinda busy-ish until the end of the month, so I haven't yet had time to look into this (sorry!). But let me point out that these days autopkgtest/DEP-8 development in Debian mostly happens on the following mailing list: http://lists.alioth.debian.org/mailman/listinfo/autopkgtest-devel I'll bounce there your mail, you might want to include that address in future exchanges. HTH, Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club » ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild continuous integration testing: status and plans
Hey, Matthias, could you explain more on gtester faults or propose alternatives? Just for explanation - I proposed this change as gtester produces nice html report and XML output, which, being converted to JUnit XML, can be used to collect stats of failing tests - this can be used to spot unstable tests. Note, that this feature is not essential (EDS bug doesn't replace old 'make check' system), but might be very useful. Thanks, Vadim - Original Message - From: Matthias Clasen matthias.cla...@gmail.com To: Tristan Van Berkom t...@gnome.org Cc: GNOME release team release-t...@gnome.org, desktop-devel-list desktop-devel-list@gnome.org Sent: Wednesday, March 13, 2013 12:07:27 PM Subject: Re: jhbuild continuous integration testing: status and plans On Wed, Mar 13, 2013 at 6:54 AM, Tristan Van Berkom t...@gnome.org wrote: Did I miss some important information (i.e. is this already done somewhere at least partially and I'm not aware of it) ? I'd really rather get off gtester - as you've noticed, it is somewhat lacking, and the Makefile integration is really not great. See https://bugzilla.gnome.org/show_bug.cgi?id=692125 for my attempt at this. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Another showstopper review for 3.8
GNOME-DOCUMENTS https://bugzilla.gnome.org/show_bug.cgi?id=686527 Pickup ownCloud accounts from GOA OwnCloud feature completion - I'll drop this is a simple patch doesn't appear before .92 Lets push this back to 3.10. Files already show up in Nautilus and GtkFileChooser, so this isn't that much of a loss. Happy hacking, Debarshi -- If computers are going to revolutionize education, then steam engines and cars and electricity would have done it too. -- Arjun Shankar pgpzlxEKFPrXv.pgp Description: PGP signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
