Re: temporal snapshot of cvs source is prepared

[Mojca M. <moj...@gm...>]

On Sat, Feb 12, 2011 at 18:13, Daniel J Sebald wrote:
>
>> When people submit patches to sourceforge (as .diff files):
>
> There are still diff files in distributed source control programs. Can't
> save a whole repository for each bug fix and feature in SourceForge.

There is no need to. I didn't talk about saving the whole repository.

But just as an example ... one could have one main repository and one
repository with patches where each patch would be in its own branch
(until it gets incorporated into main tree or deleted as useless).

People willing to play would just check out the branch with patch they
want to test without having to do anything else at all. Bringing
patches up-to-date and including them into main tree could be 99%
automatic (apart from cases when patches conflict). The other
alternative is to allow users to clone projects, apply the patches in
their personal repositories and submit patches as "pull requests".

But it all takes some expertise from the main developer.

> Looking at other projects
> that have used a distributed source control program would be a good plan.

Probably an extreme case:
    https://github.com/mxcl/homebrew

Almost 1700 forks, 141 pull requests.

Mojca