If ASANA was public, I'd vote for that over PT.<div><br></div><div>+1 for Lighthouseapp.</div><div><br></div><div><br><div class="gmail_quote">On Tue, Mar 1, 2011 at 3:52 PM, Joe Corneli <span dir="ltr"><<a href="mailto:holtzermann17@gmail.com">holtzermann17@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">My only care in all of this is that I think issues should be managed<br>
in a non-opaque way and that they are linked to a somewhat clear<br>
roadmap. I have zero preference about "how" that happens. If someone<br>
else can drive this process better or further using a different tool,<br>
please do that. I can't take it further myself anyway, until there is<br>
more input from people who know and understand the background issues.<br>
<div class="im"><br>
On Tue, Mar 1, 2011 at 7:06 PM, Philipp Schmidt <<a href="mailto:phi.schmidt@gmail.com">phi.schmidt@gmail.com</a>> wrote:<br>
</div><div><div></div><div class="h5">> Can I suggest we retire the Community PT in favor of lighthouse? PT is great for<br>
> software development but not intuitive for other people and tasks.<br>
> Lighthouse is better at that and allows contributions from anyone (as<br>
> oppose to PT). Would you be ok with that Joe? P<br>
><br>
> On Tuesday, 1 March 2011, Joe Corneli <<a href="mailto:holtzermann17@gmail.com">holtzermann17@gmail.com</a>> wrote:<br>
>>> Lighthouse will be used not<br>
>>> only for dev-related things (<a href="http://p2pu.lighthouseapp.com/dashboard" target="_blank">http://p2pu.lighthouseapp.com/dashboard</a>)<br>
>>> so there is also a Community and Org projects.<br>
>><br>
>> If this can be simultaneously hooked into the "P2PU" (community, org)<br>
>> tracker on Pivotal that I set up, that would be nice.<br>
>><br>
>> <a href="https://www.pivotaltracker.com/projects/230399" target="_blank">https://www.pivotaltracker.com/projects/230399</a><br>
>><br>
>> (Zuzel you'll likely want to join that, anyway...)<br>
>> _______________________________________________<br>
>> p2pu-dev mailing list<br>
>> <a href="mailto:p2pu-dev@lists.p2pu.org">p2pu-dev@lists.p2pu.org</a><br>
>> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
>><br>
> _______________________________________________<br>
> p2pu-dev mailing list<br>
> <a href="mailto:p2pu-dev@lists.p2pu.org">p2pu-dev@lists.p2pu.org</a><br>
> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
><br>
_______________________________________________<br>
p2pu-dev mailing list<br>
<a href="mailto:p2pu-dev@lists.p2pu.org">p2pu-dev@lists.p2pu.org</a><br>
<a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://about.me/ebaako" target="_blank">http://about.me/ebaako</a><br>
</div>