Blanking sheet (was: Re: [jox] Chaos or transparency?)
- From: Stefan Merten <smerten oekonux.de>
- Date: Sun, 30 Jan 2011 12:27:26 +0100
Hi project!
5 days ago Athina Karatzogianni wrote:
Reading this exchange I am wondering whether we can have a new beginning
here, a sort of blank sheet and restart by taking on board only what has
been achieved so far, without any other useless baggage.
Well, I thought about it and after another sleepless night I think
Athina is right here.
I tried to help the journal by having a modern web based solution
which is easy to use for all parties and creates transparency as a
side effect. I really started this a year ago. This approach has been
ignored and is still refused. So it certainly falls in the category of
"other useless baggage".
I agree with Mathieu when he says that it is useful to do what works.
I learned my approach did not work so I finally give up. From my
understanding of peer production it's the maintainer's duty to keep
the project on track and I feel Mathieu is doing this.
I had fun thinking about and proposing a good solution. This is the
type of reward which is in inherent in Selbstentfaltung and so there
are no bitter feelings about the energy I put into this. After all
creation of software is also my job and I really like my job :-) . But
as the saying goes: "If you recognize the horse you mounted is dead,
unmount." I have really enough fields of Selbstentfaltung which will
benefit from this :-) .
I just blanked the sheet insofar as I removed everything which would
have been part of a solution I had in mind. This is good insofar as
exactly these pieces were those which Mathieu regularly stumbled over.
For instance there are no annoying update mails any more when new
submissions are done. Mathieu created the editor log which might be a
good alternative for this.
Since I failed so deeply I feel I can't help with another solution.
Well, Mathieu has all the solutions anyway and so in the end my
support for another solution is not needed. Mathieu has admin rights
in the journal's Plone instance so he can do anything I can. The same
applies to the mailing lists.
The infrastructure for the journal is donated by project Oekonux and
this doesn't change just because I as a member of the journal project
can't help a solution on top of this infrastructure. A result of this
is that I'm of course ready to care about platform problems and if new
Plone products are needed of course I will care about this too (this
needs root access to the server and insofar is special). May be Toni's
solution for instance (however, Toni, please note that this Plone is a
3.x version - not 4).
@Mathieu: Since you appreciate such information here it is: No, I
won't respond to any mail which has any part of a possible solution as
topic.
I'll stay in the project because I'm still interested in the project.
However, I'll step back to the second row and hope that a big
hinderance for success is removed by this step.
Grüße
Stefan