[Coterie-users] A few questions to get it working...
Jason M. Felice
jfelice at cronosys.com
Mon Dec 26 20:32:54 EST 2005
This reply was written somewhat non-linearly. Apologies if it doesn't
flow right :)
Quoting Thomas 'ange' Riboulet <ange at librium.org>:
> well, I don't really know what to say about this mail. First : a big thank.
> Now, here is the state of the project :
> I'm sorry to say that the project is quite asleep since the 0.1
> release. I, as the lead and only developper, have been pretty busy on
> some other projects including my day job so it's more or less dead.
Ah I know the feeling. There's an RPG compiler floating out there in
the ether that I get pinged about at odd times... and I have to Google
in order to find the source myself :)
> This said, I'm quite aware of the fact that Coterie has its place in
> the world and it could be a real nice and usefull tool so I'm
> thinking about restarting the project from scratch in first half of
> I've got lot of ideas but also lot of questions.
Hmm, I'm curious why you'd want to start from scratch. I haven't
delved too deeply into the code, but I haven't seen any evidence of
something that will be painful to refactor, either. I'd enjoy some
understanding on what you're thinking.
We have some put some pretty heavy thought into our processes (we are a
technology consulting company and we plan on using this internally, and
to facilitate communication with the customers eventually). I wouldn't
mind answering questions about how we'd use it, what we are looking
Internally, I'm trying to focus on collecting user stories for our
projects. I would enjoy using that mechanism here.. actually I presume
I'd be using it anyway if you didn't see them.
I've just posted two patches on rubyforge--one large one for an update
to rails 1.0.0 (it was actually relatively painless) and another for an
omission in the .psql file. We're moving forward on this because of
our need for a central development server and our commitment to rails.
We've got it running as of now, although it looks like there are a half
dozen little nits to work out.
I'm using a darcs repository--if you were to use the same, I could more
easily send you patches.
> Atm Coterie isn't really usable, but could reborn in 2006. I know
> there is some people out there interested, and waiting after it.
> I'll be glad to listen to your needs before (and while) I'll be
> starting the new development branch.
Hmm. Where to start? Here's one for recursiveness: Coterie needs to
have a database of user stories for a project. Once that's
implemented, the coterie coterie project can begin collecting user
Or, it could be a per-project wiki. But it would be nice to have some
lose structure present throughout all the projects--I'd hate to have to
query for user stories by grepping page contents. A particular kind of
document in the document manager? Nah.
http://c2.com/cgi/wiki?UserStory (in case you don't already know)
> Thomas 'ange' Riboulet
> On Mon, 26 Dec 2005 11:18:59 -0500, "Jason M. Felice"
> <jfelice at cronosys.com> wrote:
>> Hi guys. This is exactly what we need, it seems. I've got a few
>> questions to get it working, and a couple comments:
>> * What version of rails was this built for? (I'll be updating it to 1.0)
>> * The homepage linked to by rubyforge.org fails with some sort of proxy
>> Is there an updated URL for the homepage? Do you need some hosting
>> space for
>> such a thing?
>> * Is there a publicly readable version control system for this? Any
>> changes since
>> 0.1 was released?
>> * We'd like to make this work for the darcs version control system,
>> anything you
>> might know offhand about that would be useful.
>> Jason M. Felice
>> Cronosys, LLC <http://www.cronosys.com>
>> 216-221-4600 x302
>> Coterie-users mailing list
>> Coterie-users at rubyforge.org
> Coterie-users mailing list
> Coterie-users at rubyforge.org
Jason M. Felice
Cronosys, LLC <http://www.cronosys.com>
More information about the Coterie-users