ingres janitors

On Web wrote:
[snip]
> I spent over two years working full time on ingres ports and patches (err..
> 6.x..) and I can't see myself going back there - I have too many other
> things to do and I know just how involved that code is. It's been ten years
> (or more) since I invoked a C compiler!

Even though you're rusty, the pool of people with that level of
experience, historical or contemporary, with INGRES source is very
limited. I hope that you continue to monitor the list and if you have
any suggestions at all please post; you never know what "nuggets" are
still there until you look.

> You're completely right - I hadn't realised which way this initiative had
> been born. You guys may surprise me yet!

That's the idea

> I really do admire your spirit.

Thanks, and keep beating the drum!

Mark R. Winston
www.datavailable.com
 >> Stay informed about: ingres janitors 

At 6:34 PM +0000 11/16/07, On Web wrote:
>
>Here's a fond reminder from those days: select * from xyzzy()
>


If you're running a recent-ish Ingres, you'll have to do:

select xyzzy(1)

Nothing happens, of course.

Karl

(I'm old enough to remember the entire software department
at On-Line Systems (the timesharing company, not the games
company) ceasing all work for two weeks until advent was
solved. Operations tried to delete the thing but it kept
reappearing, and they finally gave up and just let it
play out... I bet I could still find my way through
part of the maze, at least.)
 >> Stay informed about: ingres janitors 

"Mark R. Winston" wrote in message

> On Web wrote:
> [snip]
>> I spent over two years working full time on ingres ports and patches
>> (err..
>> 6.x..) and I can't see myself going back there - I have too many other
>> things to do and I know just how involved that code is. It's been ten
>> years
>> (or more) since I invoked a C compiler!
>
> Even though you're rusty, the pool of people with that level of
> experience, historical or contemporary, with INGRES source is very
> limited. I hope that you continue to monitor the list and if you have
> any suggestions at all please post; you never know what "nuggets" are
> still there until you look.
>
>> You're completely right - I hadn't realised which way this initiative had
>> been born. You guys may surprise me yet!
>
> That's the idea

Here's a fond reminder from those days: select * from xyzzy()

(No, nothing to do with me, but brings a smile if you're old enough to enjoy
the reference)

Paul

>
>> I really do admire your spirit.
>
> Thanks, and keep beating the drum!
>
> Mark R. Winston
> www.datavailable.com
 >> Stay informed about: ingres janitors 

"Karl & Betty Schendel" wrote in message

> At 6:34 PM +0000 11/16/07, On Web wrote:
>>
>>Here's a fond reminder from those days: select * from xyzzy()
>>
>
>
> If you're running a recent-ish Ingres, you'll have to do:
>
> select xyzzy(1)

Oops, forgot the parameter!

> Nothing happens, of course.

I suspect that ingres.com has a maze of twisty passages..

LOL

> Karl
>
> (I'm old enough to remember the entire software department
> at On-Line Systems (the timesharing company, not the games
> company) ceasing all work for two weeks until advent was
> solved. Operations tried to delete the thing but it kept
> reappearing, and they finally gave up and just let it
> play out... I bet I could still find my way through
> part of the maze, at least.)
>
 >> Stay informed about: ingres janitors 

Another task that someone in the community might be interested in would be to
create a Debian package:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401157
which could also find its way into Ubuntu very easily.

Making it compile successfully under recent versions of gcc, if not already
done, would also help.

A Debian and Ubuntu package would help to increase the visibility of the
project. Licencing of the documentation is another issue that would need to be
clarified, I suspect, if Debian free software guidelines were to be met to
allow inclusion of the manuals with the packages.

Just a suggestion from an interested onlooker. The last time I tried, Ingres
failed to compile under gcc 4.1. Debian Unstable is up to gcc 4.2 now.
 >> Stay informed about: ingres janitors 

Jason wrote:
> Another task that someone in the community might be interested in would be to
> create a Debian package:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401157
> which could also find its way into Ubuntu very easily.
>
> Making it compile successfully under recent versions of gcc, if not already
> done, would also help.
>

I'm pretty sure a .deb install package is being worked on, and that the
latest version of ingres will build with the latest gcc.

--
Paul
 >> Stay informed about: ingres janitors 

>I'm pretty sure a .deb install package is being worked on, and that the
>latest version of ingres will build with the latest gcc.

Those are both excellent moves in the right direction. Once the dpkg package
exists, getting it into the Debian and Ubuntu repositories so that system
administrators can find and install it easily, would be the next step.
 >> Stay informed about: ingres janitors 

If "Ingres Janitors" is an idea to gather open-source developers around
Ingres products, then I believe Ingres needs to change the process of
development and adopt more "open" ways of development. There is also not
clear (read documented) way of what a person should do in order to
submit a patch.

Correct me if I am wrong, current way is still via e-mail / forum . In
other words a direct contact to some of the developers. Second way is
via development sprints... - Not good at all, IMHO.

If you care about my opinion - put Ingres on github, assign one or few
persons to watch for pull requests, and review them, and naturally,
apply them if they are good. THAT is a modern approach to open-source
development!


--
dejan
------------------------------------------------------------------------
dejan's Profile: http://community.ingres.com/forum/member.php?userid=13077
View this thread: http://community.ingres.com/forum/showthread.php?t=8988
 >> Stay informed about: ingres janitors 

Thanks for the suggestion, Dejan. I'll discuss it with the team and get
their thoughts on it.
Cheers
Emma

-----Original Message-----
From: info-ingres-bounces.TakeThisOut@kettleriverconsulting.com
[mailto:info-ingres-bounces@kettleriverconsulting.com] On Behalf Of
Ingres Forums
Sent: Monday, September 19, 2011 6:13 AM
To: info-ingres.TakeThisOut@kettleriverconsulting.com
Subject: Re: [Info-Ingres] ingres janitors


If "Ingres Janitors" is an idea to gather open-source developers around
Ingres products, then I believe Ingres needs to change the process of
development and adopt more "open" ways of development. There is also not
clear (read documented) way of what a person should do in order to
submit a patch.

Correct me if I am wrong, current way is still via e-mail / forum . In
other words a direct contact to some of the developers. Second way is
via development sprints... - Not good at all, IMHO.

If you care about my opinion - put Ingres on github, assign one or few
persons to watch for pull requests, and review them, and naturally,
apply them if they are good. THAT is a modern approach to open-source
development!


--
dejan
------------------------------------------------------------------------
dejan's Profile:
http://community.ingres.com/forum/member.php?userid=13077
View this thread:
http://community.ingres.com/forum/showthread.php?t=8988

_______________________________________________
Info-Ingres mailing list
Info-Ingres.TakeThisOut@kettleriverconsulting.com
http://ext-cando.kettleriverconsulting.com/mailman/listinfo/info-ingres
 >> Stay informed about: ingres janitors