XOOPS: Watching a great project fall apart

[doctormo at gmail.com (Martin Owens)]

Be the change you wish to see in the world;

But also assume command, you've got indignation, just fight the devs
directly and don't be concerned with what ever assumed power they
think they have. eventually all poisonous people must be removed from
projects.

If it comes to it a coop will work too, it is open source. post to the
list that your going to knife and fork (cut and run and start a new
project) with the expressed aimed of replacing this corrupt swine's
who run the show at the moment. the existing developers are welcome to
join in when they agree to the pre set rules of dealing with people
and patches from people.

I'd also recommend watching googles guide to poisonous people in open
source software development. it contains very good information.

Good luck,

Regards, Martin

On 17/04/07, Mark Richards <mark.richards at massmicro.com> wrote:
> Eric C wrote:
> > "Everything dies as they say.
>
> This nearly happened over at busybox when a former maintainer had a
> dispute with busybox's creator which then expanded into an ego-infested
> flame war which had a severely discouraging impact.
>
> Fortunately the new chief maintainer is a balanced fellow who, like his
> predecessors, wants to do it right, just with less ego.
>
> I think it's important to have a central person who encourages others
> and helps keep things focused.
>
> All of these good products come from a need.  If the need is gone, or
> waning, I can understand how interest in maintaining something might
> dwindle, however.
>
>
> /m
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.