<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On gio, 2014-07-10 at 20:20 -0500, Kunda Loves Scribus wrote: <BR>
<BLOCKQUOTE TYPE=CITE>
Thank you so far for you attention and participation. If you've not read the first 2 parts, no worries, you can read this independently. <BR>
<BR>
<BR>
<BR>
Contnuing Pt.1 (Mediawiki) and Pt.2 (MantisBT) of this series of email the next iteration of this idea would be to restore utility to what can be done via Freenode #scribus <BR>
<BR>
<BR>
So, I understand that historically there used to be a #Scribus channel bot that did cool bot things on the channel :) Not sure the history of why it doesn't anymore. Nevertheless, here is what my vision is and perhaps you can see the utility of it. What I'd like to propose is bringing some functionality back or introducing some functionality that may not have been there:<BR>
<BR>
<BR>
1) Return to logging the channel. Many impromptu ad-hoc meetings tend to emerge on the channel. It would be nice to be able to record them and reference them for later use. For many reasons including making documentation and tutorials, creating wiki pages from discussions oriented around design or architecture of a problem/solution brainstorm, making sure we identify any witchlike behavior and burn the witches in question (not before we prove they are witches by weighing them against a duck to see if they are made of wood and can float)<BR>
</BLOCKQUOTE>
<BR>
+1 on another open source project i am involved with, we have a similar problem in that most of the discussion/problem solving/etc. occur in IRC, which unlike a mailing list is not logged and available for perusal/reference later. thus, IMHO having IRC logged and searchable would be a great, though wordy/chaotic, resource.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
2) For the bot to be triggered to create the legit URL from just the issue numbers (saves time). <BR>
<BR>
<BR>
3) To search Mantis from IRC (if possible, saves time)<BR>
<BR>
<BR>
4) Remote control Mantis from IRC (if possible, because...Science!)<BR>
<BR>
<BR>
5) To log which issues are discussed the most (bot on #Drupal does this)<BR>
<BR>
<BR>
6) To send notes back and forth between folks (historical use of a bot)<BR>
<BR>
<BR>
7) Update the channel when SVN is updated with commit message (useful)<BR>
<BR>
<BR>
8) Remotely search the Wiki and return results<BR>
<BR>
<BR>
9) Sync the SVN repo with the git (if not sophistications are present)<BR>
<BR>
Optional) Update the channel when there is activity on Mantis <BR>
<BR>
<BR>
Optional) Update the channel when there is activity on the forums<BR>
<BR>
<BR>
Optional) Update the channel a summary of topics discussed on the MLs<BR>
<BR>
<BR>
Optional) Auto change topic to reflect the most updated revision # of the dev version<BR>
<BR>
<BR>
<BR>
etc....<BR>
<BR>
<BR>
Looking forward to participating in some discussions on theses topics. <BR>
<BR>
<BR>
Cheers,<BR>
/Kunda
<PRE>
_______________________________________________
scribus-dev mailing list
<A HREF="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</A>
<A HREF="http://lists.scribus.net/mailman/listinfo/scribus-dev">http://lists.scribus.net/mailman/listinfo/scribus-dev</A>
</PRE>
</BLOCKQUOTE>
<BR>
<BR>
</BODY>
</HTML>