[sldev] Code Dusting

[JB Kraft]

I was kind of thinking the other way around. I wouldn't expect that a Linden
would take the time to muck through the jira looking for someone doing a
small refactoring or decoupling but if there was hit list of some sort that
came out of the lab, a TODO of sorts, we folks outside the ship would at
least know that something was on the radar internally and could then make
the appropriate noises, find the right people and verify the implementation
plan, etc, before proceding into the code. I was looking for such a thing
before I sat down with this one particularly but could find nothing on it so
I figured it should be safe to do it without treading on some other work.


On Wed, May 28, 2008 at 12:57 PM, Lawson English <lenglish5 at cox.net> wrote:

> Robin Cornelius wrote:
>
>> On Wed, May 28, 2008 at 3:01 AM, JB Kraft <kwerks.sl at gmail.com> wrote:
>>
>>
>>> Hi all. I had some spare time today so I spent a few hours implementing
>>> gridinfo class as a way to load other grids via an xml file into the
>>> login
>>> panel. The hard coded ones were getting annoying as I jump from aditi,
>>> agni,
>>> local, opensim, etc., and the mac burying the arguments.txt file is no
>>> help
>>> either. So, tested, tada and I figured I'd create a patch for it and
>>> stick
>>> it on the jira, but first I'd make sure it worked against the 1.20.8
>>> code.
>>> Well lo and behold, someone already did most of the work for this between
>>> 1.20.5 and 1.20.8 in llviewernetwork.*, etc. by creating a LLViewerLogin
>>> class and at least making the lookup vectored, tho no xml load as of yet
>>> that I can see. (I can add that tho ;)  Anyway, no big deal but it did
>>> give
>>> me a shiver that I could have wasted a lot more time then I did, so I am
>>> wondering where a list of trivial features like this for upcoming
>>> versions
>>> might be available, if at all. I consider stuff like this cleaning rather
>>> then a real feature addition and the JIRA seems like a good place for
>>> this
>>> stuff to just get lost really. I don't know. It doesn't seem like
>>> something
>>> Joe Resident would care about thats for sure but the code sure could use
>>> this type of abstracting, refactoring, etc. So am I missing something? Do
>>> I
>>> pore over the wiki and jira before doing anything? Post here? Is it a
>>> crap
>>> shoot? Do the Lindens communicate what they are working at at this level,
>>> and if so, how, where, or should I not bother wasting my time on stuff
>>> like
>>> this?
>>>
>>>
>>>
>>
>> The only thing i can suggest is that if you are going to work on a
>> feature, post a JIRA entry and at least keep ideas and progress
>> documented, its also probably a very good idea to mention it at Rob's
>> hours too and probably discuss here. I know it can be lost in jira but
>> if you make a little noise it may be noticed.
>>
>> As you said this was quite a small feature so may be it just ground
>> someone in the dev team and they though, "rats, about time this was
>> fixed" and just did it.
>>
>> Actually this is a feature i started looking at too and i am just as
>> guilty of not telling anyone ;-)
>>
>> if your going to do the xml load too, please JIRA it now ;-)
>>
>>
>
> Perhaps a status for "new feature" of "non-linden project started" or
> something to indicate that you are in the process of working on it. "Fix
> pending" suggests that the task is done, but "in progress" suggests that its
> been taken into the internal Linden jira and there's no clear way of showing
> that a non-linden has started working on it, and just searching for ALL new
> features means you have to wade through literally thousands of *requests*
> for new features to see if someone is doing something.
>
> Lawson
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20080528/e91f2cd6/attachment.htm