having a dozen or so announcement lists is going make it harder to keep track of all new xml releases now and so make sure that they get fed into the general infosphere (by way of the jakarta news section which is now aggregated reasonably widely) but it's not such a big problem if they were all to be created straight away. (what'd make it more difficult is if projects started out by using announcements at xml and then switched to use their own announcement lists without making an announcement.)
what's more important is that there are people out there who are relying on the announcements list to find out about new releases of apache xml product. i have a feeling that someone produced some stats about this when the posting-newsletters-to-announcement flame was burning the apache newsletter (nee jakarta newsletter) to death. i recall that the figures were larger than i'd expected. maybe it'd be a good idea to either make announcements at xml into an aggrogater for announcements within the federation (subscribe all announcement lists in the federation) or close it down altogether (cleaner and let's people know they need to subscribe to the announcement lists of those projects they are interested in).
of course, this is just my tuppence...
- robert
On 14 Feb 2004, at 11:52, Berin Lautenbach wrote:
Robert,
Might even be a bit of both. My own feeling is that each TLP will make its own choice as to how much of its own infrastructure it sets up, but the xml lists etc. are there for "sharing" between XML related projects. So even if a TLP sets up its own announcements@, it could still post to the [EMAIL PROTECTED]
Cheers, Berin
robert burrell donkin wrote:
one topic that i don't think is covered in the federation proposal (http://nagoya.apache.org/wiki/apachewiki.cgi?XMLProjectPages/ FederationProposal) is how announcements are going to be handled under the new structure.
is there going to be an announcements list for each new TLP or will each TLP continue to use the communal announcements list?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
