headers
Will Kahn-Greene | 17 Dec 23:46
Favicon
Gravatar

Re: 1.5 status -- anything more to do?


Anything is fine by me.  Patches sent to the mailing list, pull requests 
on github, issues on github with comments on how to fix the issue, pinging 
me on IRC, ...

On Sat, 17 Dec 2011, Akai wrote:
> 
> What would be the best way to contribute post-hiatus?
>
> On 12/17/2011 5:17 PM, Will Kahn-Greene wrote:
>> I worked through the remaining bugs sitting in the 1.5 milestone today.
>> Now there are no more bugs sitting in the 1.5 milestone.
>> 
>> If there's anything outstanding that I haven't finished up, let me know in
>> the next two days.  Barring any issues, I'm going to ship 1.5 next week.
>> 
>> After 1.5 goes out, I'm going to spend some time moving interesting bugs
>> to the issue tracker on github and then take a hiatus from Pyblosxom
>> development for a while.  I will continue to work through patches
>> submitted by other people whether they code or docs or fixes to the
>> website.
>> 
>> /will
>>
>> 
>> ------------------------------------------------------------------------------
>> Learn Windows Azure Live!  Tuesday, Dec 13, 2011
>> Microsoft is holding a special Learn Windows Azure training event for
>> developers. It will provide a great way to learn Windows Azure and what it
>> provides. You can attend the event by watching it streamed LIVE online.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Will Kahn-Greene | 17 Dec 16:17
Favicon
Gravatar

1.5 status -- anything more to do?


I worked through the remaining bugs sitting in the 1.5 milestone today. 
Now there are no more bugs sitting in the 1.5 milestone.

If there's anything outstanding that I haven't finished up, let me know in 
the next two days.  Barring any issues, I'm going to ship 1.5 next week.

After 1.5 goes out, I'm going to spend some time moving interesting bugs 
to the issue tracker on github and then take a hiatus from Pyblosxom 
development for a while.  I will continue to work through patches 
submitted by other people whether they code or docs or fixes to the 
website.

/will

------------------------------------------------------------------------------
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure
Permalink | Reply | 0 comments |
headers
Will Kahn-Greene | 24 Nov 01:20
Favicon
Gravatar

project infrastructure


I updated the roundup package on bluesock (the server that hosts the 
Pyblosxom bug tracker) and inadvertently stomped on the fix I made to 
roundup.  Then I started getting lots of error emails from roundup because 
it's "helpful".  Took me about 30 minutes to figure out how I fixed it the 
last time and re-fix it.  Irritating.

That got me thinking.  A while back, when we talked about switching to git 
and picking a host, I remember a lot of people said they already had 
github accounts.  I picked gitorious because at the time is was close 
enough feature-wise and it was Free Software.  I picked roundup because it 
seemed like a decent choice.

At this point, I want to revisit those decisions.  I'm thinking of moving 
things around in this way:

1. Move from gitorious to github.  In doing this, we gain post-commit 
hooks some of which are wildly useful, an issue tracker, inline comments 
for pull requests, probably an order of magnitude more people who already 
have github accounts and who are used to drive-by-fixes, and probably some 
other github features I haven't yet discovered.

2. Move the Pyblosxom manual to ReadTheDocs.  We're already using Sphinx. 
If we switch to github, then it's a post-commit hook to update it 
everytime something gets checked in.  This would be really nice.

3. Ditch roundup and use the github issue tracker.

After that we can see where things are at.
(Continue reading)

Permalink | Reply | 11 comments |
headers
Akai | 9 Nov 02:07
Picon

Installing plugins

Hi everyone,

Sorry to be bugging you guys..
I can't manage to install any plugins
I tried the "new" method from the WHATSNEW file and the old ones from
the other docs
some of my attempts:

py["load_plugins"] = ["Pyblosxom.plugins.comments"]
py["plugin_dirs"] = [os.path.join(blogdir,
"plugins"),"/home/sites/bloxblog/Pyblosxom/plugins"]
etc..

I'm running the current GIT head version if that helps, using CGI
rendering (though I tried Paste as well)

-Akai

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
Permalink | Reply | 4 comments |
headers
Will Kahn-Greene | 5 Nov 15:31
Favicon
Gravatar

merged 34-plugins into master


I just merged the 34-plugins branch into master.  It seems fine.  I could 
use more help testing it, though.  I've made a lot of structural changes 
and updated the code for a lot of the plugins.

If you have 10 minutes today or tomorrow, helping me test would help a 
lot.

/will

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
Permalink | Reply | 0 comments |
headers
will kahn-greene | 4 Nov 14:46
Favicon
Gravatar

nixed two mailing lists

I nixed the pyblosxom-checkins list (we haven't used it in years) and
the pyblosxom-announce list.  In retrospect, I should have said
something on each list before nixing it, but it's too late for that now.

That leaves us with two lists: pyblosxom-users and pyblosxom-devel.  I
think that's good for now.

/will

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
Permalink | Reply | 0 comments |
headers
Will Kahn-Greene | 3 Nov 01:20
Favicon
Gravatar

things i need your help with


Hi all!

I did a bunch of pyblosxom docs work over the last few days while I had no 
power through judicious use of battery life on my laptop.  I'm feeling 
pretty good about doing a 1.5 final release soon.  However, I really need 
some help with some things:

1. I did a massive overhaul of plugins and documentation in the 34-plugins 
branch that needs testing and a second set of eyes.

Anyone who is interested in helping on this, just grab the 34-plugins 
branch and start testing and reading through the docs.

2. I need someone to do whatever it is you do with Freenode stuff to get 
the #pyblosxom channel registered so that we can get ops on it and change 
the topic and all that jazz.

We only need one person to do this, so if someone is interested, let me 
know.

3. I need someone to triage bugs in the bug tracker.  There are a bunch of 
bugs, some have been targeted at various milestones, but I don't really 
have a good sense of where things are at, what really needs to be in 1.5, 
what can be deferred and what's already done or isn't applicable any more.

If someone is interested in helping on this, go for it.  If you feel 
uncertain about making decisions, feel free to ping me on IRC with 
questions.  It's helpful to even just look at the issues you've created 
and bump them with current status.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Will Kahn-Greene | 19 Oct 03:16
Favicon
Gravatar

packages and projects


A while back, I (pretty sure it was me) moved things around and put 
PyBlosxom into the package Pyblosxom (upper-case P lower-case b).  That's 
different than the project name which is PyBlosxom.  In the Pyblosxom 
package is a pyblosxom module.  In the pyblosxom module is a PyBlosxom 
class.

Yes, seriously.  The only good thing I can say is that at least there 
isn't a pYbLOSXOM in there, too.

Anyhow, this is already a source of confusion, but the circumstances don't 
come up with enough frequency that I've decided to fix it.  Until now....

The pain of the current situation increases now that I'm moving core 
plugins into the Pyblosxom package (yes--one more round of the hokey pokey 
with the location of the plugins).  Because of this change, it's very 
likely that the confusion will cause problems for users since new users 
will be typing 'Pyblosxom.plugins.ladeedah' over and over again in the 
load_plugins list in their config.py files.

Further, after I make this change to plugins, the pain of changing the 
package name goes up astronomically.  So the time to fix it is now!

I see two options:

1. Change the name of the project from PyBlosxom to Pyblosxom.  Camel case 
is so 90s anyhow.  This makes the package the same as the project name.

Then we change the name of the PyBlosxom class to Pyblosxom and we're all 
set.  This last bit shouldn't be much pain--only the internals really use
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mark David Dumlao | 28 Aug 17:15
Picon

[pyblosxom-devel] mtimes do not appear to hide future entries on pyblosxom-1.5rc3

Hi!
I'm new to pyblosxom and I would like some clarification as to how mtimes work.

As best as I understand, entries with an mtime later than today should
not be displayed, whereas mtimes older than today should be displayed
by the blog in decreasing order of date.

Is this a correct understanding? If not, how can I help to make this
happen, and in the meantime, what is the best way for me to write
entries well in advance of their publish date?
--

-- 
This email is:    [x] actionable   [ ] fyi        [x] social
Response needed:  [x] yes          [ ] up to you  [ ] no
Time-sensitive:   [ ] immediate    [x] soon       [ ] none

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
Permalink | Reply | 4 comments |
headers
will kahn-greene | 19 Jun 15:55
Favicon
Gravatar

pyblosxom 1.5rc3 released!

Release!
========

I just release PyBlosxom 1.5rc3.  For changes, take a look at the What's 
new chapter:

    http://pyblosxom.bluesock.org/1.5/whatsnew.html

Amongst other things, it continues to reduce the difficulties in 
configuring and debugging PyBlosxom and plugins.  I encourage everyone 
to upgrade.

Going forward
=============

There are still problems that I'd like to sort out for 1.5, but this is 
another big step towards getting there.

If you're interested in helping out, see the Milestone 1.5 link on the 
left side if the issue tracker at http://pyblosxom.bluesock.org/bugs/ .

If you find issues, please write up issues there or send something to 
the pyblosxom-devel mailing list.  Details on the website at 
http://pyblosxom.bluesock.org/ .

/will

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
(Continue reading)

Permalink | Reply | 0 comments |
headers
will kahn-greene | 13 Jun 04:24
Favicon
Gravatar

status: June 12th, 2011

Hi!

I've been really busy the last few months and haven't gotten anything 
I've wanted to do on PyBlosxom done.  Things have cleared up a bit and I 
finally have some breathing space, but...  probably not for long since 
I'm on another aggressive software release schedule.

For June, I want to focus on the following three things:

1. work on pyblosxom 1.5 and finish it up

2. work on cleaning up the PyBlosxom and project documentation

3. clear out my queue of things people are waiting on me to do

I won't be able to get all of these things accomplished, but these are 
the things I am focusing on.

Today, I spent some time with gitorious and wrapped my head around merge 
requests (finally).  It makes a lot more sense now.  One thing that's 
really important for a merge request is that we switch the way we're 
doing contributions to make sure contributions are done in bugfix branches.

I've overhauled the development docs accordingly:

    http://pyblosxom.bluesock.org/static/development.html

They assume you have a working knowledge of git currently.  I plan to 
add links on how to learn git, but really don't want to host our own git 
tutorial.  With that in mind, does the changes in the documentation make
(Continue reading)

Permalink | Reply | 2 comments |

Gmane