mirror_corosync/AUTHORS
Fabio M. Di Nitto 20a5289074 drop evs service
there are several reasons for this:

1) evs is only partially implemented with no plans to complete it

typedef enum {
       EVS_TYPE_UNORDERED, /* not implemented */
       EVS_TYPE_FIFO,          /* same as agreed */
       EVS_TYPE_AGREED,
       EVS_TYPE_SAFE           /* not implemented */
} evs_guarantee_t;

2) evs has no users in any upstream distribution and no search
   engine can find any other upstream using it.

3) the only reason (I was told) to carry around evs was that evs
   receives the full ring_id struct from totem. This is only
   partially correct because while the structures are prepared
   to carry around those data, they are never transmitted from
   corosync engine down the IPC line to the user.
   CPG ring_id contains the exact same information and it's
   actually less buggy (due to prototying of the info).

worst case scenario where a user really absolutely need libevs,
it can be easily reimplemented as libcpg wrapper and avoid
lots of code duplication.

Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
Reviewed-by: Steven Dake <sdake@redhat.com>
2012-03-12 15:51:50 +01:00

25 lines
1.0 KiB
Plaintext

Last Updated Dec 2009
Main Developers
---------------
Steven Dake Maintainer, totem implementation, cfg,
logsys, service engine architecture, ipc system
poll, timers, objdb, hdb, sync, coroapi
Christine Caulfield cpg, cfg, quorum, confdb, totem ipv6 support, totem NSS
support
Fabien Thomas OS portability, BSD port
Hans Feldt logging inspiration
Angus Salkeld objdb, static code analysis cleanup, statistics
Lon Hohberger logsys
Fabio Di Nitto automake, pkgconfig, logsys, config, distro release
Jim Meyering automake, sanitizing APIs, warnings removal
Andrew Beekhof automake, integration with Pacemaker
Dave Teigland cpg specification, integration with cluster3
Jan Friesse cpg, sam
Jérôme Flesch BSD portability
Significant credit belongs in our large vibrant community members, who are
unfortunately too numerous to list. Your tireless effort in testing, deploying,
and providing bug reports of our community driven software model shows that
open source can make a difference and produces better software.