> Interesting.
>
> I like it. Actually, just the other day I was looking at OpenDarwin web site.
>
> http://www.opendarwin.org/
>
> Reasons why SAP is behaving like this are very simmilar if not the same as
> Apple's reasons.
......Darwin bit snipped......
> So how about "OpenSAPDB" project?
>
> We can have CVS that would contain only files we modify, as Daniel described?
> Or do interested people prefer patches? (You can allways make a patch later, if
> you have all files anyway...?)
>
> Or should we mirror SAP CVS, as sap_ag branch in CVS, and do development in
> branches started from it?
>
I'd be curious about which one is easiest from the build standpoint...
> Is OSDL Linux-only shop? What exactly can you provide, appart from a box? (BTW,
> SF has "compile farm", and provides more then just Linux/Intel)
At this time, OSDL is a Linux-only shop. Also Intel only. Only hard
requirement is Open Source Licensing.
As I said previous, we also make use of Sourceforge
for CVS and project homepages - we are complimentary, not competing.
Our main role is to provide access to enterprise-class hardware for
development testing,
much different than a compile farm - we are ( i think ) unique in that:
- systems are large - 4, 8, 16 way, big memory, access to disk arrays, huge
storage, NUMA.
- project has full use of system(s) for duration of project. Access is via
ssh.
( systems are not shared with other tasks/projects )
- We have a team of database performance people with a lot of database
experience (both in testing and deployment)
available for advice, possibly can help with some of the coding effort.
- We have several workloads available for stressing the database, and we are
working on more.
- We have some nice automated tools that allow us to run those workloads over
and over again on a test system.
- We have access to some really smart people who know the Linux kernel, and
know what an enterprise-class system
requires.
Again, we're not a Sourceforge replacement - we'd like to add to the effort,
where we can help.
I think our main value would be doing testing of patches/builds on a big
system, plus providing a system
that can be accessed in a secure way by all the developers who want to
participate. This allows everybody
to get a first-hand view when testing shows up a problem.
cliffw
>
> --
> Yours, Andrej Falout, http://www.falout.com/disclaimer.html
> Visit the OpenSource alternative, Aubit 4gl: http://aubit4gl.sourceforge.net
> PLEASE NOTE: All HTML email sent to me WILL BE DELETED AUTOMATICALLY WITHOUT
> READING.
>
> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
> >
> > We would be interested in helping. OSDL is chartered
> > to provide Open Source developers with resources to build
> > enhancements into Linux and it's Open Software Stack.
> >
> > We can provide a Linux/Intel development platform, and large
> > (1 -> 16 CPU ) machines for development. In addition,
> > we have several database performance workloads which run with SAP DB which can
> > be used to test patches and measure improvements.
> >
> > Best of all, it's free :)
> >
> > Our resources are tied to what we call Projects. Creating a Project is a
> > simple one-page Web form. ( http://www.osdl.org/projects/project.html )
> > We've already talked to our management, and Project approval won't be a
> > problem.
> > I'll volunteer to help with the Web-paper work :)
> > To move forward, we'd need this:
> > - Someone to step forward and be the Project Co-ordinator. ( manage the list of
> > project members, maintain communication. We'd prefer that the Co-ordinator be
> > a non-OSDl person )
> > - project people need to be OSDL Associates. Again, it's free, a simple one
> > page web-form.
> >
> > We have a current Sourceforge project for the performance test
> > (http://sourceforge.net/projects/osdldbt)
> > which also has a mailing list.
> > We don't directly provide CVS ( we normally use Sourceforge ) but we'd
> > certainly help admin
> > a repository. We could use our test kit on a development machine to provide a
> > 'nightly build'
> > kinda environment if that sounds good.
> >
> > What do you all think? Any takers?
> > cliffw
> >
> >
> > > On Tue, 2002-09-24 at 12:16, Andrej Falout wrote:
> > > > Maybe the temporary answer is to collect all patches provided by community.
> > > > Anyone?
> > >
> > > Andrej,
> > >
> > > This could be a good thing. It would allow the SAP folks to utilise
> > > those patches which are deemed appropriate for their environment, while
> > > still maintaining access to fixes/features/bugs for the rest of us.
> > >
> > > In that context, maybe it works to think of it like the Linux kernel
> > > model, with contributors providing many patches, but only the (
> > > benevilent-dictator | salary-paying-junta ) gets the say on what goes
> > > into the offically blessed code base... but there's nothing to stop
> > > anyone else patching their code as they see fit, if the resources are
> > > available.
> > >
> > > Most people will still use the offical code, but some will try the other
> > > stuff out. If feedback can be captured through lists or forums, we can
> > > all know what works for better or worse, and everyone can benefit. Also,
> > > if the "alternative" patches work better, are more portable, and end up
> > > becoming a fork, so be it - it'll only happen if there's a need.
> > >
> > > And yeah, I agree we could look at the Firebird model... (having said
> > > that, I know of local businesses using it to keep costs down for
> > > clients)
> > >
> > > Richard.
> > > _______________________________________________
> > > sapdb.general mailing list
> > > [EMAIL PROTECTED]
> > > http://listserv.sap.com/mailman/listinfo/sapdb.general
> > >
> >
>
>
>
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general
>
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
