[Members] Memberbot updates?

Peter Saint-Andre stpeter at stpeter.im
Thu Oct 8 10:47:03 CDT 2009


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

On 10/6/09 4:18 PM, Mateusz Biliński wrote:
> On Tue, Oct 6, 2009 at 23:58, anders conbere <aconbere at gmail.com> wrote:
>> I proposed a couple features to stpeter today with respect to memberbot.
>>
>> 1) Send muc invites when meetings occur
>> 2) Alert members of voting periods begin / end
>>
>> Mostly I'd just like to have a better idea about when there are events
>> occurring that I as a member would like to involve myself in, but have
>> probably forgotten about.
>>
>> stpeter suggested that the memberbot code was a little bit rotted and
>> could use a fresh start. And that there were updates made to it during
>> google summer of code last session. I was hoping to get the members
>> general opinion of embarking on a memberbot update and maybe some
>> other features other folks would want. Basically just get some ideas
>> about what more the XSF could provide to members to help make their
>> jobs more fun / fulfilling / easier.
>>
>> Having not yet seen the current implementation I would say that the
>> goals for something like this would be to.
>>
>> 1) fulfill a majority of the use cases, at a minimum meeting the
>> current feature set
>> 2) make the code easy to read and maintain in order to facilitate
>> unforeseen use cases and bug fixes
>> 3) possibly make the source more easily available to leverage the
>> number of bright folks we have in the membership already.
> 
> Agree. :)
> 
> I'm the person that has rewritten memberbot to act as sleekbot plugin.
> There are currently two separate versions of it - chat-based and
> dataForms-based.
> 
> With Alex, we agreed that we will focus on the second one and upcoming
> votings will have to be done via clients that support both data forms
> and ad-hoc commands.
> 
> Current implementation needs some final coding (mostly in aggregating
> results AFAIR), but as proof-of-concept it works pretty well. I think
> that feature (2) is implementable. Feature (1) is not connected with
> voting unless you thought of meetings that summarize results of
> surveys (if so then it could be implemented, too).
> 
> I could place the code on mercurial repo at code.google.com if needed.
> Probably it would be reasonable to finish basic functionally before
> that.

We have svn.xmpp.org and I think that would be a more appropriate place
for this code. If you don't like SVN, feel free to join the
infrastructure team and we'll work on a move to some other SC
technology. ;-)

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrOCXcACgkQNL8k5A2w/vxDwQCg16Q8sMqGzTuLRyBg7eInE4Fh
AukAoOPO+TdKZF6DniC9PuxTGJ9NiWVR
=tup3
-----END PGP SIGNATURE-----


More information about the Members mailing list