Closed Phanatic closed 7 years ago
Hi,
Thanks for your interest in continuing to work on other Pivotal Tracker items for CF Eclipse.
At the moment we use github issues for individuals that are external to our core development team to raise issues.
In terms of workflow, for external issues raised in github, after we review the github issues, we then create Pivotal Tracker items that we then assign to developers. Unfortunately there is no way to directly join the CF Eclipse public Pivotal Tracker project at the moment.
However, feel free to start working on:
https://www.pivotaltracker.com/n/projects/1027166/stories/60123062
We'll make sure nobody else is working on this item.
I'll also look into adding you as a member of the CF Eclipse Pivotal Tracker, so that we can assign this and future items directly to you. I'll let you know when I do, but it shouldn't be a problem to add you as a member of the Pivotal Tracker CF Eclipse project.
For others that are interested in joining as members of Pivotal Tracker after they have signed the CLA agreement and want to work on tracker items and submit requests, for the time being the best way is to post a request to join the Pivotal Tracker at:
https://groups.google.com/a/cloudfoundry.org/forum/#!forum/cf-eclipse
And we'll follow up with further instructions.
This is only until we have a better system in place.
@Phanatic You don't need to post in the forum to join the tracker. I'll contact you directly.
Thanks.
Hi folks, I'd like to understand how I can communicate that I'm fixing issues that are filed in the Pivotal tracker. For example, I'm working on a fix for this issue Add operation buttons to Env Variables wizard page., and before I send out the PR, I'd like to communicate that I'm working on this issue and maybe get the issue assigned to me in the Pivotal tracker. Am looking for the workflow of working between the tracker and github issues.