> On Mar 22, 2015, at 1:17 PM, Daniel Gruno <[email protected]> wrote: > > > > On 2015-03-22 21:06, Alan D. Cabrera wrote: >>> On Mar 20, 2015, at 8:10 PM, Marvin Humphrey <[email protected]> wrote: >>> >>> On Fri, Mar 20, 2015 at 5:49 PM, Alan Cabrera <[email protected]> wrote: >>>> I will add that we don't necessarily have to do use the Steve code per se >>>> and it's my opinion that collecting votes for a release is pertinent for >>>> this project. >>> Yeah, I once looked at the STeVe code base contemplating how to support >>> release votes but gave up because it was too ambitious. >>> >>> I'd be willing to chip in if I don't have to go it alone. >>> >>>>> On Mar 20, 2015, at 5:26 PM, Daniel Gruno <[email protected]> wrote: >>>>>> * Hook to LDAP for binding votes. >>>>> Very tricky, as STeVe was designed to hide what people have voted, even if >>>>> you have disk access. >>> The use case here is public voting. It may be that the current STeVe code >>> is >>> simply not a suitable starting point. Or it may be that we can produce some >>> modularized Python, portions of which could be shared by both an STV secret >>> ballot and public ballot under Apache release voting rules. >> Yeah, this is my thinking as well. It’s a bit monolithic and I think that >> it’s due to how the project came about. Much of the code mixes concerns and >> so causes discussions about extensions of functionality awkward. >> >> I agree we need to make the code base more modular. I’d like to see it >> broken out into three parts: >> >> steve-base - generic base level utilities and model management - the M and C >> of MVC > > For what it's worth, I've started refactoring the web UI to use a library for > the basic vote features like fetching issues/elections and voting. > this is currently stored in cgi-bin/lib - this should probably be moved > elsewhere and fiddled with so it can turn into a fully operational library > for doing the voting/setup via command line too. > > My plan is/was that anything you can do via the REST API, you can do with > this library as well, so you can add CLI scripts for it all as well, should > that be needed. > > I realize that this still lacks the essential part, the STV calculations, but > I'm working on it! ;)
Yeah, this stuff is most awesome. I think we should move it to steve-web. I’m getting Travis CI and Coveralls setup and then we can move your stuff into steve-web. One thing I’d like to ask you is what do you think about Flask? It’s a fast, super easy, way to setup Python based websites and REST APIs. Maybe what I can do is transliterate your site into Flask so you can judge for yourself if this is the way to go. Regards, Alan
