[p2pu-dev] Integrated Lighthouse with pivotal tracker
Joe Corneli
holtzermann17 at gmail.com
Tue Mar 1 20:52:27 UTC 2011
My only care in all of this is that I think issues should be managed
in a non-opaque way and that they are linked to a somewhat clear
roadmap. I have zero preference about "how" that happens. If someone
else can drive this process better or further using a different tool,
please do that. I can't take it further myself anyway, until there is
more input from people who know and understand the background issues.
On Tue, Mar 1, 2011 at 7:06 PM, Philipp Schmidt <phi.schmidt at gmail.com> wrote:
> Can I suggest we retire the Community PT in favor of lighthouse? PT is great for
> software development but not intuitive for other people and tasks.
> Lighthouse is better at that and allows contributions from anyone (as
> oppose to PT). Would you be ok with that Joe? P
>
> On Tuesday, 1 March 2011, Joe Corneli <holtzermann17 at gmail.com> wrote:
>>> Lighthouse will be used not
>>> only for dev-related things (http://p2pu.lighthouseapp.com/dashboard)
>>> so there is also a Community and Org projects.
>>
>> If this can be simultaneously hooked into the "P2PU" (community, org)
>> tracker on Pivotal that I set up, that would be nice.
>>
>> https://www.pivotaltracker.com/projects/230399
>>
>> (Zuzel you'll likely want to join that, anyway...)
>> _______________________________________________
>> p2pu-dev mailing list
>> p2pu-dev at lists.p2pu.org
>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>
More information about the p2pu-dev
mailing list