Creative Commons - User contributions [en]

CcHost Skins

2006-09-03T03:40:23Z

Brenton Simpson: /* CSS Stlye Sheet */

[[Category:ccHost]]
[[Category:HOWTO]]
[[Category:Guide]]
[[Category:Customization]]
[[Category:Developer]]

The following is a rough outline, with background, on what you need to do to create your own skin in [[CcHost|ccHost]].

= Create the Skin =
*Go to the cctemplates directory
*Copy all the files skin-simple*.* to skin-joesoft*.*
*In skin-joesoft.xml on approx. line 25, replace the reference to '''string:skin-simple-map.xml''' with '''string:skin-joesoft-map.xml'''
*Log in with the admin you created during setup
*Click 'Manage Site'
*Scroll down and click 'Settings'
*Select 'joesoft' from the the skins drop down and Submit

You now have your own sand box.

= What Makes a 'Skin' =

Each skin has three unique files, a style sheet, a template map and a main template.

=== CSS Style Sheet ===

100% (or close) of the style information is here, not in the code, not
in the templates. You should be able to hork things pretty good if you
never do anything but edit this one file.

=== Template Map and Main Page ===

You only need to mess with templates if you really hate the layout and
can't position using CSS (hey, it happens and yes, we use tables
occasionally)

We use phpTAL for our templates. (It's 90% amazing, 10% head
scratching crazy.)

Hint: phpTAL is 100% XML so

<hr>
<img src="">

don't work, It's

<hr/>
<img src="" />

Each area of the screen in ccHost/Mixter is represented with a template macro
<pre>
<metal:block define-macro="show_remix_children">
<tal:block define="reply record/local_menu/remix/replyremix | nothing" on-error=""/>
<tal:block define="do_children record/has_children | reply | record/is_orphan_original" tal:on-error="" />
<div id="cc_upstream_mixes" tal:condition="do_children" >
<p tal:condition="record/is_orphan_original" id="noonesampled" tal:content="php: CC_lang('(no one has sampled this)')" />
/* .... etc ...*/
</metal:block>
</pre>

These templates blocks are shared amongst skins and many outer templates refer to inner ones:

<pre>
<metal:block define-macro="show_remix_children">
...
<metal:block use-macro="${remix_line}" />
...
</metal:block>
</pre>

In the example above, the actual implementation of 'remix_line' is determined by the Template Map file. In skin-joesoft-map.xml you see that you inherit the default map from skin-blank. If you want to override a specific template, you add a single block to your map file that will do that for you (see skin-ccmixter-map.xml for an example):

<pre>
<tal:block define="
remix_line string:skin-joesoft.xml/joesofts_remix_line;
"
/>
</pre>

Now you're (finally) ready to write some XHMTL. In skin-joesoft.xml add your template:

<pre>
<metal:block define-macro="joesofts_remix_link">
...
<a class="js_remix_link" href="${rs/file_page_url}">${rs/upload_name}</a>
...
</metal:block>
</pre>

Hint: Don't put too many macros in the same XML file, it slows down page rendering. A lot.

= Viewing Variables =

You can dump various records at any time, right onto the screen. Edit index.php and change '''CCDebug::Enable(false)''' to '''CCDebug::Enable(true)'''

As long as you logged in as admin, on any page browse to:

<nowiki>http://localhost/?dump_page=1</nowiki>

Tthat will list out all the global variables available to you (the user record is the currently logged in user).

Upload an MP3 (or image or whatever) to your system. Then on the song's page add the dump_rec query:

<nowiki>http://localhost/media/files/3?dump_rec=1</nowiki>

That will list out all the variables in a given upload record (the user record here is the one that uploaded the thing).

Go crazy.

= Support =

At some point you'll probably request something that requires code changes, I think you'll find us very responsive to most things, however, you might be surprised how much interactivity policy is defined in the templates themselves.

After you reach a certain point we'll give you access to one of the ''many'' dev mirror sites we have all around the web and you can use that to test out your skin against real ccMixter data and it gives us a chance to praise you, point out issues, add internal hacks and make suggestions.

CcHost

2006-09-03T03:38:39Z

Brenton Simpson: /* Upgrading */

[[Category:ccHost]]
[[Category:Developer]]
[[Category:Software]]
[[Category:Technology]]
[[Category:ccMixter]]

'''ccHost''' is Creative Commons' open source ([http://creativecommons.org/licenses/GPL/2.0/ GPL] licensed) project that powers [http://ccmixter.org ccMixter] and is the winner of the [http://creativecommons.org/weblog/entry/6026 LinuxWorld Journal Product Excellence Award] for '''Best Open Source Solution.''' Read more about ccHost [[#Zeitgeist|here]].

= Download =

=== Current Stable Release ===

Latest stable builds of ccHost ([[CcHost_Release_Notes|NEWS]]) are available in several common archiving formats (.zip, .gzip, etc.)

[http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=156675 ccHost download page]

To install: Unpack the contents of the archive on your local machine and see the README.

=== Experimental Thrice-Daily Builds ===

Currently, ccHost packages are being made three-times a day and are available here:

[http://mirrors.creativecommons.org/cchost/packages/ ccHost 3x daily builds]

Our experience has been very good however these are minimally tested builds so ''download, install and use these packages at your own risk.''

Only 30 days worth of builds are saved currently.

= Install =

As stated above, all the information you need for installation is in the distribution package you downloaded. Treat these notes as addendums, hints and other possibly useful information.

=== Simple ===

The easiest way to get going is to start with a web hosting server. Common web hosting services like [http://www.dreamhost.com/ Dreamhost] and [http://www.websitesource.com WebsiteSource] provide an administration interface for setting up a mysql database. Hosting services also provide some FTP or SFTP mechanism to upload the ccHost installation files as well. 99% of all services provide support for PHP as well. If you have questions about support in this area, check the server requirements below and with your hosting service.

#Unzip the ccHost ZIP archive on your local system and copy the files to your server retaining the the directory structure.
#Browse to '''<nowiki>http://where_you_installed/ccadmin</nowiki>''' and follow all the instructions from then on.

=== Advanced ===

If you have basic knowledge of using FTP and you are comfortable at a terminal command line you can use these steps to before, during and after installation. Many of these can be filed under "you'll be glad you did" by the time you get to the browser-based installation steps later on.

==== Enabling 'Pretty URLs' ====

All ccHost commands and URLs based on query strings:

<nowiki>http://your_install_root/index.php?ccm=/media/people/victor</nowiki>

That same URL can be made 'pretty' on Apache installations so that it looks more like:

<nowiki>http://your_install_root/media/people/victor</nowiki>

Here is the block of code in your .htaccess file setting the rewrite rules to get pretty urls:

<pre>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ /index.php?ccm=/$1 [L,QSA]
</pre>

If you installed to a directory below the site's root make sure to specify that in the RewriteBase directive.

For perfomance reasons (and if you are given access) you should put those directives into an Apache virtual host block in the .conf file for your server:

<pre>
<VirtualHost *:80>
ServerName ccmixter.localhost
ServerPath /ccmixter
#DocumentRoot /var/www/localhost/htdocs/cchost
DocumentRoot /home/rejon/Documents/freelance/creativecommons/src/ccmixter

<Directory "/home/rejon/Documents/freelance/creativecommons/src/ccmixter">
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ /index.php?ccm=/$1 [L,QSA]
</Directory>
</VirtualHost>
</pre>

==== getID3 ====

ccHost depends on the getID3 library for verifying uploads. Install getID3 (at least 1.7.3) here: http://www.getid3.org/#download before you install ccHost. (It's a simple download-unpack operation.)

For example (on Linux):

<pre>
tar xzf getid3.tar.gz
cp -a getid3/getid3 /var/www/localhost/htdocs/getid3/
</pre>

The ccHost installer will 'find' your getID3 installation if it's roughly in the same area of the server, however it is ''not'' required that your getID3 be visible on the web and in fact, it's probably more secure if it isn't.

==== ccHost Terminal Installtion ====

*Unzip the ccHost ZIP or tar. bz2 archive on your local system and copy the files (retaining the directory structure) to your web-server directory.
* On Linux change the group and permissions of the files so they may be written by the web server (e.g., in the following lines, the web-server account is "apache").
For example:
<pre>
cp -a cchost-1.0.3 /var/www/localhost/htdocs/cchost
chgrp -R apache /var/www/localhost/htdocs/cchost
chmod g+w /var/www/localhost/htdocs/cchost/
chmod -R g+w /var/www/localhost/htdocs/cchost/cclib/phptal/phptal_cache/
</pre>
*Create a new database for ccHost (e.g., named "cchost") and create an administrative user to access it (e.g., "cchostadmin"). For example:
<pre>
mysql -p -u root
mysql> CREATE DATABASE cchost;
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE ON cchost.* TO 'cchostadmin'@'localhost' IDENTIFIED BY 'YOUR_PASSWORD_HERE';
</pre>
Make sure to change 'YOUR_PASSWORD_HERE' (and maybe 'cchostadmin') to something unique to your site.
(Many systems provide '''phpMyAdmin''' to take care of these tasks.
*Create directory /var/log/cchost or other location to store log files. Must be writable by the web-server account (e.g., "apache"). For example:
<pre>
mkdir /var/log/cchost
chown apache:apache /var/log/cchost
</pre>

==== Finish with Install ====

Browse to <nowiki>http://where_you_installed_cchost/ccadmin</nowiki>

Everything else you need to know will be on the screen from that point on, including suggested php.ini and .htaccess settings, access permissions requirements, etc.

==== More .htaccess file settings ====

Put the following into a file named '.htaccess' in your root directory of a ccHost setup if you can't set your php.ini settings for your hosting setup. These settings should work, but should be tested first. They correct many memory problems people have with ccHost.

<pre>
# php configs http://www.php.net/manual/en/ini.core.php#ini.memory-limit
# http://www.php.net/manual/en/ini.php#ini.list

php_value max_input_time 200
php_value max_execution_time 200
php_value memory_limit 20M
php_value upload_max_filesize 20M
# next line fixes noncompliant & used in php
php_value arg_separator.output &
php_flag session.use_trans_sid off
# turns off annoying autoquotes
php_flag magic_quotes_gpc off

Options +MultiViews

# Stop morons that are hammer your site
# Open Clip Art Library had someone DDoS'ing our site
<Limit GET>
order deny,allow
deny from 59.116.0.0/16
</Limit>
</pre>

=== Upgrading ===
'''Always''' make a backup of your mySQL ccHost database and the files you change (probably all of the ccfiles directory) before you start the upgrade process. Things go wrong. You have been warned.

==== General ====
In general, small updates and patches come in a few files and only require that you copy over cclib and ccextras. Once you've copied the new system files

#Log in as administrator to your current install (make sure to check 'Remember Me')
#Browse to: <nowiki>http://where_you_installed/?update=1</nowiki>

==== Upgrading from 2.x to 3.0 ====
This specific upgrade requires a few extra steps

#Make a BACKUP of your mySQL database (can be done via phpMyAdmin or from the command line using mysqldump)
#Make a BACKUP of your cchost directory onto your local machine (skip the /people and /contests directories). If you skip this step and you made changes (to say ccfiles/home.xml) then '''ALL YOUR CHANGES WILL BE LOST FOREVER'''
#Login to ccHost as your admin account and make sure to check 'Remember me'
#Unzip the cchost 3.0 package on your local machine
#Copy everything under the cchost directory '''EXCEPT''' ccadmin over your server's ccHost directory
#Delete the file '''ccextras/cc-language.php'''
#Delete ALL files under '''cclib/phptal/phptal_cache'''
#If you made changes to files in ccfiles (like home.xml), copy your local version over the ones on your server now.
#Browse to: <nowiki>http://where_you_installed/?update=1</nowiki>

=== Troubleshooting ===

==== File Access ====
By far the most common issue with new installs on Unix based systems involves file access permissions. The recommended way of dealing with this is to set the entire ccHost directory structure as all-access (0777) just while you get things going. If everything else is working then you should follow the
[[CcHost_File_Access|ccHost file access guildlines]].

==== "There is an error rendering this page" ====

The most common reason you get this error message on new installations is because the '''cclib/phptal/phptal_cache''' directory is not writable by ccHost. You should make sure this is not the case by setting that directory's permission to 0777 and trying again.

The second most common reason are template errors during development of skins and other user interface testing. If you haven't already [[#Outputting Debug Messages|turn on debug messages]] login as admin and try to render the page again.

==== "Down for upgrade, check back soon" ====

This is actually an indication that something is wrong in the code (i.e. a bug) or your installation. [[#Outputting Debug Messages|Turn on debug messages]] and try to access your site. The very least that will do is give ccHost developers the exact location of the problem.

==== Outputting Debug Messages ====

In order to help ccHost developers troubleshoot your site you should enable debugging messages in your system. The easiest way to do this is to create a file called '''_DEBUG_.php''' with the following contents:

<pre>
<?
CCDebug::Enable(true);
?>
</pre>

and put that file into the '''ccextras''' directory.

Now repeat the steps that led you to the problem and hopefully you will get more detailed information about the error.

Make sure to remove this file in your production installation. ''Hint: Changing the extension to anything other than .php is the same as removing it''

= Administration =

So you've got your ccHost up and running. now what?

''Victor is currently gathering data and writing up an Admin's Guide. If you have information you think would be useful please [https://lists.sourceforge.net/mailman/listinfo/cctools-cchost let him know].''

== User Interface ==

* [[Creating a custom user interface]]
* [[Creating a branded portal]]

= Development =

=== Source Code & Documentation ===

* [http://svn.sourceforge.net/viewcvs.cgi/cctools/cchost/trunk/ Browsable Source Code (Anonymous)]
* [http://wiki.creativecommons.org/Source_Repository_Information How to Check Out Code]
* [http://mirrors.creativecommons.org/cchost/docs/ Online Code Documentation] including developer's guide.

=== Creating Skins ===

[[CcHost_Skins|How to create a skin for ccHost]]

=== People ===

* [[User:fourstones|Victor Stone]]
* [[User:Jon Phillips|Jon Phillips]]

=== Communication ===

* Chat: #cc on irc.freenode.net
* Wiki: This page (http://wiki.creativecommons.org/wiki/CcHost)
* Mailing List: https://lists.sourceforge.net/mailman/listinfo/cctools-cchost
** [http://sourceforge.net/mailarchive/forum.php?forum=cctools-cchost Archive]

=== Submitting Code ===

Before going too far down this road you definitely want to hop on the [https://lists.sourceforge.net/mailman/listinfo/cctools-cchost dev mailing list]. If you are shy ask to speak with Victor or Jon in private.

[[HOWTO Patch|Submit Patches]]

=== Bugs and Feature Requests ===

''Make sure to use the 'ccHost' category when filing bugs. Also, please use a real email so that we can followup on any bugs posted. Be descriptive when posting and commenting on bugs (every bit counts).''

* [https://sourceforge.net/tracker/?atid=559966&group_id=80503&func=browse Report Bugs]
* [https://sourceforge.net/tracker/?group_id=80503&atid=559969 Request Features]

[[Category:CcHost]]
[[Category:Developer]]
[[Category:opensource]]
[[Category:Technology]]

= Zeitgeist =

=== Goal ===
The goal of this project is to spread media content that is licensed under
Creative Commons throughout the web in much the same way that weblogs spread
CC licensed text.

=== Short Description ===

"Web-based System Supporting Remixing and Collaboration on Media"

=== Slightly Longer Description ===
'''ccHost''' is an open source ([http://creativecommons.org/licenses/GPL/2.0/ GPL] licensed) project that provides web-based infrastructure to support collaboration, sharing, and storage of multi-media using the Creative Commons licenses and metadata. It is the codebase used by [http://ccmixter.org ccMixter] and [[#Usage Examples|other sites]].

Besides its focus on sharing content, ccHost differniates itself from other multi-media hosting programs by emphasizing the '''reuse''' (a.k.a. remixing) of content between artists, not only between artists on any given installation of ccHost, but between all installations across the web and any web site that implements the Creative Commons [http://ccmixter.org/media/viewfile/pool_api_doc.xml Sample Pool API], including non-ccHost sites such as the [http://freesound.iua.upf.edu/ freesound project].

=== Press ===

==== [[CcHost Release Notes|Release Notes]] ====

==== [[CcHost Press Releases|Press Releases]] ====

==== Sound Bites ====

* "ccHost enables you to '''run your own flickr or youtube while having an infrastructure for legally sharing audio, video, text, and other media.''" [[User:Jon Phillips|Jon Phillips]] 22:50, 25 August 2006 (UTC)

''Please add your own sound bite...''

==== [[ccHost Screenshots|Screenshots]] ====

* The text for the front page can be changed by editing ccfiles/home.xml. The other menu functions and so on are generally modified using the admin functions of the site.

=== Usage Examples ===

*[http://ccmixter.org ccMixter] - Primary usage of ccHost is the Creative Commons remix site, ccMixter.
*[http://www.opensourcecinema.com/cchost Open Source Cinema]
*[http://www.matrix-rayne.com Matrix Rayne Online]
*[http://remix.machinehasnoagenda.com/ remix.linux]
*[http://www.ccmixter.co.za/ ccmixter South Africa]
*[http://fourstones.net fourstones.net] Victor's personal website
*[http://www.openclipart.org/cchost/ Open Clip Art Library ccHost in testing]
*[http://www.esolpc.com/teacherhost/ TeacherHost] - for Instructors to share instructional materials.
*http://adrenalinicsound.com/music/
*[http://creativecommons.org.tw/formoz ccMixter Tawain]
* '''Please add your installation here.'''

----

= Appendix A: Compatibility =

=== Browsers ===

Tested on: Firefox 1.0+ Mac/PC/Linux, IE 6+ PC, Safari Mac

Cookies must be enabled.

Most skins (the ones people will want to use) require Javascript enabled.

=== Servers ===

Primary development is done on Windows XP and up-to-date Linux development systems using Apache, mySQL, and PHP.

==== Linux ====
ccHost on Apache (2.0.49 up to at least apache-2.0.55-r1) on Linux,

One should be able to easily install mySQL, PHP, and Apache (if they are not already available) through their distributions packaging system.

==== Windows IIS Server ====

Windows users with their installation disks may install optionally the Windows IIS Web Server. This option has been tested. However, there might still be issues with it, and if so, please file a bug.

Even if you using Apache on Windows you may need to have IIS installed if you plan to use mail contact functions.

==== Windows Apache ====
There are many good tutorials for setting up a Windows/Apache/MySQL/PHP site ([http://google.com/search?q=installing+WAMP Google search]) and all three subsystems now come with Windows installers making the job of installing relatively straightforward.

====== XAMPP ======
Windows installations without Apache, mySQL and PHP already installed should consider using [http://www.apachefriends.org/en/xampp.html XAMPP] for Windows, which provides an easy install of Apache web server, MySQL database server, and PHP and perl programming languages. This is an easy way to get up and running, with the underlying technology necessary to use ccHost.

Follow the instructions for installation of XAMPP to know where to put the uncompressed ccHost package to properly work with your local setup.

==== Mac OS X ====

''NOTE: This setup is similar to Linux.''

Verified:

* OS X 10.4.6
* default OS X MySQL build, 4.0.26
* GetID3 1.7.7
* default Apache/PHP

= Appendix B: Redistribution =
=== HOWTO Tag a Release ===

Really, each major release needs to be tagged, but this 2.0.1 is the first SVN release, and we did it post CVS -> SVN migration. In the future, this is the proper way to tag and branch.

<pre>
svn copy https://svn.sourceforge.net/svnroot/cctools/cchost/trunk \
https://svn.sourceforge.net/svnroot/cctools/cchost/tags/2_0_1 \
-m "Tagging 2.0.1 bugfix release"
</pre>

[http://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html Here is more about SVN merging/branching].

=== Packaging ===

==== Sign Package ====

You should do this for all packages (RPM, tar.gz, zip, tar.bz2, etc)
<pre>
gpg --detach-sign --armor cchost-VERSION.tar.gz
</pre>

==== Verify Package ====
<pre>
gpg --verify cchost-VERSION.tar.gz.asc
</pre>

Salon

2006-05-22T07:57:19Z

Brenton Simpson: /* Where */

[[Category:Salon]]
[[Category:General]]
[[Category:Event]]

<div style="border: 1px solid #ccc; padding: 2%; background: #eee; font-size: 130%;">

The CC Salon is a monthly event focused on building a community of artists and developers around Creative Commons licenses, standards, and technology. The first event is set for San Francisco with intention for the idea to replicate in other locations internationally. Have look at [[All Salons]] aorund the world ...

The format for each event is to encourage loose networking amongst participants with 2-3 brief presentations from individuals and groups developing interesting projects that relate to the Creative Commons.

</div>

<div style="padding: 2%; background: #bfcdff; font-size: 130%;">

== <span style="font-size: 130%; color: rgb(90, 122, 199);">The Next CC Salon is June 14, 2006</span> ==

=== Who ===

People interested in Creative Commons, copyright, Free Culture, Open Source, Art, Media, and Music

=== What ===

A local informal gathering of individuals around Creative Commons licenses, standards, and technology.

==== Theme ====

Publishing music, art, and video on the web

=== When ===

June 14, 2006, 6-9 PM

* During Event
** Drink & Talk
** Chat on #cc on irc.freenode.net
** wifi provided free

* '''6:00-7:00''' - Drinks, conversation, and music
* '''7:00-7:05''' - Welcome
* '''7:05-7:30''' - Victor Stone, ccmixter.org, fourstones.net
* '''7:30-8:00''' - Marisa Olson, International Artist and Curator at Large for Rhizome.org, http://lifeofmo.blogspot.com/
* '''8:00-8:30''' - Rick Prelinger, archive.org, preview of film, "Panorama Ephemera," "...using the Internet Archive as the primary means of distributing a (very) independent feature (under CC of course)..."
* '''8:30-8:45''' - Wrap-up, questions, etc.
* '''8:45-9:00''' - More drinks, conversation, and music

''See the blogpost: TBA''

=== Where ===

TBA (ALL AGES PLEASE =D)

=== Why ===

To connect with and build a community of artists and developers who are working with Creative Commons licenses, standards, and technology.

=== [[Salon 200606 Media and Recordings|Media and Recordings]] ===

=== [[Salon 200606 Planning|Planning]] ===

=== [[Salon 200606 PR|Press Release]] ===

=== [[Salon 200606 Feedback|Feedback]] ===

</div>

<table style="width: 100%; border: 1px solid #ccc; padding: 2%; background: #eee;">
<tr>
<td colspan="2" style="font-size: 150%;">

== Participate ==
</td>
</tr>
<tr>
<td style="font-size: 200%; width: 50%;">

* [[Announcement List]]

* [[Salon How to Participate|How to Participate]]

* [[Salon Communication|Communication]]

* [[Speaking at Salon]]

* [[Start Your Own Salon]]

* [[All Salons]]

</td>
<td style="font-size: 200%; width: 50%;">

* [[Salon Future Events|Future Events]] (Monthly on 2nd Wednesday)

* [[Salon Past Events|Past Events]]

* [[Salon Future Presenters|Future Presenters]] (To Be Setup)

* [[Salon Ideas|Ideas]]

* [[Salon Background|Background Information]]

* [[Salon External Links|External Links]]

</td></tr></table>

Salon Future Events

2006-05-11T05:41:54Z

Brenton Simpson: /* Location */

[[Category:Salon]]
=== Wednesday, June 14, 2006 ===

==== Announcements ====

* http://upcoming.org/event/69816/

==== Theme ====

TBD

==== Presenters ====

* Victor Stone, ccmixter.org, fourstones.net
* Rick Prelinger, archive.org, film screening of "Panorama Ephemera"
** "...using the Internet Archive as the primary means of distributing a (very) independent feature (under CC of course)..."
** question: "Panorama Ephemera" is a feature-length film; can we show it all, or should we show a segment?
** answer: show part of the film and plug for another event where the full film is shown
* Marisa Olson, International Artist and Curator at Large for Rhizome.org, http://lifeofmo.blogspot.com/

==== Location ====

TBD

'''PLEASE make this event all ages, or at least warn ahead of time if it is not.'''

==== Format ====

6-9 PM

==== [[CC Salon June PR|Press Release]] ====

=== Wednesday, July 12, 2006 ===

==== Theme ====

TBD

==== Presenters ====

TBD

==== Location ====

TBD

==== Format ====

6-8:30 PM

==== [[CC Salon July PR|Press Release]] ====

=== Wednesday, August 9, 2006 ===

==== Theme ====

TBD

==== Presenters ====

* Kevin Shockey, Editor in Chief, Tux Magazine (http://www.tuxmagazine.com)

==== Location ====

TBD

==== Format ====

6-9 PM

==== [[CC Salon August PR|Press Release]] ====

=== Wednesday, Sept 13, 2006 ===

==== Theme ====

TBD

==== Presenters ====

TBD

==== Location ====

TBD

==== Format ====

6-8:30 PM

==== [[CC Salon September PR|Press Release]] ====

Talk:Licenses in Operating Systems Specification

2006-05-05T19:55:53Z

Brenton Simpson:

Why would Windows call the Licenses folder 'create' if Mac and Linux use 'Licenses'?
-[[User:Brenton_Simpson | Brenton Simpson]]

All Salons

2006-05-05T19:55:13Z

Brenton Simpson:

[[Category:Salon]]

This is where all CC Salon meeting go. Currently there is only a San Francisco Salon, but hopefully this will grow to other cities.

* [[Salon|San Francisco]]
* Add your CC Salon after you "[[Start Your Own Salon]]"

TechChallenges

2006-05-05T19:47:48Z

Brenton Simpson:

#redirect [[Developer_Challenges]]

Talk:CcHost

2006-04-15T05:09:49Z

Brenton Simpson:

I tried to upgrade from 1.0.3 to 2.0.1 and the update script just returns ccHost Installation not complete. So, I tried doing a 2.0 then a 2.0.1, and i got the same error. I don't have much in my database yet, so I suppose I can start from 0, but that isn't cool. . .

If I wrote over something I shouldn't have (I straight copied with Overwrite existing files turned on), the instructions need to be more specific. I don't mean to complain, just to put in some constructive crit.. =) I'd hate to have someone who has lots of stuff in their database lose everything because of a botched upgrade...

[[User:Brenton Simpson | -Brenton]] April 13, 2006, 12:39AM

'''UPDATE:''' Maybe I was just being a dumbass and didn't rename ccadmin. I ended up backing up cc_tbl_user with flashmyadmin, reinstalling, and reimporting the user table. The error for this really should be more descriptive, or at least the update instructions should include a reminder regarding the ccadmin trigger. There's quite a difference between f%cking up your install in an upgrade and triggering a security warning. Speaking of which, how do I get certified by Sourceforge to help maintain this project?

Talk:CcHost

2006-04-15T05:09:38Z

Brenton Simpson:

Talk:CcHost

2006-04-15T05:09:12Z

Brenton Simpson:

I tried to upgrade from 1.0.3 to 2.0.1 and the update script just returns ccHost Installation not complete. So, I tried doing a 2.0 then a 2.0.1, and i got the same error. I don't have much in my database yet, so I suppose I can start from 0, but that isn't cool. . .

If I wrote over something I shouldn't have (I straight copied with Overwrite existing files turned on), the instructions need to be more specific. I don't mean to complain, just to put in some constructive crit.. =) I'd hate to have someone who has lots of stuff in their database lose everything because of a botched upgrade...

[[User:Brenton Simpson | -Brenton]] April 13, 2006, 12:39AM

'''UPDATE:''' Maybe I was just being a dumbass and didn't rename ccadmin. I ended up backing up cc_tbl_user with flashmyadmin, reinstalling, and reimporting the user table. The error for this really should be more descriptive, or at least the update instructions should clearer regarding the ccadmin trigger. There's quite a difference between f%cking up your install in an upgrade and triggering a security warning. Speaking of which, how do I get certified by SOurceforge to help maintain this project?

Talk:CcHost

2006-04-15T05:08:27Z

Brenton Simpson:

I tried to upgrade from 1.0.3 to 2.0.1 and the update script just returns ccHost Installation not complete. So, I tried doing a 2.0 then a 2.0.1, and i got the same error. I don't have much in my database yet, so I suppose I can start from 0, but that isn't cool. . .

If I wrote over something I shouldn't have (I straight copied with Overwrite existing files turned on), the instructions need to be more specific. I don't mean to complain, just to put in some constructive crit.. =) I'd hate to have someone who has lots of stuff in their database lose everything because of a botched upgrade...

[[User:Brenton Simpson | -Brenton]] April 13, 2006, 12:39AM

'''UPDATE:''' Maybe I was just being a dumbass and didn't rename ccadmin. I ended up backing up cc_tbl_user with flashmyadmin, reinstalling, and reimporting the user table. The error for this really should be more descriptive, or at least the update instructions. There's quite a difference between f%cking up your install in an upgrade and triggering a security warning. Speaking of which, how do I get certified by SOurceforge to help maintain this project?

Talk:CcHost

2006-04-15T05:08:14Z

Brenton Simpson:

I tried to upgrade from 1.0.3 to 2.0.1 and the update script just returns ccHost Installation not complete. So, I tried doing a 2.0 then a 2.0.1, and i got the same error. I don't have much in my database yet, so I suppose I can start from 0, but that isn't cool. . .

If I wrote over something I shouldn't have (I straight copied with Overwrite existing files turned on), the instructions need to be more specific. I don't mean to complain, just to put in some constructive crit.. =) I'd hate to have someone who has lots of stuff in their database lose everything because of a botched upgrade...

[[User:Brenton Simpson | -Brenton]] April 13, 2006, 12:39AM
'''UPDATE:''' Maybe I was just being a dumbass and didn't rename ccadmin. I ended up backing up cc_tbl_user with flashmyadmin, reinstalling, and reimporting the user table. The error for this really should be more descriptive, or at least the update instructions. There's quite a difference between f%cking up your install in an upgrade and triggering a security warning. Speaking of which, how do I get certified by SOurceforge to help maintain this project?

Talk:CcHost

2006-04-13T07:36:57Z

Brenton Simpson:

Slip A Buck

2006-03-27T20:48:45Z

Brenton Simpson: /* [http://www.slipabuck.com Slip A Buck.com] */

== [http://www.slipabuck.com Slip A Buck.com] ==

[http://www.slipabuck.com Slip A Buck.com] is a venue for artists to exhibit their work and patrons to peruse it. The site and its artists are supported via tips. The donations are pooled together and then distributed based upon which artists contributed how much to a particular project. [http://www.slipabuck.com Slip A Buck] features [[Flash]] tools that integrate seemlessly with the [[ccHost]] backend. If you would like to get involved with the project or have questions about [[Flash]]/[[ccHost]] integration, contact [[User:Brenton_Simpson | Brenton Simpson]].

User:Brenton Simpson

2006-03-27T20:47:30Z

Brenton Simpson: /* '''Brenton Simpson''' */

== '''Brenton Simpson''' ==
'''Personal Site:''' [http://www.theillustratedlife.com The Illustrated Life]

*[http://cinema.usc.edu/academic_programs/business_entertainment/academic-business-undergrad.cfm Entertainment Business] student at the University of Southern California (anticipated graduation May 2008)
*Working with [[ccHost]] to build [[Slip A Buck]], an online art community that emphasizes collaboration, DIY ethic, and compensating artists through tips
*Integrates [[ccHost]] and [[Flash]]