From tlockney at openmanagement.org  Wed Apr 18 00:50:33 2007
From: tlockney at openmanagement.org (Thomas Lockney)
Date: Tue, 17 Apr 2007 21:50:33 -0700
Subject: [ozimodo-development] Fwd: Ozimodo Feature List
In-Reply-To: <b63bd76d0704172041h8765860i85662c783c20e78b@mail.gmail.com>
References: <b63bd76d0704172041h8765860i85662c783c20e78b@mail.gmail.com>
Message-ID: <ae42e3d40704172150n71be69b2o2e99ce53d21d18c8@mail.gmail.com>

Responding via the list...

Regarding the "pages", perhaps we could just use Comatose (
http://comatose.rubyforge.org/)? I haven't ever tried it out, but it's just
a plugin, so it would be a lightweight integration, I would think.

---------- Forwarded message ----------
From: whurley <vision at whurley.com>
Date: Apr 17, 2007 8:41 PM
Subject: Ozimodo Feature List
To: Thomas Lockney <tlockney at openmanagement.org>, Matthew Buck <
techpeace at gmail.com>

Guys,

Here are the features that Chris sent to me:

- New (hotter) default theme (based on http://websushi.de/ ?)
- Keep tags
- Keep post types
- Keep multiple users
- Ditch RSS feed (Atom only)
- Ability to aggregate feeds and convert them to types (flickr photos
photo type, delicious links => link type, etc)
- Keep API
- Keep CLI tumbl'r
- Re-do localization
- Better theme system
- More tests
- Add "pages" (CMSy?!)

So the question here is how do we break these up into a release
schedule and when they're all done what should we version the project
to?

-whurley


--
whurley
+1 512-788-5353
vision at whurley.com
http://www.whurley.com
http://blog.whurley.com


-- 
Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070417/e29c2d6e/attachment.html 

From vision at whurley.com  Wed Apr 18 01:03:50 2007
From: vision at whurley.com (whurley)
Date: Wed, 18 Apr 2007 00:03:50 -0500
Subject: [ozimodo-development] feature thoughts...
Message-ID: <b63bd76d0704172203n56f833d0q3c0896dabd2b9e2b@mail.gmail.com>

Hey all,

Here is a list of features to add/keep that I received from Chris. I'd
like to start a discussion around what else should be added to this
list, and how we want to work together on how to prioritize these in
our development schedule. Here's the draft list Chris started:

- New (hotter) default theme (based on http://websushi.de/ ?)
- Keep tags
- Keep post types
- Keep multiple users
- Ditch RSS feed (Atom only)
- Ability to aggregate feeds and convert them to types (flickr photos
photo type, delicious links => link type, etc)
- Keep API
- Keep CLI tumbl'r
- Re-do localization
- Better theme system
- More tests
- Add "pages" (CMSy?!)

Let's add anything else we'd like to see in ozimodo and then talk priorities.

-whurley


-- 
whurley
vision at whurley.com
http://www.whurley.com
http://blog.whurley.com

From jay at meangrape.com  Wed Apr 18 09:22:22 2007
From: jay at meangrape.com (Jay Edwards)
Date: Wed, 18 Apr 2007 08:22:22 -0500
Subject: [ozimodo-development] feature thoughts...
In-Reply-To: <b63bd76d0704172203n56f833d0q3c0896dabd2b9e2b@mail.gmail.com>
References: <b63bd76d0704172203n56f833d0q3c0896dabd2b9e2b@mail.gmail.com>
Message-ID: <81a8869b0704180622q1df256aayeed68cea09f25a41@mail.gmail.com>

On 4/18/07, whurley <vision at whurley.com> wrote:
>
> - Ability to aggregate feeds and convert them to types (flickr photos
> photo type, delicious links => link type, etc)
>
> I'd also like it to go the other way -- a photo type could be
auto-submitted to flicker, etc.

The other thing I'd like to see is twitter posting / receiving. Both on an
individual basis and on the 'community of ozimode users' basis. I've snagged
the twitter ozimodo id already.  If a ozimodo user opts in, maybe one out of
every X posts gets sent to the ozimodo twitter channel.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070418/b68c6880/attachment.html 

From jay at meangrape.com  Wed Apr 18 09:29:24 2007
From: jay at meangrape.com (Jay Edwards)
Date: Wed, 18 Apr 2007 08:29:24 -0500
Subject: [ozimodo-development] Fwd: Ozimodo Feature List
In-Reply-To: <ae42e3d40704172150n71be69b2o2e99ce53d21d18c8@mail.gmail.com>
References: <b63bd76d0704172041h8765860i85662c783c20e78b@mail.gmail.com>
	<ae42e3d40704172150n71be69b2o2e99ce53d21d18c8@mail.gmail.com>
Message-ID: <81a8869b0704180629s54bca1b5s32f049e6a53e5cb9@mail.gmail.com>

On 4/17/07, Thomas Lockney <tlockney at openmanagement.org> wrote:
>
> Responding via the list...
>
> Regarding the "pages", perhaps we could just use Comatose (
> http://comatose.rubyforge.org/)? I haven't ever tried it out, but it's
> just a plugin, so it would be a lightweight integration, I would think.



My concern with 'pages' is that it doesn't end up being an ugly bolt-on. A
tumbleblog is inherently different from the standard concept of a blog or
wiki. Adding features is not always a good thing. I think this is something
that can wait while the implications are pondered.

Now, what I would like to see is dynamic pages for each post type.
http://www.meangrape.com/photos http://www.meangrape.com/links
http://www.meangrape.com/blog http://www.meangrape.com/video

That way if we massage the post types correctly and set up navigation on the
dynamic pages we can provide the image of a traditional blog or photostream
or whathaveyou.

I think that might obviate the need for a separate "add pages" kind of thing
which, again, I don't really see being easy to fit into ozimodo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070418/9977420d/attachment.html 

From tlockney at gmail.com  Wed Apr 18 11:30:16 2007
From: tlockney at gmail.com (Thomas Lockney)
Date: Wed, 18 Apr 2007 08:30:16 -0700
Subject: [ozimodo-development] Fwd:  Fwd: Ozimodo Feature List
In-Reply-To: <ae42e3d40704180829l73e87e72g191345b0be61f18e@mail.gmail.com>
References: <b63bd76d0704172041h8765860i85662c783c20e78b@mail.gmail.com>
	<ae42e3d40704172150n71be69b2o2e99ce53d21d18c8@mail.gmail.com>
	<81a8869b0704180629s54bca1b5s32f049e6a53e5cb9@mail.gmail.com>
	<ae42e3d40704180829l73e87e72g191345b0be61f18e@mail.gmail.com>
Message-ID: <ae42e3d40704180830g4c69a7fbn1517842472f12ec5@mail.gmail.com>

Ugh, meant to reply to the list...

---------- Forwarded message ----------
From: Thomas Lockney <tlockney at openmanagement.org>
Date: Apr 18, 2007 8:29 AM
Subject: Re: [ozimodo-development] Fwd: Ozimodo Feature List
To: Jay Edwards <jay at meangrape.com>

On 4/18/07, Jay Edwards <jay at meangrape.com> wrote:

> My concern with 'pages' is that it doesn't end up being an ugly bolt-on. A
> tumbleblog is inherently different from the standard concept of a blog or
> wiki. Adding features is not always a good thing. I think this is something
> that can wait while the implications are pondered.
>

I think it's pretty common to want to be able to put up at least an about
page, etc. and don't see why this would be much of an issue if it has a low
impact on the rest of the codebase. Part of the reason for suggesting
Comatose was precisely to keep this from involving too many changes to the
core Ozimodo code.

Now, what I would like to see is dynamic pages for each post type.
> http://www.meangrape.com/photos http://www.meangrape.com/links
> http://www.meangrape.com/blog http://www.meangrape.com/video
>

I agree. I also think that feeds generated per content type could be a way
to provide part of what you mentioned in another email regarding pushing
content to places like Flickr. I would think that the push portion of that
equation would be outside the bounds of what Ozimodo should do, but rather
should be a separate tool (which we could certainly develop alongside
things).

whurley and I have been talking for some time now about a tool that would be
able to take feeds generated by a variety of sources and then, based on
simple rule definitions, push that content out to a variety of "containers".
I think that sort of app could work quite nicely alongside tumbleblogs,
traditional blogs, flickr feeds, etc., but it seems to me that it requires
quite a different feature set from a tumbleblog or a regular blog, for that
matter.

Anyway, regarding the pages, I think if it's a very simple implementation,
it could complement things rather than being a bolt on. I'll play with it a
bit and then we can see if it's a reasonable addition.

-- 
Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net


-- 
Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070418/ac9d0af8/attachment-0001.html 

From adam at therealadam.com  Wed Apr 18 11:34:14 2007
From: adam at therealadam.com (Adam Keys)
Date: Wed, 18 Apr 2007 10:34:14 -0500
Subject: [ozimodo-development] feature thoughts...
In-Reply-To: <b63bd76d0704172203n56f833d0q3c0896dabd2b9e2b@mail.gmail.com>
References: <b63bd76d0704172203n56f833d0q3c0896dabd2b9e2b@mail.gmail.com>
Message-ID: <1E5B7D00-D723-47D8-8319-6E95C4EDDD09@therealadam.com>

On Apr 18, 2007, at 12:03 AM, whurley wrote:

> Hey all,
>
> Here is a list of features to add/keep that I received from Chris. I'd
> like to start a discussion around what else should be added to this
> list, and how we want to work together on how to prioritize these in
> our development schedule. Here's the draft list Chris started:

Here's something I spoke with Chris about.  Right now, Rails sucks  
for running a weblog on a shared host.  Most shared hosts doing Rails  
hosting apply a resident memory limit to each Mongrel or FastCGI  
process.  Processes exceeding this are killed with maximum  
prejudice.  Typo just barely fits under TextDrive's memory limit, for  
example.  Mephisto is not an option on a host like that.

So I think there's an opportunity for Ozimodo to sneak in under this  
limitation.  I think the approach that would help here is to develop  
as much functionality as possible in plugins.  In concert with some  
Capistrano cleverness, I believe you could make it easy for a user to  
deploy Ozimodo along with only the plugins they are going to actually  
use to their shared host.

Unfortunately, I've never really come across much on "memory  
profiling" Ruby or Rails.  One of the former Typo maintainers wrote a  
janky little script, but there's nothing coherent yet.

--
~akk
http://therealadam.com



From jay at meangrape.com  Wed Apr 18 12:00:38 2007
From: jay at meangrape.com (Jay Edwards)
Date: Wed, 18 Apr 2007 11:00:38 -0500
Subject: [ozimodo-development] Fwd: Fwd: Ozimodo Feature List
In-Reply-To: <ae42e3d40704180830g4c69a7fbn1517842472f12ec5@mail.gmail.com>
References: <b63bd76d0704172041h8765860i85662c783c20e78b@mail.gmail.com>
	<ae42e3d40704172150n71be69b2o2e99ce53d21d18c8@mail.gmail.com>
	<81a8869b0704180629s54bca1b5s32f049e6a53e5cb9@mail.gmail.com>
	<ae42e3d40704180829l73e87e72g191345b0be61f18e@mail.gmail.com>
	<ae42e3d40704180830g4c69a7fbn1517842472f12ec5@mail.gmail.com>
Message-ID: <81a8869b0704180900k52e2c792n36811e6de5d16fc2@mail.gmail.com>

>
> On 4/18/07, Jay Edwards <jay at meangrape.com> wrote:
>
> > My concern with 'pages' is that it doesn't end up being an ugly bolt-on.
> > A tumbleblog is inherently different from the standard concept of a blog or
> > wiki. Adding features is not always a good thing. I think this is something
> > that can wait while the implications are pondered.
> >
>
> I think it's pretty common to want to be able to put up at least an about
> page, etc. and don't see why this would be much of an issue if it has a low
> impact on the rest of the codebase. Part of the reason for suggesting
> Comatose was precisely to keep this from involving too many changes to the
> core Ozimodo code.
>

I definitely see the need for being able to add and manage static pages. I
really should look at Comatose to see how light-weight it is.

Now, what I would like to see is dynamic pages for each post type.
> > http://www.meangrape.com/photos http://www.meangrape.com/links
> > http://www.meangrape.com/blog http://www.meangrape.com/video
> >
>
> I agree. I also think that feeds generated per content type could be a way
> to provide part of what you mentioned in another email regarding pushing
> content to places like Flickr. I would think that the push portion of that
> equation would be outside the bounds of what Ozimodo should do, but rather
> should be a separate tool (which we could certainly develop alongside
> things).
>

I see the appeal of generalizing that functionality out into a separate
tool, but I don't necessarily agree that Ozimodo shouldn't be able to handle
it with some sort of ozimodo-specific plugin. OK. I'm thinking here...I
might change my mind...

I send a photo to Ozimodo. Ozimodo posts it to the front page. Ozimodo
submits "type:pointer-to-content" to the SubmitThingstoPlacesEngine. The
ST2PE looks in its catalog of types and either throws the content away or
sends it on.

The question I have is: do we report errors to Ozimodo? Or use error
notification via email or some other method in the ST2PE? I think the later
-- all ozimodo should know is that it submits things. Actually, I suppose
that the ST2PE could poll the ozimodo page, but that's relatively inelegant
even though it's more general -- maybe that could be a general method..."I
know about Ozimodo, but if I'm perfectly happy to scan generic web pages and
look for metadata".


Anyway, regarding the pages, I think if it's a very simple implementation,
> it could complement things rather than being a bolt on. I'll play with it a
> bit and then we can see if it's a reasonable addition.
>

Simplicity is what I'm looking for. Adding on a full-blown wiki/blogging
tool seems to be a bit over-the-top. Being able to add a few simple static
pages is a great idea.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070418/0d6d32b9/attachment.html 

From tlockney at gmail.com  Wed Apr 18 12:08:38 2007
From: tlockney at gmail.com (Thomas Lockney)
Date: Wed, 18 Apr 2007 09:08:38 -0700
Subject: [ozimodo-development] Fwd: Fwd: Ozimodo Feature List
In-Reply-To: <81a8869b0704180900k52e2c792n36811e6de5d16fc2@mail.gmail.com>
References: <b63bd76d0704172041h8765860i85662c783c20e78b@mail.gmail.com>
	<ae42e3d40704172150n71be69b2o2e99ce53d21d18c8@mail.gmail.com>
	<81a8869b0704180629s54bca1b5s32f049e6a53e5cb9@mail.gmail.com>
	<ae42e3d40704180829l73e87e72g191345b0be61f18e@mail.gmail.com>
	<ae42e3d40704180830g4c69a7fbn1517842472f12ec5@mail.gmail.com>
	<81a8869b0704180900k52e2c792n36811e6de5d16fc2@mail.gmail.com>
Message-ID: <ae42e3d40704180908s642b488cub9663ac9913e6052@mail.gmail.com>

On 4/18/07, Jay Edwards <jay at meangrape.com> wrote:
>
>
> I see the appeal of generalizing that functionality out into a separate
> tool, but I don't necessarily agree that Ozimodo shouldn't be able to handle
> it with some sort of ozimodo-specific plugin. OK. I'm thinking here...I
> might change my mind...
>

I can definitely see a plugin as one possible approach here. That makes a
bit more sense to me.

The question I have is: do we report errors to Ozimodo? Or use error
> notification via email or some other method in the ST2PE? I think the later
> -- all ozimodo should know is that it submits things. Actually, I suppose
> that the ST2PE could poll the ozimodo page, but that's relatively inelegant
> even though it's more general -- maybe that could be a general method..."I
> know about Ozimodo, but if I'm perfectly happy to scan generic web pages and
> look for metadata".
>

Just throwing out a couple thoughts here:

1. Generating feeds based on content type would keep the tool from needing
to poll as long as those feeds (Atom, I'm assuming) contained enough
metadata.

2. Alternately (or additionally?) we could perhaps look for any existing
microformats to see if they might make this "scraping" simpler. Microformats
in general might be a good addition to Ozimodo (where they make sense
anyway).


--
Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070418/4ee99ce8/attachment.html 

From jay at meangrape.com  Wed Apr 18 12:14:43 2007
From: jay at meangrape.com (Jay Edwards)
Date: Wed, 18 Apr 2007 11:14:43 -0500
Subject: [ozimodo-development] Fwd: Fwd: Ozimodo Feature List
In-Reply-To: <ae42e3d40704180908s642b488cub9663ac9913e6052@mail.gmail.com>
References: <b63bd76d0704172041h8765860i85662c783c20e78b@mail.gmail.com>
	<ae42e3d40704172150n71be69b2o2e99ce53d21d18c8@mail.gmail.com>
	<81a8869b0704180629s54bca1b5s32f049e6a53e5cb9@mail.gmail.com>
	<ae42e3d40704180829l73e87e72g191345b0be61f18e@mail.gmail.com>
	<ae42e3d40704180830g4c69a7fbn1517842472f12ec5@mail.gmail.com>
	<81a8869b0704180900k52e2c792n36811e6de5d16fc2@mail.gmail.com>
	<ae42e3d40704180908s642b488cub9663ac9913e6052@mail.gmail.com>
Message-ID: <81a8869b0704180914v58714ed3o494c8dd1a5c4dfc1@mail.gmail.com>

On 4/18/07, Thomas Lockney <tlockney at gmail.com> wrote:
>
> Just throwing out a couple thoughts here:
>
> 1. Generating feeds based on content type would keep the tool from needing
> to poll as long as those feeds (Atom, I'm assuming) contained enough
> metadata.
>
> I like that idea. Atom has an optional type attribute for entries.

3.1.1  "type" Attribute

Content constructs MAY have a "type" attribute, whose value indicates the
media type of the content. When present, this attribute's value MUST be a
registered media type
[RFC2045]<http://www.mnot.net/drafts/draft-nottingham-atom-format-02.html#RFC2045>.
If not present, its value MUST be considered to be "text/plain".

Sooo. We need a tool that subscribes to feeds and then submits them to
wherever based on content type. Got it. Sounds like a plan to me.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070418/1e5b5f3b/attachment.html 

From techpeace at gmail.com  Fri Apr 20 16:23:53 2007
From: techpeace at gmail.com (Matthew Buck)
Date: Fri, 20 Apr 2007 15:23:53 -0500
Subject: [ozimodo-development] ozimodo upgraded to Rails 1.2.3
Message-ID: <d0fe25890704201323u6ccd431ep99f73f305cbb9920@mail.gmail.com>

Hello all,

Just wanted to let everyone know that as of now, trunk is running on Rails
1.2.3 (and postgres, if you're so inclined), and the theme support issues
appear to have been worked out.  This means that we can really get going
full tilt on the rest of the development.

As for me, I'm going to be re-writing the tests in rspec to get a better
feel for the code and to make sure that we have all our bases covered before
we start tacking on new features.

Thanks,
Matt Buck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070420/20bb60cc/attachment.html 

From tlockney at gmail.com  Fri Apr 20 17:27:56 2007
From: tlockney at gmail.com (Thomas Lockney)
Date: Fri, 20 Apr 2007 14:27:56 -0700
Subject: [ozimodo-development] ozimodo upgraded to Rails 1.2.3
In-Reply-To: <ae42e3d40704201356v7699e91av42c04be576de5c1e@mail.gmail.com>
References: <d0fe25890704201323u6ccd431ep99f73f305cbb9920@mail.gmail.com>
	<ae42e3d40704201356v7699e91av42c04be576de5c1e@mail.gmail.com>
Message-ID: <ae42e3d40704201427o6cfc2a12y815f90762abebc7c@mail.gmail.com>

Got stung by the lack of reply-to-list functionality... meant for this to go
to the list.

On 4/20/07, Thomas Lockney <tlockney at gmail.com> wrote:
>
> You know, it seems to me maybe there should be a quick release based on
> these latest changes. I'm sure more people would be willing to use ozimodo
> if it worked on the current rails release. What do you guys think?
>
> On 4/20/07, Matthew Buck <techpeace at gmail.com> wrote:
> >
> > Hello all,
> >
> > Just wanted to let everyone know that as of now, trunk is running on
> > Rails 1.2.3 (and postgres, if you're so inclined), and the theme support
> > issues appear to have been worked out.  This means that we can really get
> > going full tilt on the rest of the development.
> >
> > As for me, I'm going to be re-writing the tests in rspec to get a better
> > feel for the code and to make sure that we have all our bases covered before
> > we start tacking on new features.
> >
> > Thanks,
> > Matt Buck
> >
> > _______________________________________________
> > ozimodo-development mailing list
> > ozimodo-development at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/ozimodo-development
> >
>
>
>
> --
> Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
>



-- 
Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070420/df8bcd46/attachment-0001.html 

From techpeace at gmail.com  Fri Apr 20 19:26:45 2007
From: techpeace at gmail.com (Matthew Buck)
Date: Fri, 20 Apr 2007 18:26:45 -0500
Subject: [ozimodo-development] ozimodo upgraded to Rails 1.2.3
In-Reply-To: <ae42e3d40704201427o6cfc2a12y815f90762abebc7c@mail.gmail.com>
References: <d0fe25890704201323u6ccd431ep99f73f305cbb9920@mail.gmail.com>
	<ae42e3d40704201356v7699e91av42c04be576de5c1e@mail.gmail.com>
	<ae42e3d40704201427o6cfc2a12y815f90762abebc7c@mail.gmail.com>
Message-ID: <d0fe25890704201626q55b3c393le12147fcb3b70db9@mail.gmail.com>

>
> You know, it seems to me maybe there should be a quick release based on
> these latest changes.


Sounds good to me.  We might want to tackle a few of the active bugs first,
though.  Any takers?

-Matt

On 4/20/07, Thomas Lockney <tlockney at gmail.com> wrote:
>
> Got stung by the lack of reply-to-list functionality... meant for this to
> go to the list.
>
> On 4/20/07, Thomas Lockney < tlockney at gmail.com> wrote:
> >
> > You know, it seems to me maybe there should be a quick release based on
> > these latest changes. I'm sure more people would be willing to use ozimodo
> > if it worked on the current rails release. What do you guys think?
> >
> > On 4/20/07, Matthew Buck <techpeace at gmail.com > wrote:
> > >
> > > Hello all,
> > >
> > > Just wanted to let everyone know that as of now, trunk is running on
> > > Rails 1.2.3 (and postgres, if you're so inclined), and the theme
> > > support issues appear to have been worked out.  This means that we can
> > > really get going full tilt on the rest of the development.
> > >
> > > As for me, I'm going to be re-writing the tests in rspec to get a
> > > better feel for the code and to make sure that we have all our bases covered
> > > before we start tacking on new features.
> > >
> > > Thanks,
> > > Matt Buck
> > >
> > > _______________________________________________
> > > ozimodo-development mailing list
> > > ozimodo-development at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/ozimodo-development
> > >
> >
> >
> >
> > --
> > Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
> >
>
>
>
> --
> Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
>
> _______________________________________________
> ozimodo-development mailing list
> ozimodo-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ozimodo-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070420/5ef3abb7/attachment.html 

From jay at meangrape.com  Fri Apr 20 21:05:57 2007
From: jay at meangrape.com (Jay Edwards)
Date: Fri, 20 Apr 2007 20:05:57 -0500
Subject: [ozimodo-development] ozimodo upgraded to Rails 1.2.3
In-Reply-To: <d0fe25890704201626q55b3c393le12147fcb3b70db9@mail.gmail.com>
References: <d0fe25890704201323u6ccd431ep99f73f305cbb9920@mail.gmail.com>
	<ae42e3d40704201356v7699e91av42c04be576de5c1e@mail.gmail.com>
	<ae42e3d40704201427o6cfc2a12y815f90762abebc7c@mail.gmail.com>
	<d0fe25890704201626q55b3c393le12147fcb3b70db9@mail.gmail.com>
Message-ID: <81a8869b0704201805u2285fd6eudc403968688a4931@mail.gmail.com>

I'll take a poke at 9899 -- feeds/atom.xml produces 'File not found' error

On 4/20/07, Matthew Buck <techpeace at gmail.com> wrote:
>
> You know, it seems to me maybe there should be a quick release based on
> > these latest changes.
>
>
> Sounds good to me.  We might want to tackle a few of the active bugs
> first, though.  Any takers?
>
> -Matt
>
> On 4/20/07, Thomas Lockney <tlockney at gmail.com> wrote:
> >
> > Got stung by the lack of reply-to-list functionality... meant for this
> > to go to the list.
> >
> > On 4/20/07, Thomas Lockney < tlockney at gmail.com> wrote:
> > >
> > > You know, it seems to me maybe there should be a quick release based
> > > on these latest changes. I'm sure more people would be willing to use
> > > ozimodo if it worked on the current rails release. What do you guys think?
> > >
> > > On 4/20/07, Matthew Buck <techpeace at gmail.com > wrote:
> > > >
> > > > Hello all,
> > > >
> > > > Just wanted to let everyone know that as of now, trunk is running on
> > > > Rails 1.2.3 (and postgres, if you're so inclined), and the theme
> > > > support issues appear to have been worked out.  This means that we can
> > > > really get going full tilt on the rest of the development.
> > > >
> > > > As for me, I'm going to be re-writing the tests in rspec to get a
> > > > better feel for the code and to make sure that we have all our bases covered
> > > > before we start tacking on new features.
> > > >
> > > > Thanks,
> > > > Matt Buck
> > > >
> > > > _______________________________________________
> > > > ozimodo-development mailing list
> > > > ozimodo-development at rubyforge.org
> > > > http://rubyforge.org/mailman/listinfo/ozimodo-development
> > > >
> > >
> > >
> > >
> > > --
> > > Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
> > >
> >
> >
> >
> > --
> > Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
> >
> > _______________________________________________
> > ozimodo-development mailing list
> > ozimodo-development at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/ozimodo-development
> >
>
>
> _______________________________________________
> ozimodo-development mailing list
> ozimodo-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ozimodo-development
>



-- 
Jay
jay at meangrape.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070420/b7c8d574/attachment.html 

From vision at whurley.com  Fri Apr 20 21:21:36 2007
From: vision at whurley.com (whurley)
Date: Fri, 20 Apr 2007 20:21:36 -0500
Subject: [ozimodo-development] ozimodo upgraded to Rails 1.2.3
In-Reply-To: <81a8869b0704201805u2285fd6eudc403968688a4931@mail.gmail.com>
References: <d0fe25890704201323u6ccd431ep99f73f305cbb9920@mail.gmail.com>
	<ae42e3d40704201356v7699e91av42c04be576de5c1e@mail.gmail.com>
	<ae42e3d40704201427o6cfc2a12y815f90762abebc7c@mail.gmail.com>
	<d0fe25890704201626q55b3c393le12147fcb3b70db9@mail.gmail.com>
	<81a8869b0704201805u2285fd6eudc403968688a4931@mail.gmail.com>
Message-ID: <b63bd76d0704201821v2f676d4dgcbf2700fe9f7a4d2@mail.gmail.com>

Thanks Jay.

On 4/20/07, Jay Edwards <jay at meangrape.com> wrote:
> I'll take a poke at 9899 -- feeds/atom.xml produces 'File not found' error
>
>
> On 4/20/07, Matthew Buck < techpeace at gmail.com> wrote:
> >
> > > You know, it seems to me maybe there should be a quick release based on
> these latest changes.
> >
> >
> > Sounds good to me.  We might want to tackle a few of the active bugs
> first, though.  Any takers?
> >
> > -Matt
> >
> >
> >
> > On 4/20/07, Thomas Lockney <tlockney at gmail.com > wrote:
> > > Got stung by the lack of reply-to-list functionality... meant for this
> to go to the list.
> > >
> > >
> > >
> > > On 4/20/07, Thomas Lockney < tlockney at gmail.com> wrote:
> > > > You know, it seems to me maybe there should be a quick release based
> on these latest changes. I'm sure more people would be willing to use
> ozimodo if it worked on the current rails release. What do you guys think?
> > > >
> > > >
> > > > On 4/20/07, Matthew Buck <techpeace at gmail.com > wrote:
> > > > >
> > > > > Hello all,
> > > > >
> > > > > Just wanted to let everyone know that as of now, trunk is running on
> Rails 1.2.3 (and postgres, if you're so inclined), and the theme support
> issues appear to have been worked out.  This means that we can really get
> going full tilt on the rest of the development.
> > > > >
> > > > > As for me, I'm going to be re-writing the tests in rspec to get a
> better feel for the code and to make sure that we have all our bases covered
> before we start tacking on new features.
> > > > >
> > > > > Thanks,
> > > > > Matt Buck
> > > > >
> > > > > _______________________________________________
> > > > > ozimodo-development mailing list
> > > > > ozimodo-development at rubyforge.org
> > > > >
> http://rubyforge.org/mailman/listinfo/ozimodo-development
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
> > >
> > >
> > >
> > > --
> > > Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
> > > _______________________________________________
> > > ozimodo-development mailing list
> > > ozimodo-development at rubyforge.org
> > >
> http://rubyforge.org/mailman/listinfo/ozimodo-development
> > >
> >
> >
> > _______________________________________________
> > ozimodo-development mailing list
> > ozimodo-development at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/ozimodo-development
> >
>
>
>
> --
> Jay
> jay at meangrape.com
> _______________________________________________
> ozimodo-development mailing list
> ozimodo-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ozimodo-development
>


-- 
whurley
+1 512-788-5353
vision at whurley.com
http://www.whurley.com
http://blog.whurley.com

From techpeace at gmail.com  Wed Apr 25 07:17:19 2007
From: techpeace at gmail.com (Matthew Buck)
Date: Wed, 25 Apr 2007 06:17:19 -0500
Subject: [ozimodo-development] New release?
Message-ID: <d0fe25890704250417g1b6c443exd7b3625a9d02a2ba@mail.gmail.com>

Hello all,

Last night I went through the tracker and added the one outstanding patch
and killed the bugs that I could replicate.  I also made some (minor)
adjustments to the admin interface. All of my changes have been committed to
trunk.

I'm writing to find out if there's still support for making a quick update
release.  Whaddya think, folks?  Should we release ozimodo into the wild
once more?

-Matt Buck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070425/96eb75d8/attachment.html 

From jay at meangrape.com  Wed Apr 25 07:47:42 2007
From: jay at meangrape.com (Jay Edwards)
Date: Wed, 25 Apr 2007 06:47:42 -0500
Subject: [ozimodo-development] New release?
In-Reply-To: <d0fe25890704250417g1b6c443exd7b3625a9d02a2ba@mail.gmail.com>
References: <d0fe25890704250417g1b6c443exd7b3625a9d02a2ba@mail.gmail.com>
Message-ID: <81a8869b0704250447x31dae4ct8a19443bd3cbe693@mail.gmail.com>

Let'er rip, man.


On 4/25/07, Matthew Buck <techpeace at gmail.com> wrote:
>
> Hello all,
>
> Last night I went through the tracker and added the one outstanding patch
> and killed the bugs that I could replicate.  I also made some (minor)
> adjustments to the admin interface. All of my changes have been committed to
> trunk.
>
> I'm writing to find out if there's still support for making a quick update
> release.  Whaddya think, folks?  Should we release ozimodo into the wild
> once more?
>
> -Matt Buck
>
> _______________________________________________
> ozimodo-development mailing list
> ozimodo-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ozimodo-development
>



-- 
Jay
jay at meangrape.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070425/2db036f3/attachment.html 

From tlockney at gmail.com  Wed Apr 25 10:37:44 2007
From: tlockney at gmail.com (Thomas Lockney)
Date: Wed, 25 Apr 2007 07:37:44 -0700
Subject: [ozimodo-development] New release?
In-Reply-To: <d0fe25890704250417g1b6c443exd7b3625a9d02a2ba@mail.gmail.com>
References: <d0fe25890704250417g1b6c443exd7b3625a9d02a2ba@mail.gmail.com>
Message-ID: <ae42e3d40704250737g23e69351t29378f0673d7d9e9@mail.gmail.com>

Go for it!

On 4/25/07, Matthew Buck <techpeace at gmail.com> wrote:
>
> Hello all,
>
> Last night I went through the tracker and added the one outstanding patch
> and killed the bugs that I could replicate.  I also made some (minor)
> adjustments to the admin interface. All of my changes have been committed to
> trunk.
>
> I'm writing to find out if there's still support for making a quick update
> release.  Whaddya think, folks?  Should we release ozimodo into the wild
> once more?
>
> -Matt Buck
>
> _______________________________________________
> ozimodo-development mailing list
> ozimodo-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ozimodo-development
>



-- 
Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070425/0dc5b303/attachment-0001.html 

From techpeace at gmail.com  Wed Apr 25 15:58:48 2007
From: techpeace at gmail.com (Matthew Buck)
Date: Wed, 25 Apr 2007 14:58:48 -0500
Subject: [ozimodo-development] New release?
In-Reply-To: <ae42e3d40704250737g23e69351t29378f0673d7d9e9@mail.gmail.com>
References: <d0fe25890704250417g1b6c443exd7b3625a9d02a2ba@mail.gmail.com>
	<ae42e3d40704250737g23e69351t29378f0673d7d9e9@mail.gmail.com>
Message-ID: <d0fe25890704251258s4ca58a6ah2cfc0706d86243f@mail.gmail.com>

I also wanted to let everyone know that I "discovered" a plugin interface.
Chris apparently added it after the last release.  You can check it out in
/lib/ozimodo/commands.rb and /lib/ozimodo/plugins.rb.  It looks pretty
slick, and it lets us work on some of that extra functionality folks have
been discussing.

-Matt Buck

On 4/25/07, Thomas Lockney <tlockney at gmail.com> wrote:
>
> Go for it!
>
> On 4/25/07, Matthew Buck <techpeace at gmail.com> wrote:
> >
> > Hello all,
> >
> > Last night I went through the tracker and added the one outstanding
> > patch and killed the bugs that I could replicate.  I also made some (minor)
> > adjustments to the admin interface. All of my changes have been committed to
> > trunk.
> >
> > I'm writing to find out if there's still support for making a quick
> > update release.  Whaddya think, folks?  Should we release ozimodo into the
> > wild once more?
> >
> > -Matt Buck
> >
> > _______________________________________________
> > ozimodo-development mailing list
> > ozimodo-development at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/ozimodo-development
> >
>
>
>
> --
> Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
> _______________________________________________
> ozimodo-development mailing list
> ozimodo-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ozimodo-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ozimodo-development/attachments/20070425/3baf5356/attachment.html 

From vision at whurley.com  Wed Apr 25 18:56:43 2007
From: vision at whurley.com (whurley)
Date: Wed, 25 Apr 2007 17:56:43 -0500
Subject: [ozimodo-development] New release?
In-Reply-To: <d0fe25890704251258s4ca58a6ah2cfc0706d86243f@mail.gmail.com>
References: <d0fe25890704250417g1b6c443exd7b3625a9d02a2ba@mail.gmail.com>
	<ae42e3d40704250737g23e69351t29378f0673d7d9e9@mail.gmail.com>
	<d0fe25890704251258s4ca58a6ah2cfc0706d86243f@mail.gmail.com>
Message-ID: <b63bd76d0704251556w7493a437vc452a68879421e67@mail.gmail.com>

Sweet on the plugins, make it happen on the release. :)

-whurley


On 4/25/07, Matthew Buck <techpeace at gmail.com> wrote:
> I also wanted to let everyone know that I "discovered" a plugin interface.
> Chris apparently added it after the last release.  You can check it out in
> /lib/ozimodo/commands.rb and /lib/ozimodo/plugins.rb.  It looks pretty
> slick, and it lets us work on some of that extra functionality folks have
> been discussing.
>
> -Matt Buck
>
>
> On 4/25/07, Thomas Lockney <tlockney at gmail.com> wrote:
> > Go for it!
> >
> >
> > On 4/25/07, Matthew Buck < techpeace at gmail.com> wrote:
> > >
> > > Hello all,
> > >
> > > Last night I went through the tracker and added the one outstanding
> patch and killed the bugs that I could replicate.  I also made some (minor)
> adjustments to the admin interface. All of my changes have been committed to
> trunk.
> > >
> > > I'm writing to find out if there's still support for making a quick
> update release.  Whaddya think, folks?  Should we release ozimodo into the
> wild once more?
> > >
> > > -Matt Buck
> > >
> > > _______________________________________________
> > > ozimodo-development mailing list
> > > ozimodo-development at rubyforge.org
> > >
> http://rubyforge.org/mailman/listinfo/ozimodo-development
> > >
> >
> >
> >
> > --
> > Thomas Lockney | tlockney at gmail.com | http://opposable-thumbs.net
> > _______________________________________________
> > ozimodo-development mailing list
> > ozimodo-development at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/ozimodo-development
> >
>
>
> _______________________________________________
> ozimodo-development mailing list
> ozimodo-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ozimodo-development
>


-- 
whurley
+1 512-788-5353
vision at whurley.com
http://www.whurley.com
http://blog.whurley.com
http://opensville.org