David Reid wrote:
Well, there is code and I'm trying to figure out how to handle some of
the more exotic aspects of my ideas to allow remote and indiscriminate
posting to be handled... If you have other ideas we'd love to hear them.

One aspect I want to look at is tying in the DOAP files with the
generated ATOM so that we have all the nice things like project names
and so on all included. I'd like to have some time, but for some reason
having more time off (and recent events) has meant I have less
time/inclination to work on this...

If projects used the projects.a.o/PMC files fully we'd also have the
name and email of the person to send reminders to.

Yes - I need to figure out the big picture (like how it actually fits into the infrastructure and gets run and such). Is it just that people just use a couple of cmdline scripts to auto-create useful snippets of structured data (eg. reports later served via ATOM to someplace else)?

Definitely agree on moving to DOAP for every project; it's a pretty small requirement to keep that updated, and if it makes visualization of oversight easier then I'd be happy to require it of PMCs eventually.

Hmm, although obviously we have to have the data visibility religion
arguments (are visible statistics good, or will they destroy all fun in
the galaxy), then we have to have the programming language religion
arguments (python is cool, sure, but any perl code created after 2006
should be wiped, and then...

If you actually believe that then f**king rewrite the thing in python.
Jeez. If you're just saying it for effect then please don't.

Jeez. Note the "religion argument" prefix (the parenthesized portion was for humor value). I don't want to have one, unless it's funny enough to make us laugh. But the parts of systems written in perl won't get my serious attention because perl confuses me and makes me want to spend my volunteer time elsewhere.

Not saying this lab should change anything, just saying where I'm coming from, and what itches I'm motivated to scratch.

- Shane

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to