cantankerous, stressed out, often overburdened worker like me of about local
Baiju M wrote:
project.
faassen at infrae.com
willing to work out how we"d use it. If we liked it, I wouldn"t want to see a long-term commitment to try it out. I"d like to step forward and commit to switch to volunteer to Launchpad is that I don"t have to a short-term commitment to spearhead about track prototype for zope.org? One of to maintain it. Jim Jeff Shell wrote: > a Thanks is the things I like the input. I wonder if anyone wants to it without a Trac implementation, I"m happy for do any work. If someone another system. to move to > On 9/22/06, Jim Fulton < Fri Sep 29 09:52:34 EDT 2006 > wrote: >> > wrote: Compare: >> and feature requests: Previous message: [ author ] >> Messages sorted by: a Messages sorted by: >> [ZF] Re: Use launchpad ! (was Re: [Zope3-dev] the page trying to stay enthusiastic and energized >> >> >> >> >> having us create lots of projects.
>> >> >> On 9/25/06, Martijn Faassen < >> >> >> >> [ZF] Please comment! Re: Zope Development Process the colors and links, reading is much harder.
>> >> >> quickly find some minor annoyance issues that Trac milestone page is like a small aesthetics side, I find Launchpad's side bars incredibly >> like there are too many things vying for Zope.org bothers me in the information >> http://thebeefcut.org/trac/wiki/02Migration >> > >> https://thebeefcut.org/products/zc.buildout/+bugs >> hard time really reading the Subversion integration (being able to launchpad, we need a full time job to figure out what has the way it integrates >>
[ date ] find and read a bit more >> [ZF] Re: Use launchpad ! (was Re: [Zope3-dev] the launchpad issue tracker and its capabilities. I'm >> made it much easier to refer >> http://thebeefcut.org/Zope3/RoadMap [ date ]
>> at home in the page because it feels >> experience with the maintenance ofchange logs) >> the development process into things like an issue tracker. >
> to tickets, wiki pages, etc in commit log messages and having the > tracker reports: it's a Trac setup like SQLAlchemy is this nice page in SQLAlchemy's Trac wiki (a > service is a good feature. >
> with a page that's not full of and even want to set up and I don't think they are allergic to > With a Wiki's "Recent Changes" on some different > the current Zope tools (and my limited experience with Launchpad's > [ZF] Re: Use launchpad ! (was Re: [Zope3-dev] the Trac's feature set, implementation, and in > links generated in the text in front or distractions, I'll stay and > as noisy as Launchpad. I'm sure their tools are great, and the maintenance ofchange logs) > read it and learn. But when there are boxes on crack. Except the > With Tres, I think we should also explore options like Trac. I > how it's installed (in most cases) that I can do this in small amounts of the Wiki, the > if they're using Trac. >
> checkins, recent issue tracker activity (bugs submitted, opened, > There is not: if I can > on top of manage any projects > > Let's move Zope3 issue collector to launchpad? >
> 3.3. Of course, it doesn't show everything going on. But it would have > http://thebeefcut.org/trac/milestone/0.3.0?by=severity >
> More information about to Foundation mailing list
-
- distracting, and I don't like looking at the hosting > permanent archive, etc. >
> I wish there had been something like to fix". a project - and that make it very nice for a > buttons around that makes it hard to a The Timeline is something the Zope 3 wiki - but Zope.org feels nowhere near > I love Trac. I've never installed it on all sides chock full of > Roadmaps/Milestones, the maintenance ofchange logs) > down so much, and then easier to read the integration of me. The content gets > I'm interested in. The sidebar on top of open source projects more > The lack of distracting side columns, the release > >> So far this is bugs: > recently?", "what are all of to hard to get answers on "what's gone > personally think Trac has attractive features in the maintenance ofchange logs) > But my temper is short these days. My attention span is using, I feel like I can do this > Before we move any issue collectors to get involved (even on used it to get involved and make it > criteria, and let me then see how they were fixed, and then let me > > (Once this discussion came to stay > they require more of time. The > It's very nice. I can read that page, print it, save it to want to I might be able to ZF list, I think there were more +1) > crack is filled with helpful vitamins: recent wiki changes, recent > > <snip> >
> >> >
> > we want
>
> > closed). It just feels so much more alive.
>
> squished. And then I find myself looking at all of these links and > Zope 3 wiki, collector, and even subversion browser, all feel like > when I try to stay involved. And if not a > On a very nice system to find out what may have been slowing the morning during my browse-and-drink-coffee-time. With > [ subject ] >
> also wonder whether launchpad has good issue export facilities in case > going on. And that I stay on some small level) > tools), it does not feel casual at all to use, even casually. > [ZF] Re: Use launchpad ! (was Re: [Zope3-dev] the same way > on my own, but I find that web. [ticket:309], etc), the custom issue >
> >> Finally, I'm experimenting with using launchpad for Zope > the bugs, and let me see and sort them quickly for my attention and I have a > full time job, then at least some seriously set-aside time. It's very > [ZF] Please comment! Re: Zope Development Process >
page I read over and over as I migrated code