Re: [Gnash-dev] Improvements ahead and forking

[Robinson Tryon]

On Tue, May 25, 2010 at 2:23 AM, strk <address@hidden> wrote:
>
> Now I'd like to commit it but dunno where.
>
> Committing to trunk (assuming I still have commit access)
> would not get appropriate review by Benjamin who knows what
> he's doing more than anyone else at this moment.
> Also, I'd incurr the risk of my improvements being thrown away
> by someone not willing to communicate about changes.
>

I don't profess much knowledge of the Gnash development process, but
is it kosher to post patches to the dev list?

If patches can be sent to the dev list, then anyone can post 'em, and
anyone can review/comment on 'em. If the maintainer(s) of Gnash think
they're up to snuff, then they'll get merged.

> Committing to a different branch / fork would make current
> divergence get larger making it harder to ever get back to
> being a single project.

I don't use bazaar much at all, but I assume that one can merge code
from different remotes, like in Git. So what about giving each
developer their own repo and then aggressively merging code, just as
long as it doesn't break anything?

That way, even if some changes don't initially get merged-in, they
wouldn't be completely lost. They'd still be there, ready to be
re-worked and re-submitted for inclusion.

--R