OpenGuides-Dev

openguides-dev@lists.openguides.org

701 discussions

Next hackfest (pre-YAPC)
by Kake L Pugh 20 Jun '07

20 Jun '07

OK, the next hackfest is looking like one of these two: Sat 21 + Sun 22 July or Sat 18 + Sun 19 August Probably at my house again. Let me know if you have a preference! Note that the latter date is quite close to YAPC, so I'm thinking the July one is probably better, unless loads of people can't make it. Kake

1 1

Review date field
by Dominic Hargreaves 19 Jun '07

19 Jun '07

OpenGuides has had a long-standing feature request from me which I'm now thinking about implementing: http://dev.openguides.org/ticket/1 The idea would be to prevent entries from getting too stale by storing some meaningful data about when the node was last checked over for accuracy (as opposed to other minor changes). This could be done a couple of ways: - as per http://london.randomness.org.uk/wiki.cgi?Trinity%2C_SW4_0JG in free-text in the node content With a ticky-box: "If you have verified the content of this article as correct, please ticky ticky [ ]" Suggested rendering of this data - at the bottom of pages: "This page was last checked for accuracy on yyyy-mm-dd" This itself could be done two ways: - as Wiki::Toolkit metadata - automatically populate it with a standard string representation of the date if appropriate The way I'm starting to favour, though, is a new sort of Wiki::Toolkit data. This has the advantage that it can be typed correctly (as a date object). It's a bit more work to implement, but not too much. The question is, whether this is an appropriate addition to Wiki::Toolkit. Since it is in many ways similar to the modified stamp, I think it is. The question also arises of whether we could also use a "should be reviewed on the following date" - ie an explicitly staleness factor, rather than just inferring such (6 months after last reviewed date, for example). Would it be overkill to be able to specify both? Kake is in favour of retaining free text descriptions (useful of only some parts of the content have been verified) but this doesn't allow systematic searches on this data (so we can proactively go out and regularly review nodes, for example. There's no reason, of course, that we can't keep both functions - people can carry on doing this even if there is more structured data available too. Or we could add a separate free text field, as a normal metadata field. Any opinions welcomed. Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

1 0

http://dev.openguides.org/ticket/113
by Dominic Hargreaves 19 Jun '07

19 Jun '07

Hi, I believe you've already implemented this - do you have any patches to share? Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

2 2

Public domain node images
by Kake L Pugh 19 Jun '07

19 Jun '07

I'd like to use some public domain photos as node images on RGL. I'm not entirely sure how to do this within the "node image" system - the OpenGuides templates automatically put the little "(c)" copyright symbol in front of the name of the person who took the photo. I found a public domain licence on the Creative Commons site: http://creativecommons.org/licenses/publicdomain/ but I don't really understand this sort of thing so I thought I'd ask for help here. What should I put in the little boxes on the OpenGuides edit form in this situation? Kake P.S. Yes, they are definitely public domain; a friend of mine took them.

3 3

Adverts on the list archives
by Kake L Pugh 19 Jun '07

19 Jun '07

Hello. I think Dom might have asked about this before, but it seems to still be going on. Many of the older openguides-dev list postings are sitting on the interweb with attached adverts. For example: http://lists.openguides.org/mail/openguides-dev/2004-August/000485.html I understand that this is unintentional - could it be fixed, please? (If it's _not_ unintentional, and the ads are necessary to pay for the list archive bandwidth, then I'm sure we can come up with alternative hosting between us all.) Kake

3 3

Summary field in atom/rss index
by Kake L Pugh 18 Jun '07

18 Jun '07

Hello. At the moment, when you ask for an atom feed of the entire site, it looks something like this: <entry> <title>Adam And Eve, SW1H 9EX</title> [...] <summary>Add Category Real Ale to GBG pubs. [AutoKake]</summary> <updated>2007-05-04T17:46:28+01:00</updated> <author><name>AutoKake</name></author> [...] </entry> Since we now have a proper summary field, should we putting its value in here instead of the latest change comment? Kake

4 8

Category_Locales
by Thomas Klausner 15 Jun '07

15 Jun '07

Hi! I'm currently working on bringing vienna.openguides.org back to life (for YAPC::Europe, among other things...). Thanks to Kake and Bob for their support... Now, I've got a small problem: This page http://vienna.openguides.org/wiki.cgi?Category_Locales doesn't seem to work right when compared to eg this page http://london.openguides.org/index.cgi?Category_Locales I'm missing the "View all pages in Category Locales" link. Was there a problem during the import of the old data, or did I damage something? Thanks! -- #!/usr/bin/perl http://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

2 1

Round-up from Summer 2007 Hackfest
by Dominic Hargreaves 14 Jun '07

14 Jun '07

Hello, I write from the train back to Oxford towards the end of the second day of our hackfest, and I'm very excited about what we've achieved. It probably doesn't look like much from the casual observer, since it's been entirely been unglamarous bugfixing, rather than enhancements, but I believe we've gone a long way towards escaping from the endless stream of dull bugs to fix. Aside from the obvious benefit of having fewer bugs, being able to clear the air (and the bugtracking system) will allow us to refocus on further development. What we've done is looked at every single outstanding bug (defect in trac parlance) in OpenGuides and discussed what needs to happen with it around the table, and commented on the ticket. With a few exceptions, we've then assigned the bug to someone with an agreed path towards fixing the bug. Some of those bugs have now been resolved, and some of them are still pending fixes. You can see the latter at http://dev.openguides.org/report/13 and http://www.wiki-toolkit.org/report/9 We hope to repeat the hackfest sometime before YAPC::Europe, with a view to ironing out any remaining bugs, and reviewing all the many enhancement requests (you can see those at http://dev.openguides.org/report/12 ). Stay tuned for more details about the next hackfest. Thanks must go to Kake for organising and hosting the hackfest. The format seemed to work really well and we managed to stay "on-topic" (bugfixing). Thanks also to those new faces who've helped bring a fresh outlook to the project (andrewb, ilmari, pfig, and klur) and of course to everyone else, for their contributions. I plan to make a new release of OpenGuides (and probably Wiki::Toolkit) in around a week's time, to push out all the fixes. I'll prod people who have assigned tickets at that stage, so that I don't miss out any work that is soon to appear. http://www.wiki-toolkit.org/report/9 That's all for now, as my interchange station is fast approaching and there's still nearly a whole cup of tea to drink. All the best, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

2 2

Bug #222 -- Node Image Metadata
by Chris Prather 14 Jun '07

14 Jun '07

Hi, Kake and I were discussing node_image data on IRC and it led to her submitting bug #222 (http://dev.openguides.org/ticket/222). Basically the Node image isn't really metadata and having it included in the vcard div makes for ugly layout. So I've moved it out to live next to the Map link (which in my mind is a similar concept and visually looks appealing). I have attached patches to the relevant templates in the bug. Now that the work is done, the question is ... is this the right way? Anybody else have an opinion? -Chris

3 2

OpenGuides Plug in Talis Podcast
by Tom Heath 13 Jun '07

13 Jun '07

Hi folks, Thought you might like to know that I managed to get a good plug in for the OpenGuides and the OG RDF support in this podcast with Talis I did yesterday: http://talk.talis.com/archives/2007/06/tom_heath_talks.html Of course the whole thing is riveting ;) but if you just want to hear the OG bit then it comes up at about 56m50sec. Seriously though, if you're wondering why the OGs bother to expose RDF, and what benefits this (and the wider web of data) can bring, then you may find the rest of the podcast interesting. A discussion of web2.0-style APIs compared to RDF starts around 28m40s. Tom.

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
71
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

OpenGuides-Dev