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/22633We'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
|
