@@ -1,3 +1,7 @@ +2007-12-16 Jonathan Matthew <jonathan@d14n.org> + + * HACKING: Now less heinously out of date. Fixes #482767. + 2007-12-13 Jonathan Matthew <jonathan@d14n.org> * configure.ac: ChangeLog @@ -14,27 +14,24 @@ Rhythmbox is also highly object-oriented using GObject. Any major additions should generally go into their own class, and not be bolted onto an existing one. -Any regular patches you send should be in unified diff format (-u -option to patch). +Where it makes sense, it's often easier to add new features as plugins, rather +than integrating them into the core. Plugins can be written in C or Python. +When writing a Python plugin, you might encounter gaps or bugs in the Python +bindings, but these are generally fixed quickly. -Rhythmbox is developed using the Arch revision control system. For -simple changes, you can just get a copy of the source tree, and hack -away. Then, you can get a changeset by doing: +You can find some information on plugin development here: +http://live.gnome.org/RhythmboxPlugins/WritingGuide -tla changes -o /tmp/my-changes.cset - -You can then tar this up (it'll be a directory) and send it via email. - -If you want to make any major changes, it is highly recommended that -you create your own branch of the source tree, and work from there. -That way you can publish your archive somewhere, and we can directly -merge your changes. - -When you are done, you can send a message to -rhythmbox-devel@gnome.org, or post a bugzilla bug with a merge -request. For more information about this, see: -http://web.rhythmbox.org/development.html +Rhythmbox is developed in GNOME Subversion. You can get an anonymous checkout +by running 'svn co http://svn.gnome.org/svn/rhythmbox/trunk rhythmbox'. Any +patches you send should be in unified diff format against current svn trunk. +You can also browse the source code and revision history using a web browser +here: http://svn.gnome.org/viewvc/rhythmbox/trunk. +Bugs and feature requests are tracked in GNOME Bugzilla +(http://bugzilla.gnome.org/) under the 'rhythmbox' product. Patches should be +attached to bugs rather than sent to the mailing list, as patches sent to the +mailing list are easily overlooked and forgotten. Finally, here is some sample code written in the correct style: @@ -63,4 +60,3 @@ foo (const char *bla, gpointer cow) ... } -arch-tag: How to hack Rhythmbox and submit patches HACKING 5da3d0a381c9ae000d3df9553d58ae4c4b5e4c76 Jonathan Matthew jonathan@d14n.org http://github.com/ivankelly/Rhythmbox-Spotify-Plugin/commit/463125543f449058685bd82f94ca937bf3e296e2 463125543f449058685bd82f94ca937bf3e296e2

2007-12-15T20:01:18-08:00

Now less heinously out of date. Fixes #482767. 2007-12-16 Jonathan Matthew <jonathan@d14n.org> * HACKING: Now less heinously out of date. Fixes #482767. svn path=/trunk/; revision=5491 665aacf4c7272056b93f3e0e226bd6fd1c1ec38e Jonathan Matthew jmatthew@src.gnome.org