If other see that as useful, I'll volunteer to have a try at it. I've started poking around the CI & Fogbugz interface code. Any further thoughts on design?
Maybe it could run as a Pharo CI job, or alternatively, it would provide me a nice goal-directed opportunity to get it run for minutes a day on a cloud service. cheers -ben On Thu, Jan 22, 2015 at 5:33 PM, Guillermo Polito <[email protected] > wrote: > Marcus, can the issue tracker send an email to the mailing list every > morning with some report? > > - # of issues opened > - # of issues in state X > - # of issues in state Y > - # of issues older than a month... > > We can try to do something like that this friday afternoon together if you > want. > > Maybe if we automatize a mail like that every morning 1) you don't have to > do it manually so it's less pain for you and 2) with numbers people will > have another feeling. > > El Thu Jan 22 2015 at 10:25:38 AM, Marcus Denker <[email protected]> > escribió: > > Hello, >> >> Now that so many people talk so much: >> >> We need more people to *regularly* look at the issue tracker: >> >> https://pharo.fogbugz.com/ >> >> -> check if reported issues are reproducable >> -> check proposed solutions >> -> comment on new features (“I don’t like that because….”) >> -> fix issues that are not yet fixed >> -> summarise issues with long discussions and distill “The next action >> that needs to be done is:” >> >> …. >> >> Marcus >> >
