pyblosxom-devel — Development Mailing List for pyblosxom

Re: [Pyblosxom-devel] All links to / screenshots of flavours are broken

[Tim G. <tg...@pr...>]

On Oct 04, 2010 at 09:51 AM -0400, will kahn-greene wrote:
> They (screenshots, tarballs, etc) are all in git.
>
> The flavour registry listings are here:
>
> http://gitorious.org/pyblosxom/pyblosxom-web/trees/master/registry/flavours
>
> And the screenshots and tarballs are here:
>
> http://gitorious.org/pyblosxom/pyblosxom-web/trees/master/htdocs/flavours

Are *all* of them broken?

Re: [Pyblosxom-devel] All links to / screenshots of flavours are broken

[will kahn-g. <wi...@bl...>]

They (screenshots, tarballs, etc) are all in git.

The flavour registry listings are here:

http://gitorious.org/pyblosxom/pyblosxom-web/trees/master/registry/flavours

And the screenshots and tarballs are here:

http://gitorious.org/pyblosxom/pyblosxom-web/trees/master/htdocs/flavours


On 10/04/2010 09:25 AM, Tim Gray wrote:
> On Oct 03, 2010 at 05:01 PM -0400, will kahn-greene wrote:
>> The existing flavours in the flavour registry (and the registry) all
>> need updating.  So while it seems like this is a problem, it's not
>> because there's a bigger one.
>>
>> I'd love to get some help updating flavours from anyone interested.
> 
> If there was a simple list of flavours/plugins that need to be updated, I'd 
> be willing to help out.

Re: [Pyblosxom-devel] All links to / screenshots of flavours are broken

[Tim G. <tg...@pr...>]

On Oct 03, 2010 at 05:01 PM -0400, will kahn-greene wrote:
> The existing flavours in the flavour registry (and the registry) all
> need updating.  So while it seems like this is a problem, it's not
> because there's a bigger one.
>
> I'd love to get some help updating flavours from anyone interested.

If there was a simple list of flavours/plugins that need to be updated, I'd 
be willing to help out.

Re: [Pyblosxom-devel] All links to / screenshots of flavours are broken

[Asheesh L. <as...@as...>]

On Mon, 4 Oct 2010, will kahn-greene wrote:

> Oh, whoops.  I thought the original author was saying that the 
> screenshot links were pointing to SourceForge and were thus broken.  I 
> didn't realize this applied to the .tar.gz files, too--missed that part. 
> Sorry about that.  I blame it on being on a cramped bus at the time.
>
> I'll try to fix the links so that the flavours can be updated today. 
> If I can't get to it today, then I'll get to it as late as next week. 
> I'm about to fly out on another trip and I have no idea if I'll be able 
> to connect to the Internet for the next week.

Yay!

-- Asheesh.

Re: [Pyblosxom-devel] All links to / screenshots of flavours are broken

[will kahn-g. <wi...@bl...>]

Oh, whoops.  I thought the original author was saying that the
screenshot links were pointing to SourceForge and were thus broken.  I
didn't realize this applied to the .tar.gz files, too--missed that part.
 Sorry about that.  I blame it on being on a cramped bus at the time.

I'll try to fix the links so that the flavours can be updated today.  If
I can't get to it today, then I'll get to it as late as next week.  I'm
about to fly out on another trip and I have no idea if I'll be able to
connect to the Internet for the next week.

/will


On 10/04/2010 08:09 AM, Asheesh Laroia wrote:
> On Sun, 3 Oct 2010, will kahn-greene wrote:
> 
>> The existing flavours in the flavour registry (and the registry) all 
>> need updating.  So while it seems like this is a problem, it's not 
>> because there's a bigger one.
>>
>> I'd love to get some help updating flavours from anyone interested.
> 
> Will, since I know you, I'll be more direct than usual (-:
> 
> I think that the attitude you described is counter-productive. In order 
> for people to fix the problems that you're describing, they have to be 
> able to see them.
> 
> So if you fix the link, I will test one flavour (within 3 days of the 
> links being fixed) and write up a guide for others to test flavours 
> (within 7 days of the links being fixed) so that we can all help you.
> 
> -- Asheesh.

Re: [Pyblosxom-devel] All links to / screenshots of flavours are broken

[Asheesh L. <as...@as...>]

On Sun, 3 Oct 2010, will kahn-greene wrote:

> The existing flavours in the flavour registry (and the registry) all 
> need updating.  So while it seems like this is a problem, it's not 
> because there's a bigger one.
>
> I'd love to get some help updating flavours from anyone interested.

Will, since I know you, I'll be more direct than usual (-:

I think that the attitude you described is counter-productive. In order 
for people to fix the problems that you're describing, they have to be 
able to see them.

So if you fix the link, I will test one flavour (within 3 days of the 
links being fixed) and write up a guide for others to test flavours 
(within 7 days of the links being fixed) so that we can all help you.

-- Asheesh.

-- 
You will become rich and famous unless you don't.

Re: [Pyblosxom-devel] broken title with 1.5rc2

[will kahn-g. <wi...@bl...>]

Hi!

The pi_* variables are related to the entries, so they're only available
in the story templates.

Fixed the html.flav/head and rss.flav/head templates accordingly.

Thanks!
/will


On 10/03/2010 04:52 PM, Dieter Plaetinck wrote:
> Hi,
> in 1.5rc2 (and git HEAD) flavours/html.flav/foot contains:
> <title>$(blog_title_with_path) $(pi_da) $(pi_mo) $(pi_yr)</title>
> 
> None of these variables expands to something (at least not for my
> freshly generated blog), resulting in a title containing only some
> spaces.
> 
> In the 1.4.3->1.5 changelog I found that:
> $(blog_title_with_path)
> must be changed to:
> $blog_title : $pi_bl
> 
> I didn't really figure out what I had to do with the pi_* vars.
> 
> Dieter

Re: [Pyblosxom-devel] All links to / screenshots of flavours are broken

[will kahn-g. <wi...@bl...>]

The existing flavours in the flavour registry (and the registry) all
need updating.  So while it seems like this is a problem, it's not
because there's a bigger one.

I'd love to get some help updating flavours from anyone interested.

/will


On 10/03/2010 04:55 PM, Dieter Plaetinck wrote:
> Hi,
> all the flavours @ http://pyblosxom.bluesock.org/registry/flavours/
> have a download link and screenshot which point to sourceforge, none of
> them works.
> This makes it hard for new users to try flavours ;-)
> 
> Dieter

[Pyblosxom-devel] All links to / screenshots of flavours are broken

[Dieter P. <di...@pl...>]

Hi,
all the flavours @ http://pyblosxom.bluesock.org/registry/flavours/
have a download link and screenshot which point to sourceforge, none of
them works.
This makes it hard for new users to try flavours ;-)

Dieter

[Pyblosxom-devel] broken title with 1.5rc2

[Dieter P. <di...@pl...>]

Hi,
in 1.5rc2 (and git HEAD) flavours/html.flav/foot contains:
<title>$(blog_title_with_path) $(pi_da) $(pi_mo) $(pi_yr)</title>

None of these variables expands to something (at least not for my
freshly generated blog), resulting in a title containing only some
spaces.

In the 1.4.3->1.5 changelog I found that:
$(blog_title_with_path)
must be changed to:
$blog_title : $pi_bl

I didn't really figure out what I had to do with the pi_* vars.

Dieter

Re: [Pyblosxom-devel] issue tracking -- let's fix this!

[Asheesh L. <as...@as...>]

On Thu, 30 Sep 2010, will kahn-greene wrote:

> I really want to solve number 1 next.  An issue is a bug, feature, 
> plugin idea, documentation suggestion, ...  I want to use an issue 
> tracking system that is:
>
> 1. maximizes ease of use
>
> 2. minimizes spam
>
> 3. maximizes ability of anonymous people to use -- people shouldn't have 
> to create an account to log a bug (maybe this is solved by people 
> sending me email--I don't know)

2 and 3 are tough together.

I would try Roundup...

> 4. maximizes the ability to figure out where PyBlosxom is at in terms of 
> issues, items that should be done, things that people can jump in and 
> work on, ...

You can do that with custom queries (if you pay attention to making a 
query) in most bug trackers except Launchpad's :P

> 5. minimizes administration, maintenance and installation difficulties
>
> 6. must be Free Software

*nod*

self-hosted Roundup is slightly less attractive for you, but on the other 
hand Roundup has a pretty high quality Debian package.

> What options are there out there?
>
> Should we go for a git-based distributed issue tracking system?

Eek, they all have really low usability as far as I know.

> Should we roll our own system using the PyBlosxom core?

Heck no. :P

> Are there other requirements I'm not thinking about?

Email interaction? Roundup has that, for what it's worth.

-- Asheesh.

-- 
<_Anarchy_> acf: maybe April 1 next year slashdot needs to run "Rob Malda
             accepts new job as head of Debian project" 8)

Re: [Pyblosxom-devel] issue tracking -- let's fix this!

[Marius G. <ma...@ge...>]

On Thu, Sep 30, 2010 at 03:14:50PM -0400, will kahn-greene wrote:
> I really want to solve number 1 next.  An issue is a bug, feature,
> plugin idea, documentation suggestion, ...  I want to use an issue
> tracking system that is:
> 
> 1. maximizes ease of use
> 
> 2. minimizes spam
> 
> 3. maximizes ability of anonymous people to use -- people shouldn't have
> to create an account to log a bug (maybe this is solved by people
> sending me email--I don't know)
> 
> 4. maximizes the ability to figure out where PyBlosxom is at in terms of
> issues, items that should be done, things that people can jump in and
> work on, ...
> 
> 5. minimizes administration, maintenance and installation difficulties
> 
> 6. must be Free Software

1, 2 and 5 are best solved by using a hosted bug tracker (Launchpad.net,
Google Code, Github, Bitbucket).  Most of them will fail 3 and 6.

3 and 2 are difficult to combine.

I get the wive that you want to host the issue tracker yourself, which
will require great effort for 2, and nontrivial effort for 5.

> To reduce the scope of this conversation, I offer the following
> anti-suggestions:
> 
> 1. no bugzilla -- it's great, I love it, doesn't meet my requirements
> for PyBlosxom
> 
> 2. no Trac -- other people like it, I don't
> 
> What options are there out there?

Roundup.  Worse than Trac, in my opinion.  Could be made to work,
perhaps, with enough effort.

I've no direct experience with other issue trackers.

> Should we go for a git-based distributed issue tracking system?
> 
> Should we roll our own system using the PyBlosxom core?

As a user I'd be happier to see efforts going into improving PyBlosxom's
core, plugins, and especially integration (a better out-of-the-box
experience with more features), than into inventing a yet another issue
tracker.  But if you find it interesting/fun, go for it!

> Are there other requirements I'm not thinking about?
> 
> I'd love to talk about this for the next couple of weeks and come to
> some kind of solution both for the software to use as well as any
> workflow suggestions that address the requirements.  Then we'll
> implement something in late October and solve this problem because it's
> seriously hampering our mojo and that sux0rz.

Why not use a hosted solution in the interim?  Pick one that lets you
export all your data easily, so you can migrate to a self-hosted tracker
later.

Personally, I like the Launchpad bug tracker.  Well, "like" is not the
right word -- it's pedestrian, doesn't invoke feelings of love, but
it gets the job done with minimum effort from my side, which I
appreciate.

Marius Gedminas
-- 
Never trust a computer you can't repair yourself.

Re: [Pyblosxom-devel] issue tracking -- let's fix this!

[Sebastian S. <Seb...@SS...>]

On 2010-09-30, will kahn-greene wrote:
> We've switched from svn to git.  That solved a bunch of problems.  Yay!

Yay!
 
> We've moved the website from Sourceforge to Bluesock (my server) and
> that's solved some problems and has the potential to solve more
> problems.  Yay!

Even more yay!

> 1. issue tracking

I have used roundup which is written in python and used by
python.org. It seems decent and has an email interface, so you can log
issues just by sending an email. (a cron script polling a mailbox, so
you could run a spamfilter before) It is pretty ok, I think. No spam
filter built into it though.

As for distributed git-based stuff, here is a list 
http://www.cs.unb.ca/~bremner/blog/posts/git-issue-trackers/

Of these, these 2 seem most interesting to me:

http://bugseverywhere.org/be/show/HomePage
http://syncwith.us/sd/

Otherwise, there are hosted things such as:

http://lighthouseapp.com/

which provide free issue tracking, but that one requires an account with them.

> Should we roll our own system using the PyBlosxom core?

Hehe, a bugtracking plugin for pyblosxom? Sounds like a cool idea.

Especiall http://bugseverywhere.org/be/show/HomePage (bugs in git
alongside the source code) which is written in
python could proabably be adapted to have a pyblosxom interface, their
current webfrontent is using web.py and some templates. it seems.

have never used it though.
Sebastian

Re: [Pyblosxom-devel] issue tracking -- let's fix this!

[Tim G. <tg...@pr...>]

On Sep 30, 2010 at 03:14 PM -0400, will kahn-greene wrote:

I've never really developed anything (haha) so take my suggestions with a 
grain of salt.  Of the couple issue tracking systems I've encountered, trac 
and google code's system both seemed easily understandable to the outsider. 
It's very easy to get a sense of what the latest progress is.

I understand you don't want to use trac though.

> What options are there out there?

ikiwiki could be interesting.  It's based off of a revision control system, 
so that's a big plus.  It can be hosted in git, so it could live right along 
side the source code.  Or in a separate repository.  Which would also make 
it distributed.  It has bug tracking, todos, etc. built in.  It also appears 
to allow for anonymous bug submissions.  Looks like a cool project to me.

Google code has a nice clean interface too.  I don't know how easy/hard it 
would be to glue it onto a project hosted elsewhere though.

> Should we go for a git-based distributed issue tracking system?

See above.

> Should we roll our own system using the PyBlosxom core?

A possibility, but I might say the time and effort spent implementing an 
issue tracking system could be better spent elsewhere.

On a separate note, I'd like to contribute more to pyblosxom development 
(when I get a bit of time).  I've hacked up a number of plugins already just 
in the last couple weeks of usage, but I'd like to help in a more meaningful 
way as well.

[Pyblosxom-devel] issue tracking -- let's fix this!

[will kahn-g. <wi...@bl...>]

We've switched from svn to git.  That solved a bunch of problems.  Yay!

We've moved the website from Sourceforge to Bluesock (my server) and
that's solved some problems and has the potential to solve more
problems.  Yay!

The next two problems to solve are these:

1. issue tracking

2. plugin/flavour registry

I really want to solve number 1 next.  An issue is a bug, feature,
plugin idea, documentation suggestion, ...  I want to use an issue
tracking system that is:

1. maximizes ease of use

2. minimizes spam

3. maximizes ability of anonymous people to use -- people shouldn't have
to create an account to log a bug (maybe this is solved by people
sending me email--I don't know)

4. maximizes the ability to figure out where PyBlosxom is at in terms of
issues, items that should be done, things that people can jump in and
work on, ...

5. minimizes administration, maintenance and installation difficulties

6. must be Free Software


To reduce the scope of this conversation, I offer the following
anti-suggestions:

1. no bugzilla -- it's great, I love it, doesn't meet my requirements
for PyBlosxom

2. no Trac -- other people like it, I don't


What options are there out there?

Should we go for a git-based distributed issue tracking system?

Should we roll our own system using the PyBlosxom core?

Are there other requirements I'm not thinking about?

I'd love to talk about this for the next couple of weeks and come to
some kind of solution both for the software to use as well as any
workflow suggestions that address the requirements.  Then we'll
implement something in late October and solve this problem because it's
seriously hampering our mojo and that sux0rz.

/will

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[Sebastian S. <sp...@ss...>]

Will kahn-greene wrote:
> Sebastian: I thought you were living in Boston.  Sorry about that.  Next
> time you (or anyone else for that matter) is in the Boston area, let me
> know--I'm game for hanging out.

I was, for exactly 3 days during a conference :-). Now I am back in good
old cheesy Switzerland, so the "right" side was merely my bad pun when
looking at a map. Sorry for confusing people.

Sebastian

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[will kahn-g. <wi...@bl...>]

On 08/05/2010 08:05 AM, Toby Smithe wrote:
> 
> 2010/8/5 Sebastian Spaeth <Seb...@ss...>:
>> On 2010-08-03, will kahn-greene wrote:
>>> On 08/03/2010 05:04 PM, Sebastian Spaeth wrote:
>>> Asheesh (OpenHatch, long time PyBlosxom user, ...) is moving to Porter
>>> Square in Cambridge soon.  After that happens, we should get a bunch of
>>> PyBlosxom-ers together and do a sprint.  Maybe on 1.6.
>>
>> Sounds good to me. Even if I am only going to participate from the
>> "right" side of the ocean. :)
> 
> This has completely confused me: Chelmsford and Cambridge are both
> ancient and well-known towns near me in England, but when Will
> mentions them, is he referring to those 'originals', or to American
> eponyms? Because,
> depending on your perspective, either side is the 'right' side...
> (Arguably, the original side is the rightest!)

Whoops!  I'm really sorry about that.  I usually add a MA to the end of
towns for exactly this reason.  I'm talking Massachusetts.

Sebastian: I thought you were living in Boston.  Sorry about that.  Next
time you (or anyone else for that matter) is in the Boston area, let me
know--I'm game for hanging out.

/will

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[Toby S. <tob...@gm...>]

Hi all,

I haven't contributed anything to the thread, because at the moment I
have no web presence. Naturally, I would (literally) check out
pyBlosxom when I get everything together again. I just wanted to
ask...

2010/8/5 Sebastian Spaeth <Seb...@ss...>:
> On 2010-08-03, will kahn-greene wrote:
>> On 08/03/2010 05:04 PM, Sebastian Spaeth wrote:
>> Asheesh (OpenHatch, long time PyBlosxom user, ...) is moving to Porter
>> Square in Cambridge soon.  After that happens, we should get a bunch of
>> PyBlosxom-ers together and do a sprint.  Maybe on 1.6.
>
> Sounds good to me. Even if I am only going to participate from the
> "right" side of the ocean. :)

This has completely confused me: Chelmsford and Cambridge are both
ancient and well-known towns near me in England, but when Will
mentions them, is he referring to those 'originals', or to American
eponyms? Because,
depending on your perspective, either side is the 'right' side...
(Arguably, the original side is the rightest!)

All the best, and good luck with the release,

-- 
Toby Smithe

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[Sebastian S. <Seb...@SS...>]

On 2010-08-03, will kahn-greene wrote:
> On 08/03/2010 05:04 PM, Sebastian Spaeth wrote:
> Asheesh (OpenHatch, long time PyBlosxom user, ...) is moving to Porter
> Square in Cambridge soon.  After that happens, we should get a bunch of
> PyBlosxom-ers together and do a sprint.  Maybe on 1.6.

Sounds good to me. Even if I am only going to participate from the
"right" side of the ocean. :)

Sebastian

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[will kahn-g. <wi...@bl...>]

On 08/03/2010 05:04 PM, Sebastian Spaeth wrote:
> 
> By the way, greetings from Mako, I relayed greetings from you, just to
> learn that you don't leave that far away from him. I am still in Boston,
> but having to leave on an family emergency right now. Otherwise I would
> have loved meeting you IRL.

A little under a year ago, I lived around the corner.  I bought a house
in Chelmsford and moved.  I'm about 45 minutes away, but I come in from
time to time.

Asheesh (OpenHatch, long time PyBlosxom user, ...) is moving to Porter
Square in Cambridge soon.  After that happens, we should get a bunch of
PyBlosxom-ers together and do a sprint.  Maybe on 1.6.

/will

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[Sebastian S. <Seb...@SS...>]

> I haven't looked at your jinja2 renderer, yet.  I'm really really sorry
> about that.  If we could get this working well in 1.6, that'd be really
> great.

By the way, my solution is a 1-template-to-render-them-all solution. And
the more I think about it the less sure I am it is the correct approach
(it is the least backward-compatible in any case). So it might just be
an inspirement to use jinja2 that code that we can simply copy. I
certainly would not be offeded if we rethought and re-did the work
properly.

Sebastian

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[Sebastian S. <Seb...@SS...>]

On 2010-08-03, will kahn-greene wrote:
> I haven't looked at your jinja2 renderer, yet.  I'm really really sorry
> about that.  If we could get this working well in 1.6, that'd be really
> great.

No need to be sorry, it is not something that should have been in the
1.5 time frame anyway.
 
> However, there are a few things we need to think about and figure out:
> 
> 1. how does this affect plugins that have their own templates?  would
> they require blosxom templates and also jinja templates?  how do they
> know which set of templates to use?
> 
> 2. would the new renderer expose a different set of rendering callbacks
> or override the existing ones?
> 
> 3. how much effort is it to package up a new renderer plugin like a
> jinja plugin?  does it require additional packaging mojo that our
> current plugin system doesn't do very well?

There are a couple of problems and issues. 

1) The simplest way is just to
replace the snippets of our current templated with jinja renderered
templates. This would be the least intrusive option and allow to insert
(or skip) tags based on the existence of variables etc. On the other
hand, it would mean we still can't set the page title in the <head>
section based on information of a plugin that comes later.

2) The other end of the scale would be a single jinja2 template that
renders a full page. This would have the advantage of being able to set
page-wide variables, but it would not work with the current system of
callbacks and "incremental" templates.

3) I wouldn't mind alternative callbacks to cater for jinja2 needs (or
whatever templating engine we could support. I don't have seintimental
feelings towards blosxom and while many plugins are in "polish mode" I
feel we could adapt them to any callback system we support.

By the way, greetings from Mako, I relayed greetings from you, just to
learn that you don't leave that far away from him. I am still in Boston,
but having to leave on an family emergency right now. Otherwise I would
have loved meeting you IRL.

Sebastian

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[will kahn-g. <wi...@bl...>]

On 08/03/2010 02:43 PM, Sebastian Spaeth wrote:
> On 2010-07-29, will kahn-greene wrote:
>> The todo list for 1.5 is primarily composed of updating plugins, adding
>> tests, and fixing/updating documentation.
> 
> I feel very comfortable about releasing what we have now. If we can
> manage to make jinx or any other templating system work in 1.6, I'd be
> happy too. Right now it is .e.g. a pain to insert a html tag if a
> specific variable exists etc.

I haven't looked at your jinja2 renderer, yet.  I'm really really sorry
about that.  If we could get this working well in 1.6, that'd be really
great.

However, there are a few things we need to think about and figure out:

1. how does this affect plugins that have their own templates?  would
they require blosxom templates and also jinja templates?  how do they
know which set of templates to use?

2. would the new renderer expose a different set of rendering callbacks
or override the existing ones?

3. how much effort is it to package up a new renderer plugin like a
jinja plugin?  does it require additional packaging mojo that our
current plugin system doesn't do very well?


I'm interested in hearing thoughts on these as well as ways we can work
around the first and second issue.

Also, who else is interested in either a better rendering system or
switching to a new rendering system?  Is it possible to use the existing
blosxom on if we add an if block and comparators?

/will

Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[Sebastian S. <Seb...@SS...>]

On 2010-07-29, will kahn-greene wrote:
> The todo list for 1.5 is primarily composed of updating plugins, adding
> tests, and fixing/updating documentation.

I feel very comfortable about releasing what we have now. If we can
manage to make jinx or any other templating system work in 1.6, I'd be
happy too. Right now it is .e.g. a pain to insert a html tag if a
specific variable exists etc.

Sebastian

[Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[will kahn-g. <wi...@bl...>]

The todo list for 1.5 is primarily composed of updating plugins, adding
tests, and fixing/updating documentation.

Given that, I'm interested in releasing pyblosxom 1.5 rc2 in the next
couple of days.  I'll address the "pip install pyblosxom doesn't work"
issue then, too.

How do you all feel about that?

Is anyone using what's in git master currently?

Are there code-related issues that still need to be fixed?

/will