Subject | web site stuff |
---|---|
Author | reed mideke |
Post date | 2001-05-02T17:22:03Z |
I mostly lurk here (what little posting I do is usually
in the firebird-devel mailing list), but I thought I'd respond to
the topic in general. Of all the things the firebird project
desperately needs, I'd put a new web site near (or below) the bottom of
the list. I believe Pavel has done an excellent job so far, and if
there are problems with the firebird.sourceforge.net site, the the
proper course would be to bring them to his attention (in a reasonable
and constructive manner, of course).
That said, Pavel has plenty of other things to do, and he
might feel that if he could offload some or all of the web stuff to
someone else, that would help him. If he makes that choice, then it
would be logical for him to offer the position to qualified members
of the community (subject to the approval the other firebird developers,
of course).
It has been suggested that the firebird 'development' site
and 'user' site should be different, but I do not agree with this
at all. The beauty of the web is it allows you to make
hierarchies. The choice between 'user' an 'developer should
only be a single click. Beyond that, firebird is essentially
a developer organization. Right now, there is very little
user content that belongs to firebird. Duplicating content
that is already available at IBID, IBPhoenix etc. only creates
more maintenance hassles. That's why we have hyperlinks.
Now if someone wanted to develop more firebird end-user content,
or a comprehensive index of available information, THAT would be a
valuable contribution.
If on the other hand, the firebird developers DO
want to have a new site, and then it MUST come with a web master
who is willing to be deeply involved with it for the long term,
and preferably has a deep involvement with all aspects of the
firebird project. A person who is great with web stuff but knows
little about firebird, (both historically and technically) is
not suited for the job. It is all well and good to design a new
site, but the real job is being up at 2:00 am trying to figure out
why a user with LYNX 1.0 on BBC Acorn can't view the Changelog file,
while at the same time harassing the hosting provider because
they misconfigured their DNS again.
The above are, of course, strictly my opinion.
Regards,
reed
(* going back to sandblasting my new car chassis *)
--
Reed Mideke
email: rfm(at)cruzers.com -If that fails: rfm(at)portalofevil.com
in the firebird-devel mailing list), but I thought I'd respond to
the topic in general. Of all the things the firebird project
desperately needs, I'd put a new web site near (or below) the bottom of
the list. I believe Pavel has done an excellent job so far, and if
there are problems with the firebird.sourceforge.net site, the the
proper course would be to bring them to his attention (in a reasonable
and constructive manner, of course).
That said, Pavel has plenty of other things to do, and he
might feel that if he could offload some or all of the web stuff to
someone else, that would help him. If he makes that choice, then it
would be logical for him to offer the position to qualified members
of the community (subject to the approval the other firebird developers,
of course).
It has been suggested that the firebird 'development' site
and 'user' site should be different, but I do not agree with this
at all. The beauty of the web is it allows you to make
hierarchies. The choice between 'user' an 'developer should
only be a single click. Beyond that, firebird is essentially
a developer organization. Right now, there is very little
user content that belongs to firebird. Duplicating content
that is already available at IBID, IBPhoenix etc. only creates
more maintenance hassles. That's why we have hyperlinks.
Now if someone wanted to develop more firebird end-user content,
or a comprehensive index of available information, THAT would be a
valuable contribution.
If on the other hand, the firebird developers DO
want to have a new site, and then it MUST come with a web master
who is willing to be deeply involved with it for the long term,
and preferably has a deep involvement with all aspects of the
firebird project. A person who is great with web stuff but knows
little about firebird, (both historically and technically) is
not suited for the job. It is all well and good to design a new
site, but the real job is being up at 2:00 am trying to figure out
why a user with LYNX 1.0 on BBC Acorn can't view the Changelog file,
while at the same time harassing the hosting provider because
they misconfigured their DNS again.
The above are, of course, strictly my opinion.
Regards,
reed
(* going back to sandblasting my new car chassis *)
--
Reed Mideke
email: rfm(at)cruzers.com -If that fails: rfm(at)portalofevil.com