Talk:LlSetPayPrice

Jira issue

It seems that VWR-8744 is fixed. Should it be crossed out or removed from here? -- Fred Gandt ^{(talk|scripts|contribs)} 00:32, 10 February 2010 (UTC)

Heyas :)

The info about the bug is stored at Template:Issues/VWR-8744. These bug templates use Template:Issue, which provides parameters to adjust the proper status. I changed the issue accordingly, which displays it striked through in the article. Guess it's good to leave it there for future reference.

-- ^{(talk|contribs)} 06:28, 10 February 2010 (UTC)

Hiya. Thanx for explaining Zai. I may actually get the hang of the templates one day. For now I am still trying to master LSL. See ya in-world! -- Fred Gandt ^{(talk|scripts|contribs)} 15:25, 10 February 2010 (UTC)

We keep the dead issues listed on the page for two reasons:

1. So there is a record of the bug having existed and it's resolution is documented. If the information were stripped from the article, it would be harder for the user to confirm the status of the bug and the functionality.
2. If the bug comes back, it's easier for a reader of the article to reopen the correct jira. It reduces the chances of a repost/duplicate bug report.

I do worry though that folks won't look for/in the "Issues" subsection when they don't find it in the "Important Issues" subsection. Maybe a link should be added to the important issues subsection (when the two do not match)? -- Strife ^{(talk|contribs)} 15:33, 10 February 2010 (UTC)

p.s we list the occasional feature request because otherwise jira gets flooded with duplicate requests. Some feature requests are universally attractive. It was my original intention not to list them, I thought they would crowd the documentation. But by not having a place for them lead them to be listed as caveats and they crowded out the useful caveats. -- Strife ^{(talk|contribs)} 15:39, 10 February 2010 (UTC)

p.p.s It's important to remember that while this is a technical resource it's one for humans. There is a social aspect that cannot be denied. We document what is there, but there is a flow to the community and it creates edies & rappids around the content. While it isn't our goal to map the river, it would be stupid not to point out the waterfalls. (I'm done rambling on about random things) -- Strife ^{(talk|contribs)} 15:53, 10 February 2010 (UTC)

Eddies and Freddies Strife! Eddies and Freddies... I thought at the start of this that a resolved jira should be crossed through. I thought that happened automatically though. Good job you and Zai are about to fix all this stuff or the wiki might get wakky. I trust your back has mended well ;-) -- Fred Gandt ^{(talk|scripts|contribs)} 16:50, 10 February 2010 (UTC)

Automatic? Not at all. It's really one of those projects that evolved; little ideas pushing the implementation forward. It started out as grass roots and non-standardized; the information was disorganized. Part of the problem was that some of the caveats were infact bugs. We don't want users depending upon bugs thinking they are features (just say "No!" to misfeatures). We started out putting the bug definitions in the articles but the content duplication was annoying. The solution was to make stub-content-templates (generally it's considered taboo to put content in the Template: namespace; Zai then ran away with the idea and used it for the KB articles).

As to the future: I'd really like to list more than just a title for the bug, maybe a couple of lines describing the bug. The reason being I want to eliminate the explanitory caveats. I've considered writing a mediawiki extension for jira integration but ... I don't remember what haulted the project (not a [clew]). It would be nice to have something to automate (aspects of) the task, its tedious and prone to error (this might be my next GM project). I do have one misgiving about making it entirely automatic, some bugs are total and utter BS. I much prefer picking and choosing, and the ability to rename them (as sometimes the names are less than discriptive). It would be nice to have it autoupdate the status/resolution. As to my health, I have back pain that comes and goes but it's not bad (the doctor says I shouldn't run a marathon... not that I was planning to with my flat feet); the ankle is still a bit swollen but it's not a bother (though twisting the leg does give a tinge of discomfort, not something I do often but I don't avoid it either). Over all I'm doing pretty well, but I do need a job again (the temp job I had ended x_x). -- Strife ^{(talk|contribs)} 04:01, 11 February 2010 (UTC)

Hehe, I missed you (^_^) Really!

Yeah, it seemed to be some kind of evolution that started with your template-ish use of the articles about constants, to populate the table in llSetPrimitiveParams. Then the subpages for version numbers of Template:Multi-lang and then the issues template. It turned out to be a benefit for me to adapt these ideas in order to turn them into the Kbl10n templates. Had the benefit that I could re-use the information in various ways (interlinking, documentation, bot file creation). Tho that project expired with the KB2Wiki Pilot, which moved the KB from its old home in Parature over to the wiki. It made the 1-template-per-article-need moot, as Multi-lang could now be used for the linking. I'm still somehow sad about the loss of the semi-automated documentation, but might turn it into a manual documentation in the future. I'll have to clean the artifacts some day, when I find some time...

As for the automated status updates from JIRA: That certainly sounds cool!

Sad to read about the job issues :( I'm not yet sure either how to survive after March (besides some rly cool part time job). Maybe we should start a company? :P

I think I managed to get the conversation completely off-topic now ^_^

-- ^{(talk|contribs)} 08:03, 11 February 2010 (UTC)

P.S.: Ontopic: History (^_^) -- ^{(talk|contribs)} 09:25, 11 February 2010 (UTC)

It's really odd that you two and another friend in SL are having such trouble with work. Zai is a genius, Strife is a wizard and my other friend is expert in 3D modeling and more coding languages than I have heard of. He was offered 8 USD per hour to do games design. He could earn more than that working as the janitor! I guess all you genius types will just have to settle for fixing everyone else's mess for now. Thanx to you both.

I'm glad to hear your back is basically ok Strife. You were truly very lucky (not the slipping and falling...the not being a write-off).

Zai.... Start a company? Why not? Everyone else seems to be doing it. Lets face it, look at twitter. Massive success for that?? O.o I could burp a better idea.

Oh and btw ... I only meant that I thought the jira resolutions were auto updated. LL should pay the two of you for all you do here. -- Fred Gandt ^{(talk|scripts|contribs)} 11:06, 11 February 2010 (UTC)

Oh, twitter rocks! Someone is lazy with tweeting tho ^^

But let's take this to a more appropriate venue. How about Google wave? I just shot Strife an invitation. @Fred: I don't have your mail addy, tho when you feel comfortable with sharing it, send it to me in an offline IM and I'll send you an invitation as well.

Oh and: ty for the genius ^_^; *flattered*

-- ^{(talk|contribs)} 11:37, 11 February 2010 (UTC)

/me smiles. My email addy is on wiki record for use Zai. Not by accident either. You and Strife are more than welcome to use it. But I'll send it to you as soon as I log back in. The thing about social networking....why use anything but SL? Farcebook? MyCrass? Twits? No thanx! -- Fred Gandt ^{(talk|scripts|contribs)} 13:59, 11 February 2010 (UTC)