how to build up the library..

[Jesse Phillips]

Regan Heath Wrote:

> That's just it however, I am not generous enough with my time to be of use  
> to you/D/phobos.  I spend my free time doing other things, and not working  
> on the code I have which could be of use.  I suspect there are quite a  
> number of people out there who are just like me.  People who have some  
> code which may be of use, in varying degrees of completeness from just an  
> idea to a pretty much complete re-usable library which just needs the  
> final touches etc.

The problem is as you say, there are many out there like you. Even if some people take the rule of getting these polished, they couldn't keep up. Finding these people his hard.

> The size of a contribution for phobos is (one complete module) whereas in  
> many open source projects you can contribute as little as a line of  
> code/fix for a problem.  The goal of this idea is to lower the bar for  
> "contributions" and "contributors" to include more people and more code  
> until even very small ideas/examples may eventually contribute to the  
> whole if only indirectly.

Contributions can be of any size. You don't even need to use Git/pull requests. Just attach a diff to a bug in BugZilla. And these changes don't go throw the formal review, just those with Phobos repo access.

What you are looking for is Dsource, or Github, or any other source repository. You place your code up on the web and license it under Boost, someone can modify it for Phobos.

But the problem is, organizing all of them. People don't have interest in placing projects on Dsource anymore because it can't be organized well and it is relies on one person to update the software. So people go else where, but they don't want to take the time to manage what their project does over on Wiki4D, so someone else does it but isn't informed when updates need made.

So please keep writing software for yourself. Choose an appropriate license for how you feel it should be used and do what you do.