cf-dev@lists.cloudfoundry.org | FW: issue tracker permissions

Home Messages Hashtags Subgroups

Date Date 1 - 12 of 12

FW: issue tracker permissions

Guillaume Berche #5663 Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/articles/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/articles/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki Guillaume. toggle quoted message Show quoted text On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies <diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: Hi, I was trying to watch a story I am interested in https://www.pivotaltracker.com/n/projects/892938/stories/105493826 I do have an account but it seems I don't have permissions to watch nor to comment. Is there something I missed? Regards Jan -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html
More All Messages By This Member
Guillaume Berche #5759 Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. toggle quoted message Show quoted text On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/articles/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/articles/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies <diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: Hi, I was trying to watch a story I am interested in https://www.pivotaltracker.com/n/projects/892938/stories/105493826 I do have an account but it seems I don't have permissions to watch nor to comment. Is there something I missed? Regards Jan -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html
More All Messages By This Member
Marco Voelz #5760 Dear Guillaume, Thanks for your efforts in this direction. As I already stated before, it is really a pain that you are not able to follow stories or comment when not being a member in a Pivotaltracker project. However, github issues aren’t more than a crutch, probably not even a good one. For example, GH issues cannot be ordered. They are in the order of creation, priorization is not visible. Therefore, if you look e.g. at the BOSH mirror [1], there are a bunch of “unstarted” and “unscheduled” issues, the first “started” one comes on page 2. For bugs, it gets more confusing. Most people have the github bot activated, which creates a PT story for each GH issue created. This is already confusing, because you have two places where potentially updates to this bug could be located in, and nobody knows where to look. Add in the mirroring, and now you have three places, see an example for the buildpacks [2]. All of this is not your fault, it is a restriction on how GH deals with issues and the fact that we’re distributing information over more than one place. While I appreciate your efforts and time spent on this: I strongly feel that is an issue that can only be solved by one of two options: • The Pivotaltracker team implementing the necessary functionality • Migrating to a different tracker I’m trying all I can to push for the first option by talking to Dan and Lisa, but other features seem to be more important to the PT team. In November, it has been a year since I asked for this, so my confidence isn’t very high that it is going to happen at all. For me that just means option two is getting more and more realistic every day. Warm regards Marco [1] https://github.com/cf-tm-bot/bosh/issues [2] https://github.com/cloudfoundry/staticfile-buildpack/issues/85 toggle quoted message Show quoted text -----Original Message----- From: Guillaume Berche <bercheg(a)gmail.com> Date: Saturday, 24 September 2016 at 12:29 To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org> Cc: Chip Childers <cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" <cholick(a)gmail.com>, Dan Podsedly <dpodsedly(a)pivotal.io>, Lisa Doan <ldoan(a)pivotal.io>, "Voelz, Marco" <marco.voelz(a)sap.com> Subject: Re: [cf-dev] Re: FW: issue tracker permissions Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/articles/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/articles/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror <https://github.com/orange-cloudfoundry/pivotaltrackermirror> [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues <https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues> [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker <https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker> [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki <https://github.com/cloudfoundry-community/cf-docs-contrib/wiki> Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies <diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: >>Hi, >> >>I was trying to watch a story I am interested in >>https://www.pivotaltracker.com/n/projects/892938/stories/105493826 >> >> >>I do have an account but it seems I don't have permissions to watch nor to comment. >> >>Is there something I missed? >> >>Regards >>Jan >> -- Sent from Jeff Dean's printf() mobile console
More All Messages By This Member
Carlo Alberto Ferraris #5764 Guillaume, thank you so much! One beer at the next CF summit is on me. :) Carlo
More All Messages By This Member
Lisa Doan <ldoan@...> #5765 Hi all, Just to re-iterate, we do have this feature prioritized on the Tracker team. I'm sorry we haven't been able to deliver this yet, but there are a number of other higher priority items that we must attend to before we can begin this work. We will keep you posted as we get closer to implementing this. Thanks, Lisa toggle quoted message Show quoted text On Sun, Sep 25, 2016 at 12:54 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Guillaume, Thanks for your efforts in this direction. As I already stated before, it is really a pain that you are not able to follow stories or comment when not being a member in a Pivotaltracker project. However, github issues aren’t more than a crutch, probably not even a good one. For example, GH issues cannot be ordered. They are in the order of creation, priorization is not visible. Therefore, if you look e.g. at the BOSH mirror [1], there are a bunch of “unstarted” and “unscheduled” issues, the first “started” one comes on page 2. For bugs, it gets more confusing. Most people have the github bot activated, which creates a PT story for each GH issue created. This is already confusing, because you have two places where potentially updates to this bug could be located in, and nobody knows where to look. Add in the mirroring, and now you have three places, see an example for the buildpacks [2]. All of this is not your fault, it is a restriction on how GH deals with issues and the fact that we’re distributing information over more than one place. While I appreciate your efforts and time spent on this: I strongly feel that is an issue that can only be solved by one of two options: • The Pivotaltracker team implementing the necessary functionality • Migrating to a different tracker I’m trying all I can to push for the first option by talking to Dan and Lisa, but other features seem to be more important to the PT team. In November, it has been a year since I asked for this, so my confidence isn’t very high that it is going to happen at all. For me that just means option two is getting more and more realistic every day. Warm regards Marco [1] https://github.com/cf-tm-bot/bosh/issues [2] https://github.com/cloudfoundry/staticfile-buildpack/issues/85 -----Original Message----- From: Guillaume Berche <bercheg(a)gmail.com> Date: Saturday, 24 September 2016 at 12:29 To: "Discussions about Cloud Foundry projects and the system overall." < cf-dev(a)lists.cloudfoundry.org> Cc: Chip Childers <cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" < cholick(a)gmail.com>, Dan Podsedly <dpodsedly(a)pivotal.io>, Lisa Doan < ldoan(a)pivotal.io>, "Voelz, Marco" <marco.voelz(a)sap.com> Subject: Re: [cf-dev] Re: FW: issue tracker permissions Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/ articles/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/ articles/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/articles/basic-writing-and- formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror < https://github.com/orange-cloudfoundry/pivotaltrackermirror> [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues < https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues> [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker < https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker> [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki < https://github.com/cloudfoundry-community/cf-docs-contrib/wiki> Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies < diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: >>Hi, >> >>I was trying to watch a story I am interested in >>https://www.pivotaltracker.com/n/projects/892938/stories/105493826 >> >> >>I do have an account but it seems I don't have permissions to watch nor to comment. >> >>Is there something I missed? >> >>Regards >>Jan >> -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html
More
Lisa Doan <ldoan@...> #5766 Hi all -- a couple people reached out asking for a date for Viewers can follow. We are currently targeting November of this year. Thanks, Lisa toggle quoted message Show quoted text On Mon, Sep 26, 2016 at 10:03 AM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all, Just to re-iterate, we do have this feature prioritized on the Tracker team. I'm sorry we haven't been able to deliver this yet, but there are a number of other higher priority items that we must attend to before we can begin this work. We will keep you posted as we get closer to implementing this. Thanks, Lisa On Sun, Sep 25, 2016 at 12:54 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Guillaume, Thanks for your efforts in this direction. As I already stated before, it is really a pain that you are not able to follow stories or comment when not being a member in a Pivotaltracker project. However, github issues aren’t more than a crutch, probably not even a good one. For example, GH issues cannot be ordered. They are in the order of creation, priorization is not visible. Therefore, if you look e.g. at the BOSH mirror [1], there are a bunch of “unstarted” and “unscheduled” issues, the first “started” one comes on page 2. For bugs, it gets more confusing. Most people have the github bot activated, which creates a PT story for each GH issue created. This is already confusing, because you have two places where potentially updates to this bug could be located in, and nobody knows where to look. Add in the mirroring, and now you have three places, see an example for the buildpacks [2]. All of this is not your fault, it is a restriction on how GH deals with issues and the fact that we’re distributing information over more than one place. While I appreciate your efforts and time spent on this: I strongly feel that is an issue that can only be solved by one of two options: • The Pivotaltracker team implementing the necessary functionality • Migrating to a different tracker I’m trying all I can to push for the first option by talking to Dan and Lisa, but other features seem to be more important to the PT team. In November, it has been a year since I asked for this, so my confidence isn’t very high that it is going to happen at all. For me that just means option two is getting more and more realistic every day. Warm regards Marco [1] https://github.com/cf-tm-bot/bosh/issues [2] https://github.com/cloudfoundry/staticfile-buildpack/issues/85 -----Original Message----- From: Guillaume Berche <bercheg(a)gmail.com> Date: Saturday, 24 September 2016 at 12:29 To: "Discussions about Cloud Foundry projects and the system overall." < cf-dev(a)lists.cloudfoundry.org> Cc: Chip Childers <cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" < cholick(a)gmail.com>, Dan Podsedly <dpodsedly(a)pivotal.io>, Lisa Doan < ldoan(a)pivotal.io>, "Voelz, Marco" <marco.voelz(a)sap.com> Subject: Re: [cf-dev] Re: FW: issue tracker permissions Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/artic les/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/artic les/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/artic les/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror < https://github.com/orange-cloudfoundry/pivotaltrackermirror> [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues < https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues> [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker < https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker> [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki < https://github.com/cloudfoundry-community/cf-docs-contrib/wiki> Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies < diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: >>Hi, >> >>I was trying to watch a story I am interested in >>https://www.pivotaltracker.com/n/projects/892938/stories/105493826 >> >> >>I do have an account but it seems I don't have permissions to watch nor to comment. >> >>Is there something I missed? >> >>Regards >>Jan >> -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html
More
Guillaume Berche #5777 Thanks Lisa, the "Viewers can follow" feature will be very useful to the CF community. I plan to redact the GH issue mirrors as to reduce the confusion caused by implicit cross links between issues that Marco reminded (see related [a]). When the "Viewers can follow" feature is available, there will be no more value in discovering GH issues mirrors. Are there future plans in the tracker to enable viewers to get notifications for all stories in the backlog ? If not, the promising stack integration [4], which requires PT project owners to configure the Slack webhook URL, could help. With collaboration from owners of the Foundation trackers, this could result into a slack channel per PT project, where community members can watch related activity, much like what the buildpacks team have already set up into [b]. The remaining added value for the mirrored GH issues will then be: - community members "commenting" backlogs in context. - searching across multiple PT projects Is the tracker team also planning to address the latter two use-cases ? Thanks again, [a] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues/1#issuecomment-238706510 [b] https://cloudfoundry.slack.com/messages/buildpacks-firehose/ [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker "On that page, find the Activity Web Hook section. Add https://hooks.slack.com/services/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 as your Web Hook URL. Ensure that the API Version is set to v5 and then click Save Web Hook Settings." Guillaume. toggle quoted message Show quoted text On Mon, Sep 26, 2016 at 6:26 PM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all -- a couple people reached out asking for a date for Viewers can follow. We are currently targeting November of this year. Thanks, Lisa On Mon, Sep 26, 2016 at 10:03 AM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all, Just to re-iterate, we do have this feature prioritized on the Tracker team. I'm sorry we haven't been able to deliver this yet, but there are a number of other higher priority items that we must attend to before we can begin this work. We will keep you posted as we get closer to implementing this. Thanks, Lisa On Sun, Sep 25, 2016 at 12:54 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Guillaume, Thanks for your efforts in this direction. As I already stated before, it is really a pain that you are not able to follow stories or comment when not being a member in a Pivotaltracker project. However, github issues aren’t more than a crutch, probably not even a good one. For example, GH issues cannot be ordered. They are in the order of creation, priorization is not visible. Therefore, if you look e.g. at the BOSH mirror [1], there are a bunch of “unstarted” and “unscheduled” issues, the first “started” one comes on page 2. For bugs, it gets more confusing. Most people have the github bot activated, which creates a PT story for each GH issue created. This is already confusing, because you have two places where potentially updates to this bug could be located in, and nobody knows where to look. Add in the mirroring, and now you have three places, see an example for the buildpacks [2]. All of this is not your fault, it is a restriction on how GH deals with issues and the fact that we’re distributing information over more than one place. While I appreciate your efforts and time spent on this: I strongly feel that is an issue that can only be solved by one of two options: • The Pivotaltracker team implementing the necessary functionality • Migrating to a different tracker I’m trying all I can to push for the first option by talking to Dan and Lisa, but other features seem to be more important to the PT team. In November, it has been a year since I asked for this, so my confidence isn’t very high that it is going to happen at all. For me that just means option two is getting more and more realistic every day. Warm regards Marco [1] https://github.com/cf-tm-bot/bosh/issues [2] https://github.com/cloudfoundry/staticfile-buildpack/issues/85 -----Original Message----- From: Guillaume Berche <bercheg(a)gmail.com> Date: Saturday, 24 September 2016 at 12:29 To: "Discussions about Cloud Foundry projects and the system overall." < cf-dev(a)lists.cloudfoundry.org> Cc: Chip Childers <cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" < cholick(a)gmail.com>, Dan Podsedly <dpodsedly(a)pivotal.io>, Lisa Doan < ldoan(a)pivotal.io>, "Voelz, Marco" <marco.voelz(a)sap.com> Subject: Re: [cf-dev] Re: FW: issue tracker permissions Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/artic les/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/artic les/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/artic les/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror < https://github.com/orange-cloudfoundry/pivotaltrackermirror> [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues < https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues> [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker < https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker> [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki < https://github.com/cloudfoundry-community/cf-docs-contrib/wiki> Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies < diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: >>Hi, >> >>I was trying to watch a story I am interested in >>https://www.pivotaltracker.com/n/projects/892938/stories/105493826 >> >> >>I do have an account but it seems I don't have permissions to watch nor to comment. >> >>Is there something I missed? >> >>Regards >>Jan >> -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html
More All Messages By This Member
Guillaume Berche #5784 Thanks Lisa for the additional precisions. Related to the use of workspaces to search across multiple public pivotal trackers, I understand a workspace can only contain projects the logged in user is member of. Is there a possibility that I missed to add the public cloudfoundry tracker projects (whose non core contributors are not member of), or would that be a feature enabled along with the upcoming "viewers can follow" feature ? Regards, Guillaume. toggle quoted message Show quoted text On Wed, Sep 28, 2016 at 6:14 PM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi Guillaume, Yes, once Viewers can follow, they'll be able to set notifications like any project member can. That is, they'll be able to get notifications on an entire project. Commenting, however, would continue to be restricted to project members. Searching across multiple Tracker projects is already possible with Workspaces <http://www.pivotaltracker.com/help/articles/managing_multiple_projects_workspaces/>, but we understand that this feature is limited by not being able to share workspaces across users. In 2017, we hope to begin building in better cross-project or portfolio visibility. Thanks, Lisa On Wed, Sep 28, 2016 at 12:00 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: Thanks Lisa, the "Viewers can follow" feature will be very useful to the CF community. I plan to redact the GH issue mirrors as to reduce the confusion caused by implicit cross links between issues that Marco reminded (see related [a]). When the "Viewers can follow" feature is available, there will be no more value in discovering GH issues mirrors. Are there future plans in the tracker to enable viewers to get notifications for all stories in the backlog ? If not, the promising stack integration [4], which requires PT project owners to configure the Slack webhook URL, could help. With collaboration from owners of the Foundation trackers, this could result into a slack channel per PT project, where community members can watch related activity, much like what the buildpacks team have already set up into [b]. The remaining added value for the mirrored GH issues will then be: - community members "commenting" backlogs in context. - searching across multiple PT projects Is the tracker team also planning to address the latter two use-cases ? Thanks again, [a] https://github.com/orange-cloudfoundry/pivotaltrackermirror/ issues/1#issuecomment-238706510 [b] https://cloudfoundry.slack.com/messages/buildpacks-firehose/ [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker "On that page, find the Activity Web Hook section. Add https://hooks.slack.com/services/T02FL4A1X/B2GRZUQ56/zEswA2U fbCcJl31fCw3DLDq4 as your Web Hook URL. Ensure that the API Version is set to v5 and then click Save Web Hook Settings." Guillaume. On Mon, Sep 26, 2016 at 6:26 PM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all -- a couple people reached out asking for a date for Viewers can follow. We are currently targeting November of this year. Thanks, Lisa On Mon, Sep 26, 2016 at 10:03 AM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all, Just to re-iterate, we do have this feature prioritized on the Tracker team. I'm sorry we haven't been able to deliver this yet, but there are a number of other higher priority items that we must attend to before we can begin this work. We will keep you posted as we get closer to implementing this. Thanks, Lisa On Sun, Sep 25, 2016 at 12:54 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Guillaume, Thanks for your efforts in this direction. As I already stated before, it is really a pain that you are not able to follow stories or comment when not being a member in a Pivotaltracker project. However, github issues aren’t more than a crutch, probably not even a good one. For example, GH issues cannot be ordered. They are in the order of creation, priorization is not visible. Therefore, if you look e.g. at the BOSH mirror [1], there are a bunch of “unstarted” and “unscheduled” issues, the first “started” one comes on page 2. For bugs, it gets more confusing. Most people have the github bot activated, which creates a PT story for each GH issue created. This is already confusing, because you have two places where potentially updates to this bug could be located in, and nobody knows where to look. Add in the mirroring, and now you have three places, see an example for the buildpacks [2]. All of this is not your fault, it is a restriction on how GH deals with issues and the fact that we’re distributing information over more than one place. While I appreciate your efforts and time spent on this: I strongly feel that is an issue that can only be solved by one of two options: • The Pivotaltracker team implementing the necessary functionality • Migrating to a different tracker I’m trying all I can to push for the first option by talking to Dan and Lisa, but other features seem to be more important to the PT team. In November, it has been a year since I asked for this, so my confidence isn’t very high that it is going to happen at all. For me that just means option two is getting more and more realistic every day. Warm regards Marco [1] https://github.com/cf-tm-bot/bosh/issues [2] https://github.com/cloudfoundry/staticfile-buildpack/issues/85 -----Original Message----- From: Guillaume Berche <bercheg(a)gmail.com> Date: Saturday, 24 September 2016 at 12:29 To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org> Cc: Chip Childers <cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" < cholick(a)gmail.com>, Dan Podsedly <dpodsedly(a)pivotal.io>, Lisa Doan < ldoan(a)pivotal.io>, "Voelz, Marco" <marco.voelz(a)sap.com> Subject: Re: [cf-dev] Re: FW: issue tracker permissions Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/artic les/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/artic les/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/artic les/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror < https://github.com/orange-cloudfoundry/pivotaltrackermirror> [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues <https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues> [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker < https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker> [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki < https://github.com/cloudfoundry-community/cf-docs-contrib/wiki> Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies < diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: >>Hi, >> >>I was trying to watch a story I am interested in >>https://www.pivotaltracker.com/n/projects/892938/stories/1 05493826 >> >> >>I do have an account but it seems I don't have permissions to watch nor to comment. >> >>Is there something I missed? >> >>Regards >>Jan >> -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html
More All Messages By This Member
Guillaume Berche #5787 Hi Lisa, I double checked, and I still am unable to add public cloudfoundry tracker projects to my workspaces to be able to search mutiple trackers. See screenshots below (I'm a reader member of CLI project following kind invite by Dies Koper). There must be something I got wrong, I'd welcome help or documentation pointers, and confirmation by other CF community members that they are able to create such workspaces without being member of the CF public projects. Thanks in advance, Guillaume. https://www.pivotaltracker.com/n/workspaces/655995 [image: Inline image 1] [image: Inline image 2] Guillaume. toggle quoted message Show quoted text On Thu, Sep 29, 2016 at 12:45 AM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi Guillaume, Workspaces can only contain projects that the user is a member OR viewer of. It is already possible now for a user who is only a viewer of the public cloudfoundry tracker projects to include those projects in their workspaces. Does that answer your question? Thanks, Lisa On Wed, Sep 28, 2016 at 11:45 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: Thanks Lisa for the additional precisions. Related to the use of workspaces to search across multiple public pivotal trackers, I understand a workspace can only contain projects the logged in user is member of. Is there a possibility that I missed to add the public cloudfoundry tracker projects (whose non core contributors are not member of), or would that be a feature enabled along with the upcoming "viewers can follow" feature ? Regards, Guillaume. On Wed, Sep 28, 2016 at 6:14 PM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi Guillaume, Yes, once Viewers can follow, they'll be able to set notifications like any project member can. That is, they'll be able to get notifications on an entire project. Commenting, however, would continue to be restricted to project members. Searching across multiple Tracker projects is already possible with Workspaces <http://www.pivotaltracker.com/help/articles/managing_multiple_projects_workspaces/>, but we understand that this feature is limited by not being able to share workspaces across users. In 2017, we hope to begin building in better cross-project or portfolio visibility. Thanks, Lisa On Wed, Sep 28, 2016 at 12:00 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: Thanks Lisa, the "Viewers can follow" feature will be very useful to the CF community. I plan to redact the GH issue mirrors as to reduce the confusion caused by implicit cross links between issues that Marco reminded (see related [a]). When the "Viewers can follow" feature is available, there will be no more value in discovering GH issues mirrors. Are there future plans in the tracker to enable viewers to get notifications for all stories in the backlog ? If not, the promising stack integration [4], which requires PT project owners to configure the Slack webhook URL, could help. With collaboration from owners of the Foundation trackers, this could result into a slack channel per PT project, where community members can watch related activity, much like what the buildpacks team have already set up into [b]. The remaining added value for the mirrored GH issues will then be: - community members "commenting" backlogs in context. - searching across multiple PT projects Is the tracker team also planning to address the latter two use-cases ? Thanks again, [a] https://github.com/orange-cloudfoundry/pivotaltrackermirror/ issues/1#issuecomment-238706510 [b] https://cloudfoundry.slack.com/messages/buildpacks-firehose/ [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker "On that page, find the Activity Web Hook section. Add https://hooks.slack.com/services/T02FL4A1X/B2GRZUQ56/zEswA2U fbCcJl31fCw3DLDq4 as your Web Hook URL. Ensure that the API Version is set to v5 and then click Save Web Hook Settings." Guillaume. On Mon, Sep 26, 2016 at 6:26 PM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all -- a couple people reached out asking for a date for Viewers can follow. We are currently targeting November of this year. Thanks, Lisa On Mon, Sep 26, 2016 at 10:03 AM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all, Just to re-iterate, we do have this feature prioritized on the Tracker team. I'm sorry we haven't been able to deliver this yet, but there are a number of other higher priority items that we must attend to before we can begin this work. We will keep you posted as we get closer to implementing this. Thanks, Lisa On Sun, Sep 25, 2016 at 12:54 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Guillaume, Thanks for your efforts in this direction. As I already stated before, it is really a pain that you are not able to follow stories or comment when not being a member in a Pivotaltracker project. However, github issues aren’t more than a crutch, probably not even a good one. For example, GH issues cannot be ordered. They are in the order of creation, priorization is not visible. Therefore, if you look e.g. at the BOSH mirror [1], there are a bunch of “unstarted” and “unscheduled” issues, the first “started” one comes on page 2. For bugs, it gets more confusing. Most people have the github bot activated, which creates a PT story for each GH issue created. This is already confusing, because you have two places where potentially updates to this bug could be located in, and nobody knows where to look. Add in the mirroring, and now you have three places, see an example for the buildpacks [2]. All of this is not your fault, it is a restriction on how GH deals with issues and the fact that we’re distributing information over more than one place. While I appreciate your efforts and time spent on this: I strongly feel that is an issue that can only be solved by one of two options: • The Pivotaltracker team implementing the necessary functionality • Migrating to a different tracker I’m trying all I can to push for the first option by talking to Dan and Lisa, but other features seem to be more important to the PT team. In November, it has been a year since I asked for this, so my confidence isn’t very high that it is going to happen at all. For me that just means option two is getting more and more realistic every day. Warm regards Marco [1] https://github.com/cf-tm-bot/bosh/issues [2] https://github.com/cloudfoundry/staticfile-buildpack/issues/85 -----Original Message----- From: Guillaume Berche <bercheg(a)gmail.com> Date: Saturday, 24 September 2016 at 12:29 To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org> Cc: Chip Childers <cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" <cholick(a)gmail.com>, Dan Podsedly <dpodsedly(a)pivotal.io>, Lisa Doan <ldoan(a)pivotal.io>, "Voelz, Marco" <marco.voelz(a)sap.com> Subject: Re: [cf-dev] Re: FW: issue tracker permissions Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/artic les/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/artic les/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/artic les/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror < https://github.com/orange-cloudfoundry/pivotaltrackermirror> [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/ issues <https://github.com/orange-cloudfoundry/pivotaltrackermirror /issues> [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker < https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker> [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki < https://github.com/cloudfoundry-community/cf-docs-contrib/wiki> Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco < marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies < diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: >>Hi, >> >>I was trying to watch a story I am interested in >>https://www.pivotaltracker.com/n/projects/892938/stories/1 05493826 >> >> >>I do have an account but it seems I don't have permissions to watch nor to comment. >> >>Is there something I missed? >> >>Regards >>Jan >> -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html image.png image.png
More All Messages By This Member
Guillaume Berche #5790 Thanks Lisa for considering this extra feature to avoid the per-project invite. I understand an explicit action would still be requested to become a member of the account owning the CFF projects, for any one willing to follow, or add projects to workspaces. The CF community is quite large, so it's possible hundreds of people will request this. That's be great to have a "request to join owner account" button, as to avoid wasting time through email requests to the project owner. In the meantime until the community gets these self-service accesses, I'll try maintaining the trackermirror up as a hacky workaround. Please let me know if ever this causes troubles/inconveniences. Regards, Guillaume. toggle quoted message Show quoted text On Thu, Sep 29, 2016 at 9:41 PM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi Guillaume, You need to be invited to be a viewer or member on projects before you can add them to workspaces. In those screenshots, the only projects appearing are ones that you are a member or viewer of. In order to have the CF public projects appear there, you must be invited to the projects. I understand that it would be burdensome to ask all of the project owners to invite you to the relevant projects. We are currently working on a feature that will allow any account member to self-join projects so that this isn't as difficult. This would require you to become a member of the account that owns the CF public projects, but once you are a member, you could join any of the shared or public projects. We expect that to release later this year (it is part of the body of work that is ahead of Viewers can follow). Thanks, Lisa On Thu, Sep 29, 2016 at 7:21 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi Lisa, I double checked, and I still am unable to add public cloudfoundry tracker projects to my workspaces to be able to search mutiple trackers. See screenshots below (I'm a reader member of CLI project following kind invite by Dies Koper). There must be something I got wrong, I'd welcome help or documentation pointers, and confirmation by other CF community members that they are able to create such workspaces without being member of the CF public projects. Thanks in advance, Guillaume. https://www.pivotaltracker.com/n/workspaces/655995 [image: Inline image 1] [image: Inline image 2] Guillaume. On Thu, Sep 29, 2016 at 12:45 AM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi Guillaume, Workspaces can only contain projects that the user is a member OR viewer of. It is already possible now for a user who is only a viewer of the public cloudfoundry tracker projects to include those projects in their workspaces. Does that answer your question? Thanks, Lisa On Wed, Sep 28, 2016 at 11:45 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: Thanks Lisa for the additional precisions. Related to the use of workspaces to search across multiple public pivotal trackers, I understand a workspace can only contain projects the logged in user is member of. Is there a possibility that I missed to add the public cloudfoundry tracker projects (whose non core contributors are not member of), or would that be a feature enabled along with the upcoming "viewers can follow" feature ? Regards, Guillaume. On Wed, Sep 28, 2016 at 6:14 PM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi Guillaume, Yes, once Viewers can follow, they'll be able to set notifications like any project member can. That is, they'll be able to get notifications on an entire project. Commenting, however, would continue to be restricted to project members. Searching across multiple Tracker projects is already possible with Workspaces <http://www.pivotaltracker.com/help/articles/managing_multiple_projects_workspaces/>, but we understand that this feature is limited by not being able to share workspaces across users. In 2017, we hope to begin building in better cross-project or portfolio visibility. Thanks, Lisa On Wed, Sep 28, 2016 at 12:00 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: Thanks Lisa, the "Viewers can follow" feature will be very useful to the CF community. I plan to redact the GH issue mirrors as to reduce the confusion caused by implicit cross links between issues that Marco reminded (see related [a]). When the "Viewers can follow" feature is available, there will be no more value in discovering GH issues mirrors. Are there future plans in the tracker to enable viewers to get notifications for all stories in the backlog ? If not, the promising stack integration [4], which requires PT project owners to configure the Slack webhook URL, could help. With collaboration from owners of the Foundation trackers, this could result into a slack channel per PT project, where community members can watch related activity, much like what the buildpacks team have already set up into [b]. The remaining added value for the mirrored GH issues will then be: - community members "commenting" backlogs in context. - searching across multiple PT projects Is the tracker team also planning to address the latter two use-cases ? Thanks again, [a] https://github.com/orange-cloudfoundry/pivotaltrackermirror/ issues/1#issuecomment-238706510 [b] https://cloudfoundry.slack.com/messages/buildpacks-firehose/ [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker "On that page, find the Activity Web Hook section. Add https://hooks.slack.com/services/T02FL4A1X/B2GRZUQ56/zEswA2U fbCcJl31fCw3DLDq4 as your Web Hook URL. Ensure that the API Version is set to v5 and then click Save Web Hook Settings." Guillaume. On Mon, Sep 26, 2016 at 6:26 PM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all -- a couple people reached out asking for a date for Viewers can follow. We are currently targeting November of this year. Thanks, Lisa On Mon, Sep 26, 2016 at 10:03 AM, Lisa Doan <ldoan(a)pivotal.io> wrote: Hi all, Just to re-iterate, we do have this feature prioritized on the Tracker team. I'm sorry we haven't been able to deliver this yet, but there are a number of other higher priority items that we must attend to before we can begin this work. We will keep you posted as we get closer to implementing this. Thanks, Lisa On Sun, Sep 25, 2016 at 12:54 AM, Voelz, Marco <marco.voelz(a)sap.com wrote: Dear Guillaume, Thanks for your efforts in this direction. As I already stated before, it is really a pain that you are not able to follow stories or comment when not being a member in a Pivotaltracker project. However, github issues aren’t more than a crutch, probably not even a good one. For example, GH issues cannot be ordered. They are in the order of creation, priorization is not visible. Therefore, if you look e.g. at the BOSH mirror [1], there are a bunch of “unstarted” and “unscheduled” issues, the first “started” one comes on page 2. For bugs, it gets more confusing. Most people have the github bot activated, which creates a PT story for each GH issue created. This is already confusing, because you have two places where potentially updates to this bug could be located in, and nobody knows where to look. Add in the mirroring, and now you have three places, see an example for the buildpacks [2]. All of this is not your fault, it is a restriction on how GH deals with issues and the fact that we’re distributing information over more than one place. While I appreciate your efforts and time spent on this: I strongly feel that is an issue that can only be solved by one of two options: • The Pivotaltracker team implementing the necessary functionality • Migrating to a different tracker I’m trying all I can to push for the first option by talking to Dan and Lisa, but other features seem to be more important to the PT team. In November, it has been a year since I asked for this, so my confidence isn’t very high that it is going to happen at all. For me that just means option two is getting more and more realistic every day. Warm regards Marco [1] https://github.com/cf-tm-bot/bosh/issues [2] https://github.com/cloudfoundry/staticfile-buildpack/issues/85 -----Original Message----- From: Guillaume Berche <bercheg(a)gmail.com> Date: Saturday, 24 September 2016 at 12:29 To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org> Cc: Chip Childers <cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" <cholick(a)gmail.com>, Dan Podsedly <dpodsedly(a)pivotal.io>, Lisa Doan <ldoan(a)pivotal.io>, "Voelz, Marco" <marco.voelz(a)sap.com> Subject: Re: [cf-dev] Re: FW: issue tracker permissions Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/artic les/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/artic les/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/artic les/basic-writing-and-formatting-syntax/#mentioning-users-an d-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror < https://github.com/orange-cloudfoundry/pivotaltrackermirror> [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/ issues <https://github.com/orange-clo udfoundry/pivotaltrackermirror/issues> [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker <https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker> [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki <https://github.com/cloudfoundry-community/cf-docs-contrib/wiki> Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco < marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick < cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies < diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: >>Hi, >> >>I was trying to watch a story I am interested in >>https://www.pivotaltracker.com/n/projects/892938/stories/1 05493826 >> >> >>I do have an account but it seems I don't have permissions to watch nor to comment. >> >>Is there something I missed? >> >>Regards >>Jan >> -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html image.png image.png
More All Messages By This Member
William Martin #5862 Hi Guillaume, Sorry for chiming in late about this, we in the Garden team were a little surprised by one of the emergent properties of the tracker/github mirroring. When we include link to a GitHub issue in Tracker and you mirror, it seems something (possibly GitHub default behaviour) is updating the referenced issue, stating that WE have referenced it. This was pretty surprising behaviour to us and although we are very happy for people to read our backlog there's a disconnect between having something visible and modifying others' issues. In particular, when we discovered this behaviour, we had been referencing issues as part of ongoing investigations and later decided they were unrelated, which is essentially spamming and confusing for others. See the bottom of this issue for an example: https://github.com/docker/docker/issues/22633 We're not sure if there are any other concerning emergent properties for us but we would strongly prefer the above didn't happen. Thanks! Will On Sat, Sep 24, 2016 at 11:29 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/articles/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/articles/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies <diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: Hi, I was trying to watch a story I am interested in https://www.pivotaltracker.com/n/projects/892938/stories/105493826 I do have an account but it seems I don't have permissions to watch nor to comment. Is there something I missed? Regards Jan -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html
More All Messages By This Member
Guillaume Berche #5868 Hi William, Sorry for the inconvenience this may has caused. I have temporary disabled issues for the https://github.com/cf-tm-bot/garden repo, so back references should not be visible by now. This should give us time to further discuss best alternatives forward. I'll then renable issues in the garden mirror repo once we have found and potentially implemented a satisfactory solution. Indeed github by default automatically and implicitly maintains cross references of issues (little doc about this, quickly mentionned in https://guides.github.com/features/issues/#notifications) In our attempt to reduce undesirable side effects from mirroring (see https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues/1 ) I had originally considered redacting urls to other github issues to prevent implicit GH cross references from triggering. I had decided to leave GH issues urls unredacted as to enable discovery of mirrors from cloudfoundry submitted issues. We could consider to only limit this implicit white cross-refenreces to a set of github repos/orgs (such as cloudfoundry-* ) and redact references to issues in all other orgs (e.g. docker). What about proceeding the conversation on https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues/1 which has some more background and rationales for this initial decision ? Thanks for your understanding, Guillaume. toggle quoted message Show quoted text On Thu, Oct 13, 2016 at 9:35 PM, William Martin <wmartin(a)pivotal.io> wrote: Hi Guillaume, Sorry for chiming in late about this, we in the Garden team were a little surprised by one of the emergent properties of the tracker/github mirroring. When we include link to a GitHub issue in Tracker and you mirror, it seems something (possibly GitHub default behaviour) is updating the referenced issue, stating that WE have referenced it. This was pretty surprising behaviour to us and although we are very happy for people to read our backlog there's a disconnect between having something visible and modifying others' issues. In particular, when we discovered this behaviour, we had been referencing issues as part of ongoing investigations and later decided they were unrelated, which is essentially spamming and confusing for others. See the bottom of this issue for an example: https://github.com/ docker/docker/issues/22633 We're not sure if there are any other concerning emergent properties for us but we would strongly prefer the above didn't happen. Thanks! Will On Sat, Sep 24, 2016 at 11:29 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, The mirroring of foundation projects is around 60% complete. See [5] for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so far. I'll proceed with mirroring the remaining projects in the next days/weeks. There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see [3]. Let me know if you have interests in discussing these next steps and current challenges faced by the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest. Thanks, Guillaume. Guillaume. On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche <bercheg(a)gmail.com> wrote: Hi, We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at [1], and the experimental mirror of the buildpack tracker at [2]. I'd like to thanks the buildpacks team for accepting to join this experiment and providing us with feedback in the past few weeks. We hope this could bring the following benefits to the CF community: 1. allow use of the watching notifications <https://help.github.com/articles/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest. 2. allow use of github search features <https://help.github.com/articles/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code) 3. allow use of github @mentions <https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story 4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far [3]?) Do you have suggestions for enhancements: can you comment/vote/improve in [3]? Our plan is to progressively extend this experiment to more trackers listed in [5] (in a rate of a few projects per week). Please report issues on [3] if you observe negative side effects, or reply to this email if you have concerns about this mirroring. There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-) Thanks, Guillaume. ps: I also recently noticed a PT slack integration [4] that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel. [1] https://github.com/orange-cloudfoundry/pivotaltrackermirror [2] https://github.com/cf-tm-bot/buildpacks [3] https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues [4] https://cloudfoundry.slack.com/apps/A0F82E7H8-pivotal-tracker [5] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki Guillaume. On Sun, May 29, 2016 at 8:05 PM, John Wong <gokoproject(a)gmail.com> wrote: Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added. This at least allow a read-only mirror. Just a thought... On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote: Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a product · I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it · The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community. After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February: · To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects. · To comment on stories, the same restrictions as above apply It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state, any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on. I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on. I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this. Warm regards Marco PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done? On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Dear all, it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it. @Chip: Is there an option you could weigh in for this from the Foundation perspective? That would be great! Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem. Warm regards Marco On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote: Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature? Thanks and warm regards Marco On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote: If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback. On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote: I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here? Thanks and warm regards Marco On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote: Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker. I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want. -Dieu On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote: Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd like to keep track of. Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list? -Matt On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies < diesk(a)fast.au.fujitsu.com> wrote: Hi Marco, Jan, I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that. I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized. Will let you know if I get a reply. Regards, Dies Koper Cloud Foundry CLI PM -----Original Message----- From: Voelz, Marco [mailto:marco.voelz(a)sap.com] Sent: Monday, November 23, 2015 8:00 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: FW: issue tracker permissions Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on? Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features. Warm regards Marco On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote: Hi, I was trying to watch a story I am interested in https://www.pivotaltracker.com/n/projects/892938/stories/105493826 I do have an account but it seems I don't have permissions to watch nor to comment. Is there something I missed? Regards Jan -- Sent from Jeff Dean's printf() mobile console attachment.html attachment.html
More All Messages By This Member

1 - 12 of 12

Previous Topic Next Topic

Home Hashtags Subgroups Terms