On 06/13/2013 11:22 AM, Chris McMahon wrote:
> In recent times QA has expanded our automated cross-browser testing: we
> re-organized our builds, pointed the tests to beta labs wikis as well as
> test2wiki, and we've written a number of new tests. In the course of that
> a lot of our builds for In
On Fri, Jul 5, 2013 at 3:07 PM, Matthew Flaschen wrote:
> Yes, IE is particularly an issue for this, since it often requires a
> fair amount of specific work. However, our browser compatibility
> requirements in general are somewhat in limbo. James Forrester marked
> the guidelines at https://ww
Please see the proposal at:
http://www.mediawiki.org/wiki/Manual_talk:Coding_conventions/PHP#Recommending_some_minimum_documentation_practices
Ryan Kaldari
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/l
Hello! Our current generated documentation[1] uses doxygen, and
leaves... a number of things to be desired - such as:
1. Not be tortoise slow
2. Have usable search
3. Prettier interface
I was looking around for alternatives, and ran into phpdocumentor2[2].
The project still seems active (latest c
Could we maybe get use PHPDoc to generate MediaWiki docs, so that we can
compare them side-by-side.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
www.whizkidztech.com | tylerro...@gmail.com
On Fri, Jul 5, 2013 at 8:36 PM, Yuvi Panda wrote:
> Hello
>
> Could we maybe get use PHPDoc to generate MediaWiki docs, so that we can
> compare them side-by-side.
This is an important request because (to play devil's advocate here a
little bit)...
> 1. Not be tortoise slow
Pretty sure this only matters because we do continuous integration -- we
probab
Ack -- my [1] reference was supposed to be https://www.ohloh.net/ but
thinking about it; we want documentation search not code search and ideally
it would be opensource... but my point remains! We need a cross
language/documentation search system.
~Matt Walker
Wikimedia Foundation
Fundraising Tech
On Sat, Jul 6, 2013 at 6:36 AM, Matthew Walker wrote:
>> 1. Not be tortoise slow
> Pretty sure this only matters because we do continuous integration -- we
> probably don't need to do this for every commit...? Maybe once a day?
>
> In any case -- who says PHPDoc is any faster.
Slow to use, not sl
On Sat, Jul 6, 2013 at 6:41 AM, Matthew Walker wrote:
> Ack -- my [1] reference was supposed to be https://www.ohloh.net/ but
> thinking about it; we want documentation search not code search and ideally
> it would be opensource... but my point remains! We need a cross
> language/documentation sea
On 7/5/13, Yuvi Panda wrote:
> On Sat, Jul 6, 2013 at 6:36 AM, Matthew Walker
> wrote:
>>> 1. Not be tortoise slow
>> Pretty sure this only matters because we do continuous integration -- we
>> probably don't need to do this for every commit...? Maybe once a day?
>>
>> In any case -- who says PHP
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 alter
11 matches
Mail list logo