Nope. Makes sense to me. —Mark
On Mon, Apr 22, 2019 at 11:08 PM Mark Anderson <[email protected]> wrote: > Nope. Makes sense to me. > > —Mark > _______________________ > Mark E. Anderson <[email protected]> > > > On Mon, Apr 22, 2019 at 1:43 PM Mojca Miklavec <[email protected]> wrote: > >> Hi, >> >> When we switched to GitHub Ryan made a test conversion of Trac tickets >> to GitHub issues, but there were several problems with that approach, >> the biggest one being inability to easily filter by ports, and >> generally the GitHub's issues were less powerful than what Trac is >> offering, so it made sense to stick with Trac. >> >> The situation is slightly different with smaller standalone projects >> where issues might in fact be a better fit and easier to use. >> >> For smaller standalone projects like those suggested for GSOC >> (excluding base-related ones) I would like to experiment with the >> built-in issue tracker, including milestones etc. Like this one, for >> example: >> https://github.com/macports/macports-webapp/issues >> These would mainly be projects on which we would likely have a single >> developer at the moment, but more contributors in the future. Are >> there any objections? >> >> To make it clear: I don't want to suggest moving any of the >> macports-base or macports-ports tickets to GitHub, at least not at >> this point. I'm just curious whether anyone would be strongly opposed >> to keeping some issues at a different location from trac for the sake >> of easier GSOC administration. >> >> Thank you very much, >> Mojca >> >
