Community Development Features...

[Dean C]

Originally Posted by Wayne Luke

Quite simply if you don't like the idea than don't participate. The suggestion was meant to augment the current offerings not replace them. If you don't want someone taking over the project than don't invite anyone to be on your team.

However if you're interested in a more open development environment and willing to create an open project the capabilities should be available here instead of elsewhere.

So let me get this straight, I'm not allowed to participate and express my opinion if it disagrees with you? Last time I checked Wayne this forum is a public one, and anyone can contribute to discussions.

My point stands, change has generally not been embraced here partly due to what I feel has been a misdirected administration, but mainly because of lack of resources.

I think the best thing that could happen is to allow the community to work together on improving the vB.org platform. Have some coders put their money where their mouth is and do the development It's easy for people like you and I to make these suggestions but it's the administration (who have day jobs, and some families) who have to put in the work.

[Floris]

My same arguments still stand .. https://vborg.vbsupport.ru/showthread.php?t=225025 (last few posts where dean basically says the same)

Plus, all that wayne is saying is that if you have no trust in this and dont feel it's worth it, its obviously not to your interest .. so why bother posting ?

[bobster65]

Originally Posted by Dean C

So let me get this straight, I'm not allowed to participate and express my opinion if it disagrees with you? Last time I checked Wayne this forum is a public one, and anyone can contribute to discussions.

Dean, Wayne wasn't talking about you not participating in this discussion, he was saying that if they actually did implement this idea, that you as a coder would have the choice to either do it or just keep doing what you've always done.

[Adrian Schneider]

Originally Posted by Floris

git is the "new thing" apparently ..

Well... it's not really a fad or anything, it's just an alternative to Subversion that is a bit more intuitive and easier to use. I also seem to find GitHub much more modern and usable than SourceForge. Git is distributed, so it's actually possible to set up your own local repositories within a few minutes. Getting coders and designers into the habit of throwing their stuff into version control is very beneficial to the community!

Maybe it's just me, but there are already very good tools and services that perform these tasks... why re-invent the wheel? All vBulletin.org's role needs to be is with distributing these releases, and pointing coders in the right direction who want to help (repository location).

[Dean C]

Originally Posted by bobster65

Dean, Wayne wasn't talking about you not participating in this discussion, he was saying that if they actually did implement this idea, that you as a coder would have the choice to either do it or just keep doing what you've always done.

Apologies then

[Princeton]

I agree that product owners (manager) should have the means to add co-authors - to allow for updates, etc.

An issue that will come up is how will the point system be addressed for co-authors? eg. install count, status titles, etc

With that said, I believe our current system needs a major overhaul - not small tweaks. It's current form lacks extensibility and usability.

[Princeton]

Originally Posted by Wayne Luke

Quite simply if you don't like the idea than don't participate. The suggestion was meant to augment the current offerings not replace them. If you don't want someone taking over the project than don't invite anyone to be on your team.

However if you're interested in a more open development environment and willing to create an open project the capabilities should be available here instead of elsewhere.

Our goal (on vborg) is to educate and make available addons for vbulletin. Product collaboration is not one of our goals - at least it never has been. That's not to say that we will never consider some form of "product collaboration". If anything it may be considered as an additional service to what is already offered.

The problem that I see is that everyone is asking for "extra stuff" but no one has addressed the underlying problem - the existing system confuses and over-complicates.

Let's see ... we currently use the system to:

1. Provide product information
2. Count downloads
3. Count Installs
4. Post inquires
5. Post problems
6. Post bugs
7. Post feedback
8. Post "thank you"
9. Collaborate (not a true collaboration but nevertheless it does exist in some form)
10. Promote - as a form of promotional material
11. etc, etc

Personally, I feel that we need to start segregating similar information. ie bugs, thank you, questions, etc In addition, we need to improve usability for both the visitor and the programmer.

Most visitors just want to download and install. They want to be assured that what they are downloading is worth the time. Good/Bad feedback regarding product will help. They could care less about the hundreds of posts left by others.

Programmers should be encouraged to release more products to the community. We need to create a system that benefits the programmer as well as the visitors. I would go as far as suggesting a system that segregates members (as Premium) who donate to the product owner. Thereby, the owner (product manager) can easily tell who has donated to product.

[Dean C]

Originally Posted by Princeton

Programmers should be encouraged to release more products to the community. We need to create a system that benefits the programmer as well as the visitors. I would go as far as suggesting a system that segregates members (as Premium) who donate to the product owner. Thereby, the owner (product manager) can easily tell who has donated to product.

The problem with premium support is that you will then be indirectly responsible (in donator's eyes) for policing any authors that don't provide enough support to those who pay. I think it's a good idea for honest people but there's a few bad apples around

[Princeton]

Originally Posted by Dean C

The problem with premium support is that you will then be indirectly responsible (in donator's eyes) for policing any authors that don't provide enough support to those who pay. I think it's a good idea for honest people but there's a few bad apples around

I'm not suggesting anything advance ... just something in addition to what we currently offer via the Paypal Donate option we have. For example, if someone donates to one of your "addons" you will be able to see this when visiting your product / replying to post etc. Only you (the product author) will be able to see this - no one else.

the idea is that you can provide better support to those who donate - of course, a smart person would never ignore the others