-----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 [1][2]. 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 [3]. As usual I appreciate any contribution and we certainly need more help and good ideas. [1] https://alioth.debian.org/tracker/index.php?func=detail&aid=313252&group_id=100127&atid=413115 [2] https://alioth.debian.org/tracker/index.php?func=detail&aid=313253&group_id=100127&atid=413115 [3] 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/ iQIcBAEBAgAGBQJObiKbAAoJEMcrUe6dgPNtEb4P/jVwf0LNKPxDniFVyrJnAgZl syIEieOaprZ3W/j16IjCWes+FwyWQ2MxeVcZDP7XgETAo9N/WDNbeZA6hTMt7u9H UnAl3kavSwHIDUfviRSiXhntiRxf1JA/ZLYDk7dcgQRvGkiWDm6l3eopAPFraXMA Id4xVZjcX6cyozaADYZG525JWvJhj5NhhwwnIgrbWB+mU1u2+rd5LV2H+h2GBuhY l7Bv9NvZmpMlDHfeIVGqvLb6i5nr5L899D5TNgCfcu/wwsDyikXOmh2hewPk8hog RHoi8u8Sr1eD3/WYZtQ8tSwgQPwQd0MVgH0B4BOLVHatnf6QzjLpDlPgoRujUu7Y zpOKpp3CfLGv5qUYrue6t38SSXBohz4wtvp1xT1npTbtp5KsuoVyTxbmojXpBTAy PuMmIwb2yhFVKOP0SHBWAoLU4lEa/vgDt/NuDwuBJaZvgSvd/6c0yx9EF7xdmX+P KD5g3Hi1yjmRC9APoLJzwQtMe6bsKto13GOWegI0vMZdspyVjRfW41ZmFdfhx4E+ UDnVvZsSZH/wVsEXFL4MedimhHADZ5bWxU8BwD3o9AmGc34T6dPE5T4f6UTi5m4I iW/6W2UZyEX7a7TGgV09F3AZVwmJoP209H7MlII/mGVgYEOiqbZGUmyxRJ0raAcm vDIjw8caJAUp/9Um+g+S =HVHf -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6e229c.5010...@toell.net