On 05/22/10 14:28, strk wrote:
> Would you ? It's your project, up to you what you want to make of
> it....
I will drop anyone that tells me I can't checkin code to my own
project... Bwy made his decision, you can do what you want. There have
been several times was very tempted to revert changes made by you or
bwy, but I've always managed to resist the temptation. I suggest you do
the same.
> I know you like coding and couldn't for long time being busy with
> fundraising and paperwork and stuff. So what about playing "hacker"
> now rather than "maintainer" ?
Well, when I hack on code, you get pissed off. :-) The funny part of
all of this is I didn't break anything... it's more a matter of
perception than reality.
> The way I see it maintainance is a boring task, give it to someone
> else and focus on the fast and furious development. You could get
> your things done and still be safe that nothing will break cause a
> maintainer will help you / force you not to break things.
Nobody has ever stepped up to help with the multitude of tasks I have
to handle as the maintainer, so I doubt anyone ever will. I've asked
repeatedly for help, and never gotten any, like with buildbot
maintainance. That's an interesting case, as I shut down buildbot as the
testsuite almost *never* passed, and I was the only one fixing all the
problems.
> I'd personally love to have you still in the team. Hopefully this can
> be sorted out with some time.
You have this backwards, I am still on the Gnash team. The issue is
whether you and bwy are...
Anyway, this is the last post I'll make on this thread. I think we've
all insulted each other enough to stop. We all have work to do. My
suggestions for going forward are pretty simple, no personal attacks,
and no threats on reverting anything. We also have to admit we have
different development styles, and to be more tolerant of those differences.
We need to focus on the features end users need if we wish to remain
relevant as a project. Before the next release we need to do a few
things, finish up the ExternalInterface support (I am willing to let
somebody else do it if they're overly sensitive), fix the cookie
problem, improve video performance to drop the cpu load and memory
footprint, and add support for using Lightspark to handle avm2. Let's
aim to make the next Gnash release a 0.9 release.
- rob -
_______________________________________________
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev
