As mentioned in the previous thread, perhaps it is time to fork phpWiki into a new project so that it can grow.
I hate seeing projects fork but, this is a decent one that deserves more TLC than it's getting. Been dead for 9 months!
I can't be a "lead" on this, but, I run phpWiki and would like to see it keep going. If there is an interest in this, please express your desire to contribute to find others who are possibly willing to do this.
If there is enough of us, it will make sense to fork. If not, then it won't.
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using a hacked up 1.3.4 and am also sad to see this project die a slow death. If a fork is on the cards then I'd also like to help out in some way.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running many wikis using several versions of phpwiki. I hacked the code a bit, wrote and hacked some plugins, wrote some themes, etc ... and I'm very sad to see this project dying ...
Let's create a new project using the current CVS to start and list some priorities like authentification, notification, context (like fractal wiki), etc ...
I'm on for a new project !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ummm... Time to review the thread. carstenklapp ( Carsten Klapp ), one of the main contributors to PHPWiki, has not only asked for suggestions, but has also been actively modifying files (see the CVS Checkin Mailing List archive).
Since it would be easy to get CVS access and checkin any changes, what is this need to fork? If the project is quiet, stick your pieces in, call your buddies, and get on it. Forking should only be done when there is a conflict on directions, and I certainly don't see that here. In fact, all of the things mentioned in this thead (Authentication, Notifications, Context, etc) all belong in PHPWiki, and I don't see why we can't start fixing the current project instead of randomly forking.
With some of the original developers still working on the tool, it would be nice if newer developers were willing to contribute to the current effort instead of forking for no perceptible reason.
IMHO,
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I promise to release 1.3.5 this weekend, which will be the nightly build with release notes; honestly, there is just so much to do for the project that it's overwhelming. Kind of amusing, that, considering I wrote the whole project in December 1999 and released it... now there are huge chunks of the code base I haven't even read!
It's also very saddening that we *still* don't have authentication and notification. Several people have stepped up to deliver this, but for one reason or another have never finished their work (mainly, because open source projects are harsh mistresses that you can easily ignore).
I'm going to assess where things are over the weekend. Rest assured, the project is not dead. There are too many cool things in it, and too many cool sites using it, to let that happen.
~swain
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As mentioned in the previous thread, perhaps it is time to fork phpWiki into a new project so that it can grow.
I hate seeing projects fork but, this is a decent one that deserves more TLC than it's getting. Been dead for 9 months!
I can't be a "lead" on this, but, I run phpWiki and would like to see it keep going. If there is an interest in this, please express your desire to contribute to find others who are possibly willing to do this.
If there is enough of us, it will make sense to fork. If not, then it won't.
Cheers
I'm using a hacked up 1.3.4 and am also sad to see this project die a slow death. If a fork is on the cards then I'd also like to help out in some way.
Where has all the interest gone? TikiWiki? Some other wiki engine? MoinMoin?
Do you have a lot of patches to the current CVS PhpWiki to make it worthwhile starting a new project?
What specific code changes or additions do you have in mind, post some patches or ideas here too! :)
Also look at joining the phpwiki-dev mailing list.
Cheers,
Carsten
I'd possibly like to help out. I'd like to create good integration with phpnuke.
Ok.
I'm running many wikis using several versions of phpwiki. I hacked the code a bit, wrote and hacked some plugins, wrote some themes, etc ... and I'm very sad to see this project dying ...
Let's create a new project using the current CVS to start and list some priorities like authentification, notification, context (like fractal wiki), etc ...
I'm on for a new project !
Ummm... Time to review the thread. carstenklapp ( Carsten Klapp ), one of the main contributors to PHPWiki, has not only asked for suggestions, but has also been actively modifying files (see the CVS Checkin Mailing List archive).
Since it would be easy to get CVS access and checkin any changes, what is this need to fork? If the project is quiet, stick your pieces in, call your buddies, and get on it. Forking should only be done when there is a conflict on directions, and I certainly don't see that here. In fact, all of the things mentioned in this thead (Authentication, Notifications, Context, etc) all belong in PHPWiki, and I don't see why we can't start fixing the current project instead of randomly forking.
With some of the original developers still working on the tool, it would be nice if newer developers were willing to contribute to the current effort instead of forking for no perceptible reason.
IMHO,
Michael
Great news !
The fork was a kind of "last chance to have this project working" solution ;)
I gonna check my mods and try to send a cvsdiff to the project leader.
It will be a very good thing to have some more developers on this project ...
It's not dead, it just smells funny.
I promise to release 1.3.5 this weekend, which will be the nightly build with release notes; honestly, there is just so much to do for the project that it's overwhelming. Kind of amusing, that, considering I wrote the whole project in December 1999 and released it... now there are huge chunks of the code base I haven't even read!
It's also very saddening that we *still* don't have authentication and notification. Several people have stepped up to deliver this, but for one reason or another have never finished their work (mainly, because open source projects are harsh mistresses that you can easily ignore).
I'm going to assess where things are over the weekend. Rest assured, the project is not dead. There are too many cool things in it, and too many cool sites using it, to let that happen.
~swain