Skip to content

Logging of #ingres on freenode

For some time there have been comments from within the “Ingres Community” that there are too many places gather to discuss topics related to Ingres. Whilst I see their point, I believe that as a community we should be available to communicate if not listen on what ever frequency / channel people are talking on, even if it is twitter (more on that another day).

Last year saw a number of Ingres users and staff start to use #ingres, an IRC channel on freenode. One problem with using IRC is that unless you were there in the room/channel when something was said then you will not know what is going on. An number of threads on comp.databases.ingres have complained that this is a problem and unlike USENET conversations are not in the open. Well as of today this should no longer be the case. There is now a channel-bot, ii_log, recording all conversations that pass through #ingres. The output of which can be found at http://irc.planetingres.org. Formatting and colour is a bit of an issue but at least now the discussions that take place there can be read by all, including you Google.

  • Share/Bookmark

Some random posts

  • Roy
    First off, logging #ingres and making the log available via http://irc.planetingres.org is hugely welcome, and many thanks for that.

    But just to elaborate a little on the grumbling you refer to at comp.databases.ingres: the problem is not the places and channels that people choose to congregate. You are absolutely right that Ingres should be ubiquitous and if twitter would be used then there should be an Ingres presence. The problem is that different people have different ways of working and different methods of delivery suit different people. For instance, I am rarely at my desk or even in the office, so I need a mailing list or a web-forum. Other people need instant help with a small problem. Other people prefer not to have to trawl all the possible forums and want email notification. And so on. The point is that we need more cross-posting otherwise instead of a community we end up with a myriad cliques, each unaware of the others, and conversations fizzle before they ever start.

    ii_log is brilliant. Now we just need to get vBulletin to talk to info-ingres and we're about done. (Actually, if I ruled the world, I would also do a hatchet job on the number of distinct forums at ingres.com--there's waaaaaaaaaaaay too many. You need one for Ingres and one for OpenROAD.)
  • Hi Roy,

    I agree that the many sources / water coolers is a problem for us.
    Getting c.d.i. into the forums is my next "project". In as much that I
    will be poking the people that can do the work rather than being able to
    do it myself. On top of c.d.i we have Ingres related blogs which need to
    be aggregated. Also there is twitter which also gets mentions of Ingres
    (artist and database). To this end I am trying to collate/aggregate
    these sources of "Ingres" information into http://planetingres.org. At
    the moment it just does blogs - typically the ones I know about or come
    across in google alert searches. The general chatter
    (c.d.i/forums/twitter/irc) can be seen at
    http://planetingres.org/chatter/. It's still a work in progress but the
    first step is to aggregate the info. The next step will be to make it
    use-able/navigable. Although I could see the need/use for a "blogs"
    feed in to the forums.

    regards

    grant



    On/El 23/02/09 10:44, Disqus wrote/escribió:
blog comments powered by Disqus