On Mon, 2006-03-06 at 19:49 +0100, Ortwin Glück wrote: > > Sandy McArthur wrote: > > As a programmer looking for useful code to help me with uploaded > > files, I'm going to look in something named Jakarta *Web* Components > > first. When I see Jakarta HTTP Components I think of interacting with > > the HTTP protocol. I know FileUpload does both, but when I'm writing > > an webapp I think I'm working with a *web* app first and while I am > > working with HTTP it is a secondary concern. > > > > -- > > Sandy McArthur > > This may be true, but it shouldn't influence how the communities around > the code are organised. This is more a matter of communication and branding.
i think that's one of the advantages of flattening karma and voting: . we need to separate the formal legal structure (karma, voting) from the community (developers hanging out) from the ontological (communicating that the components are). from an ontological perspective, fileupload needs to be tagged as both http and web component with a sideways relationship to codec. from a community perspective, martin feels more at home with the httpclient team and it sounds like there are sound reasons to believe development might be more progressive. from a legal perspective, we're all jakarta: karma and voting need to be communal. in some ways, we need to find a way since the whole of apache is going to be facing these problems soon... - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
