python-markdown-discuss

[Python-markdown-discuss] the wiki upgraded

[Yuri T. <qar...@gm...>]

I upgraded the wiki on the site
(http://www.freewisdom.org/projects/python-markdown/) and locked the
front page against edits by non-admin users because of an influx of
spam.

This upgrade also brings the option of using my own mini bug tracker,
which is finally useable.  It's still quite minimalistic, but arguably
it's hard to do worse than the sourceforge one.  If we decide to use
it, it would be just like this one:
http://sputnik.freewisdom.org/en/Tickets

The main limitation is that you cannot attach comments to the ticket -
instead, there is a single wiki page for the discussion.  (Attaching
comments is the next feature on the list, but I have some traveling in
the next few weeks, so will take some time.)

Let me know whether you prefer to stick with SF tracker for now or
switch.  Or we can revisit this when the comment functionality is
there.  Or feel free to suggest features.

  - yuri

-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] the wiki upgraded

[Waylan L. <wa...@gm...>]

On Tue, Jul 8, 2008 at 2:53 AM, Yuri Takhteyev <qar...@gm...> wrote:
>
> Let me know whether you prefer to stick with SF tracker for now or
> switch.  Or we can revisit this when the comment functionality is
> there.  Or feel free to suggest features.
>
Bug tracking is the one thing I'm the most eager to move away from SF,
so I say switch. As it stands, there aren't any discussions going on
on the SF tracker anyway. I seem to be the only one leaving any
comments - which I can easily do in the wikipage format.

If you turn on the feature, I'll copy the existing open reports over.

-- 
----
Waylan Limberg
wa...@gm...

Re: [Python-markdown-discuss] the wiki upgraded

[Yuri T. <qar...@gm...>]

> If you turn on the feature, I'll copy the existing open reports over.

http://www.freewisdom.org/projects/python-markdown/Tickets

I copied over one ticket so far:
http://www.freewisdom.org/projects/python-markdown/Tickets/000001

Keep one thing in mind when copying the tickets: the description field
is markdown, so HTML won't be expected automatically.   Some of the
bugs have HTML in them, so it needs to be escaped.

Once the bugs are copied over, we should close that tab in SF.

Feel free to suggest (simple) features.  For now, here is an
entertaining one:
http://www.freewisdom.org/projects/python-markdown/Tickets/000001.raw
will give you raw content of the ticket in Lua format.  If anyone
cares, I can add a JSON or XML output.  (Or is there a format that is
more python-friendly?)

- yuri

-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] the wiki upgraded

[Waylan L. <wa...@gm...>]

On Tue, Jul 8, 2008 at 7:17 PM, Yuri Takhteyev <qar...@gm...> wrote:
>> If you turn on the feature, I'll copy the existing open reports over.
>
> http://www.freewisdom.org/projects/python-markdown/Tickets
>
> Once the bugs are copied over, we should close that tab in SF.

Done. I also updated the link on the wiki here:
http://www.freewisdom.org/projects/python-markdown/Reporting_Bugs.
Perhaps the Ticket page should replace that page.

While I was removing the bug tracker from SF (actually hiding it - you
can't delete them so the data is still preserved and the admins can
still get to it) I also hid the SVN repo as its no longer being used.
The wiki had already been updated in that respect anyway.

Artem,

You might want to take a look at tickets 4 & 5 if you get a chance.
They both involve inline patterns.

I took the liberty of assigning ticket 2 to you as you already have a
fix in your branch and noted as much in the ticket.

Tickets 1 & 3 are ugly and should be left alone until the dust settles
from the Gsoc work.
-- 
----
Waylan Limberg
wa...@gm...

Re: [Python-markdown-discuss] the wiki upgraded

[Artem Y. <ne...@gm...>]

Waylan Limberg wrote:
> Artem,
>
> You might want to take a look at tickets 4 & 5 if you get a chance.
> They both involve inline patterns.
>
>   

OK, I think I'll fix it in GSoC version.