[sakai-pmc] Mini-Sakai 10 communications plan
Mark Reilly
mark.reilly at nyu.edu
Thu Jun 19 08:27:04 PDT 2014
HI Neal,
You'll want to install the pathauto module: https://www.drupal.org/project/pathauto
It's very easy to configure you can set up different url patterns for different content types.
The module is very stable and has been around a long time and has wide usage in the Drupal community.
Thanks,
Mark Reilly
> I'll check on that.
>
> I'm not too familiar navigating with Drupal (the engine behind
> Sakaiproject.org) and it could be that they already have aliases, but
> this is what I see when I edit. I can ask. I think mostly folks get to
> these content areas either embedded in other pages (with friendlier names).
>
> Thanks,
> Neal
>
>
>> JOSE MARIANO LUJ?N GONZ?LEZ <mailto:jmariano at um.es>
>> June 19, 2014 at 10:54 AM
>> Hi everyone!
>>
>> From point 1) - I think it would also be good to make some
>> sakaiproject.org urls a bit more user friendly before the official
>> announcement ;)
>>
>> http://www.sakaiproject.org/node/105
>>
>> http://www.sakaiproject.org/node/31
>>
>> Cheers,
>> Mariano
>>
>> El 19/06/2014 16:36, Sam Ottenhoff escribi?:
>>> What about any confluence links about the latest release, current
>>> releases, etc? Update confluence pages to put a warning at the top
>>> of the page pointing the user to the latest release.
>>>
>>> 5) Why send the user to the Apereo site to read a tiny news blurb
>>> before then being sent to the Sakai site for the information?
>>>
>>> 7) Doesn't Apereo now have formal press release capabilities?
>>>
>>>
>>> On Thu, Jun 19, 2014 at 9:09 AM, Neal Caidin <neal.caidin at apereo.org
>>> <mailto:neal.caidin at apereo.org>> wrote:
>>>
>>> Hi PMC,
>>>
>>> Here is a rough communications plan for when we get Sakai 10 out the
>>> door. I recently subscribed to one of the Educause lists, so I
>>> can post
>>> to that. Might be good to think of other outlets to get the word
>>> out in
>>> addition to, but beyond, the Sakai community.
>>>
>>> https://confluence.sakaiproject.org/display/REL/Release+Communications+Plan
>>>
>>> 1) Before sending out communications, insure that following
>>> documentation is updated:
>>>
>>> https://source.sakaiproject.org/release/ (and this needs to be
>>> redirected to the latest release)
>>>
>>> Confluence Release notes, especially summary of new features and
>>> technical requirements
>>>
>>> http://www.sakaiproject.org at the following places:
>>> http://sakaiproject.org/current-release
>>> http://www.sakaiproject.org/node/105
>>> http://www.sakaiproject.org/try-sakai
>>> http://www.sakaiproject.org/node/31
>>> http://www.sakaiproject.org
>>>
>>> 2) Communicate technical details, specifically how to access the
>>> release
>>> artifacts, to the QA, Dev, and Prod lists
>>>
>>> 3) Communicate to the broader community the main changes, in
>>> non-technical terms, for the release. Include QA, Dev, Prod and add
>>> Internationalization, Accessibility, Sakai User, Pedagogy, and
>>> Documentation.
>>>
>>> 4) Post a highlighted news item to the Apereo.org web site.
>>>
>>> 5) Social media - Post to Facebook as Sakai Project and to Twitter
>>> (point the tweet to the Apereo.org web site?)
>>>
>>> 6) Send out an Apereo Announcement
>>>
>>> 7) Should go to outlets outside of the community (Educause...
>>> others?)
>>>
>>> Cheers,
>>> Neal
>>>
>>> --
>>> Neal Caidin
>>> Sakai Community Coordinator
>>> Apereo Foundation
>>> neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
>>> Skype me! (but let me know in advance for the first interaction)
>>> - nealkdin
>>>
>>> _______________________________________________
>>> sakai-pmc mailing list
>>> sakai-pmc at collab.sakaiproject.org
>>> <mailto:sakai-pmc at collab.sakaiproject.org>
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> sakai-pmc mailing list
>>> sakai-pmc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>>
>> --
>> ******************************************
>> Jos? Mariano Luj?n Gonz?lez - Aula Virtual
>> Area de Tecnolog?as de la Informaci?n
>> y las Comunicaciones Aplicadas (ATICA)
>> UNIVERSIDAD DE MURCIA -http://www.um.es
>> _______________________________________________
>> sakai-pmc mailing list
>> sakai-pmc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>> Sam Ottenhoff <mailto:ottenhoff at longsight.com>
>> June 19, 2014 at 10:36 AM
>> What about any confluence links about the latest release, current
>> releases, etc? Update confluence pages to put a warning at the top of
>> the page pointing the user to the latest release.
>>
>> 5) Why send the user to the Apereo site to read a tiny news blurb
>> before then being sent to the Sakai site for the information?
>>
>> 7) Doesn't Apereo now have formal press release capabilities?
>>
>>
>>
>> Neal Caidin <mailto:neal.caidin at apereo.org>
>> June 19, 2014 at 9:09 AM
>> Hi PMC,
>>
>> Here is a rough communications plan for when we get Sakai 10 out the
>> door. I recently subscribed to one of the Educause lists, so I can
>> post to that. Might be good to think of other outlets to get the word
>> out in addition to, but beyond, the Sakai community.
>>
>> https://confluence.sakaiproject.org/display/REL/Release+Communications+Plan
>>
>>
>> 1) Before sending out communications, insure that following
>> documentation is updated:
>>
>> https://source.sakaiproject.org/release/ (and this needs to be
>> redirected to the latest release)
>>
>> Confluence Release notes, especially summary of new features and
>> technical requirements
>>
>> http://www.sakaiproject.org at the following places:
>> http://sakaiproject.org/current-release
>> http://www.sakaiproject.org/node/105
>> http://www.sakaiproject.org/try-sakai
>> http://www.sakaiproject.org/node/31
>> http://www.sakaiproject.org
>>
>> 2) Communicate technical details, specifically how to access the
>> release artifacts, to the QA, Dev, and Prod lists
>>
>> 3) Communicate to the broader community the main changes, in
>> non-technical terms, for the release. Include QA, Dev, Prod and add
>> Internationalization, Accessibility, Sakai User, Pedagogy, and
>> Documentation.
>>
>> 4) Post a highlighted news item to the Apereo.org web site.
>>
>> 5) Social media - Post to Facebook as Sakai Project and to Twitter
>> (point the tweet to the Apereo.org web site?)
>>
>> 6) Send out an Apereo Announcement
>>
>> 7) Should go to outlets outside of the community (Educause... others?)
>>
>> Cheers,
>> Neal
>>
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140619/e1b930cc/attachment.html
More information about the sakai-pmc
mailing list