aurelien gateau blogged about dental-on-line's new open source patches website. it presents their in-house modifications to the free software they use in a nicely sorted and annotated fashion. with the reality that not all patches will make it upstream, this is certainly one way to be a useful and upstanding free software citizen! kudos to this free software lovin' dental software company.
now i'm left dreaming of a day when there's an easy to set up website that anyone can self-host to present their patches to the world like this ... which are then linked together via some sort of grid-like web service so i could easily grep for kde patches ... a queryable patches planet ... which would give me a list of such patches from around world along with who they came from, what they do and a link to the patch itself ... all decentralized so there's no mother ship to have to coordinate with, no single point of failure ... just a low barrier mechanism to publish patches for up-, side- and down-stream adoption ...
i also want chocolate that doesn't rot my teeth. either that or the ability to grow new teeth like sharks do. that'd be nearly as cool as that distributed patch publication system idea. not quite, but nearly.
Subscribe to:
Post Comments (Atom)
8 comments:
It shouldn't be too much of a problem if all of these sites provided rss feeds or something similar. Any site can just aggregate them and make it searchable. But I suppose you would still need a central site to manage the list of feeds to the patches. Maybe one day there could be a kde-patch.org ;)
Well, i am always on the run to find and try some new patches for KDE, but there are not much... Until now i know only 2 "unofficial" patchsets i am using and which get updated when a new KDE version comes out.
http://sourceforge.net/project/showfiles.php?group_id=126070&package_id=138647
http://www.kde-look.org/content/show.php?content=35731
Anyway, a site with paches for KDE is an awesome idea, and in my opinion it would speed up the development of new features etc somewhat...
One of the big features of ubuntu/canonical's bazarre CMS is that it lets people maintain their own branches of unmerged patches. The use cases they describe on the site sound like they had this sort of thing in mind.
www.kdedevelopers.org/node/2054
http://developer.kde.org/~binner/distributor-patches/
jengu: _Any_ distributed SCM allows you doing that kind of things, at least if the canonical (pun intended) repository uses that same SCM.
aseigo: I don't know if that's what you're looking for, but I've begun writing a "patch server", a small Ruby on Rails application to store patches for arbitrary programs, mark since what upstream version they're applied, if any, see a color-highlighted version, etc.
It's maintained in a Darcs repository, at http://www.demiurgo.org/darcs/patch_server/. There's no documentation yet, as it's still a pet personal project. If you have interest, I can try to setup a demo or something, or at least write installation instructions so you can try on your machine.
Please write to my e-mail address, zoso at demiurgo (dot org), as I probably won't be reading the rest of the comments...
Thanks for the kind words Aaron! I hope we can provide more content soon.
Unfortunately, I don't have any idea to fix your chocolate problems, but if you come to Paris I can probably suggest you a good dentist :-)
> One of the big features of
> ubuntu/canonical's bazarre CMS
@jengu: bzr doesn't solve the issue of publishing and querying for patch sets outside of your branch.
canonical's web services might, but they are proprietary (if built on top of free software) and are centralized which i think are two strikes against that approach.
@daniel: yes, binner's distro patches sets are very cool. i've gleaned through them happily since he started posting them a couple years ago.
unfortunately they aren't something provided by the distros (but is rather a labour of love by binner), don't have the querying capability i'd love to see and totally misses the majority of distros (covers mostly the big ones) and obviously doesn't catch changes made by non-distro companies such as dental-on-line.
the distro patch sets are little more than a glop of patches. we could do sooo much better, no? =)
class cms_patchPage extends cms_renderer
{
function edit(...)
{
//WEBSERVICE to global DB
}
}
You just keep finding all sorts of things for us to do don't you? ;-) Stop thinking ... and finish netMessage::torpedo ... lol
P.S. call me.
Post a Comment