Add non-EULAy EULA wiki to GDO for users to sign as part of Checklist

The original idea was to ask the user to do a simple edit to a page of documentation and programmatically check the revisions. Unfortunately the revisions tab is only available to logged in users on Drupal.org.

@synchlayer and I discussed the potential for adding an end user licensing agreement (EULA) type wiki that was simpler than http://groups.drupal.org/node/270903, but included reading that and sharing it w/ the ED of your organization. This would not be a commitment to collaborate on anything specific (since the person is just getting started), but an acknowledgment that cm_ Drupal only works when the ration of users/contributors is maintained.

This wiki would have a section of text about collaboration and then a "digitial signature" section that cm_checklist could parse...

The following people have pledged to contribute in some way to the Community Media Drupal Initiative

----

kreynen
synchlayer
stefanwray 
jdcreativity
etc
etc

If the user hasn't added their Drupal.org username to the wiki, they'd still be able to use cm_checklist but it would show a warning on every page similar to when you have a security issue w/ a module. Basically we're adding a nagware feature for users who want to use the checklist to build their site without committing to contributing in some way at some point.

this mechanism doesn't apply to CMCs like MNN, BVAC or maybe other larger organizations who have hired a development team and have no need for a starter kit

While neither MNN nor channelAustin are using http://drupal.org/project/cm_starterkit_difficult yet, the plan that @libkuman, @ericG and I have been discussing for some time has been that the difficult kit would be the foundation of shared modules that the larger stations share. Updates to core functionality would have to be done in a way that still allows everything in cm_starterkit_difficult to function in both a staff driven and self service workflow or that change would NOT be committed.

I updated the documentation to reflect that use back in August http://drupal.org/node/1549468, but just got everything required to run CiviCRM from an install profile working a few weeks ago. I haven't updated the difficult kit with those changes.

Collaboration on the functionality included in the difficult kit will require more communication and development experience... beyond an EULA type agreement or what cm_checklist could walk someone through. Using specific features from the difficult kit does NOT require using the entire kit. Many stations will probably use Moderate + Reservations or CiviCRM Multiday Event, Certify, and Prerequisite Check.

If you're organizations isn't using CiviCRM, you can even use the Easy Starter kit + a few moderate and difficult features like what @westis has done at OKV with http://drupal.org/project/cm_airing_grid and http://drupal.org/project/cm_playlist_builder.

In all of these cases whether you start at the easy, moderate, or difficult level, once you've use cm_checklist to get up and running you'd disable it and while the EULA style wiki IS designed to get a site admin or independent developer thinking about contributions as soon as the start working with Drupal and CiviCRM, everyone beyond the need for the cm_checklist who wants to continue participating in a collaborative effort would also be encourage to sign.

This is just an idea, but I'd like to see some form of this if new stations are going to be introduced to this at the ACM.

This sounds good, I think it can be pretty simple: a non-EULAy EULA, which doesn't need to say much ore that @kreynen's example above.

I don't think we need to name and shame, but we could name and praise by listing the contributions of those who have contirbuted, perhaps on the wiki: http://groups.drupal.org/node/270903

First draft:

Community Media Drupal is a collaborative project, based on the co-operation of many people. The core philosophies of open source software and community media are sharing and helping others to empower themselves. If you are going to deploy any of the Community Media Drupal modules, we ask that you commit to sharing and collaborating yourself to sustain and grow this initiative further.

The existence of this work is founded on many types and levels of collaboration, from:

• Writing and committing code to Drupal.org
• Checking code
• Reporting and responding to Issues
• Co-maintaining modules
• Helping in IRC/ live chat
• Interacting on GDO - http://groups.drupal.org/community-media
• Taking part in weekly video hangouts
• Creating, proofing and updating documentation at http://drupal.org/documentation/build/community-media
• Attending camps and summits
• Organizing and/ or Leading workshops at conferences
• Conducting trainings

Updated examples of ways and menas to do this can be found in the wiki ”A Guide to Effective Collaboration - What Makes Community Media Drupal Work,” here: http://groups.drupal.org/node/270903.

Everyone will have their own way of contributing; many individuals and organizations have already done so. We respectfully ask that you sign this EULA with your Drupal username to show your commitment to collaborating as you become familiar with the project.

I don't think we actually want to use the term EULA in the text and it would be nice to encourage people to participate in local Drupal and CiviCRM related meetups so they are bringing new information, ideas, module suggestions back to the group.

Second draft:

Community Media Drupal is a collaborative project, based on the co-operation of many people. The core philosophies of open source software and community media are sharing and helping others to empower themselves. If you are going to deploy any of the Community Media Drupal modules or use one of the Starter Kits, we ask that you commit to sharing and collaborating yourself to sustain and grow this initiative further.

The existence of this work is founded on many types and levels of collaboration, from:

• Writing and committing code to Drupal.org
• Reviewing code updates
• Reporting and responding to issues and support requests
• Co-maintaining modules
• Helping in IRC/live chat
• Interacting on GDO
• Taking part in weekly video hangouts
• Creating, proofing and updating documentation
• Attending Community Media camps and summits
• Attending local Drupal and CiviCRM camps and meetups
• Organizing and/or leading workshops at conferences
• Conducting trainings

Updated examples of ways and means to do this can be found in the wiki A Guide to Effective Collaboration - What Makes Community Media Drupal Work.

Everyone will have their own way of contributing; many individuals and organizations have already done so. We respectfully ask that you sign this pledge with your Drupal username to show your commitment to collaborating as you become familiar with the project.

---

kreynen

I think this document is great. Really. The idea of a pledge towards a practice is philosophy is important.

A few possible modifications:

Community Media Drupal is a(n ongoing) collaborative project

Taking part in weekly video hangouts

Taking part in periodic video hangouts and teleconferences.

collaborating yourself (and from your organization) to sustain and grow this initiative further.

Minor thoughts:

Link up to the wikipedia entry on open source http://en.wikipedia.org/wiki/Open-source_software

Link up to the Cathedral and the Bazaar (http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar)

@kreynen and @jdcreativity - I like the revisions.

@stefanwray - My intent was to have the Agreement in the cm_checklist module, with the Wiki serving more as an up-to-date location for specific contemporaneous tasks that need attention.

EULAs get updated a lot (hello iTunes), and ask you to sign up again to confirm each time. We're being somewhat vague in the first instance, so the wiki is simply a place to see some more specifics. There's nothing legally binding so this seems eminently ethical.

I'm open to suggestions, but having the document as a wiki on GDO means that before they edit they...

1. Need a Drupal.org account
2. Need to join the GDO
3. Have to click edit on something

To me #3 is useful because it breaks the ice in establishing that cm_ Drupal isn't something an elite group have built behind closed doors.

On the technical end, I was going to parse the URL created for the username they've entered. Now this is not truly enforceable. Someone can use the Drupal username of someone who's already "signed" or just skip that check, deal with the nag messages, and disable the checklist module once the site's configured. But since the easiest way to use the distribution without the nag to add your username, I think most people will do that.

I agree that this is an 'unique' use of a GDO wiki, but it gets people involved very early in the process. As far as the pledge being editable, I don't see that as being a big problem because we can see the revisions.

Tracking progress on this in #1961826: Move to Checklist API version

Reopening this issue so @libkuman can take a stab and a better check to see that they've signed https://drupal.org/node/1860560

Note to myself:

Need to parse this page: https://www.drupal.org/node/1860560 to get user names.

Fetch it from:

https://www.drupal.org/project/cm_checklist

So I've made changes locally but have not yet committed to check for the user name on this page

https://www.drupal.org/node/1860560

Here are screenshots of the modified cm_checklist report, showing the 3 different states on the checklist and the add username pages. The last row is the one i added.

http://s32.photobucket.com/user/libkuman/library/cm_checklist?sort=3&page=1

Attached is the patch for cm_checklist

kevin is going to take my patch and push it into the 2.0