I think this depends. You can't/shouldn't force people into paying a
subscription for open source software. Unless of course, Vic wants to only
distribute binaries only and only do the code editing himself. I think he
would loose tons of users that way. I wonder if there was clear seperation
of tasks, things might work a little better. Who knows.

1. Have people that can beta test (they would need to sign up for it
though).
2. Have a formal way of submitting bug reports. Maybe bugzilla or some
workflow module for Joomla! or Drupal if you are using it.
3. People could actually join the project coding team.
4. Have a group of people talk about the future of JSonar and where it wants
to go/where it currently is.
5. Give credit for all "members of the project". Both on the website and in
the source code.
6. You could have financial sponsors if you wanted. This is where the
subscription plans come into play. Note that nobody is required to be
"sponsors", but those that do could pay a nomonal anual fee of $20 or so. If
you made the sponsor part a minimum of $20 but the people could set their
own price, that would be even better.
7. Find every way to market JSonar.
8. Have someone who could help out with the website (webmaster). I know
website management takes loads of time and resources. Find someone who
already knows the stuff and see if they could help out on the side.

If the project was set up like this, even if it is small at first, it would
go a long way as well as help Vic carry the burden. It would probably lessen
it. This also makes the project easily changable for the future.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Nicki D
Sent: Sunday, August 15, 2010 1:36 AM
To: 'JSonar -- JAWS Scripts for Sonar discussion list'
Subject: Re: [Jsonar] Question for you JSonar developers


I think the time has come for some of us to begin to think how we can help
the JSonar project, especially Vic for all the work and time and equipment
that go in the production of this wonderful product that we use for free and
sometime forget that someone is spending blood, sweat and money to make this
possible for us. Perhaps we can start an annual membership for JSonar.
Something like $20 a year. Individually it is not much but collectively this
could amount to a little something that can help cover some of the expenses
of the things it takes to make Jsonar. I believe we can all afford $20 a
year. So let us think about doing something to help and not always demanding
and requesting at times it seems a bit arrogantly as if the stuff was coming
down from the sky like a gift from God. Of course persons who wish to make
donations can continue to do so in addition to the annual dues. Just a
thought, let's the brainstorm start!

Nicki D
 

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Chris Belle
Sent: Saturday, August 14, 2010 3:19 PM
To: JSonar -- JAWS Scripts for Sonar discussion list
Subject: Re: [Jsonar] Question for you JSonar developers

Maybe Vic would be a little more motivated if a little cash came with that
request 'grin'.

Remember all you folks are geting a free ride, and ct doesn't even support
64 bit yet.


At 05:08 PM 8/14/2010, you wrote:
>Hi Vic and all,
>Yes, this has already been brought up, but I just want an answer to 
>this. CT supports audiosnap and the question is why can't JSonar 
>support that feature? I have been working at a project which I can't 
>finish. It is with a song I have to remix and need to stretch the tempo 
>of that song to follow my projects tempo so that I can add drums and a 
>few other things to
it.
>Please, reply to this.
>Many thanks,
>Christian
>
>
>_______________________________________________
>Find JSonar and Sonar FAQs, articles, guides and downloads at 
>jsonar.org.
>
>Jsonar mailing list
>[email protected] http://jsonar.org/mailman/listinfo/jsonar_jsonar.org




         WARNING!!!

This email could contain innocent phrases which, if taken out of context, or
read from an existing inclination to be hostile, or an overly politically
correct world view could induce cursing, abusive language, or other
indications of less than desirable behavior in a public venue.
No ill will is intended.
The sender takes no responsibility for mis-interpretation or otherwise
extrapolated extended meaning, intent, or purposes implied or imagined from
said phrases.
The receiver of any such email containing such phrases is solely responsible
for good interpretation and intelligent deployment of subsequent responses
to the above communication.


_______________________________________________
Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org.

Jsonar mailing list
[email protected]
http://jsonar.org/mailman/listinfo/jsonar_jsonar.org


_______________________________________________
Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org.

Jsonar mailing list
[email protected]
http://jsonar.org/mailman/listinfo/jsonar_jsonar.org


_______________________________________________
Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org.

Jsonar mailing list
[email protected]
http://jsonar.org/mailman/listinfo/jsonar_jsonar.org

Reply via email to