Hello, - I've made a couple of changes to the way CVS accounts are approved. As of now, the CVS password file is automatically updated on the server. This should simplify (and fasten) the process of approving CVS applications. Consequently, we could easily grow the team of people who can administer CVS accounts. - Next step is pruning some stale CVS accounts. I plan to block CVS accounts that have not been used (to commit files) in the past 12 months. Does that sound like a reasonable time frame? - Resetting CVS passwords is still a problem. Fortunately, Gerhard (killes) is extending the cvs.module so that it can be done using a simple form at drupal.org. This should reduce the administration overhead significantly. - We still have to do a fresh import of the CVS repository to fix some database inconsistencies that crept in the past year or two. :/ Chances are that the cvs.module's import code suffers from some bit rot so if someone wants to prepare or test the cvs.module's import code, that would be much appreciated. FYI, -- Dries Buytaert :: http://buytaert.net/
Dries Buytaert wrote:
Chances are that the cvs.module's import code suffers from some bit rot so if someone wants to prepare or test the cvs.module's import code, that would be much appreciated.
It would be helpful if there were some really good documentation on how to use Drupal to run a site like Drupal.org. I'd have to work pretty hard to set up the project module and cvs.module with my current skills, and not knowing exactly how Drupal.org runs and operates is another hurdle. Drupal is a vastly successful project. Part of the reason why it is successful is the infrastructure that has been created to support development and participation. It seems to me like this infrastructure would probably work well for a number of other projects as well, yet I've never heard of or seen anyone running a setup like Drupal.org. Maybe we'd get more people involved in the tools like project and cvs modules if we made it easier to set up other projects and sites with Drupal.org infrastructure. This would take a bit of documentation and marketing. cheers, Robert
On 5-Jan-06, at 12:38 AM, Robert Douglass wrote:
Dries Buytaert wrote:
Chances are that the cvs.module's import code suffers from some bit rot so if someone wants to prepare or test the cvs.module's import code, that would be much appreciated.
It would be helpful if there were some really good documentation on how to use Drupal to run a site like Drupal.org. I'd have to work pretty hard to set up the project module and cvs.module with my current skills, and not knowing exactly how Drupal.org runs and operates is another hurdle.
Drupal is a vastly successful project. Part of the reason why it is successful is the infrastructure that has been created to support development and participation. It seems to me like this infrastructure would probably work well for a number of other projects as well, yet I've never heard of or seen anyone running a setup like Drupal.org.
Maybe we'd get more people involved in the tools like project and cvs modules if we made it easier to set up other projects and sites with Drupal.org infrastructure. This would take a bit of documentation and marketing.
I have never gotten a currently tagged version of project module to run with a current version of Drupal out of the box. Even using a CVS version meant lots of (nasty) bugs...I suspect this is because Drupal.org (along with project.module) always runs close to head and project.module maintainers hadn't been diligent about tagging/ branching. With all the recent work by nedjo, it's shaping up nicely -- thanks (and to the man behind the curtain, Kieran, for sponsoring that). An "open source community" install profile/recipe *would* be great. -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 SKYPE borismann http://www.bryght.com
I think that Robert's idea, and Boris' amplification, are excellent. I've started working a little on this, from the other side of things, namely, the mythical 'new user'. I've spent some time writing descriptions of how the interaction between user ("I've got a problem that's bugging me"; or "I found a bug!") and project ("Drupal.org/the community") works. The idea is to create easy entry, and easy navigation, kind of like the great signage at Schiphol airport ("Make it hard to get lost") This would help in promoting the proposed "install profile/recipe" because it would present the story in two parts: 1. Here are the processes, protocols and mechanisms that the Drupal community uses to work together 2. Here is the technology recipe required to support 1.) I think that this approach is useful because - it's difficult to understand the machine if you don't know what it's used for; - some of our own community (I myself included) really don't know what's going on with respect to 1) - clarifying this would help make the process clearer, easier to use, modify if necessary, and tune. One way to improve Drupal.org performance is to save needless clicks. I know that there have been great efforts made to simplify issue tracking for users already - my main effort to this point has been trying to document the issue reporting/tracking process. Eventually I'd like to see this lead to fewer bad issue reports. Suggestions are welcome :) Djun On 5-Jan-2006, at 3:47 AM, Boris Mann wrote:
On 5-Jan-06, at 12:38 AM, Robert Douglass wrote:
Dries Buytaert wrote:
Chances are that the cvs.module's import code suffers from some bit rot so if someone wants to prepare or test the cvs.module's import code, that would be much appreciated.
It would be helpful if there were some really good documentation on how to use Drupal to run a site like Drupal.org. I'd have to work pretty hard to set up the project module and cvs.module with my current skills, and not knowing exactly how Drupal.org runs and operates is another hurdle.
Drupal is a vastly successful project. Part of the reason why it is successful is the infrastructure that has been created to support development and participation. It seems to me like this infrastructure would probably work well for a number of other projects as well, yet I've never heard of or seen anyone running a setup like Drupal.org.
Maybe we'd get more people involved in the tools like project and cvs modules if we made it easier to set up other projects and sites with Drupal.org infrastructure. This would take a bit of documentation and marketing.
I have never gotten a currently tagged version of project module to run with a current version of Drupal out of the box. Even using a CVS version meant lots of (nasty) bugs...I suspect this is because Drupal.org (along with project.module) always runs close to head and project.module maintainers hadn't been diligent about tagging/ branching. With all the recent work by nedjo, it's shaping up nicely -- thanks (and to the man behind the curtain, Kieran, for sponsoring that).
An "open source community" install profile/recipe *would* be great.
-- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 SKYPE borismann http://www.bryght.com
Chances are that the cvs.module's import code suffers from some bit rot so if someone wants to prepare or test the cvs.module's import code, that would be much appreciated.
It would be helpful if there were some really good documentation on how to use Drupal to run a site like Drupal.org. I'd have to work pretty hard to set up the project module and cvs.module with my current skills, and not knowing exactly how Drupal.org runs and operates is another hurdle.
Drupal is a vastly successful project. Part of the reason why it is successful is the infrastructure that has been created to support development and participation. It seems to me like this infrastructure would probably work well for a number of other projects as well, yet I've never heard of or seen anyone running a setup like Drupal.org.
Maybe we'd get more people involved in the tools like project and cvs modules if we made it easier to set up other projects and sites with Drupal.org infrastructure. This would take a bit of documentation and marketing.
It takes a lot of time and effort to keep the tools working with CVS head, and to implement the needs of the growing Drupal community. If only we had a couple more people working on them, we could make these tools more generic, we could make the project.module use the comment.module for issue follow-ups, fix the issues showing up on the 'recents posts' page, make it possible to reset CVS passwords, conduct a card sort for the categorization of projects, add project ratings, fix up the various database inconsistencies, etc, etc. CivicSpace has been funding Nedjo to work on the project.module. (Big thanks!) If someone else wants to fund a developer, let me know. I'd be happy to coordinate the work. That said, you're absolutely right. It has a lot of potential, and it particularly rewarding as well. :) -- Dries Buytaert :: http://www.buytaert.net/
On Thu, 05 Jan 2006 09:59:01 +0100, Dries Buytaert <dries.buytaert@gmail.com> wrote:
Chances are that the cvs.module's import code suffers from some bit rot so if someone wants to prepare or test the cvs.module's import code, that would be much appreciated.
It would be helpful if there were some really good documentation on how to use Drupal to run a site like Drupal.org. I'd have to work pretty hard to set up the project module and cvs.module with my current skills, and not knowing exactly how Drupal.org runs and operates is another hurdle.
Drupal is a vastly successful project. Part of the reason why it is successful is the infrastructure that has been created to support development and participation. It seems to me like this infrastructure would probably work well for a number of other projects as well, yet I've never heard of or seen anyone running a setup like Drupal.org.
Maybe we'd get more people involved in the tools like project and cvs modules if we made it easier to set up other projects and sites with Drupal.org infrastructure. This would take a bit of documentation and marketing.
It takes a lot of time and effort to keep the tools working with CVS head, and to implement the needs of the growing Drupal community. If only we had a couple more people working on them, we could make these tools more generic, we could make the project.module use the comment.module for issue follow-ups, fix the issues showing up on the 'recents posts' page, make it possible to reset CVS passwords, conduct a card sort for the categorization of projects, add project ratings, fix up the various database inconsistencies, etc, etc.
Is there a list somewhere of the top Drupal.org issues and feature requests? -- Tim Altman
On 1/5/06, Tim Altman <web@timaltman.com> wrote:
Is there a list somewhere of the top Drupal.org issues and feature requests?
Like this Page: http://drupal.org/project/issues/?projects=3202&categories=bug,task,feature,... RSS: http://drupal.org/project/issues/?projects=3202&categories=bug,task,feature,... The search should get that fixed in whatever way you want to change it: http://drupal.org/project/issues/search/ Greg
On Thu, 05 Jan 2006 15:37:32 +0100, Greg Knaddison <greg.knaddison@gmail.com> wrote:
On 1/5/06, Tim Altman <web@timaltman.com> wrote:
Is there a list somewhere of the top Drupal.org issues and feature requests?
Like this Page: http://drupal.org/project/issues/?projects=3202&categories=bug,task,feature,...
That's a list of issues in the Drupal.org category. It does not list the top issues with Drupal.org that Dries would like to see fixed, which is what I was after. -- Tim Altman
On 05 Jan 2006, at 16:49, Tim Altman wrote:
Is there a list somewhere of the top Drupal.org issues and feature requests?
Like this Page: http://drupal.org/project/issues/? projects=3202&categories=bug,task,feature,support&states=1,8,13,14,2
That's a list of issues in the Drupal.org category. It does not list the top issues with Drupal.org that Dries would like to see fixed, which is what I was after.
1. http://drupal.org/node/35814 In addition (more technical issues): 2. Update the project module to work with the comment.module (rather than having its own comment implementation). This will make it easier to maintain and will make it easier to roll out new functionality in future (eg. site-wide subscriptions) 3. Work on the mail backend and build a good, all-around subscription functionality that we can use on drupal.org (and that we can include in core as part of tracker.module?). Update project.module and simplenews.module to use the mail backend. 4. Performance improvements: (i) project issue pages, (ii) the forum overview page (?q=forum), and (iii) the CVS log page (?q=cvs) are really slow. (ii) is likely to be a problem for sites with many forum (topics). 5. Make sure that the cvs.module can import the current repositories so we can fix the database inconsistencies that crept into the cvs.module's SQL tables. 6. Improve the code-style checker (and thus the code reports). Many security problems in contributed modules go unnoticed. 7. Test the project.module and the simplenews.module and their upgrade path so we can upgrade drupal.org. Create a Drupal HEAD module for http://drupal.org/mailing-lists. -- Dries Buytaert :: http://www.buytaert.net/
On Thu, 05 Jan 2006 17:22:15 +0100, Dries Buytaert <dries.buytaert@gmail.com> wrote:
On 05 Jan 2006, at 16:49, Tim Altman wrote:
Is there a list somewhere of the top Drupal.org issues and feature requests?
Like this Page: http://drupal.org/project/issues/? projects=3202&categories=bug,task,feature,support&states=1,8,13,14,2
That's a list of issues in the Drupal.org category. It does not list the top issues with Drupal.org that Dries would like to see fixed, which is what I was after.
1. http://drupal.org/node/35814
In addition (more technical issues):
[...] Thanks, Dries. -- Tim Altman
On Thursday 05 January 2006 12:38 am, Robert Douglass wrote:
It would be helpful if there were some really good documentation on how to use Drupal to run a site like Drupal.org. I'd have to work pretty hard to set up the project module and cvs.module with my current skills, and not knowing exactly how Drupal.org runs and operates is another hurdle.
I just started using project module to keep track of my own work. It seems like a great tool to coordinate with the people I work with, and provide some visibility to my clients. I've just started to do this, it's still an experiment for me. My impression so far is the project module is not quite ready for public consumption. I say this because its short on documentation and there's a few things about that seem very drupal.org specific. For instance there's a reference to url 'forum/18' with no easy way to change it. But without too much pain I'm using it to track issues. As I understand it better I'll submit issues (and patches) to drupal.org. All this module needs is more users and a little time. -Dave
I just started using project module to keep track of my own work. It seems like a great tool to coordinate with the people I work with, and provide some visibility to my clients. I've just started to do this, it's still an experiment for me.
But without too much pain I'm using it to track issues. As I understand it better I'll submit issues (and patches) to drupal.org. All this module needs is more users and a little time.
I've tried to make patches for features that our community needs. I got lost in the weeds and finally gave up. IMO, this module needs much more than users and time. It needs a casket. I'd ecourage folks to write a basic ticketing module for Drupal. This would be a good test case for a relations API, since we would want projects => issues relationship and issues => issues relationship (for dependencies/blockers). -moshe
Dave Cohen wrote:
On Thursday 05 January 2006 12:38 am, Robert Douglass wrote:
It would be helpful if there were some really good documentation on how to use Drupal to run a site like Drupal.org. I'd have to work pretty hard to set up the project module and cvs.module with my current skills, and not knowing exactly how Drupal.org runs and operates is another hurdle.
I just started using project module to keep track of my own work. It seems like a great tool to coordinate with the people I work with, and provide some visibility to my clients. I've just started to do this, it's still an experiment for me.
I did this too once and it generally worked well.
My impression so far is the project module is not quite ready for public consumption. I say this because its short on documentation and there's a few things about that seem very drupal.org specific. For instance there's a reference to url 'forum/18' with no easy way to change it.
Please create patches and file issues. It appears that Nedjo is the current de-facto maintainer of the module and I think he will like some help in improving it.
But without too much pain I'm using it to track issues. As I understand it better I'll submit issues (and patches) to drupal.org. All this module needs is more users and a little time.
Yes. The problem was and still is to some degree that is was very drupal.org specific so nobody else could use it. Cheers, Gerhard
participants (9)
-
Boris Mann -
Dave Cohen -
Dries Buytaert -
Gerhard Killesreiter -
Greg Knaddison -
Moshe Weitzman -
puregin -
Robert Douglass -
Tim Altman