Well, I've asked a few places if they're okay with us linking to them. I followed Dave's advice and found a bunch of success stories off the web and added links to them.
Sim's contribution looks much less lonely now! Thanks for the ideas, Patricia. I think that's exactly what we should do. I don't see the need to wait until graduation; although, that does feel like a really good watershed. We can start hitting the user list for requests and letting them know of upcoming releases now. Which reminds me of the roadmap thread... On Mon, Nov 15, 2010 at 3:22 PM, Patricia Shanahan <[email protected]> wrote: > Tom Hobbs wrote: > ... >> >> As for engaging users, I think that has to be a must. The user list >> is not hugely active; I kind of get the feeling that people accepted >> the Jini 2.1 code and have pretty much ignored River since. At least, >> that's my experience of "Jini vs River". We need to publicize River >> and get people downloading and using it. I've seen commit and >> download charts on other open source projects. Does anyone know how >> we can get those - or if they think it's a good idea? > > ... > > We may have an opportunity in conjunction with graduation. When that happens > we should try to get out a press release, and distribute it every way we > know how, with the following messages: > > 1. Apache River has an active development team and is now a full fledged > Apache project. > > 2. The development team welcomes input from both active users of River, and > from users and potential users of Jini who are not yet River users. Here are > some ways to supply input to the team: (mailing list, issue tracker...). You > do not have to become a contributor to the source code to influence it - > just make a good case that a change would improve River. > > I know the wording here is very rough - I'm definitely not a marketing > person - but I think if we make enough of a splash with these messages it > should help both spread use of River and get us that input we are looking > for. > > Patricia >
