Re: ballot system back on

["Michael S. Tsirkin" <mst@redhat.com>]

On Fri, Jun 07, 2024 at 03:43:30AM +0000, Parav Pandit wrote:
> 
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Friday, June 7, 2024 1:26 AM
> > 
> > On Thu, Jun 06, 2024 at 06:51:24PM +0200, Cornelia Huck wrote:
> > > On Thu, Jun 06 2024, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > >
> > > > So, things seem to be working, even if they are now a bit harder to
> > > > set up.
> > > > Let's start wrapping up 1.3?
> > > > I think we need to pack up and then do a ballot to ask OASIS to get
> > > > a special majority vote for us.
> > > >
> > > > Right? Cornelia, want to start that?
> > >
> > > I've now created a ballot to request a special majority vote; please
> > > double-check whether I got the incantations right.
> > >
> > > And because all that work is not really visible: Thank you for getting
> > > those ballot scripts working with the new platform! This looks really
> > > painful and time consuming...
> > 
> > Yes it was!
> > But in two months we did not get API access so reverse engineering it is.
> > What made it hard was that the new system does so much in javascript. Both
> > the login system (it's a single site why does it need
> > SAML?) and the ballot form itself (lots of asychronous stuff, animations, even
> > a simple checkbox is hidden and implemented from scratch in javascript
> > because reasons). So I could not just use selenium APIs (wasted a ton of time
> > trying to figure out why). I started trying to emulate keypresses and mouse
> > clicks but that proved too hard to get right. In the end I hit on the approach
> > of injecting javascript into page to interact with the hidden form elements.
> > Thanks,
> > 
> Thanks a lot Michael for the heavy lifting to get this operational.
> At least I didn't realize why the voting system needs such additional work specially when its upgraded.
> Is it for the github integration?

Exactly.

-- 
MST