Eiffel Hub ecosystem

[Jocelyn Fiat]

Hi Eiffel users,

In addition to this group, we are also building http://www.eiffelhub.org/

So far; this is just a default drupal installation, but content will come soon.

In the meantime, you are free to register and start adding content (blog, comments, ...)

And we decided to use http://github.com/ to host any source code.

So you can also look at http://eiffelhub.github.com/

We will communicate more about how we plan to use the web site, github, and this group.

This is not all well defined yet, so don't hesitate to post suggestion.

One of the main goal is to get Eiffel users sharing their Eiffel code, their Eiffel libraries, and then start collaborating on specific libraries.

Thomas Beale suggested to work on a kind of application framework.

We can think of many other goals, such as writing examples, tutorials, documentation, articles about Eiffel, and the various projects around Eiffel.

Don't hesitate to suggest actions, projects, ...

Eiffel Hub is your community, it is an open community for

Eiffel users to share software,questions and experience. EiffelHub is not 
affiliated with any company or individual, and is run by its members. 

To be continued

[Thomas Beale]

Dear all,

the following are my notes from our last f2f meeting in Prague. We had 3h of discussions and created some actions to get started. Obviously the long haul depends on everyone, but in the initial phases I, Jocelyn and I think some others are happy to create some initial structure on the website corresponding to the ideas below.

Community tools

• ACTION # 1 - create Eiffelhub @ googlegroups - Jocelyn [DONE]
  
• ACTION #2 - website - Drupal - Jocelyn to organise move with Berend [DONE]
  
• ACTION #3 - Website basic structure - TB, JF [IN PROGRESS]
  
• home page + mission, vision,
  
• Eiffel registry page
• Eiffelhub library documentation guidelines
• link to issue tracker
• contribution guidelines
• demonstrator
• documentation
  
• platform definition
• blog aggregator
• tools for obtaining code
• apt-get
• Paul-Georges/Olivier - concept = obtain lib, env vars, (node.gs) dependency
  
• EiffelSoftware - new library download concept
• platform component description
  

Github

• ACTION #4 - Request facility - create as 'EiffelHub' project under EiffelHub on Github - Jocelyn
  

Public Relations

• ACTION #5 - FB page, LinkedIn, Google+ => 'EiffelHub" - Laurent
  
• Twitter?
• donations - sponsoring
• explain what donations might be for, how money will be used

EiffelRoom

• copy blogs, articles, eiffel code registry to EiffelHub.org - Group discussion on this before doing anything.
  
• note that articles are already indexed in google, so don't trash them
  

Meeting in the future

• propose e.g. 1 monthly meeting telcon
  

Website committee

• 3 editorial committee - TB, JF, Roger?
  

Governance

• openEHR: governance for part of openEHR that creates specifications - overall charter; terms of reference; change management plan.
• create a governance doc that describes: - TB first draft
  
• what being a 'member' means
• committee structure
• voting rights and procedures
• ...bvss
  

NICE

• ACTION #6 - Ask Joseph / Berend (on board?) TB
  
• about renaming or 'Doing Business As' - tradename
  
• how to get board to resign
• need new board of 3 - probably need at least one US citizen

Final comments

• Howard -
  
• getting software that actually works - knowing where it is;
• high quality 'real' demonstrator app - PHP replacement
• fully built downloadable, like Eclipse

Some more ideas (TB)

• we should have a regular webinar - above I mentioned the idea of a telecon, but how about we organise a short meeting every month for the EiffelHub 'committee' (that's us) but also a webinar where one person presents one idea - it could be their library, a new idea for how to make EiffelHub better, a better installer concept or whatever.
  
• we should 'test-drive' all of the above with our own 'private libraries' that we have never shared (or like me, they are on a public SVN, but I have never explained them to anyone in Eiffel-land) - i.e. let's not try to get 'other' people initially to donate stuff, let's get donation working with one library or tool per person from this organising group (from those who develop software, obviously), and get the basics right for how to describe a new library, how to package it and so on.