Menu
▾
▴
pyblosxom-devel
|
From: Dieter P. <di...@pl...> - 2010-10-03 20:55:25
|
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 |
|
From: will kahn-g. <wi...@bl...> - 2010-10-03 21:01:23
|
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 |
|
From: Asheesh L. <as...@as...> - 2010-10-04 12:10:01
|
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. |
|
From: will kahn-g. <wi...@bl...> - 2010-10-04 13:03:53
|
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. |
|
From: Asheesh L. <as...@as...> - 2010-10-04 13:06:03
|
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. |
|
From: will kahn-g. <wi...@bl...> - 2010-10-04 20:21:26
|
I updated the links to thumbnails and .tar.gz files for flavours in the registry. Additionally, I added a note about how the flavours probably need updating. For flavours that are contributed from other non-Ryan/non-me/non-other-people-on-this-list, we should ditch them and add new flavours. Also, I've got copies of the .tar.gz files on bluesock. It's possible that whoever created the flavour in the first place has newer versions of the flavour. So that might be a good option for updating the flavour, too. If someone(s) could take a look at these and update them, that'd be really great. If no one gets to it in a couple of weeks, I'll probably take them all down and we can start over with new flavours. /will On 10/04/2010 09:05 AM, Asheesh Laroia wrote: > 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. |
|
From: Tim G. <tg...@pr...> - 2010-10-04 13:25:24
|
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. |
|
From: will kahn-g. <wi...@bl...> - 2010-10-04 13:51:31
|
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. |
|
From: Tim G. <tg...@pr...> - 2010-10-04 14:07:16
|
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? |
|
From: will kahn-g. <wi...@bl...> - 2010-10-04 14:14:53
|
I'm pretty sure they *all* need to be updated. At a minimum, they all need to be looked at. On 10/04/2010 10:07 AM, Tim Gray wrote: > 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? |
Thanks for helping keep SourceForge clean.
X