Projects Needing Volunteer Developers

Alternative Currency Support

matslats — Fri, 25 Apr 2008 16:30:59 +0000

Hundreds of communities trading with complementary currencies need this!

Two years ago, working with the UK Coordinator for LETS I prototyped an architecture to support these communities with all their variants. Right now I have time to port it to Drupal which is the obvious platform. Progress is slow because I'm learning on the job, so this project needs mentoring.

So I'm working on a collection of modules which will include an offers/wants directory with autocategorisation, and a transaction contentType which will have a lot of rules and a couple of hooks for things like taxation mechanisms. Then it will be wrapped up in a recipe and delivered to an expert I know who's ready to test it with a community.

I'm keeping track of my work and of my problems (about one a day, at the moment) on the development site where I'm developing things, and when views 2 works it will be available as a feed! It needs is a bit more attention than one is likely to find on IRC.

This project has no real competitor. It really needs doing. There are some weak looking commercial providors, some whacky schemes like regenerosity and ripple, but apart from that, most of the action still happens on paper and by snail mail. It's no wonder the young people aren't signing up!

Projects Needing Volunteer Developers

Semantic Repository for Green Building Research Project Wanted | SkySite Property

jeffchi@drupal.org — Sun, 20 Apr 2008 19:18:51 +0000

We are seeking a developer to assist us with creating a new or re-purposing an existing dynamic research repository that can capture various case studies, articles, websites and other semantic information from a multi- member research team. Our focus is green building and sustainability to which we use this research content to populate our online learning portal, develop curriculum and increase our consulting knowledge.

Some of the repository attributes would include:

Drupal based or Drupal friendly alternative (MySQL)
Able to recognize existing information as new content is being contributed.
Confidential modes for various levels of permission access
Dynamic to add major Categories and sub-categories to expand research scope
Tracks semantic data with relationships to other data
Dynamic means to expand data classification to tie into CRM (Sugar)
Able to deliver end data to multiple users and media outlets

We are eager to hear back of your abilities to assist us with this project or better yet, your success with a similar system that we can re-orientate to this particular subject field. We are here to make a difference on the planet through our research on sustainability- come join us.

Research and academia

Drupal Config Specialist/Themer | SkySite Property

jeffchi@drupal.org — Sun, 20 Apr 2008 18:51:47 +0000

Job Description: Drupal Config Specialist/Themer

The Drupal configuration specialist will have a solid understanding of the Drupal Content Management Framework. Listening to our needs you will gather a collection of modules that provide a best fit, and you will work with our developers to provide any customizations that are required. You live online, you thrive in #drupal-support and #drupal-themes. You Blog, Skype, Twitter and Pownce your way through the day to get your points across.

Essential skills.
• General understanding of Drupal 5x core and contrib
• Ability to install and configure Drupal
• Strong command of the drupal 5 theme layer
• HTML and CSS skills to produce validating, cross-browser layouts.
• Particpation in the Drupal community in any capacity.

You'll be considered a stronger candidate if you possess the following:
• Web site design experience
• User interface design
• Agile project methodology
• Photoshop/Illustrator (or equivalents)
• Demonstrated participation on open source projects (not necessarily Drupal)

You'll be able to demonstrate your possession of these skills with a portfolio. You'll be able to demonstrate your activitiy within the Drupal community by providing your Drupal user ID and your IRC handle.

About Project and Company:

SkySite Property is focused on supporting Green Building; environmentally sound best practices of building and management of real estate. We are dedicated to positively impact the world through education, predominately with high level websites supported by online marketing and live conventions. We have secured key relationship within the industry to enable high traffic to our pending green building portal. We need help to get our online initiatives up and running quickly and extensively.

Projects Needing Volunteer Developers

volunteer enthusiasts / consultants for Iraq initiative | International Initiative to Prosecute US Genocide in Iraq

Ian Douglas — Wed, 12 Mar 2008 08:20:54 +0000

Dear Drupalers,

This is a call to persons with a comprehensive understanding of what is possible in Drupal (particularly via contributed modules) — in other words, Drupal consultants or enthusiasts.

I am in need of general volunteers able to discuss (preferably via Skype) and suggest solutions for various aspects of the implementation of the following (see below) — even just to provide general one-on-one guidance on the nature of certain modules (CCK, CiviCRM, Views, etc.) and their various functions or possibilities.

I am in the process of developing an international initiative aimed at prosecuting the United States, its leaders and allies, on charges of the crime of genocide in Iraq. The site I aim to develop has three main aims:

1) To provide a virtual workspace for international lawyers to build a legal memorandum on US genocide in Iraq; one that can be used in international fora and be the basis of a move towards legal action against the United States, its leaders and allies;

2) To provide a rigorously data secure interface for the online submission of witness testimony on war crimes and grave human rights abuses in Iraq, using this repository to build the case of US genocide in Iraq;

3) To be a focus for the antiwar movement, grounding the claim that the only honest and accurate way to understand and describe US policy and actions in Iraq is as genocide.

This initiative I am developing stems from several years' work on Iraq with the BRussells Tribunal (www.brusselstribunal.org), in defence of the Iraqi people, its resistance and its sovereignty, against the illegal US invasion and occupation. Like the BRussells Tribunal, the International Initiative to Prosecute US Genocide in Iraq will also work on a zero budget and represent no political party.

In effect, this is a call for general guidance, to help me, a non-developer, get up to speed and understand more fully the potential of Drupal.

Please contact me if you are able to assist.

Thank you,
Dr Ian Douglas, coordinator
iandouglas@USgenocide.org

International Initiative to Prosecute US Genocide in Iraq
مبادرة دولية لمحاكمة جريمة الإبادة الجماعية الأمريكية في العراق
www.USgenocide.org

Projects Needing Volunteer Developers

volunteer themer for Iraq initiative | International Initiative to Prosecute US Genocide in Iraq

Ian Douglas — Fri, 08 Feb 2008 21:19:56 +0000

Dear Drupal users,

This is a call to accomplished, high-level themers.

I am in the process of developing a soon-to-be-launched international initiative aimed at prosecuting the United States, its leaders and allies, on charges of the crime of genocide in Iraq. I need significant volunteer resources in all aspects of Drupal, but in particular in theming and aesthetics.

The new initiative currently being built offline is a sober and serious undertaking. Given the subject matter — the destruction of the state of Iraq, and attempted destruction of the nation of Iraq, entailing the deaths of 1.2 million Iraqis since 2003 — I need the highest level of skills in aesthetic presentation and sensibility.

At present I am working on the Garland theme as a basis, partly because I like elements of it, and partly because the site is complex in its architecture, so I need the theme to not interfere but rather facilitate work in a complex online environment.

This initiative stems from several years' work on Iraq with the BRussells Tribunal (www.brusselstribunal.org), in defence of the Iraqi people, its resistance and its sovereignty, against the illegal US invasion and occupation.

The BRussells Tribunal works on a zero budget and represents no political party. The International Initiative to Prosecute US Genocide in Iraq will also work on a zero budget and represent no political party.

The basis of the initiative is an understanding that at stake in Iraq is not only the sovereignty of a nation, but the standing and future of international law, indeed of humanity itself. The Iraqi people and its resistance is defending values upon which all our lives depend.

If you share a sense that what the United States is doing and has done in Iraq is intolerable, and if you have theming skills, fine attention to detail, and refined aesthetic taste, please write me for more details.

Thank you,
Dr Ian Douglas, coordinator
iandouglas@USgenocide.org

International Initiative to Prosecute US Genocide in Iraq
مبادرة دولية لمحاكمة جريمة الإبادة الجماعية الأمريكية في العراق
www.USgenocide.org

Theme development

volunteer developer / programmer for Iraq initiative | International Initiative to Prosecute US Genocide in Iraq

Ian Douglas — Thu, 24 Jan 2008 00:46:14 +0000

Dear Drupal users,

I am looking for short, medium and long-term programming / development assistance for an international initiative soon-to-be-launched aimed at prosecuting the United States, its leaders and allies, on charges of the crime of genocide in Iraq.

The new initiative is currently being built offline. It already needs significant volunteer resources, particularly in establishing capacity to provide content in Arabic and Spanish as well as English. There are also significant security considerations that need expert input.

If you share a sense that what the United States is doing and has done in Iraq is intolerable, and that the purposive destruction of a state and nation cannot be allowed to be a precedent for the opening of this century, and if you have programming skills, development skills, design skills and / or security related skills, please write me for more details.

Thank you,
Dr Ian Douglas, coordinator
iandouglas@USgenocide.org

International Initiative to Prosecute US Genocide in Iraq
مبادرة دولية لمحاكمة جريمة الإبادة الجماعية الأمريكية في العراق
www.USgenocide.org

Projects Needing Volunteer Developers

Sessions on "Community: Role of the Contributor" Wanted For Drupalcon 2008

mpare — Sat, 19 Jan 2008 01:02:14 +0000

My name is Matthew Pare and I'm a Co-Chair for the "Community and Core" track for Drupalcon Boston 2008. Over the last couple of weeks we have been planning and brainstorming to make Drupalcon Boston 2008 the best Drupalcon to date! One of our recommended track session topics is "Community: Role of the Contributor" and since your viewing this post on the Projects Needing Volunteer Developers group I thought you would be excellent candidates for submitting sessions on the topic.

How To Submit Your Session

We have several recommended topics for Community and Core sessions but now its your turn to submit your session.

Visit boston2008.drupalcon.org to learn more about Drupalcon Boston 2008, register to attend, view already submitted sessions, and even submit your own session.

Save the Date

Drupalcon Boston 2008 takes place from March 3, 2008 to March 6, 2008 in Boston Convention and Expo Center. In addition, there will also be a Drupal Code Sprint on March 7.

Useful Links

Please submit your session proposals as soon as possible and I hope to see you all in Boston real soon.

Cheers,

-mpare

DON'T MISS EARTH'S LARGEST GATHERING OF DRUPAL PROFESSIONALS!
Drupalcon Boston 2008 - March 3-6, 2008
Learn more at http://boston2008.drupalcon.org

Projects Needing Volunteer Developers

Content manager | New Media Denver

kappaluppa@drupal.org — Tue, 01 Jan 2008 19:57:38 +0000

We are in the process or reorganizing the website for Arthur Blessitt. He has walked around the world carrying a cross to spread the Gospel.

We are in porting over a site with pages numbering a thousand plus. We would appreciate volunteers would be willing to contribute time to add content and create pages.

Please contact kathy@newmediadenver.com if you are interested or would like more information.

Thanks!
Kathy

Projects Needing Volunteer Developers

DBA module 5.x-1.0 release roadmap

dww — Sun, 14 Oct 2007 22:23:09 +0000

Here's what has to happen before a 5.x-1.0 official release can be made for the DBA (Database administration) module:

The first 2 entries are in priority order. Those two must be done first, and I won't commit any patches to DBA until #154227 is in...

~~http://drupal.org/node/154227 Simplify dba_get_active_tables() and use arrays for the list of active tables everywhere.~~ 2007-10-15
http://drupal.org/node/138877 Can't backup database from table list
http://drupal.org/node/103911 Failure of automatic backup with large database
As many of the other bugs from the issue queue as possible.
Going through all of the patches that need review.

Those are the main things. Obviously, some more testing would be great. And, if there are additional features or API enhancements necessary to make it easier to interact with, I'd be open to adding those to the list.

Any help would be most appreciated.

Thanks!
-Derek

Projects Needing Volunteer Developers

Stay-at-Home Drupal Mom/Dad? | Careers In Common

kcherrywa — Fri, 13 Jul 2007 19:01:15 +0000

I am working on launching a website that will help professionals and employers learn about and adopt non-traditional work arrangements such as part-time, flex time and job-sharing. www.CareersInCommon.com will launch this fall with a content hub/"Learning Center;" with the long-term goal of adding a job board. The site will be targeted mainly to professionals who do not want to work a 40 hour, 9-5, Monday-Friday work week -- moms of young kids, people caring for disabled or elderly family members, people transitioning into retirement, entrepreneurs, people going back to school, people volunteering for non-profits/churches, etc.

I am hoping to find someone who can take an existing Drupal add-on module for job boards (like http://drupal.org/project/jobsearch) and tweak it to provide additional resume/profile fields, and enhanced search/match functionality.

Is there a stay-at-home mom or dad (like myself) who is itching to do something productive when their kids are napping ;-) who can help me with this part of the site? I know there's got to be someone out there with a little time on their hands, who believes in the altruistic benefit this site will provide to people like us around the world.

Projects Needing Volunteer Developers

an experimental platform

Bèrto ëd Sèra@drupal.org — Fri, 15 Jun 2007 14:37:47 +0000

You might be interested in an experimental platform based on Drupal 5.1 that we are making for small linguistic entities. Basically it delivers the capability of speaking, along with reading, by introducing an added MP3 vocal file to all nodes and comments.

The english version is at http://eng.i-iter.org a first running example in the piemontese language is at http://pms.i-iter.org

We look for volunteer developers and translators to localize the platform into other languages, so feel free to add requests to join the alpha stage. Bear in mind that alpha really means alpha...

Social Networking Sites

Marketplace for Module Development and Improvement– pooling resources of developers

Benjamin Melançon — Tue, 15 May 2007 12:23:14 +0000

I'm glad Darren Oh has got a solid proposal for this group. I would suggest that the most needed aspect of a Drupal marketplace would be a way for individual Drupal users and Drupal shops – especially smaller shops – to pool resources to fund specific module development.

User dahacouk called for more structure and a funding model to make the quality of contributed modules the best they can be.

To quote from my endorsement and proposal:

I applaud Walt's work in promoting projects needed financing and projects needing developers, and I see this idea as a way to build on it.

Letting people put money up for specific needs will give people who have that fabled itch to scratch – but without the time or Drupal experience to do it themselves – actually do something by putting money behind their words, "I want this feature / bug fix / functionality / module".

The Drupal Association could hold the money (and use interest off it to pay overhead) until the financed improvement is made

In the vast majority of cases the money would go to a developer or developers at the independent approval of the people who put up the money initially. (It would have to go to people who signed up to work on the request, to avoid someone redirecting the cash to a cousin at the last second.) Some appointed board (or democratic sample) could make a quick decision (including to have Drupal Association keep the money, or have the dispting parties split the difference) in the minority of cases where disagreements arise.

If not enough money is raised or work isn't done for some other reason, the Drupal Association can offer to refund it at a certain point-- but most people will re-assign it to another project, rather than cashing out.

This should be integrated into Drupal.org as much as possible, as in the issue queue and projects' pages. Two Summer of Code projects will be working in this area, Project quality metrics system and Extend Case Tracker Module, so now is a good opportunity to work in this area.

The same system can be used to support needed core changes, of course, although in this case its more likely to take the form of Dries or someone else with a bit of core developer cred pointing to an issue, saying this needs support, and letting us freeloaders give back. Also, people could make general donations at any time which some Drupal Association appointed group (or maybe someday a broad democratic vote) could direct.

It looks like this would have to start independently and prove itself before being integrated with Drupal.org or the Drupal Association. I'm part of a nonprofit (pending 510c3 application) which could probably provide fiscal sponsorship for such a venture. I think it's important that it be under nonprofit rather than for-profit aegis.

Agaric would love to hear feedback and especially interest.

~ ben, member, Agaric Design Collective

Projects Needing Volunteer Developers

How to help with the project* modules

dww — Mon, 16 Apr 2007 09:45:37 +0000

The project* collection of modules (Project, Project issue tracking, and CVS integration) is the largest set of code running on drupal.org besides Drupal core. They are the key tools that power all Drupal development, including the Drupal issue queue and Drupal release system. Because of the huge user base, high visibility, complex requirements and feature requests, and size and scope of the existing code base (and issue queues) there is a ton of work to be done. This wiki page is how I (dww, the primary maintainer of project*) will try to communicate the best ways for other people to get involved in helping. One of the ways to help is to improve this list, so please add your own ideas here.

This list is roughly in order of what kind of skills you'd need, but not exactly. It's not in priority order, since all of it would be helpful, and it's hard to prioritize given there might be many people with different skills or interests. So, just read the whole list and decide what parts of it you'd like to help with. In terms of the issue queues, you can obviously prioritize things marked as critical.

Join the New Release System group.
Read the handbook pages about the project* modules on drupal.org. Figure out how to install your own local test site running 5.x Drupal core and the latest versions of these modules. Improve and/or extend the handbook pages as you go.
Read this post about the drupal.org testing installation profile. See if you can help make that profile more complete, if you can get it to work, if you can contribute documentation on how to use it, etc.
Read these 2 issues about testing on http://scratch.drupal.org :
- 5.0 release candidate now running on scratch.drupal.org (http://drupal.org/node/105004)
- Testing the 5.0 port of the release system on scratch.drupal.org (http://drupal.org/node/105016)
They're slightly out-dated, but the basic idea is still valid: see if you can find any new bugs, and if so, report them. Both of those pages include detailed instructions on where to report any bugs or problems you find. Please don't submit duplicates, see below. ;)
Read through the Project* issue queues:
Familiarize yourself with what's there now (this is a fairly huge task on its own). Then, here are the ways you can help clean-up the queues to make them more manageable for other users and developers:
- Find duplicate issues and mark the newer issues duplicate, including a link to the oldest issue in the queue about the same thing.
- Older issues that are no longer relevant should be marked "Fixed" (e.g. things that are now working because of the new release system, etc).
- If an issue's title isn't clear, try to figure out what the issue is about and give it a more descriptive and acurate title.
- See if you can reproduce any of the bug reports on a local test site. Start digging into the code and see if you can figure out anything about what's going wrong. No matter what, report your findings in a follow-up in the issue so other people can see your results. Just knowing if you can (and how to) reproduce a bug on a local test site is a huge step towards fixing the problem.
- ... (feel free to add other suggestions here)
Keep an eye on the webmasters and infrastructure issue queues for bug reports and feature requests that really belong in one of the project* issue queues:
- Drupal.org webmasters
- Drupal.org server administrators
Since project* is so central to the functionality on drupal.org, people often request features or report bugs to these issue queues, not necessarily realizing that there are separate queues for the project* modules themselves, and these bugs or features almost always exist or would work on other sites running the project* modules. If you find issues in either of these queues that is general to Project* code, not specific to how it is setup on drupal.org, move the issue into the appropriate project* queue.
Keep an eye on the drupal.org forums for questions about project* and see if you can answer them, point the person to the appropriate issue if it's a known bug or feature request, etc.
Read the CVS handbook. See if you can find ways to make any of the pages more clear. If you've got documentation powers on drupal.org, try to fold comments into the body of the page and delete them. If you're unsure, just ask me (see below).
Read the Maintaining a project on drupal.org handbook. See if it makes sense. See how much of it should be folded into the general project* documentation, or if there's a better way to organize this information.
If you haven't already, read the patch handbook. Then, take a look at the "patch queue" for these modules (all issues marked as "Patch (code needs review)"):
See if the patch still applies to the version it's reported against. If not, set the issue to "Patch (code needs work)". If you can, resolve the conflicts and re-roll the patch for that branch, post your new patch to the issue, and set the status back to "code needs review". If it's a patch for a feature request, see if it applies against HEAD, or the DRUPAL-4-7--2 branch, and set the version of the issue accordingly. No matter what, if the patch applies, test it. Again the patch handbook has great instructions on how to apply, review and test patches, so read that if you're unsure what to do.
Test all of these modules using PostgreSQL. There are some known issues in the queue, so review, apply, and test those patches first. If you find any new problems, submit detailed bug reports about them.
Dig into the code and see if you can understand any of it. ;) If you figure out something that seemed cryptic at first, write some helpful comments in the code and provide a patch for it. If you find a function without doxygen comments that explains what the function does, what kind of input it expects, and what output it produces, write the comment and post a patch (feel free to include more than one function's comments in the same issue/patch).
Check out the list of Future work for the new release system, and see if any of it interests you enough that you'd like to start working on a patch for something. If so, follow-up to the issue, assign it to yourself, and start sketching out your thoughts on what needs to happen. Feel free to just ask questions in the issue about implementation details, etc.
Add to this list.

I'm often available on IRC in #drupal (my nick is also "dww"), and I try to lurk in #drupal-dojo whenever I get the chance. Feel free to add a comment below if you want to get my attention about something. If you have a question about an issue, just followup to the issue itself, since other people might be able to answer it.

That should be more than enough to get anyone started, no matter what skills you have to offer. ;) Please dive right in and help in whatever ways you can. Drupal.org and project* need you!

Thanks,
-Derek

Projects Needing Volunteer Developers

Projects Needing Volunteer Developers - you can now add/change/update your own project!

Walt Esquivel — Sat, 31 Mar 2007 19:25:56 +0000

This is an informal list of projects needing volunteer developers. To be clear, this group is for Drupal maintainers/developers who would like volunteer help from the Drupal community in order to complete a Drupal core or Drupal contributed module. This group is not for folks desiring help with their web sites.

In order to periodically update the status of Projects Needing Volunteer Developers, please refer to the table which is an informal list by the respective project maintainers/developers. ANY maintainer/developer can easily make updates to a project's table with a few clicks because the table exists on a wiki page!

If you maintain a project with a reverse bounty and have knowledge on any of the info listed in the table for your respective project, please add your comment to Projects Needing Financing so that it can be included there instead of here since this is more along the lines of code contribution/collaboration.

To help clarify a few columns:
Status Date refers to the latest Status update as submitted by the Maintainer / Developer under Source.

Source is a link which leads the reader to more info as posted by the Maintainer / Developer somewhere on groups.drupal.org and/or drupal.org.

Project	Status Date	Status	Maintainer / Developer	Source
drupal.org testsite install profile	Mar. 25, 2007	An idea i've been thinking about. Posting it here so other folks can add to it, provide feedback, etc.	dww	(same as under "Project" column)
complementary currency project	April 2008	Solo project, at the moment, needs mentoring	matslats	recipe and modules

Projects Needing Volunteer Developers

Proposal: drupal.org testsite install profile

dww — Sun, 25 Mar 2007 11:06:51 +0000

this is an idea i've been thinking about. posting it here so other folks can add to it, provide feedback, etc.

Summary

we could really use an install profile that setup a test site similarly to how drupal.org is configured (especially the project* modules and CVS integration). obviously, it wouldn't have the bluebeach theme, but otherwise, it would look fairly similar to d.o in terms of structure, content, permissions, etc.

this would greatly help people who wanted to reproduce bugs and test patches for the project* family of modules, which is something we desperately need more of. it also might be a popular profile as a starting point for people looking to setup software-collaboration sites (though ideally we'd have a separate "software development site" profile eventually).

here's what i envision (but please edit this to expand or modify it):

enables and configures all the project* modules and the CVS repo stuff
sets up the d.o project taxonomy stuff (project types, module categories, etc)
enables and configures the devel.module
configures the d.o roles and permissions
generates a bunch of random users
generates a few targetted users for each of the main roles on d.o, with documented usernames and initial passwords
generates a skeleton set of project nodes (core, some of the common contribs, cross-section of different project types (modules, themes, translations, etc))
generates a bunch of random releases
generates a bunch of random issues
(optionally) generates some random forums and comments
...

so, you download all the right versions of things, install this profile, and you're ready to start testing patches for the d.o infrastructure.

in his "State of Drupal" talk, Dries was making a plea for more people to help with making our home on d.o more like a palace. this should significantly facilitate getting more "builders" involved in the construction. ;)

Details

specific modules

see http://drupal.org/node/27367 to start with. ;) otherwise, contribs i'm specifically interested in, are:
* cvslog
* project (including project_release)
* project_issue
* code filter

taxonomy

The project taxonomy stuff is a little weird. you get the basic idea: there's a "project" vocabulary, which is hierarchical. top level terms are "Module", "Theme", "Installation profile", etc, etc. At this point, only Module has sub-terms, which are the module categories (see http://drupal.org/project/Modules for a list of them). Once http://drupal.org/node/105986 is done, and contrib translations are in their own projects, we'll have sub-terms for each language under the "Translations" term, but that's getting ahead of myself. ;)

There's also the project release vocabulary -- "Drupal Core compatibility" (for the "5.x", "4.7.x", etc terms on release nodes, which is also used in a bunch of the download pages, etc).

I see 2 possible solutions for this:

you just manually re-create a subset of this structure (not every single module category, etc)
we actually export the relevent records from the {term_*} tables directly (and regularly) from d.o. not sure this idea will fly, but perhaps we could have a cron job that just does a selective mysqldump and sticks the .mysql file somewhere folks can just download. ;) i'm *only* talking about the structure of the project (and project release) vocabularies, nothing more.

cvs repository

ideally, the install profile would include a tarball of a pre-configured cvs repository that had the right basic directory structure, and some files for the project nodes that would get created with the profile. all the contributions/modules/cvslog/xcvs* stuff would be configured in the CVSROOT of this repo, and would be customized during install to point to the right drupal database. there's a pretty thorough README.txt in there now. we'd probably want to create 2 repos, in fact -- the contrib and core ones.
then, of course, the drupal site would be configured to know about each repo (via [site]/admin/project/cvs-repositories).

specific nodes

i don't think it's feasable or desireable to actually replicate all of the project, issue, and follow-up content from d.o. i was thinking we'djust creating a small handful (~10) different projects that are representative of the structure on d.o. these would be the same small handful of directories in the stub CVS repository. they'd have some specific CVS tags and branches, too, and the corresponding release nodes. once that's in place, i'd say we just randomly generate a bunch of issues and comments automatically.

roles and permissions

i'm not sure how much of this i can share, nor how much of it is really necessary for the needs of this profile. basically, we should just configure the anonymous and authenticated users with the appropriate perms, and then make an uber-site-admin role with all perms enabled. the whole "document maintainer" vs. "site maintainer" vs. "site admin" stuff probably isn't essential -- though it might be nice to tackle in a future version once the other parts are working smoothly.

other settings

i'm not sure what's the best way to deal with this: if i should (can?) just provide a dump of the relevent entries in the {variables} table, like i'm proposing for the {term_*} stuff. i'll try to get some of the more senior powers that be to comment on this part, too.

Projects Needing Volunteer Developers

Alternative Currency Support

Semantic Repository for Green Building Research Project Wanted | SkySite Property

Drupal Config Specialist/Themer | SkySite Property

volunteer enthusiasts / consultants for Iraq initiative | International Initiative to Prosecute US Genocide in Iraq

volunteer themer for Iraq initiative | International Initiative to Prosecute US Genocide in Iraq

volunteer developer / programmer for Iraq initiative | International Initiative to Prosecute US Genocide in Iraq

Sessions on "Community: Role of the Contributor" Wanted For Drupalcon 2008

How To Submit Your Session

Save the Date

Useful Links

Content manager | New Media Denver

DBA module 5.x-1.0 release roadmap

Stay-at-Home Drupal Mom/Dad? | Careers In Common

an experimental platform

Marketplace for Module Development and Improvement– pooling resources of developers

How to help with the project* modules

Projects Needing Volunteer Developers - you can now add/change/update your own project!

Proposal: drupal.org testsite install profile

Summary

Details

specific modules

taxonomy

cvs repository

specific nodes

roles and permissions

other settings

Related Links