This wiki stems from the Forming a Drupal in Higher Edu Consortium conversation started a few months back. Let's start identifying the requirements for a website, or series of websites, that help those of us in higher education communicate and share resources & best practices.
Share any requirements you would find valuable in this community, then also any suggestions for Drupal projects or distributions that might solve the requirement.
Knowledge Sharing
Aggregation of tutorials, blog posts, videos, etc from drupal.{universityname}.edu websites
A place to post tutorials and resources if institution does not have a drupal.{universityname}.edu website
Managing News, ELMS, OpenScholar
Discussion and networking
Targeted communities around specific higher education Drupal issues. Examples: Libraries, Education features, Curriculum and Training, etc.
Not meant to supplant the main g.d.o groups, but to enhance communication specific areas of interest.
Code sharing
If there's interest in an edu-based features repo, this would be it.
Comments
Starting the discussion
I just wanted to get this discussion moving about we would actually want in a higher education consortium website or network of websites.
For me a priority would be the aggregation of resources from all universities that share Drupal tutorials. Many times I feel like we're reinventing the wheel solving problems solving similar problems when others in the community may have already tackled them. Maybe there's a possibility to use this as an opportunity to develop edu-based features for departmental websites or some common best practices.
Thanks for getting this going!
Thanks for getting this going bneil. I was very happy with the response of the community of the consortium posting and would like to see that energy carried forward. I'm knee-deep in trying to get a featurized version of elms out the door for some reaction but just wanted to add some quick thoughts:
Knowledge Sharing
I support the drupal.{site}.edu idea heavily. I know it's brought great exposure to the psu drupal community and now we have most people blogging on there then just me so knowledge share is spreading even further internal and external. I think we need some kind of aggregator hub / community site to capture that. That might be better served with Commons but I'm not sure. As far as future plans, as ELMS gets closer to a full release I'll probably throw up an elms.btopro.net and post lots of mini-drupal courses on various topics. This satisfies my personal desire to teach, showcases the platform's usage as an OER repo-builder and hopefully gets more people active in our community / learning about what's going on in education in general.
Code Sharing
I'd recommend github for quick and dirty collaboration. As for the feature server, I'll actually be publishing the drupal.psu.edu setup as an install profile. There's an early version of it there now but I'll add in the post-feature-server changes and only remove the content / users currently in there. Hopefully that can kick start other groups and at least generate some ideas.
I don't want to see this be a "use modules xyz" kind of a thing. It's nice to use similar modules and recommend them to others but I'd rather it not be a "hey lets all standardize on views, cck, regions, etc". While I'd like that, mandates always make people uncomfortable :p
Ex Uno Plures
http://elmsln.org/
http://btopro.com/
http://drupal.psu.edu/
Agreed
I think your idea of rolling fserver into the drupal.{site}.edu profile sounds like a much more flexible approach to code sharing than a more centralized approach that I initially posted.
That's great to hear - It's quite possible that people would be more comfortable posting to these local university sites than to a centralized source. I'm starting to really like this drupal.{site}.edu approach.
I support the
I support the drupal.{site}.edu idea heavily. I know it's brought great exposure to the psu drupal community and now we have most people blogging on there then just me so knowledge share is spreading even further internal and external.