Report from the Hephaistos Conference

As you know from previous posts, I’ve attended much of the recently held Hephaistos Conference, and presented there our experience on developping PicoForge and using Shibboleth.

I was glad to see many interesting presentations and talking to all these people interested in Forges, either promoters of the use of forges for specific communities, or developers/maintainers of forge software.

I’d like to report on some of the bits I remember, hoping that others will provide their reports too.

First of all, I think that the organisers have organised a great conference, for a first edition, and the only criticism may be that I would have prefered to be able to talk to more people from Mandriva there, as the conf was held at Mandriva’s building. Too bad… maybe next time.

Several people were present from Public Administrations or institutions related to this sector, who try and promote the use of the libre software model for developments in the public administrations sector : folks from the Adullact’s forge, and Admisource (the official french administration’s one), or the forge of the Junta in Extremadura, and also someone from Sweden, and even a representative of the IDABC program.

Being able to discuss questions of interoperability was the main topic of interest for me. Some elements have been shown like the search facility between partner forges implemented in GForge, and used by the GForges relating to PA projects, for instance (Hephaestos project at Adullact). Recent activity was made around this topic like discussions in the frame of the Overcrowded initiative, and older bits like our proposals for CoopX.

I think we have discussed interesting ideas like using Web 2.0 techniques also in the forges, things like tagging / taxonomy for projects identification / categorisation, maybe.

Some presentations have provided us with interesting perspective on software development and integration basing on J2EE components, and in particular on ObjectWeb’s technology, like what the IRCAD did with xwiki and other tools. Also, using similar technologies were the elements proposed by the LibreSource project. I think they have developped a very interesting tool, which could be a solid basis for building forges of next generation, but whose paths for adoption by projects in the libre software communities remain to be confirmed.

There would be lots of other elements to note, but I must say I don’t remember that much at the present time, and let others contribute in the comments 😉

Last, we mentioned that we (at GET/INT) are hosting a mailing-list which was setup in the frame of the “overcrowded” project, which is meant for improving contacts between people involved in the field of forges, like maintainers of several forge applications. At the moment there are mostly french-speaking people, but we’re inviting all interested parties to join us… and maybe we can continue with discussions in english. You may contact me for more details.

Update 2006/12/09 : the proceedings are on-line : http://www.ethiqa.com/hephaistos/proceedings2006.html

Presentation of Shibboleth integration in PicoForge at Hephaistos Conference

Here are the slides of our presentation of PicoForge and integration in a federation identity with Shibboleth, made at the Hephaistos Conference.

Update 2006/12/09 : the paper is now online, included in the preliminary version of the proceedings of the conf. It’s also available in PDF format.

Presentation of PicoLibre/PicoForge at phpGroupware Conference 2006

Here are the slides of my presentation of PicoLibre / PicoForge made at the phpGroupware Conference 2006.

We tried and emphasize some issues relating to phpGroupware’s architecture in the last slides… but of course, it would be better with the sound 😉

Update 2006/11/10 : I’ve updated the files in order to reflect the latest version, which is the one I presented, with more details on Shibboleth and Subversion in the FileManager.

“beta” PicoLibre/PicoForge Debian packages

Christian has just issued some new PicoLibre/PicoForge packages in order to be able to get more tests on a hopefully much more phpgroupware-compliant code.

Nothing spectacular so far, but a major rewrite of many picolibre modules in phpGroupware, which should easy a lot maintainability (and enhance security).

Next steps :

  • Integration of subversion in addition to CVS in the picolibre-backend, protected through chroot jail, with SSH and LDAP. It’s almost ready and should be in a testable state next week…
  • Integration of TWiki : some bits are almost ready too : we should be able to use a LDAP plugin in TWiki to be able to use the LDAP users and groups of PicoLibre, and a new phpgroupware application is currently being written to allow project’s wikis creation…

I hope that we will be able to test all that on the production platforms at INT and ENST Bretagne soon (before the Hephaistos and phpGroupware confs in november).

For the installation instructions, for the curious : more details in the CVS

RecentChanges in Picolibre…

There have been several recent efforts around Picolibre at INT. Maybe they will attract some interest of the curious ones. We hope they will help enhance phpGroupware quite a bit.

Reminder : more details on what Picolibre is may be found here, but quite old [en] and more recent here [fr].

  • Picolibre packaged for Debian : not really new, as I blogged about that earlier ([fr]), but mostly working for our needs ;). It’s not an official packaging yet, but Picolibre is not meant to fit every system configuration anyway, as it requires pretty much control of all the system (users and groups through LDAP for CVS, etc.)… but who knows, some day, we could make some regular packages and go for official package ?
  • After having made the packaging, Christian is also working on rewriting some PicoLibre components so that they are much more object oriented, and maintainable. Cool ;).
  • Picolibre should fit in a Shibboleth network, to allow single sign-on, as we (actually students doing their internship here) have developped adapters for Shibboleth for phpGroupware. Using these mechanisms we can more easily integrate the platforms with enterprise networks, using external auth sources, and have SSO, as well as integrate several Picolibre platforms : one developer may do single sign-on when working on different projects hosted on different platforms. Next step is to integrate several kinds of platforms, like picolibre, gforge, sf, etc. ? 😉
  • Picolibre may be using soon Subversion (SVN) instead of CVS, which will allow users to get more advanced mechanisms, and another of the students in internship here has been working on integrating the phpgroupware filemanager with SVN. SVN can be accessed as a DAV server, so he added some modifications to be able to manage documents on a versioned DAV server, with this new SVN backend. The goal is to offer users of the platform ways to manage versioned information even if they don’t understand SVN and wouldn’t know how to use it or install its client programs. It may also be useful for the remote user. And using a DAV client on SVN in autocommit mode is pretty interesting too for the average user… wtill being able to access the history through the filemanager. Nice addons to phpgroupware to come when it will be ready.
  • Last thing : one of the students has worked on integration of PicoLibre and TWiki, to be able to offer wikis for the hosted projects in addition to the other tools. It may also use bits of what was done for the shibbolethisation, for managing user mappings between these applications.

That was it : Picolibre is not dead, although most of this work is happening behind the scene, and not everything has been published yet… but we expect to be able to release some of these elements in next phpgroupware versions, and published a new release of PicoLibre in the future. More testing and coding is awaiting us still ;).

I hope we have enough time to document all that also… and maybe submit some articles about that to the Hepahaistos conference ?.