In today's OCT meeting we discussed the need for better marketing and advocacy for OpenACS. The key result was the realization that the OCT is not the body to drive this forward.

Therefore I'd like to invite all people with marketing interest in OpenACS and .LRN to exchange their ideas (and materials) as well as coordinate efforts in this regard.

Areas where I see potential for collaboration:

- Attendance at conferences. This has two benefits. On the one hand you have the possibility to demonstrate OpenACS and how cool it is to outsiders. Furthermore the exchange with other developers will help greatly in bringing in new ideas and prevent our community from thinking in the box.

- General marketing materials. There have been some initiatives, but none really successful in the past. I'm not sure what marketing materials other companies are using for OpenACS, but we have ours online at http://www.cognovis.de/services/download/. Sadly they are in German. Maybe the least we could do is provide a repository for marketing materials?

- Defining a message about OpenACS that is appealing to clients and developers.

- Submit Feedback from clients along with the areas where we must improve. Make a priority listing by the number of times an item has popped up and how important it was to the respective clients.

Looking forward to read what others think in this regard.

Advocacy and marketing strategies certainly are vital for the future of the toolkit and the community. I'm interested in hearing what people mean by these notions, though, as I've always been confused about what is being marketed and to whom, with OpenACS specifically and I guess with open source projects generally. Perhaps the answer is "all of the following", but even if so, they seem to require different approaches:

• Marketing the platform to organizations not now using it for use by their developers/IT staff who aren't now part of the community. This seems to be the group for which the Apache support critical thread pertains. Since OpenACS is GPL'd, the only return to the community occurs if those new developers contribute new code back to the platform or if those organizations hire current OpenACS developers for gigs or for full-time. Well, there's the pride of creating a dominant platform, but that is intangible at best. But other than the "gig-getting" objective, what is being marketed here is really just convincing other people to use the same free software tools we use. This doesn't seem like a compelling marketing strategy to me (nothing really is being sold, and no one really is buying), but perhaps I'm missing something fundamental here.

• Marketing custom consulting/hosting solutions to organizations that don't currently have a web infrastructure or else need one with the far greater capabilities that OpenACS makes possible over other toolkits. I presume that most people in the community who make money with OpenACS are in this category, and so a "guild presence" at end-user conferences (eg NGO meetings where non-techie purchasers who know their tech needs and are shopping for solutions) would make sense. This could even be formalized somehow so that when one developer team is too busy to take a gig, they refer to others. Maybe this sort of thing is already going on. The marketing story here would most compelling focus on success stories from existing clients -- what they needed, how quickly and beautifully OpenACS developers delivered, etc.

• Marketing vertical solutions to specific industry segments that either currently don't have comparable solutions or else have inferior ones. This differs somewhat from the above approach in that instead of making custom one-off systems for client organizations, the objective here is to assemble teams with both domain expertise and OpenACS chops to create more or less turnkey solutions. I think .LRN is more like this than anything else. The marketing story here again is most compellingly the success stories from existing customers, but it suffers the risk of developing a product that -- without a specific client -- might miss the mark and also has to be funded some other way. However, the advantage of this approach is that all the technical details (AOLServer vs Apache, etc etc) can be blackboxed. Install the whole system on a Mac Mini or a OSX server rack depending on the scale of the client and let them turn it on. Or simply sell them monthly services.

  Personally, I find this latter strategy most interesting. What new product categories can be devised with OpenACS or else created better with it? For instance, there are a number of clinical trials infrastructure companies out there whose products/systems demand very high rates but which all have significant limitations. This is a significant opportunity that an OpenACS-based solution could target. An OpenACS-based electronic medical record is another idea; daunting in scope and problematic in business model (healthcare is broken in the US), but certainly an opportunity. And I'm certain that there are many other domains where vertical applications around which could be built a new company or a new marketing opportunity within an existing company.

• Marketing to current OpenACS or ACS developers who are already working in organizations and whose work is underwritten by their current jobs -- but who aren't part of the current OpenACS community and aren't using current OpenACS code because their code base forked so long ago. These folks could contribute huge amounts back to the platform as well as benefit from the huge advances made since they "left" -- if compelling benefits could be articulated and practical technical approaches identified. I think that there are probably quite a few groups like this: UCLA (Buddy's work?), GetActive, others? Actually, what I do sort of fits here, as I've evolved the 3.2.5 toolkit so far sideways that I haven't yet made the effort to migrate to the 5.x bleeding edge.

Anyway, I'd like to hear what others are thinking here when they talk about marketing and when they project their own work with the platform over the next several years. The answers will help define a strategy, IMHO.

There is a need for a sub-community for non-tech people in this community. As discussed at the Heidelberg meeting of .LRN in spring 2004, end users should be able to find answers on their questions and there should be non-tech volunteers to contribute to this non-tech community. Currently openacs.org forums are not very useful to find anwers on questions like “which layout of portlets on the page I should better use for my system?” or “How to ease navigation on the system for user?”. Having such forum would be by itself a marketing strategy.

Otherwise there is a need for budget. Development of marketing materials, promotional tag-lines, positioning gudelines etc. requires time.

This discussion should be also brought to higher level – what is the legal body that could apply for funding on behalf of the community? Or are there any mechanisms for people to know which community needs to include into their applications for funding? It is not strictly marketing but it is where marketing efforts bring you to – submitting an application / proposal.

To Stan – in my opinion many of the options for marketing efforts listed in the posting should be left to the competition between different companies and/or individual OACS specialists in this community. Market should be left to market. However, I liked the idea of Stan to promote community to the developers. But it is a separate discussion alltogether.

Some other suggested next steps:
- Identify people behind installations of OpenACS (do not look for successful ones, as there are none, the better platform – more requirements are users putting on it – code is not available that fast - owners are never happy as a result), approach them and invite to the sub-community.
- Consider possibility of sharing bug reports across different installations [to the point of getting priorities of users]. I believe it is more a technical problem than anything else.
- Create calendar and list of events where OACS should be / could be promoted, at least for reference.

Hope this contribution from non-technical person would be useful.
Wishes,
Volodja

Isn't the OpenACS Q&A forum the non-technical forum? It seems that a marketing discussion can build in this forum with no objections. I would be curious to hear from people who were afraid to post to a general question forum with a general question. "How to ease navigation on the system for user?" is a question that is quite appropriate for the OpenACS Q&A forum.

I don't think a budget is needed to market and advocate for OpenACS. It would be nice, of course, but OpenACS is an open source project, and there are volunteers who contribute to the code, so I see no reason that volunteers can not contribute to a marketing effort. It makes sense that those who need the marketing could offer some time and resources. Malte has already offered some materials his company uses for selling OpenACS.

I do think inviting users, developers and any other people from major installations of OpenACS is a great idea. I really don't think anyone would find they were not welcome if they want to contribute to discussions about OpenACS. It's clear from the results so far, that we need more feedback from real users requirements to improve OpenACS.

Marketing is about enlarging the size of the OpenACS community, bringing more developers and users into the community, and growing the viability and strength of OpenACS.

We all benefit when this happens.

So in my opinion the marketing group needs to be a group, not an ad hoc discussion on the forums. They need to meet regularly, like the OCT does, perhaps once a week via IRC.

They need to be thinking about what we need to do short-term and long-term to improve OpenACS. They need to be looking at OpenACS as a product, and as a community, and seeing where our weaknesses are, and organizing us around improving those weaknesses. And they need to be making sure we highlight what we're good at.

That's my vision for the OpenACS Marketing Team.

It doesn't have to happen. The community will move along just fine without it. But if we want OpenACS to be the big thing, it will take someone really paying attention to it. I think.

I'm willing to participate in a marketing group and would love to be joined by anyone who has an interest in seeing the OpenACS toolkit get higher adoption and is willing to spend some time to think about how to target our audiences.

If the group is to work effectively I propose that we create a new forum for this, so non developers can subscribe just to this forum without the need to read through OpenACS Q&A. I personally feel very strongly about splitting discussions into multiple forums, depending on target audiences as it has already happened successfully at other OS Projects. So this is why a marketing forum is the least to start with (there is no need for high traffic on any forum and if the group dies, so does the forum. That's evolution.).

Torben, the reason for a different forum is justified by the fact that not all people interested in Marketing OpenACS are interested in reading and digging through the OpenACS Q&A Forum.

As for going the whole way, I'm totally with you, except for the company bit as it should not be called arsdigita2, but OpenACS Foundation and have no commercial interest whatsoever.

Concerning the idea of a TEMP agency, I think Caroline and myself have already setup our companies in a way that will allows us (and the developers) to provide this functionality.

All I can say that the marketing process so far has not worked at all, everyone has done their bit independently and judging from past experience, the total impact from a marketing group is larger than the sum of it's participants impact.

Let me ask a few questions, to give you an example where we are lacking *coordinated* efforts. How many people showed up to Linux World Expo in the US or Europe? Do we have some information paper that allow a user to quickly see the functionality OpenACS has to offer? Is there an introduction into .LRN with the focus on how a university can make use of an LMS? Do we have a description how well OpenACS works as an enabler for Communities of Practise? Are there documents why OpenACS is the best solution a NGO can go for?

Yes, some of this information is contained in the forums. But are you going to dig through the forums if you are looking for a new tool to help you achieve XYZ? I for myself look for information that helps me *quickly* decide if it is worth reading more or not. And OpenACS does not provide this at the moment.

I could go on about the deficiencies of our marketing efforts here, but I guess we should only start this if there is enought interest from the community at large to tackle this problem. If there is not, I'll continue to do this on my own and go the informal path of contacting e.g Caroline and Jeff privately.

Perhaps it's time to extract those documentation requirements into their own page(s), and then use http://openacs.org/storage/ to share works in progress?

What are we marketing here and who are we marketing to?

There are at least 2 different groups to market to.

1) Developers who will use OpenACS to build applications for their clients and hopefully contribute to the community.

2) Selling OpenACS to decision makers at potential clients.

#1 is about growing the community and improving OpenACS. #2 is about using OpenACS as a toolkit or product for commercial purposes.

I think the needs of these two goals are quite different.

Aldert, "Not a well coordinated community". Having looked at a lot of open source communities I would have to dispute this assertion pretty strongly. We have never forked and things that get developed tend to be done with some consideration of what the community would like to see. I think you are confusing being resource constrained with not being coordinated. If OpenACS were a commercial product it would

The notion that you can "restructure the community" by fiat betrays a pretty profound misunderstanding of what community means.

I just don't know how you can build a roadmap for non-funded volunteer work or make paid client work conform to a community consensus roadmap. I do think we could write a "where do we want to go" type of roadmap but I don't think we could attach a timeline to that.

That said, I just don't think what matters most for marketing is whatever wishes and empty promises we put on some "roadmap", what matters are the things you mentioned: easy installation and making what we already have look and work better.

One aspect I would hope would come out of a marketing discussion would be what sorts of live demo sites would best showcase what people care about from openacs. I would also like to see the companies who have built real sites to put together a page with links to the "best examples" of what people are doing with openacs. There are good sites out there that are a testimony to what openacs can do but it's not easy to seperate the wheat from the chafe.

OpenACS's key selling point, IMHO, is its potential for robust, secure, industrial-grade web applications based around user/group access controls and complex, integrated processes -- "intranet" applications if you will (does anyone use that term anymore?). It is overkill for people who simply want to stick up a blog or photo album in the web space they get from their ISP.

Consequently, the story that "sells" (to developers, decision makers, developers-who-are-decision-makers, etc) should include the following:

• The OpenACS core is stable, bug-free and robust.
• Packages are well-defined units and package management is robust and error-free (things install and uninstall cleanly).
• Inter-package processing is well-documented via service contracts so that it is easy to "connect" existing packages to do new things, and it's easy and clear how to design new packages and make them interact with existing ones.
• The entire toolkit has been designed from the ground up with performance, reliability, and security in mind through tools like developer-support, automated-testing, and aggressive and documented bug detection/eradication. If you need to build a new financial, healthcare, auditing, commerce, or educational system, OpenACS will let you deliver a provable system that meets regulatory expectations of whatever bodies run your world view.
• The toolkit includes crucial pieces -- CR and Workflow -- that make it easy to build systems that verifiably handle data versioning and state transitions, tailored to user roles and access. And it is easy and clear how to use these subsystems in the toolkit.

That is the story that motivates me to engage the difficult task of moving my stuff from 3.2.5 to 5.x anyway. But as I do so, I'm finding out that a number of these attributes aren't yet fully realized.

• Packages don't uninstall cleanly (still) and it is amazingly hard to figure out why.
• It's hard to know how to use Workflow correctly, and whether problems you run into with client packages are due to errors in the client or in Workflow.
• The toolkit documentation is vastly better than before, but it helps mostly with how to do easy things, while hard things are still obscure. Sure, anyone smart enough to do complex things with the toolkit can eventually figure it out by reading source, but we're discussing the "elevator pitch" here where we're trying to impress people quickly that this system is a magnitude leap over the alternatives.
• There are lots of old still-open bugs in bug-tracker.
• Best-of-breed example packages and systems aren't clearly identified in a way that can inspire and educate.

So the "marketing" steps that need to be taken IMHO include both a better articulation of OpenACS's capabilities as well as making sure that those capabilities are really there -- tasks that need the joint attention of OCT as well as whatever new marketing committee is created. My $0.02 anyway.

Well, I posted some new calls to action to remind us that we have some work to do in improving OpenACS. Specifically in the areas of package uninstall and maintaining the bugtracker. Thanks to Don, the bugtracker is now fast enough to use for an extended time with fixing bugs.

Stan, I didn't take your post as criticism, and in fact I agree with most of it. Just pointing out that yeah, the OCT (and others) have recognized these weaknesses for a long time, and to make sure everyone understands that it is a resource issue, not a problem with the community's opinion as to what's important ...

The most organized community in the world, if too small for the task at hand, will still fall short.

I think we're very well organized, actually, there just aren't many of us who are active and we have a huge code base (quarter-million lines of code or so), are supporting mulitiple operating systems and RDBMS backends, etc.

The fact that many people in the community will be too busy with their day jobs to help clean out bug reports is, again, a reflection of lack of resources, not organization. If we had the money (a resource), we could just hire twenty of them from their day jobs and put them to work without modifying our organization at all ...

Still, marketeers will want to know what's ahead, concerning technical issues and resources.
I wonder what unused resources are available in the community.

Right, that's my point, in general.

Jade & Others,

If resources were available, what are the types of things that need to be done to encourage more developers to join the community?

Looks like Malte beat me to the punch. I was going to recommend quarterly bootcamps that are free or extremely reasonably priced with quality supporting materials that are easily found.

Bootcamps and Philip's talks were the best marketing tools that aD had. Interestingly they were under the banner of education. Oh yeah, the book makes that a marketing triad. All of the above generated press. The free aspect being one of the keys to gaining outside interest.

I must admit that my reaction to the periodic "we need marketing" discussions is a kind of nausea. OpenACS is simply a tool. When it stops being an effective solution for solving web based problems for me, I'll stop using it. It seems to me that the best "marketing" we can have is a community that is focused on improving the toolkit. A big part of that is reaching consensus on what problems we are trying to solve and what problems we have already solved well. Maybe an inventory of what we have is in order. This would be a nice complement to a roadmap.

Semi-related random thoughts:

I have a lot of respect for projects like Postgresql and AOLserver because they never forced themselves on me. They continued to stay focused on solving the problems at hand and thus continued to stay relevent, trusting developers that they were smart enough to choose the right tool for the job. A large community does not necessarily equal a better community. Here's an old chestnut, "small is beatiful".

Dear all,

just one thought that came to my mind. We are using a very simple technique to record lectures and talks. All you need is enough space on disk, the software and a microphone connected to your computer. Once the talk starts the software records the talk and the voice of the speaker by simply recording what ever is displayed on the speaker's computer.

For windows we use Camtasia but there are definetly free tools around for any platform. I found this link, but maybe there is a more updated link:
http://all-streaming-media.com/record-video-stream/screen-capture-software.htm

So the idea is this. When ever a talk on OpenACS or dotLRN is taking place you simply record that stuff and make it available on OpenACS. Maybe we can use lars-blogger for that. If disk space is a problem we can host the files here at the university of mannheim.

This would allow us to create a large repository of talks. I use virtual dub to decrease the size of a recorded session to a tenth since these type of recordings contain tons of redundant info.

For 90 min I always end up with around 15 MB.

Greetings,
Nima

• We are all here because we like using OpenACS instead of alternatives
• OpenACS continues to realize only a small fraction of its realistic (not blue-sky, ideal world, but real, tangible, one-step-away) potential.
• We have adequate organization and processes and code; what we're lacking is resources.
• We would benefit as users of OpenACS if the project had more resources.
• We would benefit as Free Software developers if more people used OpenACS, and if we knew about it.

Thus marketing, both to get more users and to get more resources, is currently the limiting factor in our success. From here, i see Stan's original post in this thread as a good starting point for more discussion. The first problem in marketing, as I see it, is that we don't have information to tell us where to focus our very limited resources (those being the donated time and energy of people in the forum, and maybe some cash from the .LRN consortium or other donors we can find). I see the problem as a funnel:

1. There are X people in the world whose problems could be practically solved by OpenACS. We could increase X by improving the quality, usability, or functionality of OpenACS.
2. Of those X people, only Y have heard of OpenACS. We could increase Y by advertising, going to conferences, etc.
3. Of those Y people, only Z are interested. We could increase Z by changing parts of OpenACS that are unattractive, by making better arguments or brochures, more screenshots, etc.
4. Of the Z people who are interested in OpenACS, only W actually succeed in trying it. We could increase W with binary installers, better installation, stable demo sites, installfests, boot camps, etc.
5. Of the W people who try OpenACS, only V actually adopt in for their use.

My question is thus, where is the leverage? Is it feasible to get some hard numbers for X->Y->Z->W->V? It would then be much easier to tell which of very many different things we could be doing would be most worth doing.

I therefore find Stan's post interesting because it is a start in this direction, albeit unencumbered by numbers. I can only respond in similarly anecdotal form:

"Marketing the platform to organizations not now using it for use by their developers/IT staff who aren't now part of the community. ... This doesn't seem like a compelling marketing strategy to me (nothing really is being sold, and no one really is buying), but perhaps I'm missing something fundamental here." Well, isn't this how almost the entire community to date grew? We were attracted by the book, by a boot camp, or by a Phil lecture. How many people have become active members of the community through other means? I don't know if this is the best leverage going forward, but it's what has worked the best in the past.

"Marketing custom consulting/hosting solutions to organizations that don't currently have a web infrastructure or else need one". I don't think the community grows when this happens. I've built OpenACS solutions for a few paying customers, but they aren't part of OpenACS now; they just rely on me. Maybe it works better for bigger companies/institutions that actually have staff that could contribute back.

"Marketing vertical solutions to specific industry segments that either currently don't have comparable solutions or else have inferior ones." How will this grow OpenACS? Will consulting firms add it to their quiver? Will we get new developers who decide "I'll learn OpenACS so I can sell it in my niche?" I think this approach (as .LRN, in the higher-ed market) is the only thing other than recruiting developers that has worked well for OpenACS. How would we move forward (extend a pseudopod?) as a community?

"Marketing to current OpenACS or ACS developers who are already working in organizations" I like this because it fits the adage, "your existing customers are your best market." How would we do it? Appoint a lost-sheep liason?

Deleted (SPAM)