<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Ignacio and I have started working on a new irc bot. You can check it out here: </span><a href="https://github.com/ignaciouy/sugar-irc/" target="_blank" style="font-family:arial,sans-serif;font-size:13px">https://github.com/ignaciouy/sugar-irc/</a><div style="font-family:arial,sans-serif;font-size:13px">

We also have a top ten tickets list (which is kind of random) here: <a href="https://github.com/ignaciouy/sugar-irc/wiki/Top-Ten-Tickets-This-Week" target="_blank">https://github.com/ignaciouy/sugar-irc/wiki/Top-Ten-Tickets-This-Week</a></div>

<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Hopefully this helps someone</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">

On Thu, Jan 23, 2014 at 11:02 AM, Ignacio Rodríguez <span dir="ltr"><<a href="mailto:nachoel01@gmail.com" target="_blank">nachoel01@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Just now for starters users I use:<br>
"!join username"<br>
and gcibot says :P<br>
 < gcibot >   username, WE NEED YOU! <a href="http://join.sugarlabs.org/" target="_blank">http://join.sugarlabs.org/</a><br>
<br>
"!install username"<br>
 < gcibot >   username, please read:<br>
<a href="http://developer.sugarlabs.org/dev-environment.md.html" target="_blank">http://developer.sugarlabs.org/dev-environment.md.html</a><br>
<br>
All users didn't read the topic of #sugar I think<br>
<br>
2014/1/22, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>>:<br>
<div class="HOEnZb"><div class="h5">> Conversation about the tasks to work on issue on #sugar<br>
><br>
> 23:27 < SAMdroid_> dnarvaez: What sort of projects are good to recomend?<br>
> Should<br>
>                    we make a big list of activity ideas?<br>
> 23:30 < dnarvaez> SAMdroid_: I think the big problem with lists is that<br>
> they<br>
>                   need to be maintained, otherwise they are soon more<br>
> confusing<br>
>                   then useful because they contain stuff that has already<br>
> been<br>
>                   done, that it's not very interesting anymore etc<br>
> 23:30 < SAMdroid_> Yes, I see<br>
> 23:30 < dnarvaez> SAMdroid_: so yeah, I think we need that kind of list,<br>
> but we<br>
>                   should try to figure out the best way to write it so that<br>
>                   it's maintained easily<br>
> 23:31 < SAMdroid_> Don't we the sugar-love tag on the bug tracker?<br>
> 23:32 < dnarvaez> SAMdroid_:<br>
> <a href="http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&keywords=~sugar-love&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority" target="_blank">http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&keywords=~sugar-love&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority</a><br>


> 23:32 < dnarvaez> SAMdroid_: very little stuff on it and likely not<br>
> maintained<br>
> 23:32 < SAMdroid_> Your right :(<br>
> 23:33 < dnarvaez> In a way, I'm not sure we need a sugar-love keyword<br>
> 23:33 < dnarvaez> every valid bug is a good way to get started<br>
> 23:33 < SAMdroid_> I agree<br>
> 23:33 < dnarvaez> most of the time you can't say what is hard or easy for<br>
>                   someone<br>
> 23:36 < dnarvaez> laying with was to keep someting like a top 10 bugs list<br>
> 23:36 < dnarvaez> that wouldn't be a lot of work to maintain<br>
> 23:36 < SAMdroid_> dnarvaez: I think we need to look down to the core of<br>
> this<br>
>                    issue; what do we need to do? How do we better find our<br>
>                    vision?<br>
> 23:38 < dnarvaez> SAMdroid_: that's really difficult to answer though :)<br>
> And in<br>
>                   a way what we need to do is determined by what<br>
> contributors<br>
>                   like to do...<br>
> 23:38 < dnarvaez> s/what we need/what we can<br>
> 23:40 < SAMdroid_> dnarvaez: So then we sort of get back to posting bug<br>
> lists<br>
>                    and vauge things. A bug list does sound like a good idea<br>
> :)<br>
> 23:40 < dnarvaez> SAMdroid_: we sort of have a bug list for core, see<br>
> "Sugar<br>
>                   tickets" on <a href="http://bugs.sugarlabs.org" target="_blank">bugs.sugarlabs.org</a>. But nothing for<br>
> activities.<br>
> 23:41 < dnarvaez> I mean there are activities bugs there but I'm not sure<br>
> in<br>
>                   what state of triaging<br>
> 23:42 < SAMdroid_> Why don't we do a top ten tickets this week thing<br>
> (ttttw: it<br>
>                    has a cool abbrivation)<br>
> 23:42 < dnarvaez> a list of activities list is good btw I think, maybe we<br>
>                   should put that in a trac compoennt or something<br>
> 23:43 < SAMdroid_> Ok sounds great!<br>
> 23:43 < dnarvaez> SAMdroid_: yeah the top 10 thing is something we should<br>
> try I<br>
>                   think<br>
> 23:43 < dnarvaez> SAMdroid_: I need to leave but I'll post this to the list<br>
> 23:43 < dnarvaez> SAMdroid_: thanks for the ideas :)<br>
><br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Saludos.<br>
Ignacio Rodríguez<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</font></span></blockquote></div><br></div>