Thank you all for the good ideas. Trying to summarize this thread. 1) Blogging is an important communication tool - We should all attempt to do this more often. The type of interesting information for blogs would be things that we'd want to communicate instantly. Cool features that are becoming available, actual user use cases, ....
2) There seems to be a set of things that fall into important information to communicate, but does not quite fit the blog profile (Jeff also points to this). These are things that give a high level view of f where things are and heading to in the project without digging into tons of mail, etc. For example, high level roadmap, pointer to current release discussion, pointer to use cases Mathew suggests a weekly news digest. Although a great idea, it requires a dedicated person on an ongoing basis (since everyone will rely on this ;). What I was proposing is simpler. It is a bulletin board where everyone posts information of type (2) above. I am not sure if we are agreeing that a news bulletin per subproject is worth the effort or not given all the new ideas that were shared on this thread. I could go ahead and start this as an experiment, but its content is dependent on input from everyone. We can try it for a while and evaluate if it is useful or should be removed. I'll wait another day for feedback before I proceed. Thanks, Haleh On 8/7/07, Luciano Resende <[EMAIL PROTECTED]> wrote: > > On 8/6/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > > <snip> > > > 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. > > +1, we could have a Tuscany aggregation (e.g individual committers > would aggregate into a planetTuscany) plus planetApache aggregation. > More technical committer, involved in specific feature, would probably > blog around what's going on, new enhancements, etc... Release Managers > would probably blog about what's being planned for the release, other > could write a weekly summary as Haleh proposed. > > As for the notification part, or basically to be aware of new items > posted, Google Alert is one way to get notified. You could also use > other options such as google/ig, feed readers, etc > > > On 8/7/07, Anderson, Jeff T (CA - Toronto) <[EMAIL PROTECTED]> > wrote: > > I agree that this is a useful feature, you can never put enough effort > into making information more accessible, > > as for the type of information, everything that you've mentioned below > is appropriate > > -plus actual case studies of usage > > -high-level roadmap items > > etc., etc. > > > > ________________________________ > > > > From: haleh mahbod [mailto:[EMAIL PROTECTED] > > Sent: Mon 2007-08-06 15:31 > > To: tuscany-dev; Tuscany Users > > Subject: Tuscany Subproject News Bulletin? Would it be useful? > > > > > > > > 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. > > > > Haleh > > > > > > > > > > ----------------------------------------- > > > ************************************************************************************** > > Confidentiality Warning: This message and any attachments are > > intended only for the use of the intended recipient(s), are > > confidential, and may be privileged. If you are not the intended > > recipient, you are hereby notified that any review, retransmission, > > conversion to hard copy, copying, circulation or other use of this > > message and any attachments is strictly prohibited. If you are not > > the intended recipient, please notify the sender immediately by > > return e-mail, and delete this message and any attachments from > > your system. Thank you. > > > > Information confidentielle: Le présent message, ainsi que tout > > fichier qui y est joint, est envoyé à l'intention exclusive de son > > ou de ses destinataires; il est de nature confidentielle et peut > > constituer une information privilégiée. Nous avertissons toute > > personne autre que le destinataire prévu que tout examen, > > réacheminement, impression, copie, distribution ou autre > > utilisation de ce message et de tout fichier qui y est joint est > > strictement interdit. Si vous n'êtes pas le destinataire prévu, > > veuillez en aviser immédiatement l'expéditeur par retour de > > courriel et supprimer ce message et tout document joint de votre > > système. Merci. > > > ************************************************************************************** > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Luciano Resende > Apache Tuscany Committer > http://people.apache.org/~lresende > http://lresende.blogspot.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
