[DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

John D. Ament-2
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
start to track other things in whimsy, which mirrors what's in the status
file.  This can include IP Clearance/SGAs, Podling Name Searches, the
various dates we track.

Ultimately, I want to simplify how podlings are managed and make it a bit
easier on an end user.  Rather than needing to svn checkout to get files,
they simply go to a webpage, and assuming they're on that podling's roster
they would have access to update the status.  We could even automate
certain events so that when the board passes a resolution to graduate the
podling, the status file is updated along side any other record the podling
may have.

This does mean that the status file format is likely to change.  It also
means we're likely to move away from the java based build tool that has to
parse the XML templates into web pages and instead rely on a more
structured format for the status.

It doesn't mean you have to change.  If you like using SVN to edit this
stuff that's fine, you would still be able to.  Just what you're editing is
likely to be different.

Thoughts? Opinions?

John
Reply | Threaded
Open this post in threaded view
|

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

Chris Mattmann-4
+1 from me.

Cheers,
Chris


On 6/4/17, 4:33 PM, "John D. Ament" <[hidden email]> 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 improve upon is the overall experience around
    managing the podling.  Sam's done a great job with rosters, but we can
    start to track other things in whimsy, which mirrors what's in the status
    file.  This can include IP Clearance/SGAs, Podling Name Searches, the
    various dates we track.
   
    Ultimately, I want to simplify how podlings are managed and make it a bit
    easier on an end user.  Rather than needing to svn checkout to get files,
    they simply go to a webpage, and assuming they're on that podling's roster
    they would have access to update the status.  We could even automate
    certain events so that when the board passes a resolution to graduate the
    podling, the status file is updated along side any other record the podling
    may have.
   
    This does mean that the status file format is likely to change.  It also
    means we're likely to move away from the java based build tool that has to
    parse the XML templates into web pages and instead rely on a more
    structured format for the status.
   
    It doesn't mean you have to change.  If you like using SVN to edit this
    stuff that's fine, you would still be able to.  Just what you're editing is
    likely to be different.
   
    Thoughts? Opinions?
   
    John
   



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

Jim Jagielski
In reply to this post by John D. Ament-2
+1

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

Julian Hyde-3
In reply to this post by John D. Ament-2
+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 present the other option(s) at all. When my project was going through incubation I was forever worried about stepping on some infrastructure landmine and as a result did nothing for several months.

Julian


> On Jun 4, 2017, at 7:33 PM, John D. Ament <[hidden email]> 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 improve upon is the overall experience around
> managing the podling.  Sam's done a great job with rosters, but we can
> start to track other things in whimsy, which mirrors what's in the status
> file.  This can include IP Clearance/SGAs, Podling Name Searches, the
> various dates we track.
>
> Ultimately, I want to simplify how podlings are managed and make it a bit
> easier on an end user.  Rather than needing to svn checkout to get files,
> they simply go to a webpage, and assuming they're on that podling's roster
> they would have access to update the status.  We could even automate
> certain events so that when the board passes a resolution to graduate the
> podling, the status file is updated along side any other record the podling
> may have.
>
> This does mean that the status file format is likely to change.  It also
> means we're likely to move away from the java based build tool that has to
> parse the XML templates into web pages and instead rely on a more
> structured format for the status.
>
> It doesn't mean you have to change.  If you like using SVN to edit this
> stuff that's fine, you would still be able to.  Just what you're editing is
> likely to be different.
>
> Thoughts? Opinions?
>
> John


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

Felix Meschberger-4
+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 <[hidden email]>:
>
> +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 present the other option(s) at all. When my project was going through incubation I was forever worried about stepping on some infrastructure landmine and as a result did nothing for several months.
>
> Julian
>
>
>> On Jun 4, 2017, at 7:33 PM, John D. Ament <[hidden email]> 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 improve upon is the overall experience around
>> managing the podling.  Sam's done a great job with rosters, but we can
>> start to track other things in whimsy, which mirrors what's in the status
>> file.  This can include IP Clearance/SGAs, Podling Name Searches, the
>> various dates we track.
>>
>> Ultimately, I want to simplify how podlings are managed and make it a bit
>> easier on an end user.  Rather than needing to svn checkout to get files,
>> they simply go to a webpage, and assuming they're on that podling's roster
>> they would have access to update the status.  We could even automate
>> certain events so that when the board passes a resolution to graduate the
>> podling, the status file is updated along side any other record the podling
>> may have.
>>
>> This does mean that the status file format is likely to change.  It also
>> means we're likely to move away from the java based build tool that has to
>> parse the XML templates into web pages and instead rely on a more
>> structured format for the status.
>>
>> It doesn't mean you have to change.  If you like using SVN to edit this
>> stuff that's fine, you would still be able to.  Just what you're editing is
>> likely to be different.
>>
>> Thoughts? Opinions?
>>
>> John
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

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

Pierre Smits
+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 <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, Jun 6, 2017 at 10:33 AM, Felix Meschberger <
[hidden email]> wrote:

> +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 <[hidden email]>:
> >
> > +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 present the other option(s) at all. When my
> project was going through incubation I was forever worried about stepping
> on some infrastructure landmine and as a result did nothing for several
> months.
> >
> > Julian
> >
> >
> >> On Jun 4, 2017, at 7:33 PM, John D. Ament <[hidden email]>
> 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 improve upon is the overall experience around
> >> managing the podling.  Sam's done a great job with rosters, but we can
> >> start to track other things in whimsy, which mirrors what's in the
> status
> >> file.  This can include IP Clearance/SGAs, Podling Name Searches, the
> >> various dates we track.
> >>
> >> Ultimately, I want to simplify how podlings are managed and make it a
> bit
> >> easier on an end user.  Rather than needing to svn checkout to get
> files,
> >> they simply go to a webpage, and assuming they're on that podling's
> roster
> >> they would have access to update the status.  We could even automate
> >> certain events so that when the board passes a resolution to graduate
> the
> >> podling, the status file is updated along side any other record the
> podling
> >> may have.
> >>
> >> This does mean that the status file format is likely to change.  It also
> >> means we're likely to move away from the java based build tool that has
> to
> >> parse the XML templates into web pages and instead rely on a more
> >> structured format for the status.
> >>
> >> It doesn't mean you have to change.  If you like using SVN to edit this
> >> stuff that's fine, you would still be able to.  Just what you're
> editing is
> >> likely to be different.
> >>
> >> Thoughts? Opinions?
> >>
> >> John
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>