Andreas J. Koenig wrote:
[...]
> Do you think it'd be helpful if I could invest some time in helping with
> that issue (granted I'm not familiar with pause code)?
I'd start turning my mail into two scripts:
1. Write a script to find out if there are any packages in the current
modperl release that are not owned by APML. Write the URLs needed
to resolve offending packages and send each URL to the respective
owner.
The problem is that the script requires login/passwd to PAUSE and it'll
have to do screen scraping to get the information. Why doing screen
scraping when someone has an access to the database.
2. Before a release make the release manager co-maintainer of all
APML-owned packages. Do it manually or with a Mech script.
again, this is far from trivial, if you have to do screen scraping. Unless
there is some magical publicly accessible PAUSE API that I'm not aware of.
> I'd start with a simple suggestion I've suggested in the last
> email:
> step1: when a package containing new modules is submitted: the indexer
> needs to alert the submitter that there were new packages added and
> suggest to check whether others need to get perms to it, hopefully provide
> a one-click link to accomplish the task."
For my taste, far too complicated and too APML-centric.
I suppose it is if mod_perl is the only project that uses groups. However
a bunch of other Apache- modules and dev communities around those suffer
from the same issue.
since APML is not the only one, writing this script won't help other
projects, since they won't know it even exists.
> step2: when a package is submitted by another developer, who for some
> reason doesn't have perms for some of the modules, the indexer could
> suggest one-click link to fix the problem. It could suggest emailing the
> person who have added the package in first place and have a list of ready
> links to click for them to fix the problem. all this can be automated and
> will save everybody a lot of time.
Ditto
> Does this sound like a lot of work? it doesn't solve the problem, but it
> suggests to automate all the steps that you've described in this email,
> and saves your time, Andreas.
I'm not fond of adding any code to PAUSE infrastructure that doesn't
actually solve problems and must then be maintained. Please consider
the two scripts I suggest above. They seem pretty trivial to me.
--
_____________________________________________________________
Stas Bekman mailto:[EMAIL PROTECTED] http://stason.org/
MailChannels: Assured Messaging(TM) http://mailchannels.com/
The "Practical mod_perl" book http://modperlbook.org/
http://perl.apache.org/ http://perl.org/ http://logilune.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
