in reply to Version control over contributed codes
The flow of sourceforge is 'register as a user', 'file for a new project', and then 'upload files'.
The flow of my idea is that snippets(or just any code) are automatically pushed into the source tree(and you may say it becomes a project). The original author is the project manager, and he can give permissions to others as co-contributors and they can commit to the main branch. Users who are not co-contributors still can create their own local branches. And all changes are visible to the public.
My idea would be more flexible than sourceforge thing. Codes are created everyday and it's sometimes to heavy to call them real projects. Why not just build a big perlmonk contribution tree and let people check out and check in?
This project can also be isolated from perlmonks and built as an independent one. It just needs to mirror the codes and push them into the tree.
Thanks
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Version control over contributed codes
by chromatic (Archbishop) on Sep 19, 2004 at 05:59 UTC | |
|
Re^2: Version control over contributed codes
by Anonymous Monk on Sep 19, 2004 at 06:06 UTC |