The state of DaisyDiff

[Guy Van den Broeck]

Dear DaisyDiff users,

Despite my inactivity, and thanks to many other people, DaisyDiff has been growing steadily in the past 5 years.

I can report that we have:

- 3 releases

- almost 10,000 downloads

- 9 committers

- 50-100 daily views

- a (large?) number of CMSs using DaisyDiff

- a MediaWiki plugin (http://gitorious.org/htmldiff)

- a Drupal plugin (http://drupal.org/project/diff_revision)

- at least 2 forks (https://github.com/nuxeo/daisydiff and https://github.com/gregopet/daisydiff-jquery-ui)

- 105 people who 'starred' the project

- 24 open issues

...so clearly there is a demand for DaisyDIff.

Given how bad a job I am doing at managing/maintaining/promoting this project, I wonder if people feel the need to rethink how this project is run?

People like Kostis, Carsten, etc., would certainly do a better job of being in charge. 

We could have a better system for community involvement and issue tracking than the random contributions that happen now. Instead of accepting spontaneous patches, we could, as a community, decide we want certain features and improve DaisyDiff from release to release, on a schedule.

The people doing the work should get more of the recognition.

The website is terribly outdated and does not promote DaisyDiff well. For example. the page with demo's is broken (https://dev.localwiki.org/Front_Page/_history/13...14 looks like a cool alternative showcase!). and we should maintain a list of all the CMSs that use DaisyDiff.

Would anyone like to step and to take charge of DaisyDIff? Or shall we continue in the same fashion?

Cheers,

Guy

[Kostis Kapelonis]

Hello Guy

I think that Daisydiff needs some direction but there isn't someone
that has enough time and devotion to this (I am also guilty of this).

I have been thinking for some time to do a sweep on open issues and
Wiki pages to clean up things.

As far as the WIKI is concerned what do you have in mind? I can devote
some time for the changes.

As far as issues are concerned I think that at least 2-3 people need
to verify and propose solutions. I don't want to approve patches
that have been tested only by me.

Regarding new features, again they need extensive testing in order to
avoid regressions. I think that users would be really mad if DaisyDiff
1.5 for
example broke things that worked well in 1.1 (despite of any new features)

So in general I am happy as the same fashion goes (the project is in
hibernate) but I will support anybody who wants to take full charge.

Kostis