headers
Bryan Tong Minh | 1 Sep 2007 20:26
Picon
Gravatar

Re: New branch ApiEdit_Vodafone

I took a more thorough look through the docs, and have a question
about those "tokens" needed for editting. Are you forced to pass those
tokens through a post request? Or can you also use the old cookie way?

upfile=<path_to_file>. I assume that that should be the actual file contents?

upsourcetype = <file>. And what does this mean? The mimetype?

Thanks for your great work!

Bryan

On 8/31/07, Frisa, Raquel, VF-ES (rfrisar)
<raquel.frisa@...> wrote:
> My will is to have it as soon as possible, but it doesn't only depend on us.
>
> Raquel
>
> -----Mensaje original-----
> De: mediawiki-api-bounces@...
[mailto:mediawiki-api-bounces@...] En nombre
de Bryan Tong Minh
> Enviado el: jueves, 30 de agosto de 2007 11:56
> Para: MediaWiki API announcements & discussion
> Asunto: Re: [Mediawiki-api] New branch ApiEdit_Vodafone
>
> Great news! When can we expect this to be enabled?
>
> Bryan
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nick Jenkins | 3 Sep 2007 09:54
Picon
Gravatar

Re: New branch ApiEdit_Vodafone

> > Great news! When can we expect this to be enabled?
> > 
> > Bryan
>
> My will is to have it as soon as possible, but it doesn't only depend on us.
> 
> Raquel

From a software release and stability perspective, whilst also trying to maximize speed, it
would probably ideally go down something like this:

* Api Edit ongoing development in a branch (as is currently happening).
* MediaWiki 1.11 released. Does not include Api Edit, because it's a substantial new feature
  and therefore should be allowed sufficient time to stabilize and be thoroughly tested
  before being included in a stable MediaWiki release.
* One week or so passes after 1.11 release so as to deal with any general post-release issues
  (e.g. people with different configurations find that things that work okay for us are broken
  for them)
* Api Edit deemed by Vodafone developers & Yuri to be ready for public consumption.
* General announcement sent to wikitech-l and this list, announcing the imminent merge of Api Edit,
  giving examples of how to use Api Edit, how to test it, things to test, reminder of how to log
  bugs in bugzilla under the "API" category in the event of finding problems, pointers to
  the documentation, pointers to this mailing list, and so forth.
* Perhaps one last pre-Api-edit scap / sync to servers.
* Api Edit merged into SVN trunk. I am assuming that the Vodafone folks are mostly Mon-Friday
  9-to-5 folks, and therefore the merge should probably happen on a Monday or a Tuesday, rather
  than a Thurs / Fri / Sat / Sun, so that they are accessible for a few days after the merge.
* Other developers get a few days to play with the merged Api Edit on their SVN test machines,
  try it, and test it, etc. Presumably some bugs are logged, some bugs are fixed, there's some
  standard whinging about instead of doing A can it do B, etc.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Frisa, Raquel, VF-ES (rfrisar | 3 Sep 2007 10:31

Re: New branch ApiEdit_Vodafone

Umm,  indeed, we're 8-to-3 folks (summer time), but from 17th we'll be
8.30-to-5.30 folks.  And we're based in Spain, GMT+1.
Anyway, our position is to facilitate as much as we can all this
process, so we'll be flexible for the "important" days, , it would be
great to make it come true in three weeks!

At this moment:

- Api Edit deemed by Vodafone developers & Yuri -->  we've already
started with that.
- Examples about how to use Api Edit. --> It's already public at:
http://www.mediawiki.org/wiki/API:Changing_wiki_content 
- Examples about what to test and how to test -->  I don't really know
what it is expected.  Could someone provide me with an example given
before?  It's our first time, :-))  We are just offering a new interface
to existing functionality in Mediawiki Core: we're not changing core
functionality to edit, upload, etc.. so the things to test are the same
as in the graphical mediawiki.

Raquel 

-----Mensaje original-----
De: mediawiki-api-bounces@...
[mailto:mediawiki-api-bounces@...] En nombre de Nick
Jenkins
Enviado el: lunes, 03 de septiembre de 2007 9:55
Para: MediaWiki API announcements & discussion
Asunto: Re: [Mediawiki-api] New branch ApiEdit_Vodafone

> > Great news! When can we expect this to be enabled?
(Continue reading)

Permalink | Reply | 2 comments |
headers
Yuri Astrakhan | 3 Sep 2007 19:13
Picon

Re: New branch ApiEdit_Vodafone

Nick, thank you for an excellent comment - I couldn't have said it better :)

On 9/3/07, Nick Jenkins <nickpj@...> wrote:
> > > Great news! When can we expect this to be enabled?
> > >
> > > Bryan
> >
> > My will is to have it as soon as possible, but it doesn't only depend on us.
> >
> > Raquel
>
> From a software release and stability perspective, whilst also trying to maximize speed, it
> would probably ideally go down something like this:
>
> * Api Edit ongoing development in a branch (as is currently happening).
> * MediaWiki 1.11 released. Does not include Api Edit, because it's a substantial new feature
>   and therefore should be allowed sufficient time to stabilize and be thoroughly tested
>   before being included in a stable MediaWiki release.
> * One week or so passes after 1.11 release so as to deal with any general post-release issues
>   (e.g. people with different configurations find that things that work okay for us are broken
>   for them)
> * Api Edit deemed by Vodafone developers & Yuri to be ready for public consumption.
> * General announcement sent to wikitech-l and this list, announcing the imminent merge of Api Edit,
>   giving examples of how to use Api Edit, how to test it, things to test, reminder of how to log
>   bugs in bugzilla under the "API" category in the event of finding problems, pointers to
>   the documentation, pointers to this mailing list, and so forth.
> * Perhaps one last pre-Api-edit scap / sync to servers.
> * Api Edit merged into SVN trunk. I am assuming that the Vodafone folks are mostly Mon-Friday
>   9-to-5 folks, and therefore the merge should probably happen on a Monday or a Tuesday, rather
>   than a Thurs / Fri / Sat / Sun, so that they are accessible for a few days after the merge.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Platonides | 3 Sep 2007 20:10
Picon

Re: New branch ApiEdit_Vodafone

Raquel Frisa escribió:
> Umm,  indeed, we're 8-to-3 folks (summer time), but from 17th we'll be
> 8.30-to-5.30 folks.  And we're based in Spain, GMT+1.
> Anyway, our position is to facilitate as much as we can all this
> process, so we'll be flexible for the "important" days, , it would be
> great to make it come true in three weeks!
> 
> At this moment:
> 
> - Api Edit deemed by Vodafone developers & Yuri -->  we've already
> started with that.
> - Examples about how to use Api Edit. --> It's already public at:
> http://www.mediawiki.org/wiki/API:Changing_wiki_content 
> - Examples about what to test and how to test -->  I don't really know
> what it is expected.  Could someone provide me with an example given
> before?  It's our first time, :-))  We are just offering a new interface
> to existing functionality in Mediawiki Core: we're not changing core
> functionality to edit, upload, etc.. so the things to test are the same
> as in the graphical mediawiki.

Examples like http://www.mediawiki.org/w/api.php
http://www.mediawiki.org/wiki/API:Changing_wiki_content already has some 
information but adding it to the "information" page would be good too.

 From http://www.mediawiki.org/wiki/API:_Changing_wiki_content-_Upload 
"ns: 6       Show title’s namespace except when ns=0"
Does that mean that i could uipload a file to the main namespace??

Nick, on the "Other developers get a few days to play with the merged 
Api Edit on their SVN test machines" i'd also make it available on
(Continue reading)

Permalink | Reply | 1 comment |
headers
Yuri Astrakhan | 3 Sep 2007 22:05
Picon

Re: New branch ApiEdit_Vodafone

On 9/3/07, Platonides <platonides@...> wrote:
> Raquel Frisa escribió:
> > Umm,  indeed, we're 8-to-3 folks (summer time), but from 17th we'll be
> > 8.30-to-5.30 folks.  And we're based in Spain, GMT+1.
> > Anyway, our position is to facilitate as much as we can all this
> > process, so we'll be flexible for the "important" days, , it would be
> > great to make it come true in three weeks!
> >
>
> Examples like http://www.mediawiki.org/w/api.php
> http://www.mediawiki.org/wiki/API:Changing_wiki_content already has some
> information but adding it to the "information" page would be good too.

Yes, the API doc pages should be substantially edited to work out the
exact API call semantics. Please remember that unlike the web
interface, changing API is *very* disruptive, so lets get this done
right from the start. Rushing to market is baaaaad, ok?! :)
>
>  From http://www.mediawiki.org/wiki/API:_Changing_wiki_content-_Upload
> "ns: 6       Show title's namespace except when ns=0"
> Does that mean that i could uipload a file to the main namespace??
>
Fixed.
>
> Nick, on the "Other developers get a few days to play with the merged
> Api Edit on their SVN test machines" i'd also make it available on
> test.wikipedia.org A client interface it is, you shouldn't need a local
> mediawiki install.
>
Yep, needs Brion's blessing.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frisa, Raquel, VF-ES (rfrisar | 5 Sep 2007 12:39

Re: New branch ApiEdit_Vodafone

The API can be used by third party applications, and not only by web applicatiosn...  In our case, we are using
it for a client on a mobile device and thus no cookies are supported, that's why all information stored in
cookies must be managed through the request.  POST is just our election, we feel more conformate passing
sensible information via POST.

About upfile --> that's right, the file contents.

upsourcetype = yes mime-type.  Currently, only images can be uploaded, but we have plans to upload also video/audio.

I take the point to add examples to the docs!

Raquel

-----Mensaje original-----
De: mediawiki-api-bounces@...
[mailto:mediawiki-api-bounces <at> lists.wikimedia.org] En nombre de Bryan Tong Minh
Enviado el: sábado, 01 de septiembre de 2007 20:26
Para: MediaWiki API announcements & discussion
Asunto: Re: [Mediawiki-api] New branch ApiEdit_Vodafone

I took a more thorough look through the docs, and have a question
about those "tokens" needed for editting. Are you forced to pass those
tokens through a post request? Or can you also use the old cookie way?

upfile=<path_to_file>. I assume that that should be the actual file contents?

upsourcetype = <file>. And what does this mean? The mimetype?

Thanks for your great work!
(Continue reading)

Permalink | Reply | 0 comments |
headers
Magnus Manske | 14 Sep 2007 13:53
Gravatar

api.php links messed up

When going to the api.php page on wikimedia projects, all the example
links have &amp; in the URLs, which breaks them.

Just FYI.

Magnus
Permalink | Reply | 2 comments |
headers
Bryan Tong Minh | 14 Sep 2007 16:49
Picon
Gravatar

Re: api.php links messed up

http://bugzilla.wikimedia.org/show_bug.cgi?id=11296

Caused by a fix of an older bug I reported but am unable to find now.

Bryan

On 9/14/07, Magnus Manske <magnusmanske@...> wrote:
> When going to the api.php page on wikimedia projects, all the example
> links have &amp; in the URLs, which breaks them.
>
> Just FYI.
>
> Magnus
>
> _______________________________________________
> Mediawiki-api mailing list
> Mediawiki-api@...
> http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
>
Permalink | Reply | 1 comment |
headers
Daniel Cannon | 14 Sep 2007 20:06
Picon

Re: api.php links messed up


Bryan Tong Minh wrote:
> http://bugzilla.wikimedia.org/show_bug.cgi?id=11296
> 
> Caused by a fix of an older bug I reported but am unable to find now.
> 

The relevant bug was 11158[1] and the fix was r25742[2]. There is,
however, more at play here than just a simple jsonfm formatting problem;
in particular, this bug presented a potentially serious security
vulnerability that prompted a security release. As such, we need to find
a way to fix the link formatting without reintroducing the
vulnerability, which I will be working on.

For the time being, please just hold tight, and do note that after
following a bad link, you can usually just replace "&amp;" with "&" in
the URL to get a working link.

[1] http://bugzilla.wikimedia.org/show_bug.cgi?id=11158
[2] http://svn.wikimedia.org/viewvc/mediawiki?view=rev&revision=25742

--
Daniel Cannon (AmiDaniel)

http://amidaniel.com
cannon.danielc@...
Permalink | Reply | 0 comments |

Gmane