Re: [technology-pmc] Minutes for July 23, 2014 Meeting

[Wayne Beaton <wayne@xxxxxxxxxxx>]

The longer answer is that we know that projects want to use GitHub issues and we've laid some of the groundwork for a solution. Unfortunately, we don't yet have a time frame for implementation.

There are two things at work here. First, we have a vendor neutrality requirement that we need to meet. Second, we have a "freedom of action" requirement from the board of directors: if we're leveraging external services, we need to be able to pick up and keep going when/if that service becomes unavailable.

Having an API is great, but we still need to be able to do something with the data should that service go offline (and there are lots of reasons why that service might go offline). There are some software solutions for doing this, but these themselves then become external software/services that we need to have "freedom of action" from.

I know that this all feels a little academic with regard to something like GitHub. What are the chances that GitHub will shut down this service, or go out of business, or change their business model, or whatever? With increasing time scales... the chances are pretty good, actually.

FWIW, we have a further requirement on our infrastructure that we only use open source software (this really extends from the "freedom of action" requirement). This, combined with the vendor neutrality concern, is why we can't use JIRA.

HTH,

Wayne

On 07/28/2014 09:27 AM, david.w.smiley@xxxxxxxxx wrote:

I see a GitHub API for issues:

https://developer.github.com/v3/issues/

To each their own, but BugZilla is the worst bug-tracker I’ve ever used.

~ David Smiley

Freelance Apache Lucene/Solr Search Consultant/Developer

http://www.linkedin.com/in/davidwsmiley

On Mon, Jul 28, 2014 at 8:14 AM, richard burcher <richard.burcher@xxxxxxxxxxx> wrote:

Hi David,

That's correct, projects can not use GitHub issues (we have no mechanism in place to sync with Bugzilla). You will need to migrate current issues etc to Bugzilla. This ensures everyone in the community can view and access them; both today and far into the future (our perspective being what happens if we no longer used GitHub due to changes in its business model for instance).

HTH,

Richard

On 2014-07-27, 5:15 PM, david.w.smiley@xxxxxxxxx wrote:

On Thu, Jul 24, 2014 at 2:22 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:

This is why, for example, we can have code in GitHub repositories (which the Webmaster mirrors on Eclipse Foundation servers), but cannot use GitHub Issues (because we currently do not have a solution for mirroring the issues).

Woah.  Does that also mean that projects on GitHub (like Spatial4j) should not use GitHub issues to track features, bugs, etc?

~ David Smiley

Freelance Apache Lucene/Solr Search Consultant/Developer

http://www.linkedin.com/in/davidwsmiley

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc

-- 
Cheers,

Richard


Richard Burcher
Community Manager at the Eclipse Foundation

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc

--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
Learn about Eclipse Projects