Re: Report from the debconf11 sponsoring/mentors BoF.
I would like to confirm that I am still interested in dedicating some
of my time to write code for debexpo. Serafeim, thanks for CC-ing me.
I am on debian-mentors list already.
I will look at the code, and probably have some questions. Idea of
developing metrics plugin for collecting statistics and informations
about sponsors and packages for improving mentoring process is
interesting for me. I will just need some time to see how debexpo
works. If there is no final decision of metric implementation, I will
certainly have some ideas...
On Mon, Sep 12, 2011 at 17:17, Arno Töll <email@example.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Hi Serafeim,
> (keeping your CCs:)
> On 11.09.2011 23:56, Serafeim Zanikolas wrote:
>> I understand that there's two sides in this effort: debexpo plugins that
>> produce additional info about certain package features, and a repository of
>> sponsors' interests/preferences/requirements. Do I understand correctly that
>> you implement both things within debexpo? Are DDs expected to enter their
>> preferences via the debexpo web ui?
> Yes. Debexpo runs certain plugins on incoming packages. Among those
> several QA plugins, which for example run Lintian, or check bugs being
> closed by the upload. Have a look to any given package on mentors.d.n to
> get the idea.
> On the other hand there are concepts and ideas to extend the mentors
> platform by social network functionalities to bring together packages
> with sponsors. Aside of the mentioned metrics, I am referring in
> particular to Lucas' idea here . As far as I know there are
> currently no concrete plans to work on that though.
> Regarding the sponsor metrics: Yes, I do expect Debian developer to file
> their preferences via Debexpo web UI.
> The third key concept of the mentoring process is the package review
> itself. That's the part which is currently done by email on the
> debian-mentors mailing list. As we mentioned in the report you are all
> invited to join the current discussion going on there, how to improve
> the situation by moving the discussion part to the BTS (or not).
>> My idea instead was to maintain DDs' preferences via an ikiwiki instance
>> (using something structured like yaml), and make the wiki data accessible to
>> debexpo via a REST interface. At the end of the day, it's up to whoever will
>> do the work, but it's wise to remember that geeks prefer their favourite text
>> editor than a web browser.
> I am not particularly thrilled by that idea. If you want to implement
> that, feel free to do, but I don't see any real benefit here. Really, I
> think I don't expect too much from a Debian Developer if I want him/her
> to register once in Expo and fill out a form if there is some general
> interest to sponsor packages. That's about two minutes of work if you
> have no free text to add.
> Also you should take into account, that human editable semi-structured
> data is error prone and lacks validation.
>> Anyhow, thanks for stepping up, and whatever your approach, please share any
>> code you have with Janos and see whether/how you could work together.
> Its all in our Git repository . As usual I appreciate any
> contribution and we certainly need more help and good ideas.
>  http://anonscm.debian.org/gitweb/?p=debexpo/debexpo.git
> - --
> with kind regards,
> Arno Töll
> IRC: daemonkeeper on Freenode/OFTC
> GnuPG Key-ID: 0x9D80F36D
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----