Hello all,<br><br>As a new user to Drools, I have been frustrated often and unable to find much information. Below is an IM session where a couple of us discuss what is missing and how we can fix it? <br>A lot of knowledge imparted in the IRC channels does not get recorded. I believe it is the same with the mailing lists. They contain a lot of code samples and fixes to them.<br>
We also could utilize <a href="http://drools.pastebin.com/">http://drools.pastebin.com/</a> for our code samples that do not need persistence.<br><br>I would like to hear from the members ( and most importantly) from the core group on what they think of this. Since they are meeting together anyways, I hope that this is one of the discussions they have over beer.<br>
<br><br><br>==============================================================<br>mallen: Calling all BRMS / Guvnor experts! Does anyone know how to upload multiple (50+) rules packages in one go? either through the web interface or perhaps even programatically so we could knock a maven task together for it?<br>
[06:05am] krisv left the chat room. (Ping timeout)<br>[06:06am] wheter_: mallen: I will be interested in such a solution as well? jarek, can we start open JIRAs for such knowledge sharing too. If you ( or others) update the JIRA, this will be more visible. there is a lot of stuff that is posted on this IRC channel that just goes away. How about a JIRA category called &quot;FAQ&quot; or &quot;Knowledge sharing&quot;? Will it pollute the JIRA process?<br>
[06:08am] wheter_: The nice thing would be that as bugs are fixed and workarounds are found, they could be moved to the &quot;FAQ&quot; category as well so that others who get the same problems can search and find it there<br>
[06:08am] bjornelo: sounds like something that belongs on a wiki or something else that isn&#39;t an issue tracker<br>[06:08am] wheter_: right, but see the state of our wiki<br>[06:08am] bjornelo: it&#39;s empty, afaik<br>
[06:09am] wheter_: bjornelo: people will not go and update the wiki after something is posted/a solution is found<br>[06:09am] wheter_: mostly<br>[06:09am] wheter_: we need to make the process easier and as automated as possible<br>
[06:09am] bjornelo: but people will go and update JIRA?<br>[06:10am] wheter_: In this idea, the conversation itself is tracked and no further updates are needed.<br>[06:11am] wheter_: No, mallen has to create a JIRA and bring that to the attention of the IRC folks bjornelo.  When you have a solution, instead of typing it into the chat channel, you update the JIRA and the conversation should continue there for subjects that are really useful<br>
[06:12am] bjornelo: aha<br>[06:12am] wheter_: bjornelo, if i was not around at this time, I would not have known that there are others like mallen who are interested in this solution<br>[06:12am] wheter_: some conversation does belong here in IRC but for example see how me and Jaroslaw (jarek) communicated in GUVNOR-353<br>
[06:12am] jarek: wheter_: sounds like a &#39;feature request&#39; - which can be also created in jira (besides bugs and tasks); however I wouldn&#39;t use jira as a FAQ/wiki <br>[06:12am] bjornelo: what mallen posted sounds to me like what should be a feature request on JIRA<br>
[06:13am] wheter_: we used both the IRC and JIRA<br>[06:13am] wheter_: I beleive now that GUVNOR-353 is very well documented<br>[06:13am] wheter_: bjornelo: I suggest lets give it a try<br>[06:14am] wheter_: If it looks too bad, you can always blow it away<br>
[06:15am] wheter_: bjornelo: I agree; but someone might post such a solution on IRC, and this knowledge just goes away<br>[06:15am] bjornelo: i&#39;m not trying to be adversarial. i want to see a more structured source of information about drools as much as the next guy. i&#39;m just not sure JIRA is the place to put it<br>
[06:15am] wheter_: I am suggesting a way to steadily improve our knowledge collection<br>[06:16am] wheter_: bjornelo: the wiki is an awesome idea but needs effort. The JIRA i believe is the current best way to go about it. I am going to take this conversation of ours and post in the dev mailing list to see how others think about it<br>
[06:16am] bjornelo: how about if there&#39;s an interesting thread of conversation on IRC, we create a new page on the drools wiki and paste in the conversation there? then give it a headline that describes the subject. link to it from some index of informal rule engine conversations?<br>
[06:16am] wheter_: yes bjornelo; but see, it requires an active action; how many people follow up<br>[06:17am] wheter_: the devs are so busy<br>[06:17am] bjornelo: then, if someone wants to formalize and clean up the information in the conversation, that person can edit the page or create a replacement<br>
[06:17am] wheter_: the rest of the users have their own problems<br>[06:17am] bjornelo: how do you plan to avoid an active action for posting stuff on JIRA? if nothing else, the registering process for jboss community is a PITA<br>
[06:18am] wheter_: i have GUVNOR-353 resolved, but do you think I am going to take the time to load it into the wiki right now? My immediate problem is over and I am looking to solve my next one<br>[06:18am] bjornelo: i suppose we could have an irc bot in here that we could send triggers to that would autogenerate something on a webpage.. how does <a href="http://bash.org">bash.org</a> work, for example?<br>
[06:18am] wheter_: bjornelo, it really is one time, and your argument is defeated, since you update the wiki, you need to register too <br>[06:19am] bjornelo: hmmm<br>[06:19am] wheter_: bjornelo: I am not familiar with IRC bots&#39; capability<br>
[06:20am] wheter_: reg. your comment about structured source of information, I think the JIRA is highly structured<br>[06:20am] wheter_: since it has its own category, it will not come in the way of developers looking for bugs to fix or feature requests<br>
[06:20am] wheter_: and we can cross-link FAQs to other bugs / feature requests<br>[06:21am] bjornelo: difficult to search through, though. i guess if you could have a category of &#39;issues&#39; that are just knowledge exchange, it would be easier to find, but that would also require someone opening a new issue or something<br>
[06:22am] wheter_: that is what I suggested at the very beginning<br>[06:22am] wheter_: a new category like &quot;bug&quot; or &quot;feature request&quot;<br>[06:22am] wheter_: it really is not hard..JIRA also allows you to put in the version of drools it is eligible for<br>
[06:23am] wheter_: i believe the JIRA has more structure for adding information that the wiki does ( in the wiki, you need to enter everything manually)<br>[06:23am] wheter_: you can search better on a JIRA<br>[06:23am] bjornelo: so you mean that the devs should look at the comments on the issue and move it to a &#39;knowledge&#39; category when they solve the issue, if they feel that it&#39;s an interesting topic?<br>
[06:24am] wheter_: now, maybe the search engines might not index it.<br>[06:24am] wheter_: bjornelo: Agreed<br>[06:24am] wheter_: yes<br>[06:24am] wheter_: see my comments above on that<br>[06:24am] wheter_: me, being new to Drools am really stuck and could use the wide body of information<br>
[06:25am] wheter_: this also frees up the devs, since people do not come back asking for the same issue<br>[06:26am] bjornelo: i&#39;d suggest that this new category is another type of &#39;unresolved&#39; or something, signalling that the information contained in the issues is stuff that needs to be structured and moved into some kind of documentation. be it either wiki or the manual or whatever else<br>
[06:26am] bjornelo: &#39;due for documentation&#39; or something<br>[06:26am] wheter_: To integrate the wiki with the JIRA, we could categorize knowledge based on subcomponents, like Guvnor, Core, Solver, Chance etc in wiki, under that the wiki should have different FAQs and then under that, a link to the JIRA in question<br>
[06:27am] wheter_: bjornelo: documentation that is pushed off for later, especially for minor things, in my experience does not happen...it does not have the urgency and in open source projects, people participate for the urgency<br>
[06:28am] bjornelo: true, but in that case it would still be available on jira. the category is just named slightly differently<br>[06:28am] wheter_: I can start off on the initial integration of the wiki and JIRA if conan and the rest of the folks ok it..my small bit for the community<br>
[06:29am] wheter_: right - so information is available from wiki, but in a very structure format...<br>[06:29am] bjornelo: i think of it a bit like forums online. if you want to find some old piece of information, you often have to go digging through 20+ pages of old threads to find what you&#39;re looking for. and often it&#39;s hiding in a thread that isn&#39;t really relevant to what you&#39;re looking for<br>
[06:29am] wheter_: also, people can add to that body of knowledge in the JIRA as well<br>[06:30am] wheter_: right, but the main info can be summarized and put on the wiki, if someone will do it, with a link to the JIRA<br>
[06:30am] wheter_: bjornelo: very few JIRAs run like comment threads<br>[06:30am] bjornelo: i&#39;m picturing a bunch of JIRA issues containing irc convos and other interesting bits of information. the issues are &#39;open&#39; in the sense that they are waiting for someone to pick them up and write an article or whatever about it and stick it on the wiki. if and when they do, they close the corresponding JIRA issue, since the wiki now has structured information to replace it<br>
[06:31am] wheter_: I agree, if the wiki has captured all this information, then this JIRA can be moved to a closed state, but the link still kept<br>[06:31am] bjornelo: and the wiki could be divided into expert, guvnor, flow etc. each headlined with a link to the corresponding list of open JIRA issues<br>
[06:32am] wheter_: now, we are echoing each other <br>[06:32am] bjornelo: so, the user starts by looking at the wiki. if the information is not found there, the user follows the link to the JIRA issue list and can look further<br>
[06:32am] wheter_: agree<br>[06:32am] bjornelo: yep <br>[06:32am] wheter_: Here&#39;s what I am going to do<br>[06:32am] bjornelo: now we just need someone to implement it <br>[06:33am] wheter_: I am going to send a mail to the mailing lists with our chat conversation out there, and see the responses to it, specifically from the core team.<br>
[06:33am] wheter_: bjornelo: are you core?<br>[06:33am] bjornelo: not at all. relatively newbie user <br>[06:33am] wheter_: well, we are doing our bit I guess<br>[06:34am] bjornelo: i&#39;ll be quite interested in seeing responses to this<br>
[06:34am] wheter_: the funny part is we buried mallen&#39;s question and no one will see it now<br>[06:34am] wheter_: sorry mallen <br>[06:34am] bjornelo: lemme just do this, then.<br>[06:34am] bjornelo: 12:04 &lt; mallen&gt; Calling all BRMS / Guvnor experts! Does anyone know how to upload multiple (50+) rules packages in one go? either through the web interface or perhaps even programatically so we could knock a  maven task together for it?<br>
<br><br>==============================================================<br><br clear="all">Regards,<br>Prem<br>