BHW Community Projects - Read.

i am guessing modes or admin are going to be involved in management of this service? because with great potential comes great responsibility
 
Don't presume you speak for all of us! :)
I'm more than happy to contribute code towards a project without pay, and I'm sure there are other BHW members here who would feel the same!

Good. Then how about you put your actions where your mouth is and start an open source blackhat project without pay - see how many others contribute. Action trumps words and since you 've started the words, let 's see you do the action.

Also, if you 'd ever worked with a big team, you 'd know that this shit does not scale. Try managing all those "contributors" and see how much fun it is.
 
Last edited:
So what kind of project would people be interested in? Keep in mind. We should start with some small tool and work our way up.
 
So what kind of project would people be interested in? Keep in mind. We should start with some small tool and work our way up.
Scrapebox clone with a one click deploy to heroku would be an interesting project.
 
Good. Then how about you put your actions where your mouth is and start an open source blackhat project without pay - see how many others contribute. Action tramps words and since you 've started the words, let 's see you do the action.

Also, if you 'd ever worked with a big team, you 'd know that this shit does not scale. Try managing all those "contributors" and see how much fun it is.

jazzc,
I fully intend to start an open source project myself, but I wanted to gauge public interest first to see if there were any other interested collaborators.

I don't really understand how the open source methodology 'doesn't scale', considering it's used for a number of absolutely massive technology projects, but provided things are managed and handled properly (GitHub for example) projects can be pretty easily handled between multiple offsite developers.

I'm not expecting to get credit for making a suggestion, I'm a developer myself and I'm keen to start these projects, I just wanted to see whether or not I can expect collaboration or not! Ideally, I'd like to start with smaller projects and then once reliable contributors have been identified we could work on bigger projects.

For example, an open source version of SerpBook would be a good initial concept, it could be developed in just a few weeks in PHP, which is used and understood by a lot of us in the community, and would allow for easy deployment for 'newbies' on their own servers. This could easily be developed initially by two or three individuals (hell, one developer and one designer even) and then scaled up with community contributions from there!

EDIT: The staff of BHW have enough on their plate as it is, unless they want to contribute any projects would be developed and maintained by volunteers, not BHW staff.
 
I support the idea of leveraging the massive resources available on this forum. I have project management experience and could help with the organization.
 
I don't really understand how the open source methodology 'doesn't scale', considering it's used for a number of absolutely massive technology projects, but provided things are managed and handled properly (GitHub for example) projects can be pretty easily handled between multiple offsite developers.

It doesn't scale when you try to build one from scratch with "crowd sourcing". Notice how all those massive technology projects all started from a tiny core of developers (usually 1 guy or 1 company).

Why? Because there are a lot of decisions to be made in the beginning. A project isn't about "let 's hit the keyboard". It involves numerous design decisions (not graphic design). The more complex the project, the more important those decisions - try juggling with 20 people to decide without breaking everything apart :)
 
It doesn't scale when you try to build one from scratch with "crowd sourcing". Notice how all those massive technology projects all started from a tiny core of developers (usually 1 guy or 1 company).

Why? Because there are a lot of decisions to be made in the beginning. A project isn't about "let 's hit the keyboard". It involves numerous design decisions (not graphic design). The more complex the project, the more important those decisions - try juggling with 20 people to decide without breaking everything apart :)

This is exactly the problem I see aswell... Especially since we are looking at the creation of tools here to help making money with.
 
Last edited:
It doesn't scale when you try to build one from scratch with "crowd sourcing". Notice how all those massive technology projects all started from a tiny core of developers (usually 1 guy or 1 company).

Why? Because there are a lot of decisions to be made in the beginning. A project isn't about "let 's hit the keyboard". It involves numerous design decisions (not graphic design). The more complex the project, the more important those decisions - try juggling with 20 people to decide without breaking everything apart :)

I'm more than familiar with how open source projects work, I contribute to a couple and I've started one or two myself! :P

At the moment I'm working on product for a pretty huge website, so I understand the requirements involved in starting, developing and managing a project of this size, and you're completely correct. However, I would just like to reiterate again. I've said this a couple of times in this thread but people still keep saying things about how hard it is to 'manage a project with 20+ people', that is not what I would propose we do initially!

My post from a few days ago in this thread sums it up quite well:
For example, an open source version of SerpBook would be a good initial concept, it could be developed in just a few weeks in PHP, which is used and understood by a lot of us in the community, and would allow for easy deployment for 'newbies' on their own servers. This could easily be developed initially by two or three individuals (hell, one developer and one designer even) and then scaled up with community contributions from there!

This is usually how open source projects work, and I would see no issues with the projects functioning this way on BHW. I'm not saying we'll suddenly have a team of 30 people working on one project, I'm saying that we start with a few core developers and build it up from there - exactly the same way thousands of open source projects are started and maintained daily! :)


EDIT:
This is exactly the problem I see aswell... Especially since we are looking at the creation of tools here to help making money with.
I don't really follow your logic here, are you saying that people won't want to contribute time when they could be doing it themselves and making money? Quick clarification would be much appreciated! :)
 
However, I would just like to reiterate again.

There 's no need to, I 've said my opinion and the rest is only action based. Make the open source projects, see if it works out or not, have fun & profit. :)
 
Back
Top