Comments on: Pulse http://blogs.gnome.org/shaunm/2008/03/03/pulse/ Fourteen hours to save the Earth Thu, 02 Feb 2012 10:02:40 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: shaunm http://blogs.gnome.org/shaunm/2008/03/03/pulse/comment-page-1/#comment-42 shaunm Tue, 04 Mar 2008 00:01:58 +0000 http://blogs.gnome.org/shaunm/2008/03/03/pulse/#comment-42 I've thought about trying to identify translation and documentation commits. I do know what domains and documents are in the module, and which directory those are in. So I could see if all the files of a given commit are in a particular directory. I'm not sure I'd want to use only code commits for the graph though. To me, it's interesting to see the effect translations have on the total activity. But certainly being able to filter out non-code commits in the activity listing could be useful. As for developers, maintainers have a star next to their names. Other types of developers will be identified by other badges. It's just that, at the moment, the MAINTAINERS file is the only source of information for developers. That will certainly change once I get bugzilla stuff integrated. Suggestions for other sources of developers are welcome. (You can see, for instance, on documentation pages we have maintainers, authors, editors, publishers, and generic developers. But I don't have icons yet for anything other than maintainers.) I’ve thought about trying to identify translation and documentation commits. I do know what domains and documents are in the module, and which directory those are in. So I could see if all the files of a given commit are in a particular directory. I’m not sure I’d want to use only code commits for the graph though. To me, it’s interesting to see the effect translations have on the total activity. But certainly being able to filter out non-code commits in the activity listing could be useful.

As for developers, maintainers have a star next to their names. Other types of developers will be identified by other badges. It’s just that, at the moment, the MAINTAINERS file is the only source of information for developers. That will certainly change once I get bugzilla stuff integrated. Suggestions for other sources of developers are welcome. (You can see, for instance, on documentation pages we have maintainers, authors, editors, publishers, and generic developers. But I don’t have icons yet for anything other than maintainers.)

]]> By: Johannes http://blogs.gnome.org/shaunm/2008/03/03/pulse/comment-page-1/#comment-41 Johannes Mon, 03 Mar 2008 23:35:54 +0000 http://blogs.gnome.org/shaunm/2008/03/03/pulse/#comment-41 Really cool! For the activity view/commits I would really like to see a split between translation and code. For me as developer, translation updates are not that interesting so it would be good to be able to filter them. Another thing is that you should either rename "Developers" to "Maintainers" or at least import the developer list from bugzilla. But really rocking! Really cool!

For the activity view/commits I would really like to see a split between translation and code. For me as developer, translation updates are not that interesting so it would be good to be able to filter them.

Another thing is that you should either rename “Developers” to “Maintainers” or at least import the developer list from bugzilla.

But really rocking!

]]> By: PMPope http://blogs.gnome.org/shaunm/2008/03/03/pulse/comment-page-1/#comment-40 PMPope Mon, 03 Mar 2008 22:34:10 +0000 http://blogs.gnome.org/shaunm/2008/03/03/pulse/#comment-40 Awesome Feature, Shaun! KUGW! Awesome Feature, Shaun! KUGW!

]]> By: shaunm http://blogs.gnome.org/shaunm/2008/03/03/pulse/comment-page-1/#comment-39 shaunm Mon, 03 Mar 2008 21:43:30 +0000 http://blogs.gnome.org/shaunm/2008/03/03/pulse/#comment-39 Marko, while maintainers do tend to know everything developer-related about their projects, Pulse can be a good way for them to see how the documentation and translation teams are keeping up with them on their modules. Even for the things the maintainers know about, though, the Pulse page for their module can serve as a quick start page with links to things they want to see when hacking. But your point is taken. The real value lies in presenting information to people who aren't already in the know. And that includes, in large part, new and occasional developers. Blog aggregation is something I've thought about as well. I wouldn't want to turn Pulse into a full-blown Planet, but links to recent blog posts would be nice. Note that a number of projects have their own blogs, independant of the blogs of their maintainers, and we could feed these into project pages. I have a fairly flexible mechanism for putting data into Pulse manually. My general workflow is often to put data in that way, write some processing code, and then figure out how I could get that data automatically. A few things just have to be entered manually, as they're the starting point for everything else. Marko, while maintainers do tend to know everything developer-related about their projects, Pulse can be a good way for them to see how the documentation and translation teams are keeping up with them on their modules. Even for the things the maintainers know about, though, the Pulse page for their module can serve as a quick start page with links to things they want to see when hacking.

But your point is taken. The real value lies in presenting information to people who aren’t already in the know. And that includes, in large part, new and occasional developers.

Blog aggregation is something I’ve thought about as well. I wouldn’t want to turn Pulse into a full-blown Planet, but links to recent blog posts would be nice. Note that a number of projects have their own blogs, independant of the blogs of their maintainers, and we could feed these into project pages.

I have a fairly flexible mechanism for putting data into Pulse manually. My general workflow is often to put data in that way, write some processing code, and then figure out how I could get that data automatically. A few things just have to be entered manually, as they’re the starting point for everything else.

]]> By: Marko Anastasov http://blogs.gnome.org/shaunm/2008/03/03/pulse/comment-page-1/#comment-38 Marko Anastasov Mon, 03 Mar 2008 21:12:30 +0000 http://blogs.gnome.org/shaunm/2008/03/03/pulse/#comment-38 I think that this kind of a system would be most helpful to contributors (to some degree), and anybody who wants to check out what's going on with the development of a certain project. I'm not sure how really useful would it be to maintainers, who already "know everything" about their projects, except that it is indeed nice to occasionally take a look at such a unifying "collection of random interesting facts". So then it would be definetely good to show most recent mailing list posts, with links to complete archives, and latest bugzilla entries. A separate page could show links to all components etc. Perhaps also a post or two from developer's blogs - or an even more clever way would be to display only posts tagged as "project"; you would just need to announce it somewhere so that everyone would start doing it properly. Although I'm not sure if it would be possible to do it completely automatically - developers would probably need to create some "GNOME Pulse" profile - integrated with existing infrastructure? - and specify feed URLs. I think that this kind of a system would be most helpful to contributors (to some degree), and anybody who wants to check out what’s going on with the development of a certain project. I’m not sure how really useful would it be to maintainers, who already “know everything” about their projects, except that it is indeed nice to occasionally take a look at such a unifying “collection of random interesting facts”.

So then it would be definetely good to show most recent mailing list posts, with links to complete archives, and latest bugzilla entries. A separate page could show links to all components etc. Perhaps also a post or two from developer’s blogs – or an even more clever way would be to display only posts tagged as “project”; you would just need to announce it somewhere so that everyone would start doing it properly. Although I’m not sure if it would be possible to do it completely automatically – developers would probably need to create some “GNOME Pulse” profile – integrated with existing infrastructure? – and specify feed URLs.

]]> By: shaunm http://blogs.gnome.org/shaunm/2008/03/03/pulse/comment-page-1/#comment-37 shaunm Mon, 03 Mar 2008 21:02:58 +0000 http://blogs.gnome.org/shaunm/2008/03/03/pulse/#comment-37 ATOM, RSS, RDF, and whatever other machine-readable formats would help are certainly on the radar. Pulse could then function as a base body of knowledge upon which other systems could be built. I haven't yet added these things because, well, there's a lot of information in Pulse, and it's not yet clear to me what would be most useful. ATOM, RSS, RDF, and whatever other machine-readable formats would help are certainly on the radar. Pulse could then function as a base body of knowledge upon which other systems could be built. I haven’t yet added these things because, well, there’s a lot of information in Pulse, and it’s not yet clear to me what would be most useful.

]]> By: Christian Hergert http://blogs.gnome.org/shaunm/2008/03/03/pulse/comment-page-1/#comment-36 Christian Hergert Mon, 03 Mar 2008 19:24:28 +0000 http://blogs.gnome.org/shaunm/2008/03/03/pulse/#comment-36 Can we get an ATOM or RSS feed? Can we get an ATOM or RSS feed?

]]>