As a result of the recent TechMeet meeting that happened last Sunday, it has been decided to revive the Imc-CMS discussion and to try and pick a CMS to focus indymedia developer attention to.
I volunteered to try and coordinate it with whoever else wants to help.
They are trying to have this info ready by December 1st.
The other teams are the IndyPlone and a lot of IMCistas trying to develop a code-base from scratch with CakePHP.
The goal:
- work on an environment they assigment for and investigate it
- collect the pros and cons
- perform some customizations (according to indymedia needs)
- present it to the rest in 1 month
This is what we need to work on.
http://www.techmeet.org/txt/CMSWhatWeHave and
http://www.techmeet.org/txt/CMSWhatWeWant
Here are responses that people made.
http://techmeet.sarava.org/English/CMSSurveyReportDrupal
http://lists.indymedia.org/pipermail/imc-cms/2007-February/0222-0h.html
http://lists.indymedia.org/pipermail/imc-cms/2007-February/0213-bj.html
Other resources posted
http://docs.indymedia.org/view/Devel/ImcDrupalDev - the Drupal Doc site Wiki contains a lot of the below links.
http://phillymedia.wikispaces.com/ - The PhillyIMC drupal
http://worcesteractivist.org/wiki/Building_an_Indymedia_site_on_Drupal - WoosterHowTo
http://www.ucimc.org/wiki/index.php/Drupal_Migration - Urbana-Champaign IMC migration HowTo
http://docs.indymedia.org/view/Local/ImcBoston - has a section about moving over from Dada to Drupal
http://lists.indymedia.org/pipermail/imc-cms/2007-January/0126-lq.html -
is a post about Dada-Drupal but most of the links are down and the IMC is still on Dada from what I can tell. I e-mailed the author to see if they had usable code.
Development will be coordinated via e-mail on imc-cms@lists.indymedia.org and #cms but I think that a repository for Drupal specific docs and analysis would be useful. I will also post this to the Indymedia group on http://groups.drupal.org.
The next step is setting up a meeting on IRC for everyone interested. I'm on EST - in the US, and I know that Ekes is in CET in Europe and I remember their being quite a few devs in Australia years ago when I was trying to organize this.
Who wants to help with Team Drupal ?
Comments
I looked thru the what we
I looked thru the what we have/what we want and looks like everything can be provided by drupal and the various contrib modules. Some exceptions:
Also, some of the requirements are provided by drupal 6 core but need contrib modules in drupal 5.
yeah i hear you, i think
yeah i hear you, i think that drupal 6 in some ways would be ideal, of course this would prevent us from using too much in the way of CCK & Views until they are ported.
I think what this effort could lead to is a set of best practices and an install profile for INdymedia with better documentation, because every Drupal IMC site looks different and has completely different functionalities enabled by default, which can be good if that is the way the group decided it to be but I bet a lot of it just was the result of haphazard hacking and experimenting with the modules vs. a detailed analysis cuz Drupal is full of modules that try to do about everything.
Thanks for contributing to the wiki.
OpenID
I want to put in a good word for OpenID technology, which ideally would be built into as many different potential IMC platforms as possible. Shared techs that provide more networked strength, like OpenID shared authentication, would help everyone (and does not need to be Drupal dependent at all).
Workflow for stories (i.e. draft -> review -> published)?
Howdy, I've been working on a drupal IMC at http://reboot.stlimc.org. The site dev has been done largely by me, and, unfortunately, not as well coordinated with this group as perhaps it should have been.
Anyhoo, something that I've had difficulty setting up is a coherent workflow for editorial stories and newswire stories. In particular, I was hoping to implement the following workflows, based on those from dadaIMC:
Editorial Features:
A. Draft (visible to eds) -> B. Peer Review (visible to eds) -> C. Published in center column (visible to all)
- transition from state A to B occurs when author has completed story (e.g. unchecks a box marked "Draft" or something)
- transition from state B to C occurs when a proposed feature receives enough votes from editors
Newswire Stories
A. Initial submission (visible to all) -> B. Promotion to feature (visible only to eds?) -> C. Published in center column (visible to all)
- transition from state A to B occurs when the story receives enough votes from users or editors (different vote thresholds for users vs. editors)
- transition from state B to C occurs when a proposed feature receives enough votes from editors
Users/editors should be able to opt for email notification about any of these state changes, e.g. "a story was just submitted for feature consideration..."
Drupal has the workflow and actions modules, which should be ideally suited for this task, but I've encountered a problem with setting up workflow states with restricted access (e.g. draft stories only visible to eds) because of incompatibilities I found between the workflow_access and taxonomy access modules.
Furthermore, I'm reluctant to use Drupal's built-in published/unpublished property since A) that only represents 2 states, and B) that would require giving all editors Node Admin access, which makes for very cluttered node submission forms that can confuse less-than-web-savvy editors. There are hacks related to the published/unpublished switch, but they don't look pretty. Also, the Node Admin access would let eds circumvent revision control (e.g. change a story w/o storing the previous revision), which can become a problem with accountability.
On the up side, I was able to create a functional voting system whereby editors vote features into publication using a combination of taxonomy access, voting API, voting actions, vote up/down, and a custom action to assign taxonomy terms. Maybe this would be of use to the IndyDrupal project?
In terms of features for an
In terms of features for an install profile, these workflow/access issues could probably be second priority vs. a nice configuration for handling media. But I do think they're very important. Not sure if this is what you're doing, but seems like delegating access to taxonomies and workflow states would make it easy to partition a site into different regional sections that editors are given access to.
I don't have answers for this specific issue aside from saying check out all the node access related threads, which includes a few issues which have been postponed to drupal 7.
Looking forward to the project; and a very minor feature request
I was halfway through creating a project for an Indymedia installation profile, just to track my own very minor feature request of the moment, when I saw discussion has is very much active here.
So for the record that was to make sure the 'forward to friend' module didn't ask for your name when you're logged in (or at least prefilled it) and ideally allowed anonymous forwards with captcha.
Looking forward to this being a project on Drupal.org!
(no longer relevant)
benjamin, agaric
Still momentum? Look at Open Media Project?
This thread hasn't been too active since 2007, but I'm curious what progress was made or what momentum remains. The Open Media group http://groups.drupal.org/open-media-project is working on a more broad install profile for Community Media Centers, with support from the Knight Foundation. It would be great to combine the efforts and ensure these tools work for IMCs, Public Access TV stations, and other Community Technology Centers.
Whatever your first issue of concern, media had better be your second, because without change in the media, the chances of progress in your primary area are far less likely. http://denveropenmedia.org