Re: [DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

+1 from me. Self-service is always a good solution. But then... It already was like that regarding various aspects of managing an incubating project. Just more cumbersome. And more out of sync with the processes and procedures for graduated projects. Best regards, Pierre Smits ORRTIZ.COM

Re: [DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

+1 Particularly as these are not day-to-day but every-now-and-then tasks .. Regards Felix > Am 05.06.2017 um 17:32 schrieb Julian Hyde : > > +1 > > It moves us towards a self-service (dare I say “github-like”) experience for > podlings, and that is always good. > >

Re: [DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

+1 It moves us towards a self-service (dare I say “github-like”) experience for podlings, and that is always good. Furthermore, if there are choices to be made (e.g. svnpubsub vs. CMS) I think the tooling should strongly encourage them to take the “standard” option. Maybe it doesn’t even

Re: [DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

+1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

+1 from me. Cheers, Chris On 6/4/17, 4:33 PM, "John D. Ament" wrote: All, I want to bring up this discussion to see others opinions. I would like to move forward on migrating podling status maintenance into Whimsy. Some of the key things I want to

[DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

All, I want to bring up this discussion to see others opinions. I would like to move forward on migrating podling status maintenance into Whimsy. Some of the key things I want to improve upon is the overall experience around managing the podling. Sam's done a great job with rosters, but we can