[okfn-help] KForge community development

[John Bywater]

Hi Rufus,

Thanks for your comments! As no objections have been raised, and some
time has gone by, there appears to be some consensus on this list for
the proposals...

Perhaps now it would make good sense to try to broaden the consensus (in
particular, on the club proposal) to include the members of the
okfn-discuss list? Also the OKF working groups, since they might use
knowledgeforge.net? And the OKF board might like to know/object/consent.

>> 1. Merge the kforge-dev and kforge-user lists.

Let's schedule IRC time to decide and act on these lists?


>> 2. Encourage a thread on okfn-help regarding KForge community development.
> 
> +1. I suggest that this will work best once we have done 5.

Sure...


>> 3. Propose and build consensus on an incremental and iterative process
>> of encouraging other sponsors to invest.
>>
>> In respect of Task 3, I also propose:
>>
>> 4. To establish a software club [1] for KForge (and perhaps other Open
>> Knowledge software), to be called "KForge Club" (or perhaps "Open
>> Knowledge Software Club") [2].
>>
>> 5. To write an initial prospectus of proposals of the club, to provide a
>> statement of the proposed work, the desired benefits, the expected
>> costs, and the reporting of activity.
> 
> Great. I would note we already have (though not updated for a while):
> 
> <http://www.okfn.org/kforge/>
> <http://www.knowledgeforge.net/kforge/trac/>

Yes, doing the next milestone is certainly one good proposition. :-)
<http://www.knowledgeforge.net/kforge/trac/query?status=assigned&status=new&status=reopened&group=status&milestone=v1.0b>

BTW, the KForge Trac CSS isn't being served ATM, so there are no styles.
404 Not Found <http://www.knowledgeforge.net/trac/css/trac.css>

> 
>> 6. To identify and approach the existing KForge (and perhaps the broader
>> Open Knowledge) community, to solicit further proposals for KForge
>> development, and to solicit cash (and in-kind) contributions to the club.
> 
> Sounds great. I think developers and bug-reporters could be as
> valuable as those becoming "paying-members" of the club.

Absolutely.

> 
>> 7. To repeat proposed tasks 5. and 6. each quarter, according to the
>> Operational Cycle for Software Clubs [3].
> 
> Might make sense to put this bi-yearly but quarterly seems good at the start.

Indeed it might.

Best wishes,

John.