pyblosxom-devel — Development Mailing List for pyblosxom

Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

[Akai <ope...@gm...>]

Dieter,

I'll learn up about it and see if its possible to seamlessly offer both.


On 12/4/2012 4:06 PM, Dieter Plaetinck wrote:
> why not just allow both?
> depending on the preference of the original plugin creator, he should be able to choose
> whether his pull request includes the plugin directory itself, or a submodule definition.
>
> personally i think submodules are the better option, you can ask people to include a lot of info
> in their files and/or README's, but it will never be as complete as a submodule using the original
> git repository itself.
> but i would just allow both... as long as you end up with a subdirectory containing the plugin and maybe some documentation
>
> On Tue, 04 Dec 2012 12:30:21 +0100
> Florian Bäuerle <flo...@gm...> wrote:
>
>> I just did a pull-request (breadcrumb-plugin) - first time i've been
>> using git and/or github. I hope I did not mess up anything.
>>
>> Anyway, great idea, keep it up!
>>
>> Regards, 
>> Flo
>> Am Dienstag, den 04.12.2012, 11:28 +0200 schrieb Akai Kistune:
>>> Wari -
>>>
>>> Thats why I ask people put contact information with the plugin. While 
>>> there really is nothing I can do about stagnation, I feel this is a good 
>>> solution for all the people running non-git setups or people who 
>>> frequently break their build.
>>>
>>> Also, there is the URL field in the plugin docstring which should be the 
>>> git/svn/server where one can find the 3rd party plugins repos or 
>>> download which should also help counter the issue.
>>>
>>>
>>> Asheesh -
>>> Thanks!
>>>
>>>
>>>
>>>
>>> On 12/04/2012 05:20 AM, Wari Wahab wrote:
>>>> Git submodules are really pointers to commits of a particular repos.
>>>> Therefore a release of a plugin would mean a specific commit at the
>>>> original site. Publishing it together with the plugins.git (instead of
>>>> submodules) would mean that all historical logs regarding to a
>>>> particular version is lost.
>>>>
>>>> Anyway, there are pros and cons of both approaches, but I have a feeling
>>>> that putting it all in to the plugins.git would lead to the contrib
>>>> situation where plugins get stale after a while. At least with
>>>> pointers/submodules, one can look up the original maintainer, and
>>>> provide updates if needed instead of updating plugins.git, and you then
>>>> have to go back to the original maintainer to update their copy.
>>>>
>>>> Anyway, it's all up to you what you think best, I still think the
>>>> submodule idea is great, but I guess there are others out there using
>>>> CVS or Subversion, in which case, submodules don't work for them.
>>>>
>>>> On 04/12/2012 10:36, Asheesh Laroia wrote:
>>>>> On Tue, 4 Dec 2012, Akai Kistune wrote:
>>>>>
>>>>>> Because its not just other git repos, its all over the place. Also -
>>>>>> While I'm not sure how the git submodule process would work, in any
>>>>>> case, publishing to the repo should be akin to a "release" of your
>>>>>> plugin, while the versions in people's personal repos would be the
>>>>>> development versions.
>>>>>> I hope that it will always be possible to pull a working version of a
>>>>>> 3rd party plugin from the repo.
>>>> ------------------------------------------------------------------------------
>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>> Remotely access PCs and mobile devices and provide instant support
>>>> Improve your efficiency, and focus on delivering more value-add services
>>>> Discover what IT Professionals Know. Rescue delivers
>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>> _______________________________________________
>>>> Pyblosxom-devel mailing list
>>>> Pyb...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>> Remotely access PCs and mobile devices and provide instant support
>>> Improve your efficiency, and focus on delivering more value-add services
>>> Discover what IT Professionals Know. Rescue delivers
>>> http://p.sf.net/sfu/logmein_12329d2d
>>> _______________________________________________
>>> Pyblosxom-devel mailing list
>>> Pyb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Pyblosxom-devel mailing list
>> Pyb...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

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

why not just allow both?
depending on the preference of the original plugin creator, he should be able to choose
whether his pull request includes the plugin directory itself, or a submodule definition.

personally i think submodules are the better option, you can ask people to include a lot of info
in their files and/or README's, but it will never be as complete as a submodule using the original
git repository itself.
but i would just allow both... as long as you end up with a subdirectory containing the plugin and maybe some documentation

On Tue, 04 Dec 2012 12:30:21 +0100
Florian Bäuerle <flo...@gm...> wrote:

> I just did a pull-request (breadcrumb-plugin) - first time i've been
> using git and/or github. I hope I did not mess up anything.
> 
> Anyway, great idea, keep it up!
> 
> Regards, 
> Flo
> Am Dienstag, den 04.12.2012, 11:28 +0200 schrieb Akai Kistune:
> > Wari -
> > 
> > Thats why I ask people put contact information with the plugin. While 
> > there really is nothing I can do about stagnation, I feel this is a good 
> > solution for all the people running non-git setups or people who 
> > frequently break their build.
> > 
> > Also, there is the URL field in the plugin docstring which should be the 
> > git/svn/server where one can find the 3rd party plugins repos or 
> > download which should also help counter the issue.
> > 
> > 
> > Asheesh -
> > Thanks!
> > 
> > 
> > 
> > 
> > On 12/04/2012 05:20 AM, Wari Wahab wrote:
> > > Git submodules are really pointers to commits of a particular repos.
> > > Therefore a release of a plugin would mean a specific commit at the
> > > original site. Publishing it together with the plugins.git (instead of
> > > submodules) would mean that all historical logs regarding to a
> > > particular version is lost.
> > >
> > > Anyway, there are pros and cons of both approaches, but I have a feeling
> > > that putting it all in to the plugins.git would lead to the contrib
> > > situation where plugins get stale after a while. At least with
> > > pointers/submodules, one can look up the original maintainer, and
> > > provide updates if needed instead of updating plugins.git, and you then
> > > have to go back to the original maintainer to update their copy.
> > >
> > > Anyway, it's all up to you what you think best, I still think the
> > > submodule idea is great, but I guess there are others out there using
> > > CVS or Subversion, in which case, submodules don't work for them.
> > >
> > > On 04/12/2012 10:36, Asheesh Laroia wrote:
> > >> On Tue, 4 Dec 2012, Akai Kistune wrote:
> > >>
> > >>> Because its not just other git repos, its all over the place. Also -
> > >>> While I'm not sure how the git submodule process would work, in any
> > >>> case, publishing to the repo should be akin to a "release" of your
> > >>> plugin, while the versions in people's personal repos would be the
> > >>> development versions.
> > >>> I hope that it will always be possible to pull a working version of a
> > >>> 3rd party plugin from the repo.
> > >
> > > ------------------------------------------------------------------------------
> > > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> > > Remotely access PCs and mobile devices and provide instant support
> > > Improve your efficiency, and focus on delivering more value-add services
> > > Discover what IT Professionals Know. Rescue delivers
> > > http://p.sf.net/sfu/logmein_12329d2d
> > > _______________________________________________
> > > Pyblosxom-devel mailing list
> > > Pyb...@li...
> > > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
> > >
> > 
> > 
> > ------------------------------------------------------------------------------
> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> > Remotely access PCs and mobile devices and provide instant support
> > Improve your efficiency, and focus on delivering more value-add services
> > Discover what IT Professionals Know. Rescue delivers
> > http://p.sf.net/sfu/logmein_12329d2d
> > _______________________________________________
> > Pyblosxom-devel mailing list
> > Pyb...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
> 
> 
> 
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

[Florian B. <flo...@gm...>]

I just did a pull-request (breadcrumb-plugin) - first time i've been
using git and/or github. I hope I did not mess up anything.

Anyway, great idea, keep it up!

Regards, 
Flo
Am Dienstag, den 04.12.2012, 11:28 +0200 schrieb Akai Kistune:
> Wari -
> 
> Thats why I ask people put contact information with the plugin. While 
> there really is nothing I can do about stagnation, I feel this is a good 
> solution for all the people running non-git setups or people who 
> frequently break their build.
> 
> Also, there is the URL field in the plugin docstring which should be the 
> git/svn/server where one can find the 3rd party plugins repos or 
> download which should also help counter the issue.
> 
> 
> Asheesh -
> Thanks!
> 
> 
> 
> 
> On 12/04/2012 05:20 AM, Wari Wahab wrote:
> > Git submodules are really pointers to commits of a particular repos.
> > Therefore a release of a plugin would mean a specific commit at the
> > original site. Publishing it together with the plugins.git (instead of
> > submodules) would mean that all historical logs regarding to a
> > particular version is lost.
> >
> > Anyway, there are pros and cons of both approaches, but I have a feeling
> > that putting it all in to the plugins.git would lead to the contrib
> > situation where plugins get stale after a while. At least with
> > pointers/submodules, one can look up the original maintainer, and
> > provide updates if needed instead of updating plugins.git, and you then
> > have to go back to the original maintainer to update their copy.
> >
> > Anyway, it's all up to you what you think best, I still think the
> > submodule idea is great, but I guess there are others out there using
> > CVS or Subversion, in which case, submodules don't work for them.
> >
> > On 04/12/2012 10:36, Asheesh Laroia wrote:
> >> On Tue, 4 Dec 2012, Akai Kistune wrote:
> >>
> >>> Because its not just other git repos, its all over the place. Also -
> >>> While I'm not sure how the git submodule process would work, in any
> >>> case, publishing to the repo should be akin to a "release" of your
> >>> plugin, while the versions in people's personal repos would be the
> >>> development versions.
> >>> I hope that it will always be possible to pull a working version of a
> >>> 3rd party plugin from the repo.
> >
> > ------------------------------------------------------------------------------
> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> > Remotely access PCs and mobile devices and provide instant support
> > Improve your efficiency, and focus on delivering more value-add services
> > Discover what IT Professionals Know. Rescue delivers
> > http://p.sf.net/sfu/logmein_12329d2d
> > _______________________________________________
> > Pyblosxom-devel mailing list
> > Pyb...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
> >
> 
> 
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

[Akai K. <ope...@gm...>]

Wari -

Thats why I ask people put contact information with the plugin. While 
there really is nothing I can do about stagnation, I feel this is a good 
solution for all the people running non-git setups or people who 
frequently break their build.

Also, there is the URL field in the plugin docstring which should be the 
git/svn/server where one can find the 3rd party plugins repos or 
download which should also help counter the issue.


Asheesh -
Thanks!




On 12/04/2012 05:20 AM, Wari Wahab wrote:
> Git submodules are really pointers to commits of a particular repos.
> Therefore a release of a plugin would mean a specific commit at the
> original site. Publishing it together with the plugins.git (instead of
> submodules) would mean that all historical logs regarding to a
> particular version is lost.
>
> Anyway, there are pros and cons of both approaches, but I have a feeling
> that putting it all in to the plugins.git would lead to the contrib
> situation where plugins get stale after a while. At least with
> pointers/submodules, one can look up the original maintainer, and
> provide updates if needed instead of updating plugins.git, and you then
> have to go back to the original maintainer to update their copy.
>
> Anyway, it's all up to you what you think best, I still think the
> submodule idea is great, but I guess there are others out there using
> CVS or Subversion, in which case, submodules don't work for them.
>
> On 04/12/2012 10:36, Asheesh Laroia wrote:
>> On Tue, 4 Dec 2012, Akai Kistune wrote:
>>
>>> Because its not just other git repos, its all over the place. Also -
>>> While I'm not sure how the git submodule process would work, in any
>>> case, publishing to the repo should be akin to a "release" of your
>>> plugin, while the versions in people's personal repos would be the
>>> development versions.
>>> I hope that it will always be possible to pull a working version of a
>>> 3rd party plugin from the repo.
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>

Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

[Wari W. <wa...@ho...>]

Git submodules are really pointers to commits of a particular repos.
Therefore a release of a plugin would mean a specific commit at the
original site. Publishing it together with the plugins.git (instead of
submodules) would mean that all historical logs regarding to a
particular version is lost.

Anyway, there are pros and cons of both approaches, but I have a feeling
that putting it all in to the plugins.git would lead to the contrib
situation where plugins get stale after a while. At least with
pointers/submodules, one can look up the original maintainer, and
provide updates if needed instead of updating plugins.git, and you then
have to go back to the original maintainer to update their copy.

Anyway, it's all up to you what you think best, I still think the
submodule idea is great, but I guess there are others out there using
CVS or Subversion, in which case, submodules don't work for them.

On 04/12/2012 10:36, Asheesh Laroia wrote:
> On Tue, 4 Dec 2012, Akai Kistune wrote:
> 
>> Because its not just other git repos, its all over the place. Also -
>> While I'm not sure how the git submodule process would work, in any
>> case, publishing to the repo should be akin to a "release" of your
>> plugin, while the versions in people's personal repos would be the
>> development versions.
>> I hope that it will always be possible to pull a working version of a
>> 3rd party plugin from the repo.

Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

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

On Tue, 4 Dec 2012, Akai Kistune wrote:

> Because its not just other git repos, its all over the place. Also -
> While I'm not sure how the git submodule process would work, in any
> case, publishing to the repo should be akin to a "release" of your
> plugin, while the versions in people's personal repos would be the
> development versions.
> I hope that it will always be possible to pull a working version of a
> 3rd party plugin from the repo.

I'd just like to say, as a user of pyblosxom:

In my opinion this is *amazing*.

Sincerely,

Asheesh.

Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

[<wa...@ho...>]

Well, if its actually hosted in other git repos, why not link to it as a
git submodule within the plugins.git project? At least the pointers are
there, and the original maintainers can update as they please.

> Hi!
>
> By request, I've created a plugin repo
> (https://github.com/pyblosxom/plugins.git) for 3rd party plugins and I
> hope to make another for flavours as soon as I have the time.
>
> The idea is to make it easier for people to contribute to existing 3rd
> party plugins and to build up a library of updated plugins (which was
> difficult when they were hosted on other people's githubs/servers)
>
> Feel free to tell me why this is a great/horrible idea and/or to add and
> update plugins.
> I plan on adding the existing plugins as soon as I test them for
> compatibility with the latest version of Pyblosxom.
>
> The core plugins will (with the exception of the "sample" plugin) stay
> out of the 3rd party repo.
>
> -akai
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>
>

Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

[Akai K. <ope...@gm...>]

Because its not just other git repos, its all over the place. Also -
While I'm not sure how the git submodule process would work, in any 
case, publishing to the repo should be akin to a "release" of your 
plugin, while the versions in people's personal repos would be the 
development versions.
I hope that it will always be possible to pull a working version of a 
3rd party plugin from the repo.



On 12/04/2012 03:54 AM, wa...@ho... wrote:
> Well, if its actually hosted in other git repos, why not link to it as a
> git submodule within the plugins.git project? At least the pointers are
> there, and the original maintainers can update as they please.
>
>> Hi!
>>
>> By request, I've created a plugin repo
>> (https://github.com/pyblosxom/plugins.git) for 3rd party plugins and I
>> hope to make another for flavours as soon as I have the time.
>>
>> The idea is to make it easier for people to contribute to existing 3rd
>> party plugins and to build up a library of updated plugins (which was
>> difficult when they were hosted on other people's githubs/servers)
>>
>> Feel free to tell me why this is a great/horrible idea and/or to add and
>> update plugins.
>> I plan on adding the existing plugins as soon as I test them for
>> compatibility with the latest version of Pyblosxom.
>>
>> The core plugins will (with the exception of the "sample" plugin) stay
>> out of the 3rd party repo.
>>
>> -akai
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> pyblosxom-users mailing list
>> pyb...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>>
>>
>
>
>

[Pyblosxom-devel] 3rd party plugin repo

[Akai K. <ope...@gm...>]

Hi!

By request, I've created a plugin repo 
(https://github.com/pyblosxom/plugins.git) for 3rd party plugins and I 
hope to make another for flavours as soon as I have the time.

The idea is to make it easier for people to contribute to existing 3rd 
party plugins and to build up a library of updated plugins (which was 
difficult when they were hosted on other people's githubs/servers)

Feel free to tell me why this is a great/horrible idea and/or to add and 
update plugins.
I plan on adding the existing plugins as soon as I test them for 
compatibility with the latest version of Pyblosxom.

The core plugins will (with the exception of the "sample" plugin) stay 
out of the 3rd party repo.

-akai

[Pyblosxom-devel] Working update

[Akai K. <ope...@gm...>]

Hi PyBlosxom devs!

I've been travelling in the US so I haven't been able to address issues 
as quickly as I'd like. I'd like to assure the community that I've been 
working hard and am available by email if you don't see me on IRC.

If you see any issues that you feel like fixing, feel free!

-Akai

Re: [Pyblosxom-devel] Location of release source tarballs

[Akai <ope...@gm...>]

I just realized my emails never reached the list:

I've fixed the issue (apparently GitHub doesn't like PHP very much)
enjoy:
http://pyblosxom.github.com/download/

Originally, the files were there just github didn't show the directory
contents

Get them from the active site:
https://github.com/pyblosxom/pyblosxom.github.com/tree/master/download

Get them from the site's source github:
https://github.com/pyblosxom/pyblosxom-web/tree/master/htdocs/download

Even the old links work
http://pyblosxom.github.com/download/pyblosxom-1.5rc3.tar.gz for example
just the index page wasn't up.

-Akai

Re: [Pyblosxom-devel] Location of release source tarballs

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

I'm fairly sure that those are tarballs generated from whatever was 
tagged at that point. That's not the same thing as a release tarball 
where a release tarball is generated by running:

     python setup.py sdist

and possibly some other things. I don't remember offhand what I did for 
Pyblosxom releases, but I know other projects I've worked on had very 
different release tarballs from the tag tarballs that Github hosts.

/will


On 07/16/2012 04:45 PM, Tim Gray wrote:
> On Jul 16, 2012 at 10:10 PM +0200, Hauke Fath wrote:
>> Would it be possible to set up the release source tarballs under the same
>> path as on pyblosxom.bluesock.org?
>
> I don't know if it is possible or not, hopefully others will chime in,
> but tarballs of the various releases should be available here:
>
> https://github.com/pyblosxom/pyblosxom/tags

Re: [Pyblosxom-devel] Location of release source tarballs

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

On Jul 16, 2012 at 10:10 PM +0200, Hauke Fath wrote:
>Would it be possible to set up the release source tarballs under the same
>path as on pyblosxom.bluesock.org?

I don't know if it is possible or not, hopefully others will chime in, 
but tarballs of the various releases should be available here:

https://github.com/pyblosxom/pyblosxom/tags

[Pyblosxom-devel] Location of release source tarballs

[Hauke F. <ha...@Es...>]

Hi,

a late "Thank you" to Will for all his work on PyBlosxom, and another
"Thank you" to Akai for taking over!

I maintain the NetBSD pkgsrc pyblosxom package. Trying to update the
package, I found that http://pyblosxom.github.com/downloads/ is dangling.
Would it be possible to set up the release source tarballs under the same
path as on pyblosxom.bluesock.org?

Thanks,
	hauke


--
"It's never straight up and down"     (DEVO)

[Pyblosxom-devel] Latest Update/Direction

[Akai <ope...@gm...>]

Whats been going on:

The migration to GitHub is mostly complete, all the files are hosted in
the right place and the old site redirects to the new one - but there is
the occasional pesky link that doesn't point to the right place. I think
I got the vast majority of them today.

Other than just keeping the site up and the project existing, I've been
doing some thinking as to what could make PyBlosxom better (besides
getting to the bug reports and pull requests, which I AM addressing).

It seems pretty apparent to me that our plugins are both one of the best
parts of PyBlosxom as well as our Achilles heel. They can be difficult
to choose from, configure and include, and they easily get out of date
and buggy.

If we had a central way of managing plugins which could handle the worst
of the heavy lifting if the user desired (finding the right plugin, the
right version and making sure it has all the dependencies and
configurations needed to run [like a package manager]) PyBlosxom could
be a lot more viable when compared to some of the other blog engines
mentioned earlier. It would have the added benefit of making the
documentation more accessible because it could display the relevant
parts during the install process.

Obviously, such an endeavor would require some design thinking for a
management interface as well as going though all the existing plugins to
test them, make sure they are fully documented and then integrating them
into such an interface - But that pretty much has to be done anyway to
at least some degree and I think it would pay off in usability, even if
we only included a fraction of the plugins we have accumulated into the
interface.

/Akai

Re: [Pyblosxom-devel] licenses on things

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

Oops--let me rescind that and redo it.

I hereby release into the public domain under CC0 all the bits of the 
Pyblosxom manual and web-site that I wrote.

http://creativecommons.org/publicdomain/zero/1.0/

That's better. Sorry about the previous iteration.


On 06/27/2012 05:29 PM, will kahn-greene wrote:
> I hereby license all the bits of the Pyblosxom manual and web-site that
> I wrote under a Creative Commons Attribution-ShareAlike 3.0 Unported
> License.
>
> http://creativecommons.org/licenses/by-sa/3.0/
>
> The code is already licensed under the MIT license.
>
> That should cover all the problems with moving things around and let
> people do the things they need to do.
>
> /will

[Pyblosxom-devel] licenses on things

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

I hereby license all the bits of the Pyblosxom manual and web-site that 
I wrote under a Creative Commons Attribution-ShareAlike 3.0 Unported 
License.

http://creativecommons.org/licenses/by-sa/3.0/

The code is already licensed under the MIT license.

That should cover all the problems with moving things around and let 
people do the things they need to do.

/will

Re: [Pyblosxom-devel] Stepping up as maintainer

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

On Mon, Jun 25, 2012 at 10:22:32PM +0300, Akai wrote:
> I'll definitely look over your plugins and configuration - I don't
> know under what license you released it, but I assume you would
> license it appropriately [MIT licence
> <https://github.com/pyblosxom/pyblosxom/blob/master/LICENSE>] for
> inclusion in pyblosxom if I choose to include some of the features?

Yes, absolutely.

Marius Gedminas
-- 
"Nuclear war can ruin your whole compile."
                -- Karl Lehenbauer

Re: [Pyblosxom-devel] Stepping up as maintainer

[Akai <ope...@gm...>]

Thanks for the excellent feedback!
I've been devoting a lot of thought towards new users and improving the 
ease of use in general these last few days. Once I deal with the burning 
issues related to the move, I'd like to focus on making setup and 
configuration easier.

I'll definitely look over your plugins and configuration - I don't know 
under what license you released it, but I assume you would license it 
appropriately [MIT licence 
<https://github.com/pyblosxom/pyblosxom/blob/master/LICENSE>] for 
inclusion in pyblosxom if I choose to include some of the features?

-Akai


On 6/25/2012 5:57 PM, Marius Gedminas wrote:
> Hello!
>
> On Sat, Jun 23, 2012 at 09:23:58PM +0300, Akai wrote:
>> I've stepped up as maintainer of pyblosxom and I'd like to know a little
>> bit about what both I and we as a team can do to make the project better.
>> I know there are a lot of blog engines out there so I'd like an idea of
>> what attracts you to using pyblosxom specifically, so I can make sure to
>> keep the best parts of what led you here, while continually making
>> things better.
> I wanted a blog that
>
>    * was written in Python, in case I had to customize it (which I had to
>      do a lot)
>    * was easy to install (sudo apt-get install pyblosxom)
>    * would let me edit blog posts using vim and keep them in a version
>      control system (Subversion at the time, which was 2004)
>    * would let me preview the blog posts on my laptop (even offline), and
>      then publish them using the aforementioned version control system
>      (svn post-commit hook that did an svn update on the web server)
>    * would take care of the little details like formatting a valid
>      RSS/JSON feed
>
> My preferences have changed slightly, and if I were looking for a blog
> today, I'd look for something that
>
>    * had all of the above (although virtualenv + pip install something
>      would be fine, I wouldn't insist on apt-get install'ing stuff from
>      Ubuntu's repos any more; also I'd prefer git instead of Subversion)
>    * worked a bit better out of the box (archives, tags, comments, pretty
>      styles -- I had to waste too much time digging through various
>      plugins trying to figure out what they did, how they did it, and
>      then tweak the code/write my own plugins half of the time)
>    * worked like a static blog compiler, integrating with Disqus for
>      comments (AFAIU pyblosxom can already do that)
>
> The one thing that would most improve the experience of new Pyblosxom
> users would be a nice documentation site (built with Sphinx and hosted on
> Read The Docs, perhaps).  And maybe a cookbook with recipes for the most
> common needs of blog users, like:
>
>    * how can I have tags instead of exclusive categories for my posts?
>      with a nice tag cloud or something?
>    * how can I enable comments on my blog?  what about spam filtering?
>    * where can I find pretty themes?
>    * what about a mobile skin?
>    * yearly archives?
>    * URLs that include year/month/day/blog-title.html?
>    * paging?
>    * next/previous post links on each individual post page?
>    * dynamic archive tree on the sidebar a la blogger?
>    * search box?
>    * "read more after the split" for very long posts?
>
> I'm sorry about the lack of coherency for the latter part of the list;
> I'm a bit tired.
>
> I've some of these suggestions implemented on my blog.  You can take a
> look at my plugins in this svn repository mirrored as a Bazaar
> repository on Launchpad: https://code.launchpad.net/~mgedmin/+junk/blog
>
> I've never found the time to clean up any of my plugin patches (or just
> merge them with the latest pyblosxom git and see if they work),
> unfortunately, and I don't see myself finding extra spare time at any
> time in the near future :(
>
>> I'd also like to know what versions you guys are using (and how many
>> people are using the latest version off GIT) so I can get a general idea
>> of how often changes should be made into an actual release.
> I currently use whatever is in the latest Ubuntu LTS.  Or the one
> version before the latest, actually, at the moment.  Ubuntu 10.04 LTS
> has pyblosxom 1.4.3-1.  Actually, 12.04 LTS has the same version.
>
>> Also, since Will is retiring the site, we have moved to github (the site
>> part will be up soon). As such, bugs and issues should be submitted
>> here: https://github.com/pyblosxom/pyblosxom
> I'm very excited about the Github move and the promise of increased
> activity.
>
> Marius Gedminas
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

Re: [Pyblosxom-devel] Stepping up as maintainer

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

Hello!

On Sat, Jun 23, 2012 at 09:23:58PM +0300, Akai wrote:
> I've stepped up as maintainer of pyblosxom and I'd like to know a little 
> bit about what both I and we as a team can do to make the project better.
> I know there are a lot of blog engines out there so I'd like an idea of 
> what attracts you to using pyblosxom specifically, so I can make sure to 
> keep the best parts of what led you here, while continually making 
> things better.

I wanted a blog that

  * was written in Python, in case I had to customize it (which I had to
    do a lot)
  * was easy to install (sudo apt-get install pyblosxom)
  * would let me edit blog posts using vim and keep them in a version
    control system (Subversion at the time, which was 2004)
  * would let me preview the blog posts on my laptop (even offline), and
    then publish them using the aforementioned version control system
    (svn post-commit hook that did an svn update on the web server)
  * would take care of the little details like formatting a valid
    RSS/JSON feed

My preferences have changed slightly, and if I were looking for a blog
today, I'd look for something that

  * had all of the above (although virtualenv + pip install something
    would be fine, I wouldn't insist on apt-get install'ing stuff from
    Ubuntu's repos any more; also I'd prefer git instead of Subversion)
  * worked a bit better out of the box (archives, tags, comments, pretty
    styles -- I had to waste too much time digging through various
    plugins trying to figure out what they did, how they did it, and
    then tweak the code/write my own plugins half of the time)
  * worked like a static blog compiler, integrating with Disqus for
    comments (AFAIU pyblosxom can already do that)

The one thing that would most improve the experience of new Pyblosxom
users would be a nice documentation site (built with Sphinx and hosted on
Read The Docs, perhaps).  And maybe a cookbook with recipes for the most
common needs of blog users, like:

  * how can I have tags instead of exclusive categories for my posts?
    with a nice tag cloud or something?
  * how can I enable comments on my blog?  what about spam filtering?
  * where can I find pretty themes?
  * what about a mobile skin?
  * yearly archives?
  * URLs that include year/month/day/blog-title.html?
  * paging?
  * next/previous post links on each individual post page?
  * dynamic archive tree on the sidebar a la blogger?
  * search box?
  * "read more after the split" for very long posts?

I'm sorry about the lack of coherency for the latter part of the list;
I'm a bit tired.

I've some of these suggestions implemented on my blog.  You can take a
look at my plugins in this svn repository mirrored as a Bazaar
repository on Launchpad: https://code.launchpad.net/~mgedmin/+junk/blog

I've never found the time to clean up any of my plugin patches (or just
merge them with the latest pyblosxom git and see if they work),
unfortunately, and I don't see myself finding extra spare time at any
time in the near future :(

> I'd also like to know what versions you guys are using (and how many 
> people are using the latest version off GIT) so I can get a general idea 
> of how often changes should be made into an actual release.

I currently use whatever is in the latest Ubuntu LTS.  Or the one
version before the latest, actually, at the moment.  Ubuntu 10.04 LTS
has pyblosxom 1.4.3-1.  Actually, 12.04 LTS has the same version.

> Also, since Will is retiring the site, we have moved to github (the site 
> part will be up soon). As such, bugs and issues should be submitted 
> here: https://github.com/pyblosxom/pyblosxom

I'm very excited about the Github move and the promise of increased
activity.

Marius Gedminas
-- 
Life begins when you can spend your spare time programming instead of
watching television.
                -- Cal Keegan

[Pyblosxom-devel] Stepping up as maintainer

[Akai <ope...@gm...>]

Hi everyone!

I've stepped up as maintainer of pyblosxom and I'd like to know a little 
bit about what both I and we as a team can do to make the project better.
I know there are a lot of blog engines out there so I'd like an idea of 
what attracts you to using pyblosxom specifically, so I can make sure to 
keep the best parts of what led you here, while continually making 
things better.

I'd also like to know what versions you guys are using (and how many 
people are using the latest version off GIT) so I can get a general idea 
of how often changes should be made into an actual release.

Also, since Will is retiring the site, we have moved to github (the site 
part will be up soon). As such, bugs and issues should be submitted 
here: https://github.com/pyblosxom/pyblosxom

Thanks!

-Akai

Re: [Pyblosxom-devel] pyblosxom maintenance

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

Added.

On 06/21/2012 07:49 PM, Akai wrote:
> my username is AkaiKitsune
>
> On 6/22/2012 2:28 AM, will kahn-greene wrote:
>> The release process I used is documented here:
>>
>> http://pyblosxom.bluesock.org/1.5/dev_release.html
>>
>> For that, you need a PyPI account and permisions to push new versions.
>> If you have a PyPI account, I can add you.
>>
>> /will
>>
>>
>> On 06/21/2012 07:07 PM, Akai wrote:
>>> Do we need anything do a new release?
>>> I imagine we need something to make a new version of the PIP package.
>>>
>>> On 6/22/2012 12:16 AM, will kahn-greene wrote:
>>>> On 06/21/2012 05:00 PM, Akai wrote:
>>>>> Will - If we move the site to GH-pages, could you point the old site to
>>>>> the new one, or do you plan to take down the domain completely?
>>>> I can redirect all traffic to the new site. That's fine.
>>>>
>>>>
>>>>> is there a way to just backup the issue tracker?  that way we could
>>>>> start fresh without all the legacy mess, but still refer back to it if
>>>>> we find ourselves needing to fix something and nothing in the new
>>>>> tracker or wanting to migrate more issues and you wouldn't have to host
>>>>> it [and it wouldn't confuse users]
>>>> I think there are like 100 users total. I don't think "confusing users"
>>>> is really a problem you're going to have once the search engines figure
>>>> out that things have moved.
>>>>
>>>> I don't think there's much useful acrhival data in the roundup tracker.
>>>> I think it's best to look through it, move over whatever you think is
>>>> useful, and otherwise ditch it. The useful commentary is in the git
>>>> commit comments. The bug data is pretty meh.
>>>>
>>>> I'm not sure how I feel about backing it up and making it available.
>>>> It's non-trivial work to separate out the user data from the issue data
>>>> and I don't think it's responsible to be providing the user data in a
>>>> public form. So I think if you can get along without it, that's the best
>>>> option. If you really can't, then I'll add "figure out how to back up
>>>> the roundup tracker keeping peoples' privacy in mind" to my todo list.
>>>>
>>>> /will
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond. Discussions
>>>> will include endpoint security, mobile security and the latest in malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Pyblosxom-devel mailing list
>>>> Pyb...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Pyblosxom-devel mailing list
>>> Pyb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Pyblosxom-devel mailing list
>> Pyb...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>

Re: [Pyblosxom-devel] pyblosxom maintenance

[Akai <ope...@gm...>]

my username is AkaiKitsune

On 6/22/2012 2:28 AM, will kahn-greene wrote:
> The release process I used is documented here:
>
> http://pyblosxom.bluesock.org/1.5/dev_release.html
>
> For that, you need a PyPI account and permisions to push new versions.
> If you have a PyPI account, I can add you.
>
> /will
>
>
> On 06/21/2012 07:07 PM, Akai wrote:
>> Do we need anything do a new release?
>> I imagine we need something to make a new version of the PIP package.
>>
>> On 6/22/2012 12:16 AM, will kahn-greene wrote:
>>> On 06/21/2012 05:00 PM, Akai wrote:
>>>> Will - If we move the site to GH-pages, could you point the old site to
>>>> the new one, or do you plan to take down the domain completely?
>>> I can redirect all traffic to the new site. That's fine.
>>>
>>>
>>>> is there a way to just backup the issue tracker?  that way we could
>>>> start fresh without all the legacy mess, but still refer back to it if
>>>> we find ourselves needing to fix something and nothing in the new
>>>> tracker or wanting to migrate more issues and you wouldn't have to host
>>>> it [and it wouldn't confuse users]
>>> I think there are like 100 users total. I don't think "confusing users"
>>> is really a problem you're going to have once the search engines figure
>>> out that things have moved.
>>>
>>> I don't think there's much useful acrhival data in the roundup tracker.
>>> I think it's best to look through it, move over whatever you think is
>>> useful, and otherwise ditch it. The useful commentary is in the git
>>> commit comments. The bug data is pretty meh.
>>>
>>> I'm not sure how I feel about backing it up and making it available.
>>> It's non-trivial work to separate out the user data from the issue data
>>> and I don't think it's responsible to be providing the user data in a
>>> public form. So I think if you can get along without it, that's the best
>>> option. If you really can't, then I'll add "figure out how to back up
>>> the roundup tracker keeping peoples' privacy in mind" to my todo list.
>>>
>>> /will
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Pyblosxom-devel mailing list
>>> Pyb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Pyblosxom-devel mailing list
>> Pyb...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

Re: [Pyblosxom-devel] pyblosxom maintenance

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

The release process I used is documented here:

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

For that, you need a PyPI account and permisions to push new versions. 
If you have a PyPI account, I can add you.

/will


On 06/21/2012 07:07 PM, Akai wrote:
> Do we need anything do a new release?
> I imagine we need something to make a new version of the PIP package.
>
> On 6/22/2012 12:16 AM, will kahn-greene wrote:
>> On 06/21/2012 05:00 PM, Akai wrote:
>>> Will - If we move the site to GH-pages, could you point the old site to
>>> the new one, or do you plan to take down the domain completely?
>> I can redirect all traffic to the new site. That's fine.
>>
>>
>>> is there a way to just backup the issue tracker?  that way we could
>>> start fresh without all the legacy mess, but still refer back to it if
>>> we find ourselves needing to fix something and nothing in the new
>>> tracker or wanting to migrate more issues and you wouldn't have to host
>>> it [and it wouldn't confuse users]
>> I think there are like 100 users total. I don't think "confusing users"
>> is really a problem you're going to have once the search engines figure
>> out that things have moved.
>>
>> I don't think there's much useful acrhival data in the roundup tracker.
>> I think it's best to look through it, move over whatever you think is
>> useful, and otherwise ditch it. The useful commentary is in the git
>> commit comments. The bug data is pretty meh.
>>
>> I'm not sure how I feel about backing it up and making it available.
>> It's non-trivial work to separate out the user data from the issue data
>> and I don't think it's responsible to be providing the user data in a
>> public form. So I think if you can get along without it, that's the best
>> option. If you really can't, then I'll add "figure out how to back up
>> the roundup tracker keeping peoples' privacy in mind" to my todo list.
>>
>> /will
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Pyblosxom-devel mailing list
>> Pyb...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>

Re: [Pyblosxom-devel] pyblosxom maintenance

[Akai <ope...@gm...>]

Do we need anything do a new release?
I imagine we need something to make a new version of the PIP package.

On 6/22/2012 12:16 AM, will kahn-greene wrote:
> On 06/21/2012 05:00 PM, Akai wrote:
>> Will - If we move the site to GH-pages, could you point the old site to
>> the new one, or do you plan to take down the domain completely?
> I can redirect all traffic to the new site. That's fine.
>
>
>> is there a way to just backup the issue tracker?  that way we could
>> start fresh without all the legacy mess, but still refer back to it if
>> we find ourselves needing to fix something and nothing in the new
>> tracker or wanting to migrate more issues and you wouldn't have to host
>> it [and it wouldn't confuse users]
> I think there are like 100 users total. I don't think "confusing users"
> is really a problem you're going to have once the search engines figure
> out that things have moved.
>
> I don't think there's much useful acrhival data in the roundup tracker.
> I think it's best to look through it, move over whatever you think is
> useful, and otherwise ditch it. The useful commentary is in the git
> commit comments. The bug data is pretty meh.
>
> I'm not sure how I feel about backing it up and making it available.
> It's non-trivial work to separate out the user data from the issue data
> and I don't think it's responsible to be providing the user data in a
> public form. So I think if you can get along without it, that's the best
> option. If you really can't, then I'll add "figure out how to back up
> the roundup tracker keeping peoples' privacy in mind" to my todo list.
>
> /will
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel