Re: Requirements for bugsquad team for alternatives to Bugzilla/cgit
Carlos Soriano <[email protected]> Mon, 8 May 2017 19:58:37 +0200
| Newsgroups | gmane.comp.gnome.bugsquad |
|---|---|
| Message-ID | <CAPoe4L5Eo0Tf1ww05yOQNcwayANpBJ_HS1Fi66ZY4hug8+Qrhg@mail.gmail.com> |
--===============1648048049816775506== Content-Type: multipart/alternative; boundary=f403045dc12a4b48e4054f06fe73 --f403045dc12a4b48e4054f06fe73 Content-Type: text/plain; charset=UTF-8 Ping here, now it's your time to make your needs heard. Cheers, Carlos Soriano On Wed, May 3, 2017 at 7:12 PM, Carlos Soriano <[email protected]> wrote: > Hello Bugsquad team, > > I'm trying to writte down the requirements of the bugsquad team regarding > git repository and issue tracker, in the context on evaluating possible > alternatives to cgit and Bugzilla. Could someone help on this and write > down what are the requirements and workflow the bugsquad need to have? > You can write it here https://wiki.gnome.org/Sysadmin/ > CodeHostingComparisonMatrix/Bugsquad > > We are focusing on your current needs and not regress on those, but you > can add a section that is "nice to have" and we will take that into account > too. > > You can write it in prosa, an example would be "In an upcoming release, we > need to make sure blockers are seen by maintainers. For that, we mark a > milestone for those bug reports, and we search across projects for those > blockers. Then we update the bug report to "ping" the maintainer" > > It will be very appreciated if we can have something for this week if > possible. > > Thanks! > Carlos Soriano > --f403045dc12a4b48e4054f06fe73 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Ping here, now it's your time to make your needs heard= .<div><br></div><div>Cheers,</div><div>Carlos Soriano</div></div><div class= =3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 3, 2017 at 7:12= PM, Carlos Soriano <span dir=3D"ltr"><<a href=3D"mailto:carlos.soriano8= [email protected]" target=3D"_blank">[email protected]</a>></span> wr= ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border= -left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hello Bugsquad team= ,<br><br>I'm trying to writte down the requirements of the bugsquad tea= m regarding git repository and issue tracker, in the context on evaluating = possible alternatives to cgit and Bugzilla. Could someone help on this and = write down what are the requirements and workflow the bugsquad need to have= ?<div>You can write it here=C2=A0<a href=3D"https://wiki.gnome.org/Sysadmin= /CodeHostingComparisonMatrix/Bugsquad" target=3D"_blank">https://wiki.gnome= .org/<wbr>Sysadmin/<wbr>CodeHostingComparisonMatrix/<wbr>Bugsquad</a><br><d= iv><br></div><div>We are focusing on your current needs and not regress on = those, but you can add a section that is "nice to have" and we wi= ll take that into account too.</div><div><br></div><div>You can write it in= prosa, an example would be "In an upcoming release, we need to make s= ure blockers are seen by maintainers. For that, we mark a milestone for tho= se bug reports, and we search across projects for those blockers. Then we u= pdate the bug report to "ping" the maintainer"</div><div><br= ></div><div>It will be very appreciated if we can have something for this w= eek if possible.</div><div><br></div><div>Thanks!</div><span class=3D"HOEnZ= b"><font color=3D"#888888"><div>Carlos Soriano</div></font></span></div></d= iv> </blockquote></div><br></div> --f403045dc12a4b48e4054f06fe73-- --===============1648048049816775506== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ gnome-bugsquad mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-bugsquad --===============1648048049816775506==--