Begin forwarded message:From: Eclipse Webmaster <webm...@eclipse-foundation.org>Subject: Re: URGENT--- Fwd: [eclipse/microprofile-marketing] e-Book: Building an API Backend by Hayri Cicek (#1) --- USE AS EXAMPLE!Date: March 12, 2019 at 11:28:59 AM PDTTo: Amelia Eiras <aei...@tomitribe.com>Cc: Hayri <ha...@kodnito.com>, EMO EMO <e...@eclipse-foundation.org>Hi Amelia,If you'd like to point the Microprofile community at bug 483563 to help define what's required, that's just fine.-Matt.On Tue, Mar 12, 2019 at 2:09 PM Amelia Eiras <aei...@tomitribe.com> wrote:Matt,Thank you for providing the link of the bug-issue, helpful & old.Are you ok if I forward this message to the MP forum?Ideally, those interested could start providing feedback via issue directly. If yes, I won’t add your email to that thread. It is for MP community consumption and reference of our exchange. :)If your answer is No, not an issue— instead, I will start a new thread and share the bug-issue link for follow up.Closing thread now that I understand your feedback, thank you,On Mar 12, 2019, at 7:42 AM, Eclipse Webmaster <webm...@eclipse-foundation.org> wrote:Hi Amelia,I wasn't suggesting that this was something for the Microprofile team to fix directly.My understanding of the issue presented is that you'd like Hayri(who is not a committer on Microprofile) to be able to create and manage issues and labels on the Microprofile Github repo. The current permissions provided by Github don't really support this kind of granularity(which is why I linked to the Github permissions doc), so we'd essentially have to give Hayri the same access as a committer, which is a problem.Currently we don't have a process to recognize community members that fall somewhere between committers and consumers of a project, but it's being discussed here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=483563-Matt.On Mon, Mar 11, 2019 at 6:06 PM Amelia Eiras <aei...@tomitribe.com> wrote:Matt,If I understand you correctly, you are telling me that it is us- MicroProfilers who need to adjust the Repo for it to enable effortless collaboration and not the EF team?If YES, fantastic and easier to scale. Please confirm either way.Thank YOU from always being fantastic with prompt responses.PS: now at home— sick with a cold bug- hello cold ATL Devnexus :)On Mar 7, 2019, at 12:52 PM, Eclipse Webmaster <webm...@eclipse-foundation.org> wrote:Hi Amelia,I'm pretty sure that the limitations in question are a result of Githubs permissions model(https://help.github.com/en/articles/repository-permission-levels-for-an-organization).Or have I misunderstood the question?-Matt.On Wed, Mar 6, 2019 at 5:19 PM Amelia Eiras <aei...@tomitribe.com> wrote:Hey Matt,Amelia, this week in from Atlanta @DevNexus! :)I have created a ticket in the general MP repo that hopefully will enable you and team to follow up and tell us how to fix the Repo so that the contributors have access to:
- create issue [done]
- add labels (not possible)
- add project (not possible)
- assign issues (not possible)
A few weeks ago, I added you to an issue comment about this, yet I dropped the ball about sending a formal ticket for you to own.Thank YOU in advance,PS: latest Contributor struggling is Hayri, cc’d on this msg.Many others are being stopped from effortless contributing via the REPO.Begin forwarded message:From: Hayri Cicek <notifi...@github.com>Subject: Re: [eclipse/microprofile-marketing] e-Book: Building an API Backend by Hayri Cicek (#1)Date: February 21, 2019 at 4:21:02 PM ESTTo: eclipse/microprofile-marketing <microprofil...@noreply.github.com>Cc: Amelia Eiras <aei...@tomitribe.com>, Author <aut...@noreply.github.com>Reply-To: eclipse/microprofile-marketing <reply+00a3bed844fb7a01716400b60d9021acd43e8d7...@reply.github.com>I don't think I have permission to assign tickets
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.---Webmaster---Webmaster---Webmaster