• View
• Edit
• History
• Print

CoEvolution's future

2010

August

• 23rd
  • lock in read-only Seedea
    • to focus on http://www.innovativ.it while still keeping lessons learned and content usable
  • organized somewhere the past related companies
    • One Technology, Inc. by Aaron Sylvan
      • used Genetic Algorithm (GA) technology, simulating evolution to solve large combinatorics problems.

July

• 21st
  • apply my paradigm (CAEE) to my data (wikis)
    • thus mix and select pages according to EE automatically
      • cf Research
      • also consider mixing with pages
        • between wikis
        • non personal websites
          • rate those

June

• 17th
  • transform the installed Fossil-SCM to a CGI for the innovativit user
  • use innovativ.it to take a fresh start
    • yet while leveraging the work done before
      • but not being limited to it
        • consider sunk costs
        • value
          • LeanThinking
• 8th
  • load files into the Fossil-SCM repository
    • which files?!
  • consider migrating the ToDo lists within Fossil-SCM
• 4th
  • before going crazy on the SCM/RCS/VCS remember
    • John Gall "A complex system that works is invariably found to have evolved from a simple system that worked. The inverse proposition also appears to be true. A complex system designed from scratch never works and cannot be made to work. You have to start over beginning with a working simple system." from Systemantics, Quadrangle 1997
    • Minimum Viable Product (MVP) cf Steve Blank
• 3rd
  • update PIM interface
    • older annotated screenshot
  • create scm project
    1. load Fossil-scm as a CGI
    2. point to it
    3. provide the URL
    4. create structure
       1. seedea.conf
          1. to run as a VM
       2. code
          1. memorization
          2. processing interface
          3. sms interface
          4. build function
          5. research/visualization
          6. seedea/backend
       3. non textual data
          1. research/datasets
  • merge meta ToDo
    • include it directly within the list
      • by definition, nothing can be outside

2009

August

• 1st
  • use Cookbook/EditTemplates for
  • Oimp (see Template)
  • CatArt (see Template)
  • ..?

July

• 28th
  • link http://art.seedea.org/ with general, music, philosophy, technology, business, ...
  • make proper CSS for /pub/css/CatArt.?.css (painting skin) and include the SeedeaOimpInterface.php with the general item (instead of just bubbles, OIMP=bubbles, Art=PaintingColors, X=b, ...)
    • see the Todo section of http://art.seedea.org/ especially on PerGroupCustomizations
• 3rd
  • understand why ?action=graphviz from GraphVizSitemap recipe fails
    • here (locked pages?)
    • on my personal wiki (pages removed by hand?)
  • Check the Toggle recipe
    • asked in the talk page how it can handle headings automatically

June

• 14th
  • associate each project with the appropriate funding source as started with Utopiahanalysis#funding (+estimated budget/cost +targeted public)
    • add Italian incubator (suggested by Paola's father) or Gwenael's cabinet and generally remember that a project isn't "bad" but more likely not targeted appropriately
    • optionally facilitate the generation of submission (outputting a business plan like structure)
  • Host my own GraphViz generator (as the remote one is limited)
    • mail sent, looks like it's an admin bug
  • use Wiki Process to model Seedea (even grossly) including payment system (using Amazon DevPay a simple-to-use online billing and account management service or PayPal) to be able later on to optimize but at least, having a clear view
    • following the discussion with Sylvain during CloudCamp Paris 2009 regarding iThink and Business Process Modeling Notation
    • this was already attempted once in Integration and detailed in Integration

May

• ?

April

• ?

March

• 23rd
  • Generalize (:seedeaoimpinterface:) markup to be able to use it for other internal groups
    • CoEvolution
    • Research
    • Seedea
    • SeedeaCore
    • SeedeaProtected
    • ..?
  • make a "MindMap style" version (Henrique should be interested)
  • make a "global" version, handling entire groups
• 17th
  • check trendhunter RSS but also (more serious) patents trends
• 15th
  • Use Creating mashups on the Google App Engine using Eclipse by Michael Galpin, August 2008 for Content.ToolsPython?
• 14th
  • Test how parallax effect could make a nice visual
  • Make adapters no just for Trac but also for MicrosoftProject, BaseCamp and try to cover most of the major PM platforms
• 11th
  • Update StartGames with the actual games
    • eventually using Projecting HTML Elements on a circle using Javascript by Chanaka
• 10th
  • continue to make simple pages like Integration to replace Integration more internal-oriented pages
    • especially the Inputs pages!
• 8th
  • when moving this ToDo list to trac, include the local per page todo sections
• 7th
  • Consider NLnet Open call for funding
  • Adapt trac visuals thanks to TracInterfaceCustomization and our visuals (especially the logo and the CSS)
• 6th
  • Trying Categories (with [[!Subject]]) instead of (:keywords word, ...:) and eventually blend with delicious API especially for suggestions (but might not work since it's mainly useful for pre-tagged pages)
• 5th
  • prepare cloud testing more seriously (ready for GAE, waiting for 80legs configuration and flexiscale answer)
    • formalize the cloud market auto-selector
  • start the Needs page to potentially integrate it in the whole Seedea process as a drive
    • better RSS client (not just trends for visual, serendipity for new feeds but integrating trends with filtering more news and less oldies)
      • check bscopes
      • check ensembli
    • ?
  • include the improved and cleaned CSS (pMwiki independent) in the visual page
• 3rd
  • Now that AutoComplete works on search, use Tutorial : Auto Completer using Prototype, Script.aculo.us by Michael to make it asynchronous
    • for textarea internal links AutoCompletion generate a dictionary with '[[Oimp', etc...
      • problem, editing the searchbox was ok by providing
    • using a 2-level suggestion box, the first being the entry itself the 2nd being generated suggestions
• 1st
  • learn how getSuggestion from Vimperator work to eventually add Seedea own suggestion mechanism to it and at least implement a JS version in our Search process

February

• 25th
  • consider replacing trac wiki and using the ticket system as a back-end to facilitate real implementation
    • too limited to software or generalist enough?
    • see more creative uses of trac like
      • writer framework
      • trac hacks
• 23rd
  • check LingPipe especially key features like
    • classify text passages by language, character encoding, genre, topic, or sentiment
    • cluster documents by implicit topic and discover significant trends over time
  • add a "I want to invest in this X" feature
    • X=money or action
    • community based innovation
    • eventually try with one of the lab project
  • check how to integrate http://www.bustaname.com/ or similar name generation engines
• 16th
  • check and learn from http://www.developersnippets.com/2009/01/20/60-stunning-scriptaculous-applications/
• 5th
  • method for idea initiator/participant to receive reminder of future tasks to do
    • example for faceface/Paola to auto-motivate them to come back and improve their ideas
    • provide them a control-board to visualize when they started, what has changed, etc...
      • as a way to motivate them to be efficient thanks to obvious visual feedback

January

• 25th
  • Integrate User friendly comic on ideas
• 12th
  • Try YouNoodle : Startup Predictor What will your startup be worth in 3 years?
• 11th
  • Consider Twitting for updates instead of our News page (eventually automatize a bridge/link, there is already an Utopiah twitt feed)
• 10th
  • Add transparency on bubbles based on the last update
  • Eventually for each page, simulate ink become older and thus harder to read (based on font transparency maybe)
• 8th
  • Eventually transform Seedea.SandIdeabox to an easy to subscribe blog to provide potential ideas to investors/wanting project holders

2008

December

• 19th
  • Study Amazon DevPay that "automatically meter [...] usage of AWS services [...] bill them based on the prices [you] set"
  • See how Wikidashboard content in Wikipedia with GM by Augmented Social Cognition from P.A.R.C. can be integrated
• 7th
  • Handling profiles more efficiently (Auth, OpenID, ...)
    • message the user through his profile
      • PageUpage() it and provide an RSS to it
• 6th
  • Re-map the website (like everyday...)

November

• 26th
  • offer a repository of innovation/creativity tools
    • On the model of BioBricks ( http://www.openwetware.org/wiki/Biobricks ) and CreativeCommon visuals ( http://search.creativecommons.org/ ) in order to become the central node of the netword and avoid "yet another creativity tool" effect.
    • Think it about more in the light of the previous writting CognitiveDevelopmentFailure
    • See how it goes with the Strategy, eventually later on check how EACH component/bricks does too
• 24th
  • Make a real authentication system since now we have the meta-module (check when ClickPass will become reliable enough)
    • understand how AuthUserOpenId and OAuth can work with AuthUser for Seedea
    • use (:noaction:) for pages to be displayed but not destinated to the public edition, unlike the others, add a real auth system, keep a noauth sandbox
    • look at RWW login feature for comments (accepting OpenID=AuthUserOpenId, Facebook, ...)
• 23rd
  • re-organize the architecture, the modules and this ToDo
  • Visualization module (to fusion with seedeaoimpinterface2 and redefine as an OptModule)
    • digg (bet on) the nodeas (ideas from Seedea)
    • filter by freshness (remove from the bottom of the list)
      • inverted creation date
      • inverted update date
      • frequency of updates
      • derivative of the frequency of updates
• 16th
  • Add the list of my projects within the strategical scoreboard to stay updated on the progresses
  • Generate an RDF of ideas (before OIMP, OIMP, PIMP, ideal nodea ...)as proposed p89,p165 of Tutorial on the Semantic Web by Ivan Herman, W3C
    • for hypergraph purposes one can try N3 since N3 extends RDF to allow a graph to be a node in a graph.
• 10th
  • Make available Our source code and Our content buttons
• 7th
  • Study if the Wireshark presentation ("Get Wireshark Now - 1.0.4 for Windows" box with just under it "Enriching - your Wireshark experience" box) could be a good template
• 5th
  • Testing the InterMap : Seedea:Seedea.Testing (need to use the .txt file, Site.InterMap didn't work)

October

• 26th
  • setup a proper CVS system (Trac or anything else) to keep up modules and a packaged version of the whole system
• 24th
  • Use EditTemplates (Specify a wiki page or pages to use as a template when a new page is created.) with Oimp.Template and Seedea.SandIdeabox#anchortonewidea
• 21st
  • Add visuals of the perfect integration of Seedea with the Seedea Key within your innovation process (based on #Interactions)
  • Add visuals to the CoEvolution.Packages page, add the "not changing anything" option too (as in before/after).
  • Integrate DI05 and the resulting offline repport?
  • Applied what I learned recently (dynamic visual pmwiki modules) by creating module in Xye.CoEvolutionTools to use
    • the visual strategical Go Board for the Strategy
    • the Cloud TCO for the HostingMatrix
  • Automatize the backup system !
    tar -cvf wiki.time().tar; mailsend(coevo) !
    • start backup 1st based on time span then evolve it to an evolution rate scheduling (high number of modification = backup often, low rate of modification = backup rarely)
    • check pmwiki cookbook before
    • decide about Trac too or eventually Launchpad (hosting and collaboration service for free software projects) or try http://en.wikipedia.org/wiki/Special:Search/Comparison_of
    • correct the dirty php version
• 19th
  • Integrate CoEvolution Ensemble de documents intéressants relatifs au projet to Xye.FormationMaterial
  • Overlay signed comment bubble on a block of text
• 18th
  • make a page called "New to seedea?" that would explain the key components and tell people NOT to be afraid of wikis (basically take users' hand thanks to Xye.FormationMaterial after they decided to take action after reaching the CoEvolution.EntryPoint
• 17th
  • Revert "hacks" from bots commented "revertpostad"
• 14th
  • offer a CIFRE (or equivalent) on "epistemologie evolutionniste assistee par ordinateur"
  • understand the behavior of page2rss (seems to fail on the txt file, probably check the header time and no a diff on content!)
  • eventually build and use our own RSS management system (to increase update time, as key as in finance), top priority feeds would have higher refresh frequencies
• 12th
  • Test Seedea with a classic mobile phone
    • eventually gracefully degrade to a mobile version
    • model : Google Mobile
  • Faire du PERT pour detecter le chemin critique et trouver les taches a ne pas decaler (suggere par Gwenael)
• 11th
  • Ask friends to evaluate/bet-on ideas from the OIMP (without feedback from others, no influence)
    • eventually built on InTrade
• 9th
  • Include (using pmWiki primitive) local todo (like SeedeaKey#ToDo) to this general ToDo
  • Fully integrate tools within our interface in order to stay perfectly focus and interact more easily
    • Seedea.ExternalTools
    • Xye.FormationMaterial
    • Xye.MotivationalSupport
• 7th
  • Design template of possible actions
    • add template on header of OIMP to add preconfigured actions per OIMP (argument as OIMP system ID : system name)
    • generate the list of actions based on Seedea.InputVisualTest "actions as cognitive processes supported by AI"
  • Design a module to generate a specialized instance of Seedea based on the running version, selected data and offer the possibility to install it remotely
    • based on pmWiki (check the existing Recipe)
    • based on another targeted architecture (eventually converter to MediaWiki)
    • possible to rely on the packager generator (for the offline use)
    • possible to rely on the backup tool
    • generated with a specific language
    • build a template
    • test it with "D:\My Documents\My Artwork\Ideas for futur artwork.xml"
• 6th
  • Explore new resources :
    • Ideonomy : the dream of Patrick Gunkel about his website.
• 5th
  • discussion pages are needed.
    • October 05, 2008, at 03:52 PM by faceface - I miss the 'discussion' tab on MW
  • SEEDEAs/E:\\/[[file:\/\/\/E:\/|/g (and also the SEEDEAs/I /We/g)
• 4th
  • once stats over 1 Seedea instance have been establish do it over time (using backups) and have a visual way to study evolution (emergence of nodes, growth, etc...)
• 3rd
  • use profiling tools like Firebug on pages like Seedea.InputVisualTest that take a while to load
  • Add a system to facilitate (to define...) the transition from Small unrefined ideas to OIMP
  • Build a RoadMap derived from
    • this very ToDo list
    • pmWiki the current environment
    • the environment choosen from Seedea.Architecture
• 2nd
  • consider a pmWiki->WikiMedia migration (after few discussions on #mediawiki and the possible non realistic GraphDB option)
  • Explore new resources :
    • Le pouvoir (et les difficultés) de la cocréation atelier sur “la puissance de la cocréation”, organisé par le Centre européen pour l’économie de l’expérience et le “cabinet de cocréation” Favela Fabric à Picnic par InternetActu.net
• 1st
  • Explore new resources :
    • Is Anything Ever New? Considering Emergence by James P. Crutchfield

September

• 30th
  • Explore new resources :
    • Smart World by Richard Ogle (and its "Further Reading")
    • Homo sapiens technologicus by Michel Puech
  • Use tools like Intrade for the valuation of ideas
    • updated SeedeaProtected.Secretingredient reflect this ;)
• 28th
  • Build statistics of efficiency based on previous result (before/after Seedea) but also based on Site.AllRecentChanges and Content.Seedealiveprogresses
  • Improve the display of the "Team" box in the current OIMP
  • Add keywords (tag cloud?) per idea (eventually use the (:keyword:) feature
• 26th
  • update or reorganize
    • Entrypoint
    • Seedea.Seedea
    • Menu
    • index
  • Print business cards
  • import from old Seedea.Seedea page
    • integrate "Seedea fitness" from GoogleDoc
    • network-walker to navigate between ideas
    • embedded statistics
    • idea refinement tools/methods
• 25th
  • Scan pages for references and extract their DOI to build DOI links
• 22nd
  • Add Seedea to the list of software that supports DataPortability in Wikipedia (see promotion/marketing page)
  • xxx fill this gap ! (work done during the US/EU transition)
  • integrate all the work done in the US
• 21st
  • Bind SMS to pmWiki?
  • Create a Co-Evo.net email redirection for email
  • Start visual interface seriously in order to be able to present the project
  • Clarify architecture to facilitate the update of robots (API)
  • add notes on Beautiful Code
• 20th
  • study DOI to eventually use it to refer to individual ideas (or HANDLE.NET FAQs assign your digital content unique identifiers, not just identify the objects by their locations) and with eventually Google Protocol Buffers : a flexible, efficient, automated mechanism for serializing structured data
  • decide on licenses
    • for data (CC so far)
    • private data (? so far)
    • whole solution (GNU Affero General Public License ?)
• 16th
  • Use Pipes (like Meta Search Alerts) to allow user for quick news following on their own idea name
  • Use APIs (like http://www.picnik.com/|PicNik]] based on FlickR) to allow visual primary representations based on keyword
  • Use APIs (like RSS or Twit) to allow to follow ideas "lifelines"
  • Use APIs (like GooglePatent to automatically find the state of the art (To move to Seedea.optmodules)
  • Evaluate the possibility of having a pmWiki compatible with DataPortability and eventually adapt of switch to a better platform (evaluation criterion : connectivity)
  • To move to Seedea.Todo : pmWiki based prototype, economy-based seedea based on pmWiki, IMified wiki, Live notes from AI94 in Palo Alto, Method, quality of an idea, Improvements for Seedea, Watermarking
  • To move to Seedea.optmodules : Seamless communication, e-resources (intangible economy resources) pool, Functionnalities emergence detector, Visual AI awareness, Build RSS flux for trend watching
  • add help on the search functionality
  • build a tool to mine LinkedIn for Xye.Targetmarket (find "friends" corporation of one to another)
    • also use it to find my contacts' companies and evaluate their potential as partners
• 15th
  • use pmWikiEditor (Python based) to have a better edition tool AND to learn how to query pmWiki? for mobile clients (especially since SMS/IM handlers are ready)
• 12th
  • Check prototype JavaScript framework (eventually script.aculo.us too
• 10th
  • key innovations of Seedea and what competitive advantage does it provide? (for communication)
  • research on wiki and the organization of knowledge
    • best practices?
    • tools?
    • ongoing projects?
    • how to get peer review for my own wiki?
• 9th
  • organize ->this , aka the to do list (a la Trac? Actually using Trac?)
    • offer a feature-ticket for users
    • put priorities on tasks with visual symbols
    • make test-case for test-driven feature dev
    • implement Agile/Scrum directly on this
• 8th
  • import the related ideas from Seedea.SandIdeabox

August

• 25th
  • Add the author to all projects
  • Add the licenses to all PIMP projects
  • Integrate ALL the work made in the US
  • Add the "share with friends" tool (delicious, StumbleUpon or email)
• 19th
  • ask external feedback from people in the cafe
  • share the OIMP#SocialAnnotating with the presenter from AI #94
• 14th
  • make the visual from CoEvolution.CoEvolution animated
  • make visual for the Mutation/Selection loop too (cf drawing from the 31/07/08 of the Examination Blue Book)
  • fusion the 2
  • redo the introduction with logos

meta ToDo

• order only by priority
• then ordered by required components recursively
• cut in blocks of X days
• draw the schedule
• start it

SCRUM InTake powered

1. use Intake.net/InklingMarkets.com API to input each as an item and ask best friends to vote on it (then potential clients, etc...)
   1. need to integrate it nicely and avoid logging requirements (lower resistance)
   2. people who voted on a now popular functionality (measured by usage, eventually ActionLog based stats) get higher points to vote

To integrate

• Content.Seedea-methodology