Re: JIRA Workflow Proposals
Hey everyone, Im just trying to keep up but I don’t think everyone needs permissions just contributors im trying to understand the letter voting system so I could better be of service to the community. Sorry if I sound naive. > On Dec 11, 2018, at 12:12 PM, Sylvain Lebresne wrote: > > 1: D C E B A (with a particularly strong feeling against A) > 2: A B C > 3: A (but don't mind much overall) > 4: Don't mind (I neither particularly like 'wish' as a priority or issue > type really) > -- > Sylvain > > > On Tue, Dec 11, 2018 at 7:42 PM Aleksey Yeshchenko > wrote: > >> 1. C, D, A, B, E >> 2. B, C, A >> 3. A >> 4. Meh >> >>> On 11 Dec 2018, at 16:28, Benedict Elliott Smith >> wrote: >>> >>> Just to re-summarise the questions for people: >>> >>> 1. (A) Only contributors may edit or transition issues; (B) Only >> contributors may transition issues; (C) Only Jira-users may transition >> issues*; (D) (C)+Remove contributor role entirely; (E) Leave permission as >> they are today >>> 2. Priority on Bug issue type: (A) remove it; (B) auto-populate it; (C) >> leave it. Please rank. >>> 3. Top priority: (A) Urgent; (B) Blocker. See here for my explanation >> of why I chose Urgent < >> https://lists.apache.org/thread.html/c7b95b827d8da4efc5c017df80029676a032b150ec00bf11ca9c7fa7@%3Cdev.cassandra.apache.org%3E >> < >> https://lists.apache.org/thread.html/c7b95b827d8da4efc5c017df80029676a032b150ec00bf11ca9c7fa7@%3Cdev.cassandra.apache.org%3E . >>> 4. Priority keep ‘Wish’ (to replace issue type): +1/-1 >>> >>> With my answers (again, sorry): >>> >>> 1: A B C D E >>> 2: B C A >>> 3: A >>> 4: +0.5 >>> On 11 Dec 2018, at 16:25, Benedict Elliott Smith >> wrote: It looks like we have a multiplicity of views on permissions, so >> perhaps we should complicate this particular vote with all of the possible >> options that have been raised so far (including one off-list). Sorry >> everyone for the confusion. (A) Only contributors may edit or transition issues; (B) Only >> contributors may transition issues; (C) Only Jira-users may transition >> issues*; (D) (C)+Remove contributor role entirely; (E) Leave permission as >> they are today * Today apparently ‘Anyone’ can perform this operation A ranked vote, please. This makes my votes: 1: A B C D E 2: B C A 3: A 4: +0.5 > On 11 Dec 2018, at 05:51, Dinesh Joshi >> wrote: > > I agree with this. I generally am on the side of freedom and >> responsibility. Limiting edits to certain fields turns people off. >> Something I want to very much avoid if we can. > > Dinesh > >> On Dec 10, 2018, at 6:14 PM, Murukesh Mohanan < >> murukesh.moha...@gmail.com> wrote: >> >> On Tue, 11 Dec 2018 at 10:51, Benedict Elliott Smith >> wrote: >>> On 10 Dec 2018, at 16:21, Ariel Weisberg wrote: Hi, RE #1, does this mean if you submit a ticket and you are not a >> contributor you can't modify any of the fields including description or >> adding/removing attachments? >>> >>> Attachment operations have their own permissions, like comments. >> Description would be prohibited though. I don’t see this as a major >> problem, really; it is generally much more useful to add comments. If we >> particularly want to make a subset of fields editable there is a >> workaround, though I’m not sure anybody would have the patience to >> implement it: >> https://confluence.atlassian.com/jira/how-can-i-control-the-editing-of-issue-fields-via-workflow-149834.html >> < >> https://confluence.atlassian.com/jira/how-can-i-control-the-editing-of-issue-fields-via-workflow-149834.html >>> >>> >> >> That would be disappointing. Descriptions with broken or no formatting >> aren't rare (say, command output without code formatting). And every >> now and then the description might need to be updated. For example, in >> https://issues.apache.org/jira/browse/CASSANDRA-10989, the link to >> the >> paper had rotted, but I managed to find a new one, so I could edit it >> in. If such a change had to be posted as a comment, it might easily >> get lost in some of the more active issues. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: dev-h...@cassandra.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org >>> >> >> >> ---
Re: JIRA Workflow Proposals
Hey Benedict, Thank you. In that case A D E B C > On Dec 11, 2018, at 12:37 PM, Benedict Elliott Smith > wrote: > > Hi Andre, > > It’s ranked vote, i.e. for each question, what is your preference order for > the outcome? > > So, for question 1, the possible outcomes are: > > (A) Only contributors may edit or transition issues; > (B) Only contributors may transition issues; > (C) Only Jira-users may transition issues; > (D) (C)+Remove contributor role entirely; > (E) Leave permission as they are today > > Sylvain’s vote was D C E B A, meaning he prefers option D first, option C > second, option E third, etc. > > There are multiple ranked voting > <https://en.wikipedia.org/wiki/Ranked_voting> schemes, but unless anyone > objects I will resolve the answers with instant-runoff voting > <https://en.wikipedia.org/wiki/Instant-runoff_voting>, which is equivalent to > single transferable voting > <https://en.wikipedia.org/wiki/Single_transferable_vote> when there is only a > single outcome, as there is here. > > >> On 11 Dec 2018, at 20:25, andre wilkinson wrote: >> >> Hey everyone, >> Im just trying to keep up but I don’t think everyone needs permissions just >> contributors im trying to understand the letter voting system so I could >> better be of service to the community. Sorry if I sound naive. >> >>> On Dec 11, 2018, at 12:12 PM, Sylvain Lebresne wrote: >>> >>> 1: D C E B A (with a particularly strong feeling against A) >>> 2: A B C >>> 3: A (but don't mind much overall) >>> 4: Don't mind (I neither particularly like 'wish' as a priority or issue >>> type really) >>> -- >>> Sylvain >>> >>> >>> On Tue, Dec 11, 2018 at 7:42 PM Aleksey Yeshchenko >>> wrote: >>> >>>> 1. C, D, A, B, E >>>> 2. B, C, A >>>> 3. A >>>> 4. Meh >>>> >>>>> On 11 Dec 2018, at 16:28, Benedict Elliott Smith >>>> wrote: >>>>> >>>>> Just to re-summarise the questions for people: >>>>> >>>>> 1. (A) Only contributors may edit or transition issues; (B) Only >>>> contributors may transition issues; (C) Only Jira-users may transition >>>> issues*; (D) (C)+Remove contributor role entirely; (E) Leave permission as >>>> they are today >>>>> 2. Priority on Bug issue type: (A) remove it; (B) auto-populate it; (C) >>>> leave it. Please rank. >>>>> 3. Top priority: (A) Urgent; (B) Blocker. See here for my explanation >>>> of why I chose Urgent < >>>> https://lists.apache.org/thread.html/c7b95b827d8da4efc5c017df80029676a032b150ec00bf11ca9c7fa7@%3Cdev.cassandra.apache.org%3E >>>> < >>>> https://lists.apache.org/thread.html/c7b95b827d8da4efc5c017df80029676a032b150ec00bf11ca9c7fa7@%3Cdev.cassandra.apache.org%3E >>>>>> . >>>>> 4. Priority keep ‘Wish’ (to replace issue type): +1/-1 >>>>> >>>>> With my answers (again, sorry): >>>>> >>>>> 1: A B C D E >>>>> 2: B C A >>>>> 3: A >>>>> 4: +0.5 >>>>> >>>>>> On 11 Dec 2018, at 16:25, Benedict Elliott Smith >>>> wrote: >>>>>> >>>>>> It looks like we have a multiplicity of views on permissions, so >>>> perhaps we should complicate this particular vote with all of the possible >>>> options that have been raised so far (including one off-list). Sorry >>>> everyone for the confusion. >>>>>> >>>>>> (A) Only contributors may edit or transition issues; (B) Only >>>> contributors may transition issues; (C) Only Jira-users may transition >>>> issues*; (D) (C)+Remove contributor role entirely; (E) Leave permission as >>>> they are today >>>>>> >>>>>> * Today apparently ‘Anyone’ can perform this operation >>>>>> >>>>>> A ranked vote, please. This makes my votes: >>>>>> >>>>>> 1: A B C D E >>>>>> 2: B C A >>>>>> 3: A >>>>>> 4: +0.5 >>>>>> >>>>>> >>>>>>> On 11 Dec 2018, at 05:51, Dinesh Joshi >>>> wrote: >>>>>>> >>>>>>> I agree with this. I generally am on the side of freedom and >>>> responsibility. Limiting
Re: JIRA Workflow Proposals
Sounds great Benedict, its a start for me as again I look forward to communicating with everyone and helping out, I know I will learn a little something just from seeing work flow and studying up on what ever task is presented in front of me. > On Dec 12, 2018, at 10:14 AM, Benedict Elliott Smith > wrote: > > Which currently leads to eliminating B, C and E first choice votes, leading > to a strong win for option D. > > I’ll leave it a few days to see if anymore votes roll in, but I don’t > anticipate a major shift in opinion. I will update the proposal with the > outcome, and call a formal vote on the final proposal in a few days. > > Thanks again everyone for participating in what I realise was not the most > exciting discussion. I’m glad everyone got a chance to air their opinions, > and that we managed to come to a decision that I hope we can all endorse.
Re: Apache Cassandra meetup @ Instagram HQ
Yes is there anyway to attend remotely? Sent from my iPhone > On Feb 18, 2019, at 6:40 PM, Shaurya Gupta wrote: > > Hi, > > This looks very interesting to me. Can I attend this remotely? > > Thanks > Shaurya > > > On Tue, Feb 19, 2019 at 5:37 AM dinesh.jo...@yahoo.com.INVALID > wrote: > >> Hi all, >> >> Apologies for the cross-post. In case you're in the SF Bay Area, Instagram >> is hosting a meetup. Interesting talks on Cassandra Traffic management, >> Cassandra on Kubernetes. See details in the attached link - >> >> >> https://www.eventbrite.com/e/cassandra-traffic-management-at-instagram-cassandra-and-k8s-with-instaclustr-tickets-54986803008 >> >> Thanks, >> >> Dinesh >> > > > -- > Shaurya Gupta - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: Apache Cassandra meetup @ Instagram HQ
Thank you for reaching out Sent from my iPhone > On Feb 19, 2019, at 8:45 AM, Dinesh Joshi > wrote: > > I’ve emailed the organizers. They didn’t intend to live stream it but will > get back to us if they can. > > Cheers, > > Dinesh > >> On Feb 19, 2019, at 1:11 AM, andre wilkinson >> wrote: >> >> Yes is there anyway to attend remotely? >> >> Sent from my iPhone >> >>> On Feb 18, 2019, at 6:40 PM, Shaurya Gupta wrote: >>> >>> Hi, >>> >>> This looks very interesting to me. Can I attend this remotely? >>> >>> Thanks >>> Shaurya >>> >>> >>> On Tue, Feb 19, 2019 at 5:37 AM dinesh.jo...@yahoo.com.INVALID >>> wrote: >>> >>>> Hi all, >>>> >>>> Apologies for the cross-post. In case you're in the SF Bay Area, Instagram >>>> is hosting a meetup. Interesting talks on Cassandra Traffic management, >>>> Cassandra on Kubernetes. See details in the attached link - >>>> >>>> >>>> https://www.eventbrite.com/e/cassandra-traffic-management-at-instagram-cassandra-and-k8s-with-instaclustr-tickets-54986803008 >>>> >>>> Thanks, >>>> >>>> Dinesh >>>> >>> >>> >>> -- >>> Shaurya Gupta >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: dev-h...@cassandra.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: Apache Cassandra meetup @ Instagram HQ
Awesome, If they do I will be watching. Sent from my iPhone > On Feb 20, 2019, at 10:57 AM, dinesh.jo...@yahoo.com.INVALID > wrote: > > Just heard back. Unfortunately they cannot live stream but they'll try to > record it and post it online. > Dinesh > >On Tuesday, February 19, 2019, 3:55:15 PM PST, Sundaramoorthy, Natarajan > wrote: > > Dinesh Thank you. > > > > -Original Message- > From: andre wilkinson [mailto:antonio...@me.com.INVALID] > Sent: Tuesday, February 19, 2019 5:14 PM > To: dev@cassandra.apache.org > Subject: Re: Apache Cassandra meetup @ Instagram HQ > > Thank you for reaching out > > Sent from my iPhone > >> On Feb 19, 2019, at 8:45 AM, Dinesh Joshi >> wrote: >> >> I’ve emailed the organizers. They didn’t intend to live stream it but will >> get back to us if they can. >> >> Cheers, >> >> Dinesh >> >>> On Feb 19, 2019, at 1:11 AM, andre wilkinson >>> wrote: >>> >>> Yes is there anyway to attend remotely? >>> >>> Sent from my iPhone >>> >>>> On Feb 18, 2019, at 6:40 PM, Shaurya Gupta wrote: >>>> >>>> Hi, >>>> >>>> This looks very interesting to me. Can I attend this remotely? >>>> >>>> Thanks >>>> Shaurya >>>> >>>> >>>> On Tue, Feb 19, 2019 at 5:37 AM dinesh.jo...@yahoo.com.INVALID >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Apologies for the cross-post. In case you're in the SF Bay Area, Instagram >>>>> is hosting a meetup. Interesting talks on Cassandra Traffic management, >>>>> Cassandra on Kubernetes. See details in the attached link - >>>>> >>>>> >>>>> https://www.eventbrite.com/e/cassandra-traffic-management-at-instagram-cassandra-and-k8s-with-instaclustr-tickets-54986803008 >>>>> >>>>> Thanks, >>>>> >>>>> Dinesh >>>>> >>>> >>>> >>>> -- >>>> Shaurya Gupta >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >>> For additional commands, e-mail: dev-h...@cassandra.apache.org >>> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: dev-h...@cassandra.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > This e-mail, including attachments, may include confidential and/or > proprietary information, and may be used only by the person or entity > to which it is addressed. If the reader of this e-mail is not the intended > recipient or his or her authorized agent, the reader is hereby notified > that any dissemination, distribution or copying of this e-mail is > prohibited. If you have received this e-mail in error, please notify the > sender by replying to this message and delete this e-mail immediately. > B�CB��[��X��ܚX�KK[XZ[�]�][��X��ܚX�P�\��[��K�\X�K�ܙ�B��܈Y][ۘ[��[X[��K[XZ[�]�Z[�\��[��K�\X�K�ܙ�B�B > - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
