(Spec 0.9) Issue in MediaItem

[Kless]

In the description says: "integer, number of comments on the photo."

And I think that it should say: integer, number of comments on the
media item.".


http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/OpenSocial-Specification.html#opensocial.MediaItem.Field.NUM_COMMENTS

[Paul Lindner]

Should we have a bug-tracker or wiki page to keep track of these things?

I agree with the terminology changes here, so +1..

[Lane LiaBraaten]

I prefer using an issue tracker for these small things, and good news is we already have one set up: http://code.google.com/p/opensocial-resources/issues/entry?template=Specification%20Issue

I thought using the wiki for the larger proposals worked well in the last iteration.  It feels like people are still working on getting v0.9 into production (and not yet ready to start up the next round of discussions), but I'd be interested to hear others' opinions.

Either way we've probably had enough v.NEXT things proposed to start a tracking page on the wiki.

-Lane

[Paul Lindner]

Seems a bit of a mess at the moment.  I see a smattering of tickets here:

http://code.google.com/p/opensocial-resources/issues/list?can=2&q=container=API

Can we get this cleaned up and more tightly integrated?

[Arne Roomann-Kurrik]

Some concerns I have about using that tracker:

1.) There's a lot of orkut developer spam in the tracker (people think it's a general orkut issue tracker).  As long as you use the template Lane linked to, then this is migitated by viewing a filtered list of issues:

http://code.google.com/p/opensocial-resources/issues/list?can=2&q=container%3AAPI&colspec=ID+Type+Container+Stars+Summary+Status&cells=tiles

Still, it's annoying to deal with.

2.) Using this tracker only really works if everyone uses it.  If we want a tracker to be part of the spec change process, I'm for it, but we should amend the process or assign someone to babysit the tracker to make sure things are kept in sync (a headache).

~Arne

On Tue, Jun 23, 2009 at 12:43 PM, Lane LiaBraaten <llia...@google.com> wrote:

[Scott Seely]

Is the idea that we will close the issues by creating a patch?

 

Also, when folks find a spec issue, does anyone have an issue with the submitter also including a spec patch? I have no problem with folks asking for assistance in creating patches if the IETF XML format is confusing to them.

 

-Scott

[Bess Ho]

http://code.google.com/p/opensocial-resources/issues/entry?template=Specification%20Issue

Need to add more category items on pull down menu. It only offers iGoogle, Orkut, hi5.

--
Bess Ho

[Arne Roomann-Kurrik]

That would be ideal.

One note though - because of the orkut spam, that tracker is out of quota for attachments (a lot of the users attached uncompressed bitmaps to their issue reports).  Deleting all of the attachments would have to be done manually to free up quota since there isn't a bulk delete tool in the admin console.  I can do this if people feel it's important, but it'll take a bit of time.

~Arne

[Arne Roomann-Kurrik]

On Tue, Jun 23, 2009 at 12:53 PM, Bess Ho <bes...@gmail.com> wrote:

http://code.google.com/p/opensocial-resources/issues/entry?template=Specification%20Issue

Need to add more category items on pull down menu. It only offers iGoogle, Orkut, hi5.

This is irrelevant - the containers available are the ones that had some sort of developer presence checking the tracker (what use is reporting issues if nobody who can fix them knows uses the tracker?).  Hi5 should probably be taken off of that list now.

~Arne
 

[Bess Ho]

Arne,

I encounter this type of manual work. You may want to consider writing automation script to do repeated tasks page by page.

I used this browser scripting tool to reduce 2 hrs job to 5min such as clicking check boxes. You can reuse the script by running it on schedule or background. See if this will work for you. It is too painful for SW engineer to do internship type of tasks.

http://www.iopus.com/imacros/firefox/

--
Bess Ho

[Arne Roomann-Kurrik]

On Tue, Jun 23, 2009 at 1:06 PM, Bess Ho <bes...@gmail.com> wrote:

Arne,

I encounter this type of manual work. You may want to consider writing automation script to do repeated tasks page by page.

I used this browser scripting tool to reduce 2 hrs job to 5min such as clicking check boxes. You can reuse the script by running it on schedule or background. See if this will work for you. It is too painful for SW engineer to do internship type of tasks.

http://www.iopus.com/imacros/firefox/

Thanks, Bess.  I just got the quota increased on the project tracker.

~Arne
 

[Dan Peterson]

Off list, as a stop-gap, I suggested Arne request more Google Code project quota.

-Dan

---

From: opensocial-an...@googlegroups.com <opensocial-an...@googlegroups.com>
To: opensocial-an...@googlegroups.com <opensocial-an...@googlegroups.com>
Sent: Tue Jun 23 13:06:08 2009

Subject: [opensocial-and-gadgets-spec] Re: (Spec 0.9) Issue in MediaItem

Arne,

I encounter this type of manual work. You may want to consider writing automation script to do repeated tasks page by page.

I used this browser scripting tool to reduce 2 hrs job to 5min such as clicking check boxes. You can reuse the script by running it on schedule or background. See if this will work for you. It is too painful for SW engineer to do internship type of tasks.

http://www.iopus.com/imacros/firefox/