Re: [PHPiCalendar-DEV] can someone help me understand bug 1417012?

[Jim Hu <ji...@ta...>]

 From what I can tell, there is one reference to publish.php in  
comments in the main code; this is a vestige from before publish.php  
split into the ical and mozilla specific scripts.  So while it should  
probably be fixed, it's not clear to me that it counts as a bug.  It  
has no effect on the functionality, but it does direct the reader to  
a nonexistent file.

I think Chad is saying is that the main phpicalendar project does not  
support the publish.ical.php or publish.mozilla.php scripts.  He says

" we do not take bugs in the pulbish system, including documentation"

These were provided by others, and while they are important to those  
in the phpicalendar community who can't or won't use WebDAV, they are  
a pain for the developers since their behavior is very sensitive to  
server configurations.  If you look on the bbs, you'll see that we  
get a LOT of people with problems using these.

If I understand your request, you are also asking for changes in the  
_comments_ on line 52 of config.inc.php, which is supported by the  
project.  But your reopening looked like you are still asking for  
stuff related to publish.ical.php and publish.mozilla.php.  You might  
try clarifying what you said earlier instead of blaming Chad for  
being confused and asking him to reread something that wasn't clear.

The instances in the README accurately reflect the project history as  
far as I can tell.


=====================================
Jim Hu

On Jan 31, 2006, at 2:13 PM, Jo Rhett wrote:

> This is regarding bug 1417012.
>
> There are several references in the code to publish.php, which  
> doesn't exist
> in the current distribution.
>
> Chad closed the bug immediately saying he doesn't support  
> documentation.  I
> realized I wasn't being clear, and reopened it explaining that it was
> references in the code itself.  Chad's final note on this is:
>
>   Please stop harrassing me, I've closed this twice. If you persist  
> I will
>   lodge a complaint with sourceforge. This is not going to be fixed.
>
> What exactly about pointing out problems in the code is  
> harrassing?  These
> problems do exist.  If there is a reason for it to be this way (I  
> suggested
> several possible explanations) then why not take a quick moment to  
> explain
> why it is this way?
>
> I'd really hate to start off my relationship with this project on  
> such an
> argumentative approach.  Frankly, I'm confused by this sort of  
> behavior.
>
> I like phpicalendar, and I'm working on a number of patches to  
> improve it
> (including several that are in your feature request list)  But if bug
> reports are going to be slammed down with threats of harrassment,  
> without
> even acknowledging or responding to the issue ... that's pretty  
> difficult
> to work with.
>
> In looking through the bugs, I've noted that Chad tends to  
> aggressively
> close out bugs even when people have documented that the issue  
> isn't fixed.
> So it apparently isn't just me that is observing this behavior.
>
> -- 
> Jo Rhett
> senior geek
> SVcolo : Silicon Valley Colocation
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD  
> SPLUNK!
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel