On 8/6/07, haleh mahbod <[EMAIL PROTECTED]> wrote: > Hi Tuscan Contributors and Users, > > I have been thinking about how we can further enhance the flow of > information in Tuscany. New interesting things happen on regular basis and > information is either embedded in an email, in code/commit log, embedded > in a webpage on TuscanyWiki or the website. Users of Tuscany may have > interesting information to share, but not have a place to share this > information. > > A new person coming to Tuscany may not be able to easily find the > information in archive since they don't know what to look for. Users who are > tracking the project may not have time to read the details of each email and > would probably appreciate finding information quickly. Note that this is not > a particular characteristic of Tuscany. It is just the nature of open source > projects. Lots of good information to dig into in svn, in mailing list, on > websites, etc. > > Here is a proposal. How about a news bulletin for each subproject that > resides on TuscanyWiki and gets linked into from Tuscany website download > page. This is a live page, contributed to by all. It is not a replacement > for any of the existing communication mechanism. It is a quick pointer to > information that will help people find the latest news. > > For example the SCA bulletin could be: > Development bulletin board > - Community is working on the next release of project. You can participate > in this thread of discussion <ML thread> if interested.. > - There is a quick guide to getting started <link here> > - Major efforts in progress, example OSGI , Integration with Geronimo, .... > .... Use your imagination... Anything that can be shared with the community > to help them understand what's going on > > Users bulletin board > - Here is a scenario that SCA is used in and here are some examples to share > < link to a page that the data is> > .... Use your imagination.... Anything that can be shared with the community > > Questions: > Do you agree that we should spend effort on further enhancing information > flow or there is enough already? > If yes, What type of information would you like to see so that information > can be better organized? > If you agree that we can further enhance information flow, would the idea of > news bulletin work? If not, what else? > > I'll take care of the initial draft of the webpages if I know there is > interest to keep these pages live, otherwise there is no point to just add > another page to the wiki.
this is a bit of a history lesson (probably a poor one since it's based on my fallible memory rather than objective research) so please feel free to skip or ignore. in fact, this would probably have been better as a blog but it's a little late now... in the beginning there was [EMAIL PROTECTED] then java became xml, jakarta and cocoon. when jakarta was young (http://jakarta.apache.org/site/news/news-2000.html), jakarta created news then lots of news (http://jakarta.apache.org/site/news/index.html). news proved very popular. too popular, in fact. so, this grew into the jakarta newsletter which then became the apache newsletter. but all things have their time: and running a newsletter takes a lot of energy. what starts as a pleasure becomes a chore. the theory was that blogging would be a better way of managing news. thus http://www.planetapache.org/. this been a very successful in many ways but it turned out that most people prefer to talk about more personal matters. which is cool in many ways. IMHO planetapache is a major force in retaining cohesiveness now that there are so many members and projects. but i still believe that news is great way to build community and interest in a project. it's also personally rewarding though it's easy to underestimate the time that maintaining good news takes. i believe now that blog aggregation is the best structure for news. for this to be effective does require a consensus that committers are going to spend a little time regularly blogging about new features. good luck and i hope this takes off :-) - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
