Hi Stephen,
Although I don't know commons net too well, I guess we have less in
common with them than for instance with Tomcat or Fileupload. The
"closest" relationship I can only see in FTP - and even that is marginal.
But we'll happily incorporate a common CSS of course. No need to
contribute even more to the existing ASF web design mess.
IMHO this whole discussion about reforming communities is twofold:
A. The project maintainer's point of view: They want a community for a
certain topic. They make certain products. That's developer community
and team structure: dev mailing lists, SVN, dev wiki, access rights.
B. Our users' point of view: They want to find information and products
in places where they expect them. That's communication and user
community structure: user mailing lists, website, downloads, user wiki,
rss, news.
Unfortunately the two abstract structures differ quite strongly from
each other. But currently it's structure A which produces the
materialization of structure B. Speaking in design terms the two are
strongly coupled. That makes it impossible to modify them individually.
Restruturing A will affect B. And to restructure B you must modify A.
That's why companies have "corporate communication": to hide complexity
from their customers behind a facade and to decouple the two structures.
Conversely here at ASF we slap our dev structure directly in the face of
our user communities who hardly can cope with it.
I quite like the meta site approach that
http://projects.apache.org/index.html takes a lot. It is very promising.
Ortwin Glück
Stephen Colebourne wrote:
Hi,
I'd like to propose something which came up during the current talks on
Jakarta's future.
One suggestion was that instead of creating Jakarta Http Components,
this group could be Jakarta Network Components.
In essence, this would mean adopting commons-net
(http://jakarta.apache.org/commons/net).
The idea is based on a premise that http and net (ftp/finger/smtp...)
might share common interests and could thus form a common community.
The downside is that it may distract this group from its current plans,
and it may also be that no-one here is that interested in ftp/smtp/nntp
etc. Also, commons-net is a mature product with relatively little
community - one which might benefit from a broader outlook.
Anyway, please consider this as a brainstorm idea. Nothing is being
forced on you. Think of it as an opportunity if you guys are interested.
If not, then at least the suggestion was made!
Stephen
PS. I'm aware that this discussion might have been better a few months
ago...
---------------------------------------------------------------------
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]
