[Webtest] Collaboration - was: Fix for 2 successive <followframe ..>
22 May 2003 11:39:33 +0200
i do totally agree that a split off like "openwebtest" or something like
that is really not a solution.
I also do understand the problem of including fixes fast into the
distribution. But isn't that the same, when having hosted this project
by a system like sourceforge? Those projects have restrictions for
receiving write access to the repository too.. And so they perform a
similar work-flow like here..
My situation some months ago was nearly the same. My implementation of
the followframe step. After some postings to the mailing-list, replies
and hints (for adding the needed tests) from Dierk, the step was added
and I received write-access to the repository. To handle it like that is
a nice solution that works in most projects like cruise-control for
example.. (See cruisecontrol doc for that)
Problems right now are perhaps that Canoo founders and maintainers are
not active enough to look at patches, answer messages very fast. (But
this is a temporary problem I think.)
And there is no howto or any documentation about delivering successfull
patches, perhaps helping to make it easier..
So the solution should really be to improve collaboration. For the missing
howto: for me it worked to read the mailing-list archive..
Ok, that was just a short presentation from my point of view..
On Wed, 2003-05-21 at 21:47, Siegfried G=F6schl wrote:
> Hi folks,
> improving collaboration with Canoo would be the best thing. It is=20
> similar to the JAKARTA projects - if you don't have commit rights you=20
> can only complain. And it takes quite an efforT to become a committer=20
> since nobody is eager to erode the code base.=20
> And I see any separate code base as a potential nightmare. Just image=20
> the next major release where nearly everything might have changed?!=20
> Who is migrating those changes for the separate code base?!
> Siegfried Goeschl
> On 21 May 2003 at 11:39, Scot Hale wrote:
> > Thank you Dirk, you seem to be the voice of reason here. I was just
> > pointing out that if we did make a sourceforge project we would have
> > to have a conversation with Canoo about the naming. Also I really
> > don't want to do anything without the consent of Canoo, and the
> > consent of the interested parties.
> > >From your list I think 1) is ideal as well.
> > To make 1) work, we would probably need a cvs branch (or branch the
> > main distro and use the trunk). Also I think we would need some sort
> > of bug tracking tool, so that we can manage the patches in a semi
> > organized manner. In order for this to happen we would need for some
> > people to have write access to cvs (ideally, a small number of
> > responsible people). And we would need to set up a bug tracking tool.
> > Where could we host something like bugzilla?
> > For 2) if we were to create patches, I would guess this is where a
> > sourceforge project would come in. But only for patches is a good
> > idea. We would just have to figure out how to make patches and apply
> > them.
> > ----- Original Message -----=20
> > From: "Dirk Olmes" <email@example.com>
> > To: <firstname.lastname@example.org>
> > Sent: Wednesday, May 21, 2003 2:09 AM
> > Subject: Re: [Webtest] Fix for 2 successive <followframe ..>
> > > Scot Hale wrote:
> > > > from canoo webtest license :
> > > >
> > > > . The names "Canoo" and "Canoo WebTest" must not be used to
> > > > endorse or
> > > > promote products derived from this software without prior written
> > > > permission. For written permission, please contact email@example.com.
> > > > . Products derived from this software may not be called "WebTest",
> > > > nor
> > may
> > > > "Canoo" appear in their name, without prior written permission of
> > > > the
> > Canoo
> > > > Engineering AG.
> > > >
> > > > Which just means we would have to get permission if we wanted to
> > > > call it Canoo, Canoo WebTest, or WebTest.
> > >
> > > Err, what are we talking about? A split off of WebTest? I don't
> > > think this would be a good thing.
> > >
> > > My preferences would be as following:
> > >
> > > 1) improve collaboration with Cannoo i.e. make patches go into the
> > > main distro
> > >
> > > 2) if 1) turns out to be impossible for whatever reasons, keep an
> > > archive of patches to the main distro so everybody can download a WT
> > > distro and the patches and apply everything themselves
> > >
> > > 3) a complete splitt off of the main codebase
> > >
> > > -dirk
> > >
> > > _______________________________________________
> > > WebTest mailing list
> > > WebTest@lists.canoo.com
> > > http://lists.canoo.com/mailman/listinfo/webtest
> > >
> > _______________________________________________
> > WebTest mailing list
> > WebTest@lists.canoo.com
> > http://lists.canoo.com/mailman/listinfo/webtest
> WebTest mailing list