{"thread":{"id":"21524","subject":"custom attributes per file","startedAt":"2009-11-07T23:55:02Z","lastAt":"2009-11-07T23:55:02Z","messageCount":1,"participants":["Daniel Poelzleithner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"127057","messageId":"4AF608D6.6010904@poelzi.org","threadId":"21524","inReplyTo":null,"subject":"custom attributes per file","fromName":"Daniel Poelzleithner","fromEmail":"poelzi@poelzi.org","sentAt":"2009-11-07T23:55:02Z","receivedAt":"2009-11-07T23:55:02Z","isPatch":false,"sender":{"key":"poelzi@poelzi.org","avatar":null},"body":"Hi git devs,\n\nI have seen on your TODO list, that you plan to add tree attributes. We \nwant to use git as a backend to store the wikipedia content in a \ndistributed manner. The exporter [1] is already quite stable it seems. \nToday I started a frontend project [2] and have a feature request :-)\n\n* Make attributes apply to trees, not just working tree.\n\nWhat we need are versioned attributes per file and per tree. Currently \nwe export each article into a file, but there is no way we could save \ncustom attributes directly bound to it, which distributes the data which \nshould be together. If the maximum value per attribute should be quite \nlarge, this way we could save reports of vote results bound to the \narticle directly.\n\nI think unicode data to an ascii key would be sufficient, but real types \ncould provide great features in the future. Changes to these values \nshould be signable by gpg signed commit messages like a normal checkin.\n\nMaybe in the long run, there could be some sort of export filter \nmechanism. For cloning repositories, for example a copy of the wiki \ndatabase based on a quality key of an article could be exported for a \nembedded device.\n\n[1] http://github.com/scy/levitation\n[2] http://github.com/poelzi/communiki\n\nkindly regards\n  Daniel Poelzleithner\n"}]}