Save the KS Toolkit wiki

From KM4Dev Wiki
Jump to: navigation, search

This is the landing page to organize the work to be done to transfer and update the content of the KStoolkit.

Initiative started by Lucie mid February 2018

Process Log and Updates

Here a rapid chronologic (yyyymmdd most recent log on top) overview of progress with 'Save the KS Toolkit' ==


20180603 Nancy shared on KM4Dev-l: I can share a bit of good financial and operational news. Simone has confirmed that CIAT will finance the move and hosting of the KSToolkit to Civihosting. We are getting the details sorted out. So you can check that off the list as covered. Carl, Sophie and I are supporting the process of the move. (This is just to move it at this point, not to do any major changes as there has not been sufficient energy from anyone to get that going.) Thanks Nancy 20180516 Peter added this paragraph and checks with Davide where we currently stand

People interested in helping out

alphabetically by first name [suggestion: please add your Skype id behind your name if indeed you are on board and interested to work as a group. NOTE: this is not to suggest that Skype would be the collab platform, it is just meant to get in touch quickly and agree on something. Our [1]coordination Skype group is here]

Ideas, suggestions and similar

Merge the KS Toolkit with the KM4Dev wiki

We could re-create the toolkit as a section of this wiki. Similarly to the Discussions and the Members sections, there would be two additional "portals": one for "KS tools" and one for "KS Methods".

Tools and methods would be created and edited through user-friendly forms. Taking advantage of the semantic capabilities of this wiki, they would be categorized by "contexts" and "keywods" similarly to (but more powerfully than) the way they are currently categorized on the KS toolkit. For example (this example is focused on "KS methods"):

  • it would be possible to filter Methods by specific contexts and specific keywords simultaneously;
  • on a Method's page it would be possible to include links to relevant Tools and relevant Discussions;
  • members of KM4Dev who have a profile on this wiki and have contributed to preparing a method's page could be credited on the page with a link to their profile, where there would be links to other contributions of such members, such as discussions in which they participated

See a prototype for Methods:


  • This would allow us to have only one platform to maintain instead of two
  • We gain semantic capabilities (already explained above)
  • We gain user-friendly forms, which makes it easier for non tech-savvy users to edit the toolkit

Disadvantages and things that might get tricky:

  • Migration is a manual process. It will take a lot of work to migrate 400+ pages including tools and methods. User-friendly forms and volunteer editors can help a great amount, however it might make sense to pay for a consultant
  • This wiki has running costs and at the moment we don't have budget for fixing it if it breaks or if it needs an update

Proponent: Davide Piga

Rebuild the KS Toolkit using Google Apps

We could consider turning the toolkit into a Google Site where each tool and each method is documented on a Google Doc instead of a website page. We would lose tagging, but we would gain printable pages and easier maintenance.

At the basis of the toolkit there would be a Google Drive folder which would contain all tools and methods.

Suggested default permissions for the folder and the documents in itwould be "anybody with the link can comment", which means that anyone would be able to suggest changes by simply typing into the documents. Edits, before reflecting in the docs, would have to be approved by admins (just like the "track changes" function).

Proponent: Davide Piga


  1. if we need to migrate again, we can just embed the folder in some other website
  2. thanks to the fact that the toolkit is also a folder, it can be easily taken offline (toolkit on the go)
  3. each tool/method is a collaborative document
  4. it’s generally easier for users to add/edit tools/methods as they would just have to create and edit a google document (possibly starting from a standard template that we would provide to them) instead of editing a wiki (which requires knowledge of wiki syntax and an account on the wiki). Assumption: the vast majority of people have a Google account.

Disadvantages and things that might get tricky:

  1. Migration is a manual process. There are currently 400+ methods/tools on the toolkit. It will take some work, or some money (approximately 30 days for one consultant)

Merge With Existing Toolkits

From Michael Hill When I look at the KS Toolkit, it looks like there is much overlap with: which is part of UNITAR's (United Nation Institute for Training and Research) Learning and Training (and KM) wiki. Perhaps rather than rebuilding you can link to what they've already done, and eventually seek a partnership with their KM folks. Their KM repository is even bigger than the toolkit. You can go to the repository by clicking on the KM link on the menu bar toward the top right of the Toolkit page.

We considered building something like UNITAR's page, after we found it we just point our students there instead.

Other options to be explored Nancy offers to explore this option (14/3/2018)

Feature Ideas

  • From Tina: For changes:

- it would be great to have an easy way in the future to differentiate languages (other than english), in my case spanish. - it would be great to have a living "organizational support page". There are two types of supporters: the big ones caring about the whole thing, smaller supporters (km for dev. staff/we and organizations). Space and visibility for the second type = may be more content support within our formal working plans.

  • From Krishan (see the larger email) The point is to pick up on how well the KS Toolkit reflects the nature and identity of the Community; I interpret it as ‘How does the Toolkit reflect the different processes we are implementing or the purposes we are addressing’ in KM4Dev. Perhaps an approach to the analysis we did may be a useful way to re-organise the KS Toolkit as we deal with the transfer of 400+ pages reflecting around 180 M&T.
  • From Nancy and Simone

Here is a new option for migrating Wikispaces. I will look into it! [[2]civihosting]

Simone: I agree with what you propose. I think we should do a major clean-up before migrating. Happy to discuss with a smaller group of volunteers. I am / CIAT is also happy to pay for the first hosting year. Best, Simone International Center for Tropical Agriculture (CIAT) Nancy White: Sent: Wednesday, March 21, 2018 4:32 AM To: KM4Dev <> I've briefly looked into this option and I'd say it may be a GREAT option if we simply want to migrate. The hosting fee is $180-240 USD/year depending on volume and the migration is $50-$100 usd. We would still need to pull in some elements so there will be some hand work to do. One of the pluses of this solution is it is much more mobile friendly than Wikispaces - a little extra bonus. If we want to UPDATE the contents, we could do that before or after. I'd suggest at least one clean up before migration to address any major changes/navigation stuff. Then do the detail fiddly bits afterwards. So, I guess this is a proposal! Waving Nancy W


  • Do we need to port over all the old discussions attached to wiki pages. This is more work. (NW - I don't see value in preserving discussions, CJ agree)
  • Do we need to carry over all old revision history for wiki pages. Again more work (CJ - agree with NW not much value in that)
  • Do we prune the Tools section out all together? (CJ seems like we loose something so no)
  • Do we improve pages during the transition (check links, create new crosslinks to new index, work to improve language stuff? - CJ optional page by page)
  • Who registered and pays for the url? (I think we should preserve this and use redirects at the least, if not host the new wiki AT this url - NW)
  • questions raised by Nancy on the KM4Dev-l on 26/2/2018:

As one of the early builders of the toolkit, I feel a motherly ownership and my feeling (not data) is that this was on behalf of KM4Dev. I feel that CIAT via Simone and Sophie at FAO have practiced organizational ownership through significant contributions, so I too, would really like to hear what they would like. I'm following the technical and operational conversations here and elsewhere. I have questions for the core group and the broader community that I would very much like answered here:

1.Where are we financially? I donated all the money that we raised through the very successful Seattle workshop with the request that first money be set aside to pay for community technology infrastructure. I was informed that that was not a lot of money. The rest I THINK was earmarked for the Zimbabwe event, but no one has responded to my questions of exactly where that money went. In fact, I can't seem to find any accounting of the community money. I've contributed several times and I'd sure like to know what happens to the money.

2. What are the voluntary or paid labor implications of any migration? Many of the tech migration suggestions come with the caveat that there is a significant amount of work to be done. I see some hands raised to volunteer, but I also see notes of the amount of consultant time it would take, which I understand as paying someone to do this. If we have no money, what then? If we have money, are we the best people to migrate the toolkit, or is it now a bit irrelevant and there are many other options out there. 3. How do we preserve the URL and linkages? The KStoolkit is linked deeply, far and wide. At the least, we should consider saving the URL (domain registration --> CIAT? Simone?) and doing a redirect page. There is a ton of community capital in that crosslinkage that may be one of the most important legacies of the toolkit. If you look at many other KS toolkits you will find almost ALL of them link back to the as a source and/or reference.

4. What options are we willing to explore and how soon do we decide? There are more options than migrating to wikispaces or Google Drive - but they have not been mentioned here. They are being discussed in the Recent Changes Slack by some of the smartest wiki people in the world. It might be good not to jump to a conclusion too fast while other options are evolving. One of them may even be an option that moves our MediaWiki community wiki AND the KStoolkit to a different wiki platform, etc. We have time. We don't need to rush this decision, right? Thanks for your consideration Nancy W