Contrast between Community Weaver 3 and present system

For more information about Community Weaver 3, go here to read the inspiring story of how it was developed. Here is everything you need to know about community weaver

I have listed the challenges that BACE is facing below, and shown how Community Weaver 3 can address those challenges.

Challenge: Currently there are only three people who attend meetings-AZ, Carl, and Ohana. They are all very busy and don’t have the time needed to do the work that is needed to move forward.

Solution: Using Community Weaver 3 would make it easier for people to once again do exchanges, thus increasing the usefulness and vibrancy of BACE. People might be more willing to step up to the plate and be in leadership roles.

Challenge: Lots of problems in the user interface.

Solution: According to Time Banks USA, after decades of working on this, they finally have found a solution! “Like all Timebanking endeavors, it has been a labor of love, streaming from the hearts of coordinators who stepped up to give their honest and passionate input and their ultimate wisdom from the field. TimeBanks USA teamed these leaders with software developer Kent Davidson, who created CW 3 with the stability and adaptability to propel the Timebank Movement forward into our bright future. We are so excited that CW 3 is now a reality!

Challenge: Usage of the time bank has diminished drastically since the last software update.

Solution: By simply using the Community Weaver 3, people may be willing to get involved again since it is so much easier to use and more effective. Read this article for the amazing list of advantages that Community Weaver offers.

Challenge: No members right now have the skills to do developing

Solution: Community Weaver 3 is already developed! No need for developers.. However, since this is an open source software, we can play a part in making CW3 even better.

Challenge: The platform is not user friendly.

Solution: after years of research, coordinators and the software engineer figured out all the challenges. This is what they say: “Community Weaver 3 is streamlined, smart, and nimble. Members will love the simplicity and responsiveness of their pages, will find it all at the click of a mouse, and they can quickly get down to building community in earnest. We are already getting rave reviews from our test sites in , PA and NOLA TB in Louisiana, and we are gearing up for a smooth transition for TB’s ready for the switch.” (this was about a year ago. Now all the time banks are getting on Community Weaver 3)

Challenge  The current platform costs  $42 a month.

Solution: Community Weaver 3 is only $25 one time fee. They have in the past tried to be funded by people paying a membership fee, but they realized that they wanted to be practicing what they preached, and just give the software away, as well as make it open source.


Facts about Community Weaver 3

Here is an overview of the Community Weaver 3

Here is something that a developer said:

I was so excited when I learned that Community Weaver 2.0 was built on Drupal, Community Accounting, and other pre-existing pieces of free code software, built by open source communities. Because building CW 2.0 on their work was only possible because they made it a public commons using free software licenses like the GNU GPL, it seemed only natural that the small modules of custom software written specifically for CW 2.0 would be released as free code, in the spirit of reciprocity.

Now we are offered CW 3.0, which still seems to built on all this work by others, but the custom work done by Kent Davidson doesn’t appear to have been contributed back the commons. This makes the CW 3.0 what we might call an “open core” softare, and the TB USA service running on it a “proprietary cloud”:

“Remember, we don’t pay the actual cost of software development because we are paying in the myriad ways of capitalism, with intrusion into our website histories and cookies; we pay dearly in the loss of control over our lives.”

I couldn’t agree more. I look forward to seeing TBUSA publish full documentation and source code for CW 3.0, under a free code license. I would recommend the GNU AGPLv3, which is intended for software used in servers running websites.

An Encouraging Letter For Developers about Community Weaver 3

I found this comment at the bottom of this page:

Danyl, thanks for your comments. We too were excited to go open source. It seemed like an ideal way to go. Here is our story with that. Community Weaver is sophisticated, complex software. We were informed that using Drupal modules, it would be way easier to develop than it had been the first time round for CW1. After some 100 modules had been modified and then joined together in extremely complex ways; after 2 years; and after a cost that was six times the original estimate, we had OK software that users had sort-of adapted to.

Jumping in to open source with all the idealism that we bring to timebanking, we learned — too late — about just how much investment in specification, coordination and management is required for the level of complexity that Community Weaver has. We also learned that Drupal 6 wasn’t really the right kind of platform for the product. (Drupal7 or 8 might be, but 6 was not.) We are not in the development community, we are the customers of the development community. What we learned –the hard way — was that open source works brilliantly under certain conditions.

Ours was not one of those conditions.

So now we’re on CW 3. We learned our lesson. We turned to a developer who had demonstrated that he runs a tight ship and could manage the complexity of this project. What he has produced has been receiving very, very high reviews from users, who have described CW3 as “easy — like kindergarten” compared to CW 2, and a “vast improvement.”

And Yes, we have used an open source underlying platform. And we hear you about giving back. Since we are not software developers, but rather, a software user, we give back where we can. We provide the software free to community timebanks that exist in the sharing economy. So far, almost 100 timebanks are receiving, without charge, the fruits of two years of work put in by our volunteer team of timebank coordinator advisors, our tech support person, and our developer.

In short, we remain true to the ideals of timebanking and to open source — but in a larger sphere that goes beyond the confines of the development community.

In closing this reply, I extend to you and all members of the development community an invitation to consider joining with us in “giving back” in ways that speak to the needs and possibilities of the world that stand outside development and to extend the notion of open source to include a more expansive view of what giving back could include.