11:35 a.m.
ACTIVITY SUMMARY (2013-08-20 - 2013-08-27)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
541 open ( +0) / 321 closed ( +3) / 862 total ( +3)
Open issues with patches: 13
Average duration of open issues: 1549 days.
Median duration of open issues: 1642 days.
Open Issues Breakdown
new 235 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 55 ( +0)
assigned 143 ( +0)
committed 18 ( +0)
documented 3 ( +0)
done/needs work 16 ( +0)
Issues Created Or Reopened (3)
______________________________
u sukz 2013-08-24
CLOSED http://tracker.xemacs.org/XEmacs/its/issue862 created anonymous
i think the issue tracker is broken 2013-08-24
CLOSED http://tracker.xemacs.org/XEmacs/its/issue863 created iWontFixYourBug
you guyz should work on your issue tracker 2013-08-24
CLOSED http://tracker.xemacs.org/XEmacs/its/issue864 created vimRULES
Issues Now Closed (25)
______________________
Set up backup regime 2045 days
http://tracker.xemacs.org/XEmacs/its/issue53 iWontFixYourBug
21.5 screen resize issue 2044 days
http://tracker.xemacs.org/XEmacs/its/issue79 iWontFixYourBug
Old mail archives. 2044 days
http://tracker.xemacs.org/XEmacs/its/issue129 vimRULES
update mh-e to MH-E 8 2013 days
http://tracker.xemacs.org/XEmacs/its/issue298 vimRULES
Crash when displaying progress bar (typically in fontlocking) 1991 days
http://tracker.xemacs.org/XEmacs/its/issue323 iWontFixYourBug
Streamline mail flow 1419 days
http://tracker.xemacs.org/XEmacs/its/issue582 iWontFixYourBug
Improving tooltip support 1412 days
http://tracker.xemacs.org/XEmacs/its/issue590 vimRULES
Add 'easy' keyword 1398 days
http://tracker.xemacs.org/XEmacs/its/issue616 vimRULES
hilit-pkg 1398 days
http://tracker.xemacs.org/XEmacs/its/issue619 iWontFixYourBug
Debug Assertion Failed! f:\dd\vctools\crt_bld\self_x86\crt\src 1374 days
http://tracker.xemacs.org/XEmacs/its/issue634 economicseries8
Update eldoc 1059 days
http://tracker.xemacs.org/XEmacs/its/issue730 iWontFixYourBug
emacs 21.5.29 fails to build 'executeable' 938 days
http://tracker.xemacs.org/XEmacs/its/issue749 iWontFixYourBug
No-mule XEmacs can corrupt UTF-8 files. 774 days
http://tracker.xemacs.org/XEmacs/its/issue780 iWontFixYourBug
[Bug: 21.5-b29] customize: Set Save Done button disappeared 704 days
http://tracker.xemacs.org/XEmacs/its/issue803 stephen
etags.xemacs21 generates garbled paths 661 days
http://tracker.xemacs.org/XEmacs/its/issue810 vimRULES
kp-divide 654 days
http://tracker.xemacs.org/XEmacs/its/issue812 vimRULES
small errors in behavior.el 589 days
http://tracker.xemacs.org/XEmacs/its/issue826 iWontFixYourBug
Scrolling Bug 460 days
http://tracker.xemacs.org/XEmacs/its/issue831 iWontFixYourBug
define-obsolete-function-alias is missing an optional paramete 265 days
http://tracker.xemacs.org/XEmacs/its/issue848 iWontFixYourBug
printing strings loses eq relationship 83 days
http://tracker.xemacs.org/XEmacs/its/issue858 vimRULES
xemacs seems to mis-compile parts of vm 25 days
http://tracker.xemacs.org/XEmacs/its/issue860 iWontFixYourBug
icalendar--decode-isodatetime should take a timezone 14 days
http://tracker.xemacs.org/XEmacs/its/issue861 iWontFixYourBug
u sukz 0 days
http://tracker.xemacs.org/XEmacs/its/issue862 iWontFixYourBug
i think the issue tracker is broken 0 days
http://tracker.xemacs.org/XEmacs/its/issue863 iWontFixYourBug
you guyz should work on your issue tracker 0 days
http://tracker.xemacs.org/XEmacs/its/issue864 vimRULES
Top Issues Most Discussed (2)
_____________________________
3 [Bug: 21.5-b29] customize: Set Save Done button disappeared 704 days
closed http://tracker.xemacs.org/XEmacs/its/issue803
3 error in isearch pre-command-hook 1979 days
committed http://tracker.xemacs.org/XEmacs/its/issue336
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:51 a.m.
you guyz should work on your issue tracker 0
days
http://tracker.xemacs.org/XEmacs/its/issue864 vimRULES
So I guess someone broke into the tracker...?
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:58 a.m.
Mike Kupfer writes:
> you guyz should work on your issue tracker
0 days
> http://tracker.xemacs.org/XEmacs/its/issue864 vimRULES
So I guess someone broke into the tracker...?
Not that I can tell in a quick look. Anybody can create a user, and
then create or comment on issues. That's what the tracker is *for*.
If somebody wants to DoS the tracker, they probably can. Spam it,
yup. I don't see any reasonable way to stop them, except to shut it
down. (OK, I guess we could run SpamAssassin on comments.)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
2:52 p.m.
Stephen J. Turnbull wrote:
Anybody can create a user, and
then create or comment on issues. That's what the tracker is *for*.
Indeed. But I was surprised that random vandals can close issues that
they neither opened or had assigned to them (e.g., issue298).
Are new user accounts required to have a verified email address before
they can start making changes to issues?
(OK, I guess we could run SpamAssassin on comments.)
Since this hasn't been a chronic problem, I don't think we need to
deploy SpamAssassin. But it's good to know that's an option.
Does the tracker get indexed by search engines (or do we configure the
tracker to tell them not to)? If we do decide to deploy SpamAssassin,
new attachments should be checked, too, if that's possible. (See, e.g.,
the sa4.html attachment to issue634.)
I've reproduced the list of defaced issues below (taken from the weekly
summary of changes that the tracker sends out). I guess some of them
don't really need to be reopened, but clearly some, perhaps most, of
them should be reopened. (I've already reopened issue298.)
mike
Issues Now Closed (25)
______________________
Set up backup regime 2045 days
http://tracker.xemacs.org/XEmacs/its/issue53 iWontFixYourBug
21.5 screen resize issue 2044 days
http://tracker.xemacs.org/XEmacs/its/issue79 iWontFixYourBug
Old mail archives. 2044 days
http://tracker.xemacs.org/XEmacs/its/issue129 vimRULES
update mh-e to MH-E 8 2013 days
http://tracker.xemacs.org/XEmacs/its/issue298 vimRULES
Crash when displaying progress bar (typically in fontlocking) 1991 days
http://tracker.xemacs.org/XEmacs/its/issue323 iWontFixYourBug
Streamline mail flow 1419 days
http://tracker.xemacs.org/XEmacs/its/issue582 iWontFixYourBug
Improving tooltip support 1412 days
http://tracker.xemacs.org/XEmacs/its/issue590 vimRULES
Add 'easy' keyword 1398 days
http://tracker.xemacs.org/XEmacs/its/issue616 vimRULES
hilit-pkg 1398 days
http://tracker.xemacs.org/XEmacs/its/issue619 iWontFixYourBug
Debug Assertion Failed! f:\dd\vctools\crt_bld\self_x86\crt\src 1374 days
http://tracker.xemacs.org/XEmacs/its/issue634 economicseries8
Update eldoc 1059 days
http://tracker.xemacs.org/XEmacs/its/issue730 iWontFixYourBug
emacs 21.5.29 fails to build 'executeable' 938 days
http://tracker.xemacs.org/XEmacs/its/issue749 iWontFixYourBug
No-mule XEmacs can corrupt UTF-8 files. 774 days
http://tracker.xemacs.org/XEmacs/its/issue780 iWontFixYourBug
[Bug: 21.5-b29] customize: Set Save Done button disappeared 704 days
http://tracker.xemacs.org/XEmacs/its/issue803 stephen
etags.xemacs21 generates garbled paths 661 days
http://tracker.xemacs.org/XEmacs/its/issue810 vimRULES
kp-divide 654 days
http://tracker.xemacs.org/XEmacs/its/issue812 vimRULES
small errors in behavior.el 589 days
http://tracker.xemacs.org/XEmacs/its/issue826 iWontFixYourBug
Scrolling Bug 460 days
http://tracker.xemacs.org/XEmacs/its/issue831 iWontFixYourBug
define-obsolete-function-alias is missing an optional paramete 265 days
http://tracker.xemacs.org/XEmacs/its/issue848 iWontFixYourBug
printing strings loses eq relationship 83 days
http://tracker.xemacs.org/XEmacs/its/issue858 vimRULES
xemacs seems to mis-compile parts of vm 25 days
http://tracker.xemacs.org/XEmacs/its/issue860 iWontFixYourBug
icalendar--decode-isodatetime should take a timezone 14 days
http://tracker.xemacs.org/XEmacs/its/issue861 iWontFixYourBug
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
11:36 p.m.
>>>> Mike Kupfer <mike.kupfer(a)xemacs.org> writes:
Indeed. But I was surprised that random vandals can close issues
that they neither opened or had assigned to them (e.g., issue298).
I thought I would get a mail on those issues I'm on the nosy list but
I didn't. Shouldn't I?
It seems like a lot of fields have been turned into garbage as well as
the tracker allows you to add new values to those fields. So there is
some cleaning that needs to be done.
icalendar--decode-isodatetime should take a timezone 14
days
http://tracker.xemacs.org/XEmacs/its/issue861 iWontFixYourBug
Tried to reopen that one but only alternative I found was to set it to
new. OK?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
8:09 a.m.
Mats Lidell writes:
>>>>> Mike Kupfer <mike.kupfer(a)xemacs.org>
writes:
> Indeed. But I was surprised that random vandals can close issues
> that they neither opened or had assigned to them (e.g., issue298).
I thought I would get a mail on those issues I'm on the nosy list but
I didn't. Shouldn't I?
You should get mail, but it might be broken.
I'll look at that later. First I wanted to clean up as many of the
changed keywords as possible.
> icalendar--decode-isodatetime should take a timezone
14 days
> http://tracker.xemacs.org/XEmacs/its/issue861 iWontFixYourBug
Tried to reopen that one but only alternative I found was to set it to
new. OK?
I guess so.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
8:46 a.m.
>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
I'll look at that later. First I wanted to clean up as many of
the
changed keywords as possible.
No problem. Just thought it could be a piece of info if we were hacked
but I guess our openness can explain why this can happen.
Is it possible to tighten the security a bit so that we don't get this
over and over again?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
9:15 a.m.
Mats Lidell writes:
Is it possible to tighten the security a bit so that we don't get
this
over and over again?
I don't know. For example, it's not hard to lock things down so that
only reviewers can change status and only I can add reviewers, but
then you need a reviewer to intervene to change a bug from "new" to
"verified", or to assign a non-reviewer person as the bug "owner".
It
kinda depends on which "bits" need tightening.
I don't think it's harmful to tighten up the keywords so that only
reviewers can edit them, for one improvement. But I don't know how
easy that would be to do.
Suggestions welcome.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4102
days inactive
4105
days old
7 comments
4 participants
participants (4)
-
Mike Kupfer -
Stephen J. Turnbull -
The XEmacs Package Smoketest -
XEmacs Issue Tracking System