It would be nice (and particularly useful for syncing projects to security.drupal.org) to have maintainer information in the solr index.

CommentFileSizeAuthor
#1 1261060-1.patch792 bytespwolanin
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pwolanin’s picture

Status: Active » Needs review
FileSize
792 bytes
dww’s picture

Status: Needs review » Needs work

Not all maintainers are created equal. Someone might just have "Maintain issues" permission, while others have full RCS write access, etc. Don't we want more structured data with the permissions each maintainer has? I'm worried that this patch, as-is, will lead to false assumptions and badness. Thoughts?

Thanks,
-Derek

greggles’s picture

Ok, so do we really want to include all 6 of the maintainer types as keys inside this? Or do we only want to include people with "write to vcs" OR "administer maintainers" OR "administer releases" ?

In my mind it seems fine to include all maintainers regardless of how much permission they have.

greggles’s picture

Issue tags: +security.drupal.org love

tagging.

drumm’s picture

I noticed the sdo-do dev site for this has gone unused. We have limited resources on our dev server and want to make sure projects are active. And you will want a fresh site when you can start work.

Can you approve deleting the dev site? You can ask again when you have time to start this project.

jbrauer’s picture

@drumm Yes. Approved. We're needing to re-think how this works overall.

drumm’s picture

Okay, done.

For the issue at hand, I personally think there might be some better alternatives to solr. Ideally, I'd like a common way of accessing project information that can be used by this, Localize.drupal.org which I hear directly accesses Drupal.org's DB, and API.drupal.org which will want a full project list in the future. And be a public API for others. There is http://drupal.org/node/1243332, which might help, but does need quite a bit of review and planning. Or keep it simple with a view outputting something machine readable. All these things shouldn't be solved here, but do keep them in mind.

apaderno’s picture

Issue summary: View changes
Status: Needs work » Closed (outdated)

I am closing this issue, as Drupal 6 is no longer supported.