Any objections to using GitHub issue tracker for GSOC projects?

[Mark Anderson]

Nope. Makes sense to me.

—Mark

On Mon, Apr 22, 2019 at 11:08 PM Mark Anderson <emer at emer.net> wrote:

> Nope. Makes sense to me.
>
> —Mark
> _______________________
> Mark E. Anderson <emer at emer.net>
>
>
> On Mon, Apr 22, 2019 at 1:43 PM Mojca Miklavec <mojca at macports.org> 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
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20190422/845791ae/attachment-0001.html>