<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Caalexand%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CDOCUME%7E1%5Caalexand%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CDOCUME%7E1%5Caalexand%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;
        mso-font-charset:1;
        mso-generic-font-family:roman;
        mso-font-format:other;
        mso-font-pitch:variable;
        mso-font-signature:0 0 0 0 0 0;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;
        mso-font-charset:0;
        mso-generic-font-family:swiss;
        mso-font-pitch:variable;
        mso-font-signature:-1610611985 1073750139 0 0 159 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {mso-style-unhide:no;
        mso-style-qformat:yes;
        mso-style-parent:"";
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:10.0pt;
        margin-left:0cm;
        line-height:115%;
        mso-pagination:widow-orphan;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        mso-ascii-font-family:Calibri;
        mso-ascii-theme-font:minor-latin;
        mso-fareast-font-family:Calibri;
        mso-fareast-theme-font:minor-latin;
        mso-hansi-font-family:Calibri;
        mso-hansi-theme-font:minor-latin;
        mso-bidi-font-family:"Times New Roman";
        mso-bidi-theme-font:minor-bidi;
        mso-fareast-language:EN-US;}
.MsoChpDefault
        {mso-style-type:export-only;
        mso-default-props:yes;
        mso-ascii-font-family:Calibri;
        mso-ascii-theme-font:minor-latin;
        mso-fareast-font-family:Calibri;
        mso-fareast-theme-font:minor-latin;
        mso-hansi-font-family:Calibri;
        mso-hansi-theme-font:minor-latin;
        mso-bidi-font-family:"Times New Roman";
        mso-bidi-theme-font:minor-bidi;
        mso-fareast-language:EN-US;}
.MsoPapDefault
        {mso-style-type:export-only;
        margin-bottom:10.0pt;
        line-height:115%;}
@page Section1
        {size:595.3pt 841.9pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;
        mso-header-margin:35.4pt;
        mso-footer-margin:35.4pt;
        mso-paper-source:0;}
div.Section1
        {page:Section1;}
-->
</style>
<p class="MsoNormal">Hi Jim,</p>
<p class="MsoNormal">I think you raise some crucial points about processes and
access. <span style=""> </span>For me, this isn’t just about technical
development but also about editorial – certainly on the main CC website. And
this is something we really need to look at urgently as a group as the new
sites go live.</p>
<p class="MsoNormal">I’ve spoken to Neil, Jon and Jonathan about content over the
last few days and, obviously, there’s major task we have to do to populate the
new site. I’m assuming there’ll be at least some editorial work to do on hyperactive
also.</p>
<p class="MsoNormal">What I’d like to suggest is that we look at website
processes – including technical - as part of the content work. I’ve no technical
expertise myself, so obviously we’d be looking to others to let us know what
works best.</p>
<p class="MsoNormal">But the crucial point is that we work as a group to develop
an agreed collective process for the new sites.</p>
<p class="MsoNormal">In the meantime, sounds to me as if having different people working
on the same install could get tricky without very careful co-ordination. So, personally,
I think it’d be best to give Jim as much space as possible to finish the
installation to keep things quick, simple and moving along – unless there are
specific tasks he requires others to do.</p>
<p class="MsoNormal">Anyway, I’m really excited about this – can’t wait to see it
launched. Jim - if you need help with anything, please let us all know.</p>
<p class="MsoNormal">Alistair</p>
<br><br><div class="gmail_quote">2009/8/11 <span dir="ltr"><<a href="mailto:theinnercityhippy@riseup.net">theinnercityhippy@riseup.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hi,<br>
<br>
was thinking that myself. I've installed on a debian and ubuntu system<br>
both with and without a graphical environment with no problems. Are you<br>
following the instructions on the hyperactive project page? What distro<br>
are you using?<br>
<br>
As for access, i was going to suggest that if a few of us are working on<br>
this i set up a git repo on the server and we can safely commit changes to<br>
that whilst the site is live as the form of the site will be quite<br>
different to the indymedia environment that the core code needs to adhere<br>
to. This means that we need to set up a hyperactive/mods/climatecamp/<br>
folder and work in there, which will override default settings, views,<br>
controllers etc and mean we can still commit core code in a meaningful<br>
way. In the meantime, if everyone gets a local copy running in a git<br>
branch we can merge changes more effectively. Do people have experience of<br>
git versioning or should i give some pointers as to its use?<br>
<br>
In order to get the time off for the camp i'm working a round the clock 72<br>
hour shift til thursday morning so i might not be too responsive until<br>
then, but i will be in london briefly on saturday and sunday if anyone<br>
needs to meet up with me from there.<br>
<br>
In terms of access to the server and admin interface, we need to come up<br>
with a plan fairly quickly as to how we decide who has this and to what<br>
level as that offer to be collectively decided. As i have a secure line of<br>
communication with jon, and he has an overview of who's doing what and<br>
stuff, and as i don't really know the rest of the web edit team very well,<br>
can i suggest that he sorts out the decision making process as to who<br>
needs it and verifies public ssh keys are authentic, then he can pass them<br>
to me and i'll put them on. It's best i'm removed from the decision making<br>
process for the above reasons and to guard against any kind of heirarchy<br>
forming where i alone get to make those decisions.. It's not a snub to<br>
anyone, just an important process decision that needs to be clarified<br>
fairly quickly.<br>
<br>
In the meantime, feel free to email me or the list with any questions or<br>
requests and i promise i'll do my best to respond as quickly as i can. I<br>
have all of next week off to devote to this too so it is ready for the<br>
camp.<br>
<br>
Solidarity<br>
<br>
jimdog<br>
<div><div></div><div class="h5"><br>
> Do you have mysql development libraries installed? The mysql gem is a<br>
> native compiled one, so it requires real header files.<br>
><br>
> Carl.<br>
><br>
> On Tue, 2009-08-11 at 11:24 +0100, Neil wrote:<br>
>> This is what I'm doing<br>
>><br>
>> neil@neil-laptop:~/rubygems-1.3.1$ sudo gem install mysql --<br>
>> --with-mysql-dir=/usr/share/mysql<br>
>> [sudo] password for neil:<br>
>> Building native extensions. This could take a while...<br>
>> ERROR: Error installing mysql:<br>
>> ERROR: Failed to build gem native extension.<br>
>><br>
>> /usr/local/bin/ruby extconf.rb install mysql --<br>
>> --with-mysql-dir=/usr/share/mysql<br>
>> checking for mysql_query() in -lmysqlclient... no<br>
>> checking for main() in -lm... yes<br>
>> checking for mysql_query() in -lmysqlclient... no<br>
>> checking for main() in -lz... yes<br>
>> checking for mysql_query() in -lmysqlclient... no<br>
>> checking for main() in -lsocket... no<br>
>> checking for mysql_query() in -lmysqlclient... no<br>
>> checking for main() in -lnsl... yes<br>
>> checking for mysql_query() in -lmysqlclient... no<br>
>> *** extconf.rb failed ***<br>
>> Could not create Makefile due to some reason, probably lack of<br>
>> necessary libraries and/or headers. Check the mkmf.log file for more<br>
>> details. You may need configuration options.<br>
>><br>
>> mkmf.log says /usr/bin/ld: cannot find -lmysqlclient<br>
>> Why not?<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Cc-webedit mailing list<br>
>> <a href="mailto:Cc-webedit@lists.aktivix.org">Cc-webedit@lists.aktivix.org</a><br>
>> <a href="https://lists.aktivix.org/mailman/listinfo/cc-webedit" target="_blank">https://lists.aktivix.org/mailman/listinfo/cc-webedit</a><br>
> _______________________________________________<br>
> Cc-webedit mailing list<br>
> <a href="mailto:Cc-webedit@lists.aktivix.org">Cc-webedit@lists.aktivix.org</a><br>
> <a href="https://lists.aktivix.org/mailman/listinfo/cc-webedit" target="_blank">https://lists.aktivix.org/mailman/listinfo/cc-webedit</a><br>
><br>
<br>
<br>
<br>
_______________________________________________<br>
Cc-webedit mailing list<br>
<a href="mailto:Cc-webedit@lists.aktivix.org">Cc-webedit@lists.aktivix.org</a><br>
<a href="https://lists.aktivix.org/mailman/listinfo/cc-webedit" target="_blank">https://lists.aktivix.org/mailman/listinfo/cc-webedit</a><br>
<br>
</div></div></blockquote></div><br>