Re: Re: [aspectj-dev] Online samples

["Adrian Colyer" <adrian_colyer@xxxxxxxxxx>]

This is a great idea... nothing convinces
people of both the power and the simplicity of aspectj more quickly than
good examples. We should make sure that the contributor of any given sample/hint/tip
etc. is clearly accredited too so that community experts can emerge over
time (though this may be difficult if a sample is refined on the list by
several parties before being posted). 

-- Adrian
Adrian_Colyer@xxxxxxxxxx

Lesiecki Nicholas <ndlesiecki@xxxxxxxxx> Sent by: aspectj-dev-admin@xxxxxxxxxxx 10/07/2003 19:49 Please respond to aspectj-dev

To:        aspectj-dev@xxxxxxxxxxx         cc:                 Subject:        Re: Re: [aspectj-dev] Online samples

OK, I agree that having commiters filter will improve
the quality and
organization. I also agree that discussion should be centralized.

Cheers,
nick
--- a@xxxxxxxxxxxxxxx wrote:
> 
> From my point of a perspective yes.
> Do what is easier to set up, to get the things started.
> 
> kind regards
>    Arno
> 
> Wes Isberg <wes@xxxxxxxxxxxxxx> schrieb am 10.07.2003, 19:19:09:
> > Hi Russell (and Nick)-
> > 
> > I like the idea of a wiki, but I'm not convinced yet.
> > 
> > Russell Miles wrote:
> > > Hi Wez,
> > > 
> > > Would this site benefit from being a Wiki 
> >  > to make it as easy as possible for contributors to
add
> >  > their samples etc? This would also make the source
> >  > searchable.
> > 
> > The one HTML page will be organized by application
> > and should be searchable.
> > 
> >  > This would not detract from a more frozen
> >  > programming guide but would benefit from it being
as easy
> >  > and as open as possible for people to add their own
works
> >  > to the site for consideration as part of the more
formal
> >  > programming guide.
> > 
> > To contribute requires only sending an email to the mail
> > list with the proposed sample.  That way, it's up for
> > discussion regardless of committer attention, and doesn't
> > change what users now do.  So it should be easier for
> > the contributor than a wiki would be.
> > 
> > That way, rather than splitting discussions between the
> > mail list and a wiki, the mail list continues to host
> > all discussions.  Plus, users can also find good samples
> > in one place, with links out to other AspectJ docs
> > and in from mail lists, etc.
> > 
> > The committers moderate somewhat for quality and
> > organization, and also can pull samples not originally
> > intended for the samples page (after emailing the
> > senders).  I hope contributors find committer moderation
> > to be quick and to be a benefit rather than a hindrance.
> > 
> > If we get to the point that we have too many contributors
> > and too much code for this format, or if the committers
> > are not helping, we'll have to manage our success
> > differently, perhaps using a wiki.
> > 
> > Sound reasonable?
> > 
> > Wes
> > 
> > > 
> > > Cheers
> > > 
> > > Russ Miles
> > > 
> > > On Thursday, July 10, 2003, at 00:48AM, Wes Isberg  wrote:
> > > 
> > > 
> > >>Let's make it easier for AspectJ users to find small
AspectJ code
> > >>samples by publishing HTML page(s) with linkable code
and discussion.
> > >>The code would include idioms and workaround, as well
as
> > >>task-oriented docs, e.g., "how do I set up Apache's
JSP compiler
> > >>to weave in my aspects?"  Some of what's in
the FAQ now would move
> > >>out to these sample pages, but the goal is that committers
would
> > >>migrate good code on the mailing list to the samples
pages. (In
> > >>theory, a "how to" question would never have
to be asked twice.)
> > >>These pages could be updated at any time, and incorporated
into
> > >>the Programmers Guide when that is revised, if appropriate.
> > >>So we'll have...
> > >>
> > >>- code samples: online html snippets and tasks, links
to all of...
> > >>- examples:     programs in the distribution
> > >>- idioms:       the programming guide
section
> > >>- exercises:    tutorial code
> > >>
> > >>Absent objection, I'll put up an initial version, linked
off
> > >>the docs page.  The goal is not to have a page maintainer,
but
> > >>for any committer to add code as appropriate (by contrast,
the
> > >>Programming Guide operates per our usual strong-lead
model).
> > >>
> > >>Wes
> > >>
> > >>
> > >>
> > >>_______________________________________________
> > >>aspectj-dev mailing list
> > >>aspectj-dev@xxxxxxxxxxx
> > >>http://dev.eclipse.org/mailman/listinfo/aspectj-dev
> > >>
> > >>
> > > 
> > > _______________________________________________
> > > aspectj-dev mailing list
> > > aspectj-dev@xxxxxxxxxxx
> > > http://dev.eclipse.org/mailman/listinfo/aspectj-dev
> > > 
> > 
> > _______________________________________________
> > aspectj-dev mailing list
> > aspectj-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/aspectj-dev
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-dev

_______________________________________________
aspectj-dev mailing list
aspectj-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-dev