[gentoo-soc] Council web app - introduction

[gentoo-soc] Council web app - introduction

[Joachim Filip Bartosik]

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

(Note: this is c&p from my blog [0])

I’m working on application for Gentoo Council[1] this year. You can see
current code in repository on GitHub[2], you can expect frequent non
fast forward changes there. You can find reviewed code in repository on
overlays.gentoo.org[3]. All changes in the repository on
overlays.gentoo.org will be fast forwardable.

Like my GSoC project in 2010[4] the main part of this will be a
hobo[5]-based ruby on rails[6] web application. I’m using hobo-devise[7]
gem to manage authentication, to provide LDAP integration. I want to
expand MeetBot[8] to provide IRC bot that will help to manage Council
meetings on IRC.

[0]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/
[1] http://www.gentoo.org/proj/en/council/
[2] https://github.com/ahenobarbi/Gentoo-Council
[3]
http://git.overlays.gentoo.org/gitweb/?p=proj/council-webapp.git;a=summary
[4]
http://ahenobarbi.wordpress.com/2010/05/25/weekly-report-1-after-first-week-of-work/
[5] http://rubygems.org/gems/hobo
[6] http://rubyonrails.org/
[7] http://rubygems.org/gems/hobo_devise
[8] http://wiki.debian.org/MeetBot


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

[gentoo-soc] Re: Council web app - introduction

[Joachim Filip Bartosik]

[-- Attachment #1: Type: text/plain, Size: 2919 bytes --]

(Note: this is c&p from my blog [0])

I’m going to finish work early (first week of August) so I started
working three weeks ago.

Some functionality is ready:

    Anyone can view agendas
        Agenda has state:
            Open – council members and administrators can edit it.
            Closed for submissions – when meeting is close and no one
should change agenda.
            Meeting ongoing – currently unused.
            Old – old agendas, no one can change them.
        There is always exactly one agenda in state different then “old”
(that is in open, closed for submissions or meeting ongoing state).  cal
this agenda “current agenda”.
        There is list of agenda items
            Every item has fields for title, description, and discussion(s).
            Any registered user can create a new item. Initially item is
not assigned to agenda. There is listing of all unassigned (suggested)
agenda items.
            Council members can add it to current agenda. Items added to
agenda don’t appear any more on the suggested agenda items list. They
appear as agenda items for a specific agenda.
            Council members can reject it. Rejected items don’t appear
on suggested agenda items list.
        For every agenda item there is voting options list.
    Anyone can register
    Registered user can be marked as administrator
    Registered user can be marked as council member
    I started work on the IRC bot
        When someone says #startmeeting (in addition to everything
MeetBot usually does) it obtains two JSON files containing:
            Array of nicks allowed to vote on the meeting
            Array of agenda items. Each agenda item is array. First item
of that array is title of agenda item. Second item is array with voting
options for agenda item.
            This looks a more complicated then it really is, so here is
an example: suppose current  has two two items: ‘What I will eat for
diner’ and ‘Should I walk the dog before or after dinner’. Voting
options for the first one are ‘Pizza’, ‘Sandwiches’ and ‘Nothing’.
Choices for the second one are ‘Yes’ and ‘No’. This results in an array:

            [["What I will eat for diner", ["Pizza", "Sandwiches",
"Nothing"]], ["Should I walk the dog before or after dinner", ["Yes",
"No"]]]
        Other commands I added are: #nextitem, #previtem (to change
currently discussed item), #startvote, #endvote, #vote(to vote).
        When someone issues #endmeeting command bot posts voting results
(JSON with hash mapping agenda item title to hash mapping nick to voting
choice).

For short description of project and sources, read this[1].

[0]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-weekly-report-1/
[1]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

[gentoo-soc] Council web app - weekly report #2

[Joachim Filip Bartosik]

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

(Note: this is c&p from my blog [0])

Last week I:

        Fixed some bugs
        Added support for proxies:
            each council member can appoint one proxy per meeting
            proxy must not be a council member
            council member who appointed proxy will not be listed as
‘voter’ (for IRC bot)
            appointed proxy will be listed as voter
        Nearly finished work on bot
            It obtains list of users allowed to vote from application
            It obtains list of agenda items (with voting options for
each item)
            It helps to manage meeting (you can use #nextitem and
#previtem commands)
            It manages voting (#startvote, #endvote)
        Application can send email reminders about meetings.

For short description of project and sources, read this[1].

[0]
http://ahenobarbi.wordpress.com/2011/06/07/council-application-%E2%80%93-weekly-report-2/
[1]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

[gentoo-soc] Re: Council web app - weekly report #3

[Joachim Filip Bartosik]

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

(Note: this is c&p from my blog [0])
Last week I:

    Wrote Supybot[1] plugin that regularly fetches JSON data from given
location. Then it checks timestamp, if timestam is newer then previous
it sends message to listed users.
    Application now tracks slaking properly - it marks participation
after meeting (council members who voted at least once are present).
Then it calculates "slacking status" for current council members based
on council term start date and participations.

For short description of project and sources, read this[2].

[0]
http://ahenobarbi.wordpress.com/2011/06/13/council-application-%E2%80%93-weekly-report-3/
[1] http://sourceforge.net/projects/supybot/
[2]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

Re: [gentoo-soc] Re: Council web app - weekly report #3

[Rich Freeman]

On Mon, Jun 13, 2011 at 4:46 AM, Joachim Filip Bartosik
<jbartosik@gmail.com> wrote:
>    Application now tracks slaking properly - it marks participation
> after meeting (council members who voted at least once are present).
> Then it calculates "slacking status" for current council members based
> on council term start date and participations.

Honestly, I've seen this kind of thing tried so many times and fail in
so many situations that I have to say that I think this isn't the
right way to go about this.

Why not let somebody in the Council just mark off attendance?
Sometimes automation isn't the best solution.  What if somebody was
present but there was only one vote and they didn't vote, or whatever?
 I could see some value in the thing helping to facilitate taking
attendance (looking at who talked during the meeting and suggesting
that to the attendance-taker for confirmation).  In the end, however,
deciding whether somebody slacked shouldn't be based on an algorithm -
if it fails for whatever reason then suddenly we're back to just doing
it manually 100%.

I'm a big fan of KISS for these sorts of things.  The 95% solution is
a lot better than the 99.9999% solution that is worth 10% when it gets
something wrong trying too hard to get it all right.

Rich

[gentoo-soc] Council web app - weekly report #4

[Joachim Filip Bartosik]

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]

(Note: this is c&p from my blog [0])

Last week I used metrical[1] on the web app and improved tests coverage
and variable naming. I also removed some stuff it reported as “code
duplication”. Metrical warned about some stuff, but I couldn’t find a
reasonable way to fix it.

I tried to switch to capybara-webkit[2] for cucumber tests but I
couldn’t find a way to remove session cookies (and I need it to test
“Remember me” feature) so I made a feature request[3] (including a
suggested patch) and I’m waiting.

I added
#option add
#option remove
#option list

commands to MeetBot[4] to allow changing voting options during meeting
(I must do some work on the webapp end to handle added and removed
option properly).

I also improved tests for my changes to MeetBot[4] and wrote test for
Reminder (the Supybot[5]  plugin I wrote last week[6]).

[0]
http://ahenobarbi.wordpress.com/2011/06/20/council-application-%E2%80%93-weekly-report-4/
[1] http://rubydoc.info/gems/metrical/0.0.5/frames
[2] http://rubygems.org/gems/capybara-webkit
[3] https://github.com/thoughtbot/capybara-webkit/issues/79
[4] http://wiki.debian.org/MeetBot
[5] http://sourceforge.net/projects/supybot/
[6]
http://ahenobarbi.wordpress.com/2011/06/13/council-application-%E2%80%93-weekly-report-3/



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

[gentoo-soc] Council application – weekly report #5

[Joachim Filip Bartosik]

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]


(Note: this is c&p from my blog [0])

Last week I worked to improve MeetBot:

    I added support for #changeitemcommand – it allows you to move
through agenda items faster then #netxitem/ #previtem.
    Bot will close voting after last vote
    Bot can  send reminders. You can add reminder with

    #timelimit add :

    remove it with

    #timelimt remove message

    list set reminders with

    #timelimit list

    or set them in web application before meeting. Changing item removes
all reminders.

For short description of project and sources, read this[1].

[0]
http://ahenobarbi.wordpress.com/2011/06/28/council-application-%E2%80%93-weekly-report-5/
[1]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

[gentoo-soc] Council application – weekly report #6

[Joachim Bartosik]

W dniu 05.07.2011 12:40, Joachim Filip Bartosik pisze:
> (Note: this is c&p from my blog [0])
> 
> Last week I was working mostly on the website part of my project:
> 
>  * I fixed some bugs:
>   * If for some reason there was no current agenda(for example it was
>     removed when application was running) the application crashed. Now
>     whenever it tries to access current agenda application will check
>     if there is a current agenda. If there is no current agenda it will
>     create one.
>   * When council didn’t have any meetings yet.
>   * Some buttons were in weird places, now they are where they look
>     nice.
>   * Now all users will be able to vote using the webapp. Those votes
>     are just to let council know what community thinks.
>   * Now it’s possible to use markdown [1] when describing ideas.
> 
> Also bot will give meeting log to agenda and it will store it for later use.
> 
> For short description of project and sources, read this[2].
> 
> [0]
> http://ahenobarbi.wordpress.com/2011/07/05/council-application-%E2%80%93-weekly-report-6/
> [1] http://daringfireball.net/projects/markdown/
> [2]
> http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/
> 

[gentoo-soc] Council application – weekly report #7

[Joachim Bartosik]

W dniu 12.07.2011 16:00, Joachim Filip Bartosik pisze:
> (Note: this is c&p from my blog [0])
> 
> Last week I continued work on hobo-based application:
> 
> * If you enter url to message on gentoo-archives[1] as “discussion” for
> agenda item application will use it to calculate how long discussion took.
> * I worked to use Doodle[2] to help planning meetings. Doodle REST
> API[3] is pretty easy (my code words with doodle-test ) but I didn’t
> manage to finish authentication. Authentication is oauth-based[4] but I
> couldn’t authenticate with oauth(2)[5,6] gems.
> 
> I made some changes to hobo[7]. In the application I’m writing I had to set
> :null => false
> for most fields, my patch adds configuration option
> null_false_by_default. If you turn it on all text, string and boolean
> fields in all models will have
> 
> :null => false
> 
> set by default.
> 
> For short description of project and sources, read this[8].
> 
> [0]
> http://ahenobarbi.wordpress.com/2011/07/12/council-application-%E2%80%93-weekly-report-7/
> [1] http://archives.gentoo.org/
> [2] http://doodle.com/
> [3] http://doodle.com/about/APIs.html
> [4] http://oauth.net/
> [5] http://rubygems.org/gems/oauth
> [6] http://rubygems.org/gems/oauth2
> [7] http://hobocentral.net/
> [8]
> http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/
> 

Re: [gentoo-soc] Council application – weekly report #7

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]

On 17:27 Fri 15 Jul     , Joachim Bartosik wrote:
> > * If you enter url to message on gentoo-archives[1] as “discussion” 
> > for agenda item application will use it to calculate how long 
> > discussion took.

There are some enhancements to this that could make it even more useful, 
which would be great if time permits later on:

- Number of posts in the thread
- Tracking council members who did and didn't participate
- Number of posts from each participant in the thread

-- 
Thanks,
Donnie

Donnie Berkholz
Admin, Summer of Code
Gentoo Linux and X.Org
Blog: http://dberkholz.com


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-soc] Council application – weekly report #8

[Joachim Bartosik]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(Note: this is c&p from my blog [0])

Last week I:

 * Opened bug[1] asking for deployment to Gentoo infrastructure.
 * Worked to push some changes I made to packages maintained by someone
   else (capybara-webkit[2], MeetBot[3], Hobo[4]).
 * Fixed some code that produced warnings

For short description of project and sources, read this[5].

[0]
http://ahenobarbi.wordpress.com/2011/07/19/council-application-%E2%80%93-weekly-report-7-2/
[1]
http://ahenobarbi.wordpress.com/2011/07/19/council-application-%E2%80%93-weekly-report-7-2/
[2] https://github.com/thoughtbot/capybara-webkit
[3] http://wiki.debian.org/MeetBot
[4] http://hobocentral.net/
[5]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOJXMrAAoJEI0yxgiYdAogNfQQAJpisuEnPWQmnrUIqBZtecGg
mpMqA9OxyqZvU79j2/pEq+DGAFL4XgGMbfzM4+DGqFtIuTf5KiRGqyuHY5AdCUVD
CioN8Q2fQoGMSE2JeeSeZuYldpQ8lgIDn8DZ0y/9MACNB29nPWcBLPxY8QpsmOOq
BDjy3wlNr8xxoQviSZbb66IrEKc41peUfpaKGRCQ/kGRaaDBsSFjBbbrgyKc/dXM
aLuAwLeiROhGyxPl2LWUQPlBQ2O88UDLY4/fQlxSa+BBpjnS8QL8EFAZEw0wUK8t
MVTMGdyK09yknpWq159uK2zVjZyFs8kMlGC7ZuED94P0kJhlkku94ephEjDa3mFZ
T+mEVJ8SeM7IWiHr4uOQ4J1NSFAtw5rYKEqaJ57VzkISHXm4yRqg10foK6e36v4j
EnRdc0MwC69PtBd9GLh6v5MQp/Htjt5aKirF9G0iJj6WODFLGBt72DbKVmc6zM1H
bRpw1zW7y6leLFzdHcGIlc4/EQgsFf6Wmr72OiXQnWQNs+ii+Vxtm9phM/LLYE3p
dEWC6lApJtR3S96kqlbN3EhbJu3Yo6qtvkH1Ics6MTxPuSnuT14ki02NtrPC/LDP
LzlJHjJqBAKAp+QoeT/yIPBc5hbySdbYvYClPiyVysrUP7EMW434xetpFU4gAfjE
BVSo72e8LoHg+gJgJJrq
=vyMW
-----END PGP SIGNATURE-----

[gentoo-soc] Re: Council web app - introduction

[Joachim Bartosik]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(Note: this is c&p from my blog [0])

Last week I was working on:
* Preparing database seed for demos.
* Made some more changes to Hobo to make it easier to use.
* Wrote custom poll functionality (I planned to use Doodle API, but I
  had problems with authentication)
* Improved code metrics.
* Added support for basic summaries:
  * Council members can edit  summaries.
  * Council members can approve summaries.
  * All approvals are canceled after summary changes.
  * Regular users can view a summary after 4 council members approve it.


For short description of project and sources, read this[1].

[0]
http://ahenobarbi.wordpress.com/2011/07/25/council-application-%e2%80%93-weekly-report-9/
[1]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOLWaQAAoJEI0yxgiYdAoglnkP/3c9F8AxV7owAz4vSEDVlrwv
Y4GlRSqApbXcT2MswLTvY5Ss4VLOOwUMzXXU3qZPrFjZ53VzXRWh0spO0L0vFfth
Fyzs3HiTNUVBJUD+If10JDhKrdmJg1cxmW7g6eUmZHj4wJNaQBvjWJ5Y6Gt/osl5
7LabboV0HDb5a994NmVkL5SjMjbPUzol2UtxnSDtE1X3VzN9f8YRnfsMDb70vTX8
A67azNrqF6v4o60c6DpTb4zRMXjp9jEGR2um8rce/rmXvvDN/YcBH3Fif0IHSTWw
/iCuJAx3PQLAacsMqebAFpfi3gqMFIRzNVs9k3ZUKTgbDvJGOMDGQyQAf+DRa4Jw
rQa716GbwwMD+SeXocXCxCCNdMrEI5Dq73qb/9R5KhBbCt7TxQEbBpNPvAUwG4WB
QLRsTQGnlFKKGnM87IAwO9uzRQAD3Ph3YDxlzsNXonKt0uvubvWmfnnwR0+1S1kD
hlyPe3gwweYFSXcAcCuQwZBZQ+l/jSTWoGETya1NKK1y19iCTfLIEmjFb0RlneTv
HQNnSmF3txSuuN6JyjhXdMmDlG5CEnbBFVNgN5IxntxZmiJrU3QXIAeuP2EYbB8G
qDwnsERmBYk/ig2qWCofOJ/EdOwbKGUVFumo0gGMuaMxoWYe7YdcZvQcsRGGMSnn
8YYaDvmBcjXxyJdov+or
=zRfB
-----END PGP SIGNATURE-----

[gentoo-soc] Council application – weekly report #10

[Joachim Bartosik]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(Note: this is c&p from my blog [0])

This is my last weekly report – I started working on my project
earlierbecause I’m leaving on Thursday morning (plane takes off on 7:40
a.m. local time, ouch). I’ll write a final report summing up what I did
during the project before I leave, this report is summary of what I did
last week.

    I fixed a problem with MeetBot tests (there was one test that failed
because it tried to create symlinks that already existed on my system
    I read all code I wrote and did some refactoring
    I wrote a proper front page for the application
    I fixed a bug in a gem the site was using (if you made a mistake
during signup it would show your password in plain text input)
    I wrote usage hints for possibly non-obvious forms in the webapp
    I added license information to webapp.

For short description of project and sources, read this[1].

[0]
http://ahenobarbi.wordpress.com/2011/08/01/council-application-%E2%80%93-weekly-report-10/
[1]
http://ahenobarbi.wordpress.com/2011/05/30/council-application-short-introduction/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJONrs/AAoJEI0yxgiYdAoguv0QAIw8xucPES7NxcqYWbIk+LNC
Hu7rtZs3B3VWuHNlYjnGvQ1aePIKG6ykn+OzkiWhgh/NLsJY0x0DJSVQ4WaTqeUt
dIIL0/AEOoRXSoOB+gjd6hHjbCFQ3wvdv8H/e4VNHx7tXfdmfe7PzwgrIyiWHchY
4UjQlFJ2lW29+7qJdPO8SoR6k+QBOLEFK+wzmTY6pWtbYzStrPEFLk4bVYchlZ93
z0bOCb6CQObcKzO0cNJHIrOTn1xv979NaIjU/E102tWAGmA6Xhhlm+FdnNKUng7b
740xA8si+FO79DQ4dHHC5ep7G+rNv0y3nTGRXHCGJDdqmFavSozTs8IvxP0r02b3
lWbp+Si+rDgO1V62cf6NPS/8wp10ZFkE6W9pFpMSWk0RyluKYRYGwsDx2Clh7xVB
gvG5YVhCwS596LLhxSO/Zx4D/7i6PgU1ybLjPcfgZbIO1zM9iEn8MXKZJuXS/mN/
nwITdZTtZt4iAhDOFdO1QgeY+8ZZ5dkWZcNEd27f5yHcrn5XsvEYoMZ+ezf+aksT
XoHsyHJw6YKHwbsL7zzlZWyUYRavXGpTqg/IfJpvHZ5MyUHGnfmqLjDmkAVMK8FT
+LXTr/uie0xMP2Y0XGMGxj3dEl0r5T9MfldQCOWJkb47/0pcfGbbreOu3xoBu4zT
F7DX2M8XD3GgDJ7eJM9Q
=z1vF
-----END PGP SIGNATURE-----