Yuvi Panda writes:
Hello! Our current generated documentation[1] uses doxygen, and
leaves... a number of things to be desired - such as:
What about a bug report [or a patch ;-)]?
Jan
1. Not be tortoise slow
2. Have usable search
3. Prettier interface
I was looking around for
Le 06/07/13 02:36, Yuvi Panda a écrit :
Hello! Our current generated documentation[1] uses doxygen, and
leaves... a number of things to be desired - such as:
1. Not be tortoise slow
I have originally migrated from PHPDoc to Doxygen because it was blazing
fast to generate doc. Doxygen also
Why you want to move from it? Just create a new project on labs
(tools) and cron a job.
It only need to checkout latest MW and regenerate the documentation,
this is so simple you could even have multiple of these interfaces and
everyone could pick what they like
On Sat, Jul 6, 2013 at 10:19 AM,
On 07/03/2013 09:22 AM, Sumana Harihareswara wrote:
The linux.conf.au call for talks closes July 6th, *Australian time*.
http://linux.conf.au/media/news/1
CFP Extension Announced linux.conf.au 2014 - linux.conf.au !!!
Now it's July 20.
http://linux.conf.au/media/news/27
I also think that
Le 02/07/13 07:03, Tim Starling a écrit :
Many RFCs are just good ideas, often attracting no comment because
there is no obvious criticism of the feature at the level of detail
given by the proposer. This raises the question of whether an RFC is a
feature request (like a Bugzilla enhancement)
On 07/05/2013 06:44 PM, Brion Vibber wrote:
These are going to balance out differently depending on the wiki feature,
on the browser features it depends on, on what the feature does/is used
for, and the relative ease of user workarounds like updating or using
another browser.
Agreed. I think
On Thu, Jun 20, 2013 at 7:42 AM, Željko Filipin zfili...@wikimedia.orgwrote:
Is there a way to enable browsertests role in a similar way, without
touching files that are under git?
This is now implemented in https://gerrit.wikimedia.org/r/#/c/72343/. It
needs a lot of testing, especially on
