Hi all,

Just giving you an update that viewers are now able to follow stories in
Tracker, along with some other project permission changes. Here is a blog
post <https://www.pivotaltracker.com/blog/project-permissions/> that
includes more info about the other privacy changes we've made recently.

Thanks,
Lisa

On Fri, Jan 27, 2017 at 9:19 AM, Chip Childers <cchilders(a)cloudfoundry.org

wrote:

+Chris Clark <cclark(a)cloudfoundry.org>

Ah... I think that's the key thing for us to setup.

Chris will be reaching out to you to discuss Lisa!

On Fri, Jan 27, 2017 at 11:17 AM Lisa Doan <ldoan(a)pivotal.io> wrote:

Hi Guillaume,

I forgot to mention that non-account members will be able to join Public
projects as viewers, and viewers will be able to follow.

Thanks,
Lisa

On Fri, Jan 27, 2017 at 9:10 AM, Chip Childers <
cchilders(a)cloudfoundry.org> wrote:

I'll have Chris Clark, a member of my team, track this down and report
back to everyone.

On Fri, Jan 27, 2017 at 10:38 AM Guillaume Berche <bercheg(a)gmail.com>
wrote:

Hi Lisa,

The Cf community members typically don't have an account which is member
of the Pivotal Enterprise account used by CFF tracker projects. What's the
recommended way for adding them (could be hundreds of members interested in
following stories) to the account ? Is there another alternative than
directly requesting the owner (is that Onsi ?) to invite them (hence my
suggestion about a google form to centralize invitation requests and avoid
email exchanges) ?

Thanks in advance,

Guillaume.




Guillaume.

On Thu, Jan 26, 2017 at 11:09 PM, Lisa Doan <ldoan(a)pivotal.io> wrote:

Hi Guillaume,

We introduced a new feature to Enterprise accounts late last year that
allows Project Owners to set their Project Privacy to "Shared with my
company." If a project has this setting, anyone at the organization can
search for and join the project as a viewer.

All of the Cloud Foundry projects belong to an Enterprise account, so
anyone who is a member on those accounts will be able to find and join the
projects once the Project Owner updates the privacy setting. Project Owners
will still also be able to invite users to their projects.

Thanks,
Lisa


On Thu, Jan 26, 2017 at 1:59 PM, Guillaume Berche <bercheg(a)gmail.com>
wrote:

Hi Lisa,

Thanks for sharing the progress on the "viewers can follow stories"
feature. Can you please detail whether this would still require CF
community members to request the tracker account owner to individually send
them an invite ?

If so, may be the CFF tracker account owner could set up something like
a google form to easily receive invitation requets and track their
completion ?

Thanks in advance,

Guillaume.

On Thu, Sep 29, 2016 at 10:12 PM, Guillaume Berche <bercheg(a)gmail.com>
wrote:
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.

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




Guillaume.

On Thu, Jan 5, 2017 at 11:40 PM, Lisa Doan <ldoan(a)pivotal.io> wrote:

Hello all,

Hope your new year has gotten off to a good start! Just wanted to give
you an update that the feature set to let Viewers follow stories is in
progress.

Thanks,
Lisa

On Thu, Dec 1, 2016 at 12:55 AM, Voelz, Marco <marco.voelz(a)sap.com>
wrote:

Dear Lisa,



Thanks for the update. Further delays are quite unfortunate, and my
trust in that this feature will ever see the light of day is really low. As
we're celebrating now the 1 year anniversary of this feature request, I
took the liberty to mirror my backlog to trello:
https://trello.com/b/ZLikX21o/bosh-openstack-cpi



For now, this was more a proof-of-concept that it is feasible to
transfer everything in an automated way. Next year, I'll be starting to
actually work from there instead of tracker.



In case other people are interested in how to migrate: I created a fork
of the pivotal-to-trello exporter, which can deal with labels as well
https://github.com/voelzmo/pivotal-to-trello



Warm regards

Marco



*From: *Lisa Doan <ldoan(a)pivotal.io>
*Date: *Wednesday, 30 November 2016 at 18:03

*To: *"Voelz, Marco" <marco.voelz(a)sap.com>
*Cc: *Guillaume Berche <bercheg(a)gmail.com>, "Discussions about Cloud
Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org>,
Dan Podsedly <dpodsedly(a)pivotal.io>, Chip Childers <
cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" <cholick(a)gmail.com>
*Subject: *Re: [cf-dev] Re: FW: issue tracker permissions



Hi Marco -- there is a chance we can start this by the end of the year.
It has taken us a little while longer than expected to complete the
features that were ahead of it, but they should be releasing in the next
few weeks, and we then can start to focus on Viewers being able to follow.
Due to the holidays and other year-end distractions, we probably won't
complete the entire feature set by end of year. But it is still very high
on our priority list as we know it is important to you and many of our
customers. My apologies for the delay.



Thanks,

Lisa



On Wed, Nov 30, 2016 at 6:54 AM, Voelz, Marco <marco.voelz(a)sap.com>
wrote:

Dear Lisa,



How is the "viewers can follow stories" feature coming along? Today is
the last day of November, I haven't seen it in Tracker's release notes or
received any update from your side since the two mails below. Any chance
that we get that feature by the end of the year?



Warm regards

Marco



*From: *Lisa Doan <ldoan(a)pivotal.io>
*Date: *Monday, 26 September 2016 at 18:26
*To: *"Voelz, Marco" <marco.voelz(a)sap.com>
*Cc: *Guillaume Berche <bercheg(a)gmail.com>, "Discussions about Cloud
Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org>,
Dan Podsedly <dpodsedly(a)pivotal.io>, Chip Childers <
cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" <cholick(a)gmail.com>


*Subject: *Re: [cf-dev] Re: FW: issue tracker permissions



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.


...