On 1/22/2010 6:20 PM, jida...@jidanni.org wrote:
> Anyway, I bet 99% of software written ends up unused. So one is lucky to
> get some users in the first place. And making it Free will make that 99%
> into a 98%... I.e., in the end one ends up begging for users before
> finally abandoning the proje
Anyway, I bet 99% of software written ends up unused. So one is lucky to
get some users in the first place. And making it Free will make that 99%
into a 98%... I.e., in the end one ends up begging for users before
finally abandoning the project, so no need to put one more stumbling
block ($) in the
Giuseppe Briotti wrote:
> Hi all, hi Bernard... probably, my response is a bit late, but I spent
> time reading (hopefully!) carefully all the answers...
>
> Thus, my 0,02$:
>
> I think that probably the correct question is: "Please convince me to
> make my business model" :-)
>
> I agree with oth
Domas Mituzas wrote:
> Hi Bernard,
>
> I think you should go entirely closed-source, and close yourself up in a
> bunker without internet.
> I just thought you may want to hear another opinion.
>
> Domas
Domas, this will come to a different stage. What happened to me was
abuse of my positive tru
Hi all, hi Bernard... probably, my response is a bit late, but I spent
time reading (hopefully!) carefully all the answers...
Thus, my 0,02$:
I think that probably the correct question is: "Please convince me to
make my business model" :-)
I agree with others that probably, the SaaS business mod
On 1/21/2010 3:03 PM, Madison Kelly wrote:
> Domas Mituzas wrote:
>> Hi!
>>
>>>We, as members of the open source community, would do well to wish
>>> him luck. Every one of us reflects the community, and snarky remarks
>>> make the community look childish. I would have preferred it become open
Domas Mituzas wrote:
> Hi!
>
>> We, as members of the open source community, would do well to wish
>> him luck. Every one of us reflects the community, and snarky remarks
>> make the community look childish. I would have preferred it become open
>> source; Not because I plan to use it but bec
Hi!
> We, as members of the open source community, would do well to wish
> him luck. Every one of us reflects the community, and snarky remarks
> make the community look childish. I would have preferred it become open
> source; Not because I plan to use it but because I want the community to
Domas Mituzas wrote:
> Hi Bernard,
>
> I think you should go entirely closed-source, and close yourself up in a
> bunker without internet.
> I just thought you may want to hear another opinion.
>
> Domas
Domas,
Having run a business myself for >10 years, I can understand where
Bernard is
Hi Bernard,
I think you should go entirely closed-source, and close yourself up in a bunker
without internet.
I just thought you may want to hear another opinion.
Domas
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimed
Hy Platonics,
Thank you very much for your reply. I have used you reply to create a
new thread "Please convince me to make my software open source (3)"
Your contribution is very valuable to me to me for making this important
decision.
With regard Bernard
Platonides wrote:
> Bernard wrote:
>
Thanks again for your reply.
*Summery of my question* :
My conditions are :
*I decide if I make Wikibox Blue Open source
*I decide when Wikibox Blue will be Open source
*I decide on which conditions Wikibox Blue will be open source.
The software is used as SAAS, designed by me and developed by
p
Bernard wrote:
> Or a competitor can create the same kind of
> SAAS solution but more cheap because I have the costs, and the
> competitor the profit.
If the competitor doesn't innovate, he will be just copying your
version, unable to provide the new features the client wants.
> Credits
> If I
E.g., I write a program to crack the AIDS virus. If it is open source,
the virus gets cracked earlier, and I am a hero and get lots of chicks.
Even if it is not me at the helm when the final solution is reached, it
would be a lot more fun than Noname Schleeb at Nurdsburg Laboratories,
who wouldn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> So its boils down to me :
> *Is a Open Source license solid, reliable.
Yes
> *Do I really get the credits.
You will always own the copyright of your work unless you hand it over.
Offering your code under an Open Source license is not giving tha
bern...@bernardhulsman.nl wrote:
> Thank you for all your responce on my previous thread. There were very
> valuable to me. Most of all I do like you all respected my conditions.
> There was even a responce to warn me I should not make my propriety
> software Open Source because then I could not
Thank you for all your responce on my previous thread. There were very
valuable to me. Most of all I do like you all respected my conditions.
There was even a responce to warn me I should not make my propriety
software Open Source because then I could not earn any money
from my extension. That ki
Boris Steipe wrote:
> But that is exactly what I meant (sorry if I was oblique). In this
> case the business is not based on selling the code. Therefore there
> are no downsides to open-sourcing the code, and many tangible
> advantages, not only altruism.
> B.
>
Boris, my model is a SAAS m
But that is exactly what I meant (sorry if I was oblique). In this
case the business is not based on selling the code. Therefore there
are no downsides to open-sourcing the code, and many tangible
advantages, not only altruism.
B.
On 18-Jan-10, at 2:22 PM, bern...@bernardhulsman.nl wrote:
>
Ryan Lane wrote:
>> You really shouldn't make it open source. If your business model at all
>> involves making money directly off these extensions, then open-sourcing
>> it will remove any barrier whatsoever to people paying you for them.
>> It's simply absurd.
>>
>>
>
> All of my extensions
Boris Steipe wrote:
> In my area of work (bioinformatics) I have not seen convincing
> business models that were based on charging for code. Integration,
> customization, consulting - yes, it needs a lot of expertise to get
> that right and people are willing to pay for that expertise.
> Co
In my area of work (bioinformatics) I have not seen convincing
business models that were based on charging for code. Integration,
customization, consulting - yes, it needs a lot of expertise to get
that right and people are willing to pay for that expertise.
Contributing to the open-source
> You really shouldn't make it open source. If your business model at all
> involves making money directly off these extensions, then open-sourcing
> it will remove any barrier whatsoever to people paying you for them.
> It's simply absurd.
>
All of my extensions are open source. I have made mone
Kurt M. Weber wrote:
> bern...@bernardhulsman.nl wrote:
>
>> We have build many extensions to improve the functionality of MediaWiki.
>> It is for
>> Enterprise use as Knowledge management infrastructure. The name of the
>> extensions and additional
>> functionality is Wikibox Blue. The softwa
> Boris. Thanks. That is indeed a good argument. But then I must be able
> to show that my expertise is indeed my expertise. My company is
> Wikiation. The bundle extensions is named Wikibox Blue. The copyright is
> and should stay mine!. That is. It can be GPL or an other Open Source
> license wh
> My question is here : Please convince me I have to make my propriety
> software open source.
>
You don't have to make it open source. I won't try to convince you
that you need to. I will, on the other hand, try to convince you that
you should open source it.
1. If your extensions are really nic
Boris Steipe wrote:
> Also: in the information-based economy, an increasingly important
> part of the revenue of your activities is "mind-share". No better way
> to demonstrate your expertise to the world than to contribute
> something useful.
> B.
>
Boris. Thanks. That is indeed a good ar
bern...@bernardhulsman.nl wrote:
> We have build many extensions to improve the functionality of MediaWiki.
> It is for
> Enterprise use as Knowledge management infrastructure. The name of the
> extensions and additional
> functionality is Wikibox Blue. The software is propriety.
>
> It can be ho
Also: in the information-based economy, an increasingly important
part of the revenue of your activities is "mind-share". No better way
to demonstrate your expertise to the world than to contribute
something useful.
B.
On 18-Jan-10, at 11:46 AM, Robert Cummings wrote:
> Hi Bernard,
>
> By
Magnus Manske wrote:
> On Mon, Jan 18, 2010 at 4:45 PM, P. Mazart wrote:
>
>> Hello Bernard,
>>
>> Am Montag, 18. Januar 2010 schrieb bern...@bernardhulsman.nl:
>>
>>> We have build many extensions to improve the functionality of MediaWiki.
>>>
>> Mediawiki is under the GPL, so if y
P. Mazart wrote:
> Hello Bernard,
>
> Am Montag, 18. Januar 2010 schrieb bern...@bernardhulsman.nl:
>> We have build many extensions to improve the functionality of MediaWiki.
>
> Mediawiki is under the GPL, so if you have done any changes to MW
> you will have to release them under the GPL, too.
On Mon, Jan 18, 2010 at 4:45 PM, P. Mazart wrote:
> Hello Bernard,
>
> Am Montag, 18. Januar 2010 schrieb bern...@bernardhulsman.nl:
>> We have build many extensions to improve the functionality of MediaWiki.
>
> Mediawiki is under the GPL, so if you have done any changes to MW
> you will have to
Hi Bernard,
By open-sourcing your work the community gains from your work; however,
this generally forms a positive reciprocity loop whereby the community
will feed back into your contributions with their own enhancements,
ideas, and bug fixes from which you will then benefit.
Cheers,
Rob.
b
Hello Bernard,
Am Montag, 18. Januar 2010 schrieb bern...@bernardhulsman.nl:
> We have build many extensions to improve the functionality of MediaWiki.
Mediawiki is under the GPL, so if you have done any changes to MW
you will have to release them under the GPL, too.
In some points OpenSource ≠
Dear Bernard,
It's hard for senior executives to imagine a world where their company could
lose control, Wikinomics book by Dan Tapscott ans Anthony Williams say, but
it's just what we live for: making the world a better place and things
easier for all. Please, consider making your property sofware
We have build many extensions to improve the functionality of MediaWiki.
It is for
Enterprise use as Knowledge management infrastructure. The name of the
extensions and additional
functionality is Wikibox Blue. The software is propriety.
It can be hosted as SAAS
Today there has been a request i
36 matches
Mail list logo
