--- Pierre Delisle <[EMAIL PROTECTED]> wrote:
> OK. I guess we're all in agreement to say it is time
> to get
> (better) organized.
>
> Glenn planted the idea. Morgan got us going.
> Here are a few more ideas that might help us link
> it all together.
>
> -- Pierre
>
> -----
> 1. Global View of what's available in taglibs as
> well as in what
> shape it is in
>
> Currently, the home pages of each taglib do not
> contain much information.
> I think it would be great if we would replace these
> home pages with
> the concept of a "dashboard" (better term?) that
> gives a quick overview
> of all that's available in jakarta-taglibs, and what
> shape it is in
> (ready for primetime, beta, experimentatl, etc...)
Good idea. A news page will be a good start, but I agree that more can be
done. Perhaps the site is a little _too_ cookie cutter now. It doesn't
help that DTDs for our site transformations are so hard to come by.
> Each taglib would display:
> - short description,
> - current status
> - links of interest
> - binary distributions (stable, nightly)
> - source distribution
> - docs
> - examples
> - news
Sounds good.
> These taglibs would be presented alphabetically
> according to their 'category'.
> (see below)
>
> *** AI: Pierre volunteers to design a first draft of
> what that "dashboard"
> would look like, and then get buy-in from
> the group.
Go for it. What's an AI? :)
> -----
> 2. What Categories?
>
> I'd suggest something like:
> 1. Released
> 2. Beta
> 3. Experimental
>
> *** AI: Need someone to define these categories and
> the
> rules that govern them
Yeah. I would say that tag libraries start out at Experimental and then
graduate to Beta and Released. Once you've performed a release, you stay
at the Released category on the main page, even if you are currently
developing an alpha or Beta. Your initial Beta and Release must be
approved by the whole Jakarta Taglibs group.
> Morgan has already taken up the challenge of writing
> up the following
> guidelines for 'released' taglibs:
> 1) How to version releases and create branches
> 2) How to create/use the "news" section
>
> Will someone (Morgan?) take up the "global"
> challenge of defining categories
> and how one migrates from one to the other?
Sure, I just did. :) Seriously, though, I'll try to formalize it and add
it to the HOWTO doc.
> -----
> 3. directory structure and build process
>
> We already have a standard way to do things in
> taglibs.
> However, we may have to revisit this in light of
> the following:
>
> 1. Tim Dawson's proposal for a new build
> process
>
> Tim had proposed a new build process
> without scripts, and much
> more user-friendly. Not clear where we left
> it off though.
>
> *** AI: Pierre will ping Tim to see where we left
> off on the new build
> process
If Tim is talking about creating one centralized build script, I may be
able to help.
> 2. If we go with the Dashboard
>
> Ideally, tag developers simply update a
> file "description.xml"
> and the build process takes care of
> everything else.
> This is not the case right now where manual
> intervention
> from the nightly build goddess (Justyna) is
> required when the
> status of a taglib changes.
>
> *** AI: Need someone to investigate what should be
> done to automate the
> nigthly build with the dashboard concept.
> Pierre will talk to Justy and have a first
> crack at it.
