Actions

From Seeks

Contents 1 Principle 2 Future actions 3 Past actions 3.1 Example of format 4 Failed or cancelled actions 5 Proposals 5.1 Dedicated customized node during a conference 6 See also

Principle

Organize non-technical actions that should be undertaken to

1. improve Seeks understanding,
2. increase its visibility,
3. facilitate contributions.

Technical quality is a pre-requisite, yet it is not sufficient by itself to insure usage beyond a certain very restricted set of users. This might be a problem for a solution that aims to be leveraging social mechanisms. Diffusion should thus be directly studied, understood and corrected over time.

Future actions

• FOSDEM data devroom Feb 5 - 2011 - Brussels
  • beniz

Past actions

To learn what worked and keep it for the upcoming actions, what did not and change.

• Drumbeat Paris, Summer 2010
  • 6x5min presenation in front of less than 10 people
  • feedback?
  • estimated benefits? (number of users?)
  • Taziden
• Drumbeat Madrid, Autumn 2010
  • type?
  • feedback?
  • beniz
• HackWeek, Autumn 2010
  • code production in the same physical location
  • feedback?
  • beniz, dachary, ...?
• Seeks used as an I2L example, Autumn 2010
  • Dachary
• Seeks a Parinux, December 2010
  • taziden
  • tweeted by @seeksproject
• 27C3 Lightning Talks, December 2010
  • Dachary
• How Seeks let you do your Web search at home FOSDEM data devroom, February 2011
  • Emmanuel Benazera

Example of format

• Action name, Date
  • type of presentation, time allocated, number of person present
    • material used (powerpoints, demo, stickers, ...)
  • feedback
    • what was not understood properly
    • what was criticized and questionned
    • what was acclaimed
  • estimated benefits?
    • number of new users
    • quality of contributions
  • contributors present

Failed or cancelled actions

To learn why it did not work and deduce how to correct it.

• CCC 2010
  • official feedback request
  • pas assez connus et pas assez politiques à mon avis. meme pas le p2p.
• nlnet grant

Proposals

Dedicated customized node during a conference

• propose to the public of a conference to do their search through a Seeks node in order to share the result live but also through few statistics at the end of the conference
  • technically modify the gateway (welcome page, a la Google on Firefox) to point to a Seeks node skinned with the colors and the logo of the conference
  • offer a sum-up page so that participants can directly see what other searched and thus benefit first hand from collaboration, what they couldn't have done on their own
  • bootstrap the node with an 'import' using links already gathered by that community for example through the conference wiki
  • potential conferences/events
    • Fosdem
    • Drumbeat
    •  ?
  • suggestion link from the interface
    • allow participants to suggest features, detected bug, etc without requiring technical expertize (or authorization for Redmine/Wiki)
    • project as a distribution of efforts, centralization of ideas, management of contributions

See also

• Why Use Seeks
• Documents