Any preference for one or the other?  If we keep both, I'd probably
want to rename the 'Lurker' one to better distinguish them.

 - Ken

On Mon, Feb 7, 2011 at 11:29 AM, Patrick Bouffard
<bouffard@eecs.berkeley.edu> wrote:
> Looks great Ken. Thanks for implementing that!
>
> Pat
>
> On Mon, Feb 7, 2011 at 9:44 AM, Ken Conley <kwc@willowgarage.com> wrote:
>> I done two prototypes here:
>>
>> http://www.ros.org/wiki/KenConley
>>
>> <<Lurker(search/20380101.000000.00000000@th:d2ff88fe)>>
>> <<LurkerSearch(th:d2ff88fe ml:ros-users)>>
>> <<LurkerSearch(roslaunch machines ml:ros-users)>>
>>
>> In the case of LurkerSearch, you can use any number of search arguments.
>>
>> Thus far, I'm preferring the 'Search' macro as the arguments I think
>> are easier to explain -- basically anything you would type into the
>> search box.
>>
>>  - Ken
>>
>>
>>
>>
>> On Sun, Feb 6, 2011 at 2:21 PM, Patrick Bouffard
>> <bouffard@eecs.berkeley.edu> wrote:
>>> Good points Eric.
>>>
>>> Probably the tree view is better for threads. Looking at bit more at
>>> the Lurker URLs, I think we can actually get both behaviours with one
>>> macro:
>>>
>>> <<Lurker(ARG)>>
>>>
>>> ...translates to:
>>>
>>> https://code.ros.org/lurker/<ARG>.en.html
>>>
>>> ...and <ARG> can be, for a link to a particular message:
>>>
>>> message/<YYYYMMDD.UTCTIME.hashcode>
>>>
>>> ...or for its associated thread:
>>>
>>> thread/<YYYYMMDD.UTCTIME.hashcode>
>>>
>>> Pat
>>>
>>> On Sun, Feb 6, 2011 at 11:42 AM, Eric Perko <wisesage5001@gmail.com> wrote:
>>>> On Sun, Feb 6, 2011 at 2:31 PM, Patrick Bouffard
>>>> <bouffard@eecs.berkeley.edu> wrote:
>>>>>
>>>>> I think that it's simply:
>>>>>
>>>>>
>>>>> https://code.ros.org/lurker/search/20380101.000000.00000000@th:<id>.en.html
>>>>>
>>>>
>>>> This error page is actually pretty
>>>> revealing: https://code.ros.org/lurker/search/20380101.000000.0000000@ml:ros-users,th:d2ff88fe.en.xml .
>>>> Note that at the end it specifies what format it expects. The Date/Time
>>>> included in there seems to be what the "Jump" button at the bottom of the
>>>> search page sets. For displaying a single thread it probably doesn't matter.
>>>>
>>>>>
>>>>> The 20380101 looks to be a default date that's far in the future. I
>>>>> noticed that the same result will come up with the mailing list name
>>>>> added, i.e.:
>>>>>
>>>>>
>>>>> https://code.ros.org/lurker/search/20380101.000000.00000000@ml:ros-users,th:d2ff88fe.en.xml
>>>>>
>>>>> And this might be good to add to the macro even if only the id is
>>>>> required to specify the thread completely--that way by looking at the
>>>>> link you're about to click you can see what list it will be taking you
>>>>> to.
>>>>>
>>>>> So how about:
>>>>>
>>>>> Lurker<<LISTNAME, ID>>
>>>>>
>>>>> becomes:
>>>>>
>>>>>
>>>>> https://code.ros.org/lurker/search/20380101.000000.00000000@ml:<LISTNAME>,th:<ID>.en.xml
>>>>
>>>> Another option would be to bypass the search completely and go straight to
>>>> the thread view.
>>>> e.g.: https://code.ros.org/lurker/thread/20090401.024344.009c814d.en.html .
>>>> That seems to be formatted like <YYYYMMDD.UTCTIME.hashcode>.<language for
>>>> interface>.html . The date/time in that case corresponds to the date that
>>>> the thread was started. There is a similar syntax for the /message if we
>>>> wanted to be able to link to a specific message.
>>>> Is it more useful to have the search view for the thread or the the tree
>>>> view for the thread?
>>>> - Eric
>>>>
>>>>>
>>>>> Pat
>>>>>
>>>>> On Sun, Feb 6, 2011 at 11:05 AM, Ken Conley <kwc@willowgarage.com> wrote:
>>>>> > This does sound useful.  If you can figure out the algorithm/API for
>>>>> > expanding
>>>>> >
>>>>> > d2ff88fe
>>>>> >
>>>>> > to
>>>>> >
>>>>> >
>>>>> > https://code.ros.org/lurker/search/20380101.000000.00000000@th:d2ff88fe.en.html
>>>>> >
>>>>> > I would be happy to turn it into a macro on our Wiki.  I don't know
>>>>> > enough about Lurker and the URL-generation scheme isn't as obvious as
>>>>> > our other macros (e.g. Youtube, Trac).
>>>>> >
>>>>> >  - Ken
>>>>> >
>>>>> > On Sun, Feb 6, 2011 at 10:54 AM, Patrick Bouffard
>>>>> > <bouffard@eecs.berkeley.edu> wrote:
>>>>> >> It's often the case that for some particular item on the wiki there is
>>>>> >> much more information available in discussions in the mailing lists,
>>>>> >> though it's not practical (or even a good idea) to add all that detail
>>>>> >> to the wiki itself. As the list archives grow however it's becoming
>>>>> >> harder to find relevant information by a simple keyword search.
>>>>> >>
>>>>> >> We can currently link to wiki pages from the mailing list simply by
>>>>> >> pasting in the appropriate URL. Could we also enable the reverse, with
>>>>> >> a wiki macro that links to the lurker archive of a particular thread?
>>>>> >> Similar to the bug tracker macro. So something like:
>>>>> >>
>>>>> >> <<Lurker(THREAD_ID)>>
>>>>> >>
>>>>> >> e.g.,
>>>>> >>
>>>>> >> <<Lurker(d2ff88fe)>>
>>>>> >>
>>>>> >> .. would expand to:
>>>>> >>
>>>>> >>
>>>>> >> https://code.ros.org/lurker/search/20380101.000000.00000000@th:d2ff88fe.en.html
>>>>> >>
>>>>> >> And would be rendered with something like *[ML], where * is a little
>>>>> >> envelope icon or something like that.
>>>>> >>
>>>>> >> Then in the wiki we can add these links pointing to discussion threads
>>>>> >> that are relevant to that part of the wiki. This could include threads
>>>>> >> on ros-developers that relate to design decisions, or threads on
>>>>> >> ros-users that have some detailed discussion on some feature.
>>>>> >>
>>>>> >> I'm not sure if this is technically possible, but perhaps the mailing
>>>>> >> list could even be configured so that the lurker thread id is printed
>>>>> >> at the bottom of every message to make it dead easy to know what
>>>>> >> thread id to use.
>>>>> >>
>>>>> >>
>>>>> >> Cheers,
>>>>> >> Pat
>>>>> >> _______________________________________________
>>>>> >> ros-users mailing list
>>>>> >> ros-users@code.ros.org
>>>>> >> https://code.ros.org/mailman/listinfo/ros-users
>>>>> >>
>>>>> > _______________________________________________
>>>>> > ros-users mailing list
>>>>> > ros-users@code.ros.org
>>>>> > https://code.ros.org/mailman/listinfo/ros-users
>>>>> >
>>>>> _______________________________________________
>>>>> ros-users mailing list
>>>>> ros-users@code.ros.org
>>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>>
>>>>
>>>> _______________________________________________
>>>> ros-users mailing list
>>>> ros-users@code.ros.org
>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>>
>>>>
>>> _______________________________________________
>>> ros-users mailing list
>>> ros-users@code.ros.org
>>> https://code.ros.org/mailman/listinfo/ros-users
>>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>