[kforge-dev] CKAN requirements specification

Mon Jan 21 21:03:41 UTC 2008

Rufus Pollock wrote:
> John Bywater wrote:
>> Just to say that I'm "moving" the product specification for CKAN here:
>> http://desire.appropriatesoftware.net/products/30/
>
> That looks great John. Am I right in assuming this is mainly for your use at the ASF -- I'd prefer to keep using the CKAN trac for tickets and planning etc if that is ok.

No worries. Yes, I expect that CKAN tIckets detailing the requirements
of the CKAN system will continue to be generated on the CKAN Trac.

>> This product has been included within the 'Open Knowledge' collection:
>> http://desire.appropriatesoftware.net/collections/4/
>
> Ditto.

:-) This doesn't seem to have anything to do with CKAN development. Or
does it? Are you collecting open knowledge development stories, or
products that support open knowledge development? Aren't you just
collecting "open knowledge" as such?

>> In terms of process and events, I've just made a general 'Open
>> Knowledge Development' process:
>> http://desire.appropriatesoftware.net/processes/33/
>>
>> Which has just one event at this time (time to register open
knowledge package):
>> http://desire.appropriatesoftware.net/events/85/
>>
>> This event has just one story (register open knowledge package):
>> http://desire.appropriatesoftware.net/stories/84/
>>
>> Which has just one functional requirement (pagination):
>> http://desire.appropriatesoftware.net/requirements/40/
>>
>> The original requirements specification is here:
>> http://knowledgeforge.net/ckan/trac/wiki/RequirementsSpecification
>
> Looks fine but is it possible to keep the requirements on trac (I know desire is much niftier and has its own domain model but do we need that for CKAN as it is ...)

Yes, we are keeping the requirements on the CKAN Trac. Desire doesn't
compete functionally with Trac, but it is complementary and it will
help us make a better CKAN.

(From the standpoint of system development, the Desire system is just
a different way of *writing* Trac tickets. Same for Eternity: from the
standpoint of development, Eternity is just another way of *reading*
Trac tickets. Of course, one adopts other standpoints from time to
time, hence their development.)

>
>> The use cases (with broken link to londonwireless.info) are still here:
>> http://knowledgeforge.net/ckan/trac/wiki/UseCases
>
> Just to say this list has long been deprecated and replaced by the trac tickets so we should definitely not work off this.

Oh that's definitely worth knowing. Can we have "deprecated" at the
top of that page, so no future confusion arises? (....just changed it,
do change it further if you want to....)

Best wishes,

John.

>
> ~rufus
>
>
>

-- 
Appropriate Software Foundation
Registered in England and Wales
17 Chapel Street, Hyde Cheshire
Company number: 04977110
W: appropriatesoftware.net
T: 0870 720 2944
M: 0781 139 2292