Éric Araujo mer...@netwok.org added the comment:
The problem with the table is that it may suggest that users need to choose one
of mnemonic or vim-style. A simpler alternative might be something like:
Keyboard Shortcuts
first message: *f* or *h*
previous message: *p* or *k
Éric Araujo mer...@netwok.org added the comment:
Allowing all developers to reclassify messages sounds good.
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http://psf.upfronthosting.co.za/roundup/meta/issue120
Éric Araujo mer...@netwok.org added the comment:
Are you aware of the issues coming with the use of accesskeys? If not, I’ll
dig up the links.
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http://psf.upfronthosting.co.za/roundup
Éric Araujo mer...@netwok.org added the comment:
I don’t think it would be a waste of time to fix the normal search too.
--
status: resolved - chatting
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http
New submission from Éric Araujo mer...@netwok.org:
It has happened more than one time that people put an ssh or private https URI
in the remote repo field, which makes Roundup error when someone wants to
create a patch. If possible, access should be checked when a repo is added.
(FTR
New submission from Éric Araujo mer...@netwok.org:
There seems to be a regression with diff generation: if you look at
http://bugs.python.org/file22839/bc362109eed8.diff (created from the repo
http://bitbucket.org/jaraco/cpython-issue12666 added to
http://bugs.python.org/issue12666), you’ll
Éric Araujo mer...@netwok.org added the comment:
+1. What about files?
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http://psf.upfronthosting.co.za/roundup/meta/issue267
Éric Araujo mer...@netwok.org added the comment:
FTR, the list on the b.p.o page does not exceed the width of my screen, whereas
b.p.o/issue does.
Ezio, do you have a public instance of Roundup with your patch applied
somewhere, or screenshots? I can’t draw TAL or CSS in my head
Éric Araujo mer...@netwok.org added the comment:
That sounds very good! I think you can just go ahead and commit, we’ll get
feedback on python-dev after real use just like for previous tracker
improvements.
On a related note, I find the use of GETs distasteful, but that’s Roundup
Éric Araujo mer...@netwok.org added the comment:
+1.
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http://psf.upfronthosting.co.za/roundup/meta/issue406
Éric Araujo mer...@netwok.org added the comment:
Which browser is the reference these days for CSS compliance? My old Iceweasel
(Firefox) 3.5.19 does not display the info in one small cell on the left.
___
PSF Meta Tracker metatrac
Éric Araujo mer...@netwok.org added the comment:
Two things I think would be useful (tell me if opening other reports would be
better than writing here):
- A link from the Rietveld issue to the Roundup one
- When someone writes a message on Rietveld, make them nosy on Roundup
Éric Araujo mer...@netwok.org added the comment:
Can you try changing your Rietveld name to match your Roundup one?
http://bugs.python.org/review/settings
--
nosy: +eric.araujo
status: unread - chatting
___
PSF Meta Tracker metatrac
Éric Araujo mer...@netwok.org added the comment:
I don’t have that. What’s your OS and browsers? (names and versions)
--
nosy: +eric.araujo
status: unread - chatting
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http
Éric Araujo mer...@netwok.org added the comment:
I don’t find anything wrong with the attached message (BOMs, control
characters). Maybe Martin can have a look at the logs to find a more detailed
error message.
--
nosy: +eric.araujo, loewis
status: unread - chatting
Éric Araujo mer...@netwok.org added the comment:
I think the bugs page in the standard docs is fine as it is: a minimal page
with links. As it is released with Python, too much detail would become
obsolete and do more harm than good.
The devguide should IMO be the main page to document
Éric Araujo mer...@netwok.org added the comment:
repo#branch is a supported format, not a convention for notation. For example,
I always recommend using “hg clone http://hg.python.org/cpython#default” to
avoid pulling 2.x branches.
___
PSF
Éric Araujo mer...@netwok.org added the comment:
How did it fail in a browser? It does not link to a fragment of the page, but
the URI prior to the # sign still references a clonable Mercurial repo.
About the schema: sure, no need to change it.
Thanks for supporting repo#branch
Éric Araujo mer...@netwok.org added the comment:
My GSoC student found the reason of the problem: When we put a full Mercurial
URI like http://blah#branch, the patch generation fails, we have to go to the
edit repo form (on another page) and fill in separately the base URI and the
branch
Éric Araujo mer...@netwok.org added the comment:
In general, duplicating browser UI in HTML (like those “go to top” links) is a
mistake IMO. The End key (and similar controls) works.
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
Éric Araujo mer...@netwok.org added the comment:
Thanks a bunch for fixing this, you made my day!
--
nosy: +eric.araujo
status: resolved - chatting
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http
Éric Araujo mer...@netwok.org added the comment:
Reclassification requires elevated tracker privileges, for a good reason
Right. Is there a list of users with admin rights somewhere?
If triage people don't have access to this function that should probably be
changed. [...] (The interface
22 matches
Mail list logo
