September 20, 2006

BitWise Open Source Thoughts

Posted at September 20, 2006 10:38 PM in BitWise .

I suppose it's time to clarify the bomb dropped several weeks ago by throwing around the words "BitWise Open Source." I do apologize for the lack of a timely followup.

There are a few major factors motiviting this idea. In no particular order:

  • Perceived security would increase due to critical review by the community
  • Availability on additional systems not currently supported (e.g. PPC Linux, BSD variations)
  • Development could be supplemented in the hands of the community
  • The server would be available for use and implementation inside a corporate network

There are some potential or real downsides:

  • Split community as different servers or clients arise
  • Feature creep takes over and bloats BitWise into MSN
  • Integration of the BW protocol into other clients leads to the demise of the actual BW client

Of these, the biggest concern is the lack of a unified community, kind of like the situation with Jabber: too many clietns, too many servers. Jabber could never be the next AIM as a result. The next biggest would the the absorption of BitWise into Trillian, gaim and other similar programs where the BW client itself is abandoned. In that case, what's the point of BitWise?

As for BitWise Professional and the server, the ideal situation that I've come up with would be like the following:

  • By license, BitWise Communications, LLC is the exclusive seller of the server as a hosted service
  • The server could be installed for private/company use at any location with unlimited use, but could not be resold
  • The server could be set up for public free access by anyone wishing to do so, but cannot advertise itself as "the" BitWise
  • Anyone is free to provide support for the server, free or for profit

I think I like the structure that exists in other open source projects, with a non-profit entity controlling the code and for-profit entity that provides a level of support and service. In this case, BitWise Communications, LLC would be the for-profit entity that is the exclusive provider of BitWise as a hosted service, and would, at least initially, retain the "Free BitWise" hosted service as it exists now. All code would become the property of some new non-profit entity.

Again, no decisions have been made. Hopefully with a little more information about the general direction, we can engage you, the community and userbase, in a more meaningful discussion. We open the floor to you.

Comments

Personally, i like BW as it is now. my main concern (and the reason i don't use it more often) is the lack of interest by more "average" users. Jabber has the same problem therefore i don't think going open source will boost the user base (after the initial, probably temporary boost)

I vote for it staying closed, while making it more attractive by adding a couple of wanted features/eye candy.

just my couple cents.

Posted by Luke at September 22, 2006 04:13 PM

Try to modify the client to be Jabber supported, but like googletalk,only can link to your site;and make the server side to jabber server to server communication enabled;offer more services to the user on your site,and provide some not affending URL links (perhaps under HELP menu) to your services.Try to Integrated your services with other web site.

Posted by freeskype at November 5, 2006 10:23 PM
Posting of new comments has been disabled for this post.