Closed (outdated)
Project:
Project
Version:
6.x-1.x-dev
Component:
ApacheSolr integration
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Aug 2011 at 14:27 UTC
Updated:
10 Oct 2019 at 23:37 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
pwolanin commentedComment #2
dwwNot 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
Comment #3
gregglesOk, 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.
Comment #4
gregglestagging.
Comment #5
drummI 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.
Comment #6
jbrauer commented@drumm Yes. Approved. We're needing to re-think how this works overall.
Comment #7
drummOkay, 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.
Comment #8
avpadernoI am closing this issue, as Drupal 6 is no longer supported.