On 2007.09.04, Dave Bauer <[EMAIL PROTECTED]> wrote:
> Since you proposed changing to Trac, why can't you let us know your
> thinking behind it be listing
> 1) the problems you hope it will solve
SourceForge's issue tracker is unattractive, IMO. Trac is simple and it
"just works."
> 2) the proce
On 9/4/07, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
> Tom,
>
> You are welcome to propose a process that you feel will lead to success.
> Those who want to participate in the AOLserver Community are invited to
> read and respond to your proposal. If the community can arrive at some
> form of reas
Tom,
You are welcome to propose a process that you feel will lead to success.
Those who want to participate in the AOLserver Community are invited to
read and respond to your proposal. If the community can arrive at some
form of reasonable consensus around the process proposal, we can
consider it
On Sunday 02 September 2007 13:51, Daniël Mantione wrote:
> The project needs to move to a model where
> users just need to stick their finger in.
In general this is true, but as you explain below, this is the catch-22 of the
history of AOLserver. If you have any respect for the community process
On 2007.09.02, Dani?l Mantione <[EMAIL PROTECTED]> wrote:
> The bureaucracy of contributing needs to be reduced.
As of late, anyone who has asked for CVS commit access has been given
it. There are some 50-odd people who have CVS commit access.
> I agree a package like Trac can help by providing
On Sunday 02 September 2007 12:08, Dossy Shiobara wrote:
> On 2007.09.01, Tom Jackson <[EMAIL PROTECTED]> wrote:
> > Why don't we have an idea-raiser? Maybe it is a common disease among
> > programmers: writing code is apparently the only thing which counts.
>
> Ideas are easy to come by; doing--or
Op Sun, 2 Sep 2007, schreef Dossy Shiobara:
> On 2007.09.01, Tom Jackson <[EMAIL PROTECTED]> wrote:
> > Why don't we have an idea-raiser? Maybe it is a common disease among
> > programmers: writing code is apparently the only thing which counts.
>
> Ideas are easy to come by; doing--or, getti
On 2007.09.01, Tom Jackson <[EMAIL PROTECTED]> wrote:
> Why don't we have an idea-raiser? Maybe it is a common disease among
> programmers: writing code is apparently the only thing which counts.
Ideas are easy to come by; doing--or, getting people to do--is the hard
part. One easy way to get p
On 2007.08.31, Dave Bauer <[EMAIL PROTECTED]> wrote:
> On 8/31/07, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
> > Agreed. How do other, successfull, open source projects--as well as
> > closed-source commercial projects--get documentation written? Through
> > my own personal (anecdotal) experience
On Saturday 01 September 2007 09:13, Dossy Shiobara wrote:
> Would there be interest in funding a tech. writer for a short period of
> time? If we had a fund-raiser, perhaps we could hire one on a contract
> basis for a couple of months? In that case, what goals would we like to
> set? Those who
On 2007.09.01, Dave Bauer <[EMAIL PROTECTED]> wrote:
>
> I agree, where is AOLserver going. What was the motivation to make the
> big changes for AOLserver 4.5?
Without violating terms of any NDAs I may still be bound to, I'll try to
describe a real scenario (names changed to protect the ignorant
> > On 2007.08.31, Tom Jackson <[EMAIL PROTECTED]> wrote:
> > > Although it is easy to try to jump in and start documenting stuff,
> > > there is so little current documentation that there might be an
> > > opportunity to rethink how to do this.
> >
> > Agreed. How do other, successfull, open sour
On Friday 31 August 2007 18:19, Dossy Shiobara wrote:
> On 2007.08.31, Tom Jackson <[EMAIL PROTECTED]> wrote:
> > Although it is easy to try to jump in and start documenting stuff,
> > there is so little current documentation that there might be an
> > opportunity to rethink how to do this.
>
> Agr
On 8/31/07, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
>
> Agreed. How do other, successfull, open source projects--as well as
> closed-source commercial projects--get documentation written? Through
> my own personal (anecdotal) experience, the lead engineers are not the
> ones that do the majori
On 2007.08.31, Tom Jackson <[EMAIL PROTECTED]> wrote:
> Although it is easy to try to jump in and start documenting stuff,
> there is so little current documentation that there might be an
> opportunity to rethink how to do this.
Agreed. How do other, successfull, open source projects--as well as
Is it possible to start with what problem we are trying to solve? This isn't a
one man community, neither you or anyone else should shoulder the entire
burden. It's a noble motivation, but we really have to play to our collective
strengths. This is even more necessary now. Apparently we have one
On 2007.08.31, Dave Bauer <[EMAIL PROTECTED]> wrote:
> We have no idea why you decided we need to have a NEW bug tracker when
> the bugs in the current one are never dealt with.
You're right, we don't need a new bug tracker.
Yes, the bugs in the current one are never dealt with. Do you have any
Dossy,
All anyone on this list knows is
1) Dossy does not work for AOL
2) Dossy has "decided" that Trac would be good for the AOLserver project.
We have no idea why you decided we need to have a NEW bug tracker when
the bugs in the current one are never dealt with.
What problems are you trying
On 2007.08.31, Tom Jackson <[EMAIL PROTECTED]> wrote:
> Why is this speaking out against Trac? Why isn't this speaking up for
> AOLserver, Tcl, OpenACS, and everyone in the community who supports
> and uses these high quality products?
I, personally, am in no position right now to volunteer and/
Why is this speaking out against Trac? Why isn't this speaking up for
AOLserver, Tcl, OpenACS, and everyone in the community who supports and uses
these high quality products?
Anyway, I seem to remember my email being a little longer than a single line.
Personally I think the standard for mo
On 2007.08.31, Dave Bauer <[EMAIL PROTECTED]> wrote:
> CVS2SVN can do it. We recenetly experiemented with importing the
> entire OpenACS CVS tree into SVN and it was possible. OpenACS is
> gigantic compared to AOLserver so it seems likely its possible.
I've attempted cvs2svn conversion back in 200
El Fri, 31 Aug 2007 15:20:13 -0400 , Dave Bauer
<[EMAIL PROTECTED]> escribió:
> CVS2SVN can do it. We recenetly experiemented with importing the
> entire OpenACS CVS tree into SVN and it was possible. OpenACS is
> gigantic compared to AOLserver so it seems likely its possible.
I agree with Dave,
On 2007.08.31, Tom Jackson <[EMAIL PROTECTED]> wrote:
> Maybe support our own instead of moving to python and Apache.
Is that your only reason to speak out against Trac?
--
Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
Dossy said:
>
> > Revision Control:
> > * Given you've also suggested a move to SVN, similar questions should be
> > asked: will the revision histories be moved, or just the tip revision?
> > How much archeology will be required to find out that "Adam Zell
> > submitted this patch in 2002?"
>
> The
On 2007.08.30, Rick Cobb <[EMAIL PROTECTED]> wrote:
> Well, here's my take on it:
>
> This is a major change. The community should get at least 24 hours to
> react before we start seeing implementation notices. And Tom's right;
> I'd feel more respected if you'd mentioned _why_ you wanted to do t
and gaining that visibility is something I know we'd all like.
>
> Also, it's a lot better looking than Bugzilla :-).
>
> -- ReC
>
>
> -Original Message-
> From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf
> Of Dossy Shiobara
> Sent: Thur
scussion [mailto:[EMAIL PROTECTED] On Behalf
Of Dossy Shiobara
Sent: Thursday, August 30, 2007 10:09 PM
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Switching to Trac to manage the AOLserver
project?
On 2007.08.30, Tom Jackson <[EMAIL PROTECTED]> wrote:
> Not a single word abou
On 2007.08.30, Tom Jackson <[EMAIL PROTECTED]> wrote:
> Not a single word about benefits, pros and cons, what is the point of
> asking about strong feelings?
Sorry, I assumed that folks were familiar with Trac and those who
weren't would read up on it, as I even provided the URL.
-- Dossy
--
D
I think it is somewhat amazing that the community process has degraded to the
point of requiring strong feelings against the vague propositions of a single
community member in order to stop a major change.
Not a single word about benefits, pros and cons, what is the point of asking
about strong
Update: I've installed the Account Manager plugin for Trac, and now you
can register yourself for an account:
http://static.panoptic.com/aolserver/trac/register
I've also put in the DNS change request to have dev.aolserver.com point
to the Trac install. As soon as that's done, this will be t
On 2007.08.30, John Buckman <[EMAIL PROTECTED]> wrote:
> >After looking more closely at Trac [1], I'm really thinking it might
> >be a good idea to use it to manage the AOLserver project. Does
> >anyone have any strong feelings about this, particularly against it?
>
> I think this is a great ide
On 2007.08.30, Bas Scheffers <[EMAIL PROTECTED]> wrote:
> Sounds good to me. They say it integrates with svn, does that also
> mean switching AOLserver to svn?
I was hoping to do that too, yes, but not at the same time.
-- Dossy
--
Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.
Sounds good to me. They say it integrates with svn, does that also
mean switching AOLserver to svn?
On 30 Aug 2007, at 13:46, Dossy Shiobara wrote:
Hi,
After looking more closely at Trac [1], I'm really thinking it
might be a
good idea to use it to manage the AOLserver project. Does any
After looking more closely at Trac [1], I'm really thinking it
might be a
good idea to use it to manage the AOLserver project. Does anyone have
any strong feelings about this, particularly against it?
I think this is a great idea.
-john
--
AOLserver - http://www.aolserver.com/
To Remove y
34 matches
Mail list logo
