I'll post here what I just added to the Bugzilla record. *Let's please continue this discussion on the bug.*
This discussion was the catalyst for a much larger discussion within the Eclipse Foundation. What, exactly, does it mean to be an Eclipse Project? I owe a much longer answer, which I'll try to address in a blog post soon, but we feel that it boils down to this: - Conforms to the EDP and Eclipse IP Policy; - Calls itself an "Eclipse Project" and conforms to branding guidelines; - Operates independently from any specific vendor; and - Uses infrastructure provided by the Eclipse Foundation for core content. We define "core content" as: - Project metadata; - Source code, including documentation; - Issues/bugs/tickets; and - Project -dev list. "Core content" is that content which fundamentally defines the project and so must persist indefinitely. For some measure of completeness, we consider the following to be non-core: - User forum discussions, presentations; - Builds and downloads; and - Examples, blogs, social media handles,... For non-core content, we require that the project team take steps to ensure that the "keys" are shared so that no single individual can domainate or otherwise bottleneck that shared resource. At present, the infrastructure that we provide for issue tracking is either the Eclipse Bugzilla instance or GitHub Issues associated with official project repositories. Tuleap is not (currently) supported infrastructure for issue tracking. The projects that are hosting issues on the test instance (that's been implemented by some of our committers) today may continue to do so. The warning that we gave the initial few projects that decided to test that instance, however, still stands. At some point in the future, we may compel them to move their content back into support infrastructure. I'm very concerned that there's been some feature creep. If any of these projects are leveraging other services that I've defined as "core", they should contact me immediately to sort out a remediation strategy. No other projects may move their core services off of supported infrastructure. HTH, Wayne 2017-10-27 13:13 GMT-04:00 Henrik Rentz-Reichert <h...@protos.de>: > Hi, > > > > for a longer time I didn’t hear anything about Tuleap in the context of > the Eclipse Foundation. > > Also the discussion in https://bugs.eclipse.org/bugs/ > show_bug.cgi?id=497333 got stuck. > > > > Is anybody willing to share his/her experiences? > > > > In particular I would like to know about > > > > · Migration from Bugzilla to Tuleap > > · Gerrit interaction with Tuleap > > · Overall level of satisfaction with Tuleap itself > > > > Thanks, > > Henrik > ------------------------------ > > Diese Nachricht wurde mit einer kostenlosen Version von Proxy-Manager > <http://www.dimastr.com/proxyman> gesendet. > Wollen Sie von Ihrem Exchange-Konto mit einer Ihrer Proxy SMTP-Adressen > senden? > Testen Sie Proxy-Manager kostenlos! > > Diese Fußzeile wird nicht in der registrierten Version von Proxy-Manager > <http://www.dimastr.com/proxyman> angezeigt. > Klicken Sie hier <http://www.dimastr.com/proxyman/register.htm>, um > Proxy-Manager zu registrieren. > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > -- Wayne Beaton Director of Open Source Projects The Eclipse Foundation
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
