Re: Some PEAR web-related proposals
| From: | Jan Lehnardt | Date: | Thu, 07 Feb 2002 23:00:44 +0000 |
| Subject: | Re: Some PEAR web-related proposals | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-4494@lists.php.net to get a copy of this message | ||
Hi,
On Thu, 7 Feb 2002 15:56:13 +0100
"Alexander Merz" <alexander.merz@s1999.tu-chemnitz.de> wrote:
> Hi boys and (unfortunalty no) girls,
sad, sad..
> 1. Add a feature request form on a prominent position on pearweb. A
user on the
> german php newsgroup wrote, he reads the feature requests on the
phpnuke
> website. Often the are written by users, not by programmers. The users
have
> intresting ideas because they doesn't think about implemention.
+1
> 2. Separate the PEAR bug tracking from the PHP bug tracking. All PEAR
related
> stuff is at the moment only covered by one drop-down issue for
pearweb, peardoc
> and all classes and extensions.
> Another problem is a user would markup a peardoc bug as documention
bug, not as
> PEAR bug.
Again +1. This may be the right place for the "new" php bugsystem wich
somebody pretends to be working on (zak?).
> 3. Add a News section equal to php.net. Nobody out there knows
something about
> the PEAR installer, important releases and other new cool stuff.
ehere we go: +1
> 4. Add a "Behind the scence" section maybe as an non standard part of
the
> manual. This section should contain a regular summary of the PEAR-Dev
> mailinglist discussions (i have the weekly ZE2-ml summary in my mind).
And this
> would be the right place for documentions about the internals of PEAR.
I.e. a
> description of the internals of PEAR::DB or why IT doesn't work like
xy. This
> could include subjective comments of the maintainer/programmer. This
section is
> directed to PEAR developers not PEAR users.
+10. Personally I find those "behind the scenes" sections very useful to
unerstand the spirit of a certain project. This e.g. helps my to
integrate into it.
> 5. Set up a Groupware. [...]
Althoug it will be challange to manage it at its startup, I think it it
worth trying. I do not mind using Horde or anything other as long as it
fits our needs and is, if needed, easily customizable.
> 6. Make more advertising! PEAR isn't brand into the mind of the PHP
people.
> Maybe you remember the IRC discussion about PEAR banners with slogans
like
> "Rasmus use PEAR, for what do you wait?". Why not create such banners?
Some
> OpenSource-related sites offers free ads for non-commercial OS
projects.
One of the best suggestions here. As I can see on mailinglists and IRC,
anytime PEAR is mentioned at least one is asking "What is Pear/Where can
I get it?"
Jan
--
Q: Thank Jan? A: http://geschenke.an.dasmoped.net/